[digikam] [Bug 375646] New: Only photos

2017-01-27 Thread J-o-h-n-
https://bugs.kde.org/show_bug.cgi?id=375646

Bug ID: 375646
   Summary: Only photos
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: digikam-de...@kde.org
  Reporter: forgivenb...@gmail.com
  Target Milestone: ---

This is kind of a feature request.  Even though digiKam just recent became able
to manage video and audio files as well as photos, perhaps it would be nice to
have a "feature" to not scan for video and audio files but only scan for
photos.  Besides, digiKam is still marketed as:
Manage your photographs like a professional, with the power of open source

Its not 'manage your media like a professional.'

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 375645] New: Altered files cause digiKam to scan always

2017-01-27 Thread J-o-h-n-
https://bugs.kde.org/show_bug.cgi?id=375645

Bug ID: 375645
   Summary: Altered files cause digiKam to scan always
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: digikam-de...@kde.org
  Reporter: forgivenb...@gmail.com
  Target Milestone: ---

When Metadata -> Behavior -> all disabled -and- Miscellaneous -> 'Scan for new
items at startup (makes startup slower)' is disabled.

If metadata is altered by an external program (exiftool, exiv2, xnView, etc),
digiKam rescans all of the altered photos.

This is time consuming.  When working with a large number of albums and photos,
excessive rescans can severely slow productivity.  (Sadly, this is why I have
time to create this bug report)

Expected behavior is digiKam should only alter the database (digikam4.db) upon
demand (photos are untouched and not scanned) and can be synced (photos altered
and scanned) overnight.

Ideally 'Use lazy synchronization' would work similar to this, however altering
large amounts of metadata using lazy synchronization takes just as long or
longer as without lazy.  DigiKam seems to be configuring the exiv2 statements
to queue which is a time consuming process.  Configuring the exiv2 statements
should be done at the time of synchronization, not before.

All scanning should be able to be disabled so working with the database is not
interrupted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmenuedit] [Bug 375464] New: The edit is not bieng saved

2017-01-23 Thread Akshaya D N
https://bugs.kde.org/show_bug.cgi?id=375464

Bug ID: 375464
   Summary: The edit is not bieng saved
   Product: kmenuedit
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: akshay.dn...@gmail.com
  Target Milestone: ---

I can't save anything in kmenuedit application. Tried creating a new item and
then a new sub menu but it doesn't appear on the menu after saving. 
I'm using Opensuse Leap 42.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 374979] New: KWallet prompt

2017-01-12 Thread Travis N
https://bugs.kde.org/show_bug.cgi?id=374979

Bug ID: 374979
   Summary: KWallet prompt
   Product: frameworks-kwallet
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: tneiheis+...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 103382
  --> https://bugs.kde.org/attachment.cgi?id=103382=edit
Screenshot

When I was adding my github account information KWallet prompted me for my user
name but the input field was marked password and it masked my username. The
next prompt used the same window but correctly asked for my password in 2
locations.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)

2016-12-03 Thread Stanislav N
https://bugs.kde.org/show_bug.cgi?id=348414

Stanislav N <stanis...@nevolin.info> changed:

   What|Removed |Added

 CC|stanis...@nevolin.info  |

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 372565] New: Crash of kate, gwenview, and dolphin

2016-11-16 Thread Kerry N
https://bugs.kde.org/show_bug.cgi?id=372565

Bug ID: 372565
   Summary: Crash of kate, gwenview, and dolphin
   Product: gwenview
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: mothli...@fastmail.fm
CC: myr...@kde.org
  Target Milestone: ---

Application: gwenview (16.08.2)

Qt Version: 5.6.1
Frameworks Version: 5.27.0
Operating System: Linux 4.7.4-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- What I was doing when the application crashed:
System was idle for 30-60 minutes. On return, kate, gwenview, and dolphin had
all crashed.

-- Backtrace:
Application: Gwenview (gwenview), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8998cbe9c0 (LWP 1186))]

Thread 4 (Thread 0x7f897ccac700 (LWP 6283)):
#0  0x7f89a5a73bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f89a7c9301a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f89af1deffb in Gwenview::ThumbnailGenerator::run() () at
/lib64/libgwenviewlib.so.5
#3  0x7f89a7c9299a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7f89a5a6e5ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f89a70860ed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f898483b700 (LWP 1188)):
#0  0x7ffed59e7b84 in clock_gettime ()
#1  0x7f89a70946f6 in clock_gettime () at /lib64/libc.so.6
#2  0x7f89a7d2eab3 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7f89a7e7e869 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7f89a7e7ec65 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f89a7e7fdac in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7f89a7e7fe75 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#7  0x7f89a31d4f59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#8  0x7f89a31d592b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#9  0x7f89a31d5b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#10 0x7f89a7e8024b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#11 0x7f89a7e2f5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#12 0x7f89a7c8e343 in QThread::exec() () at /lib64/libQt5Core.so.5
#13 0x7f89a857c559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#14 0x7f89a7c9299a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#15 0x7f89a5a6e5ca in start_thread () at /lib64/libpthread.so.0
#16 0x7f89a70860ed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f898f396700 (LWP 1187)):
#0  0x7f89a707a56d in poll () at /lib64/libc.so.6
#1  0x7f89a4871f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f89a4873b79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f89920e1da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f89a7c9299a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f89a5a6e5ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f89a70860ed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f8998cbe9c0 (LWP 1186)):
[KCrash Handler]
#6  0x7f89a6fb7765 in raise () at /lib64/libc.so.6
#7  0x7f89a6fb936a in abort () at /lib64/libc.so.6
#8  0x7f89a7c7e471 in  () at /lib64/libQt5Core.so.5
#9  0x7f89a85b3ad2 in  () at /lib64/libQt5DBus.so.5
#10 0x7f89a7e69738 in (anonymous
namespace)::customConstruct(QVariant::Private*, void const*) () at
/lib64/libQt5Core.so.5
#11 0x7f89a7e69e3f in QVariant::QVariant(int, void const*) () at
/lib64/libQt5Core.so.5
#12 0x7f89a7e3d2ca in QMetaProperty::read(QObject const*) const () at
/lib64/libQt5Core.so.5
#13 0x7f89a7e5a258 in QObject::property(char const*) const () at
/lib64/libQt5Core.so.5
#14 0x7f89ab923304 in
Solid::Backends::UDisks2::DeviceBackend::checkCache(QString const&) const () at
/lib64/libKF5Solid.so.5
#15 0x7f89ab923503 in
Solid::Backends::UDisks2::DeviceBackend::propertyExists(QString const&) const
() at /lib64/libKF5Solid.so.5
#16 0x7f89ab91c7a8 in Solid::Backends::UDisks2::Device::isMounted() const
() at /lib64/libKF5Solid.so.5
#17 0x7f89ab93a509 in
Solid::Backends::UDisks2::StorageAccess::isAccessible() const () at
/lib64/libKF5Solid.so.5
#18 0x7f89ab93a724 in
Solid::Backends::UDisks2::StorageAccess::StorageAccess(Solid::Backends::UDisks2::Device*)
() at /lib64/libKF5Solid.so.5
#19 0x7f89ab91acb0 in
Solid::Backends::UDisks2::Device::createDeviceInterface(Solid::DeviceInterface::Type
const&

[gwenview] [Bug 370978] New: Crash after idle period

2016-10-16 Thread Kerry N via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370978

Bug ID: 370978
   Summary: Crash after idle period
   Product: gwenview
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: mothli...@fastmail.fm
CC: myr...@kde.org

Application: gwenview (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
Program was running and was idle for a number hours when the crash reporter
popped up.

-- Backtrace:
Application: Gwenview (gwenview), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7a30d4b9c0 (LWP 10564))]

Thread 4 (Thread 0x7f7a0700 (LWP 10811)):
#0  0x7f7a3db00bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f7a3fd2001a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f7a4726711b in Gwenview::ThumbnailGenerator::run() () at
/lib64/libgwenviewlib.so.5
#3  0x7f7a3fd1f99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7f7a3dafb5ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f7a3f112f6d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f7a1c865700 (LWP 10566)):
#0  0x7fff0b9c7b84 in clock_gettime ()
#1  0x7f7a3f1214e6 in clock_gettime () at /lib64/libc.so.6
#2  0x7f7a3fdbbab3 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7f7a3ff0b869 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7f7a3ff0bc65 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f7a3ff0cdac in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7f7a3ff0ce75 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#7  0x7f7a3b261f59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#8  0x7f7a3b26292b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#9  0x7f7a3b262b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#10 0x7f7a3ff0d24b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#11 0x7f7a3febc5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#12 0x7f7a3fd1b343 in QThread::exec() () at /lib64/libQt5Core.so.5
#13 0x7f7a40609559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#14 0x7f7a3fd1f99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#15 0x7f7a3dafb5ca in start_thread () at /lib64/libpthread.so.0
#16 0x7f7a3f112f6d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f7a27423700 (LWP 10565)):
#0  0x7f7a3f1073ed in poll () at /lib64/libc.so.6
#1  0x7f7a3c8fef80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f7a3c900b79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f7a2a16eda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f7a3fd1f99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f7a3dafb5ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f7a3f112f6d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7a30d4b9c0 (LWP 10564)):
[KCrash Handler]
#6  0x7f7a3f0446f5 in raise () at /lib64/libc.so.6
#7  0x7f7a3f0462fa in abort () at /lib64/libc.so.6
#8  0x7f7a3fd0b471 in  () at /lib64/libQt5Core.so.5
#9  0x7f7a40640ad2 in  () at /lib64/libQt5DBus.so.5
#10 0x7f7a3fef6738 in (anonymous
namespace)::customConstruct(QVariant::Private*, void const*) () at
/lib64/libQt5Core.so.5
#11 0x7f7a3fef6e3f in QVariant::QVariant(int, void const*) () at
/lib64/libQt5Core.so.5
#12 0x7f7a3feca2ca in QMetaProperty::read(QObject const*) const () at
/lib64/libQt5Core.so.5
#13 0x7f7a3fee7258 in QObject::property(char const*) const () at
/lib64/libQt5Core.so.5
#14 0x7f7a439ad304 in
Solid::Backends::UDisks2::DeviceBackend::checkCache(QString const&) const () at
/lib64/libKF5Solid.so.5
#15 0x7f7a439ad503 in
Solid::Backends::UDisks2::DeviceBackend::propertyExists(QString const&) const
() at /lib64/libKF5Solid.so.5
#16 0x7f7a439a67a8 in Solid::Backends::UDisks2::Device::isMounted() const
() at /lib64/libKF5Solid.so.5
#17 0x7f7a439c4509 in
Solid::Backends::UDisks2::StorageAccess::isAccessible() const () at
/lib64/libKF5Solid.so.5
#18 0x7f7a439c4724 in
Solid::Backends::UDisks2::StorageAccess::StorageAccess(Solid::Backends::UDisks2::Device*)
() at /lib64/libKF5Solid.so.5
#19 0x7f7a439a4cb0 in
Solid::Backends::UDisks2::Device::createDeviceInterface(Solid::DeviceInterface::Type
const&) () at /lib64/libKF5Solid.so.5
#20 0x7f7a43958e1f in
Solid::Device::asDeviceInterfac

[dolphin] [Bug 286689] My wish-list for dolphin: creation and modification dates + Folder size

2016-09-15 Thread n via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=286689

n <yeeehi+...@gmail.com> changed:

   What|Removed |Added

 CC||yeeehi+...@gmail.com

--- Comment #11 from n <yeeehi+...@gmail.com> ---
Thank you, ultra...@yahoo.fr, for this excellent bug report/feature request.

1) In Dolphin, if the folder is listed under "Places", folder size is viewable
by clicking on the folder in "Places". This functionality ought to be ported to
the folders themselves. We should be able to hover the mouse and see folder
size/number of files. This would not require much coding or resources.

It might also be helpful if, for example, empty folders were indicated with a
slightly different appearance/colour tone. T

2) Being able to sort files by date downloaded/ created on the computer is an
excellent suggestion. This commonly used functionality is available in M$ft, it
ought to be available in Dolphin.

GNU+Linux keeps logs, these could perhaps be used as a basis for a "Created"
column. Some KDE applications, for example Digikam, already handle "Date
Created" for photo files, and have done for some time, so code is already
available.

I hope that both these bugs are fixed. They are expected features in a file
manager, as far as I am concerned.

-- 
You are receiving this mail because:
You are watching all bug changes.


[ktorrent] [Bug 368825] New: Crash on adding torrent

2016-09-14 Thread Kerry N via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368825

Bug ID: 368825
   Summary: Crash on adding torrent
   Product: ktorrent
   Version: 4.3.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: mothli...@fastmail.fm

Application: ktorrent (4.3.1)
KDE Platform Version: 4.14.20
Qt Version: 4.8.7
Operating System: Linux 4.6.7-200.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
- What I was doing when the application crashed:
Ctrl-p, added torrent, application crashed immediately afterwards.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe461190900 (LWP 15087))]

Thread 10 (Thread 0x7fe3ddc41700 (LWP 18617)):
#0  0x7fe45c7ffb7d in poll () at /lib64/libc.so.6
#1  0x7fe455ed418c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe455ed429c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fe45d530d9e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7fe45d4ff071 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7fe45d4ff3e5 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7fe45d3eeaa9 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7fe45d3f139c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#8  0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0
#9  0x7fe45c80b5fd in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fe3dcdb7700 (LWP 18664)):
#0  0x7fe45ea7fb20 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe42729d071 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib64/libQtWebKit.so.4
#2  0x7fe4275a14c6 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQtWebKit.so.4
#3  0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0
#4  0x7fe45c80b5fd in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fe3d7358700 (LWP 19320)):
#0  0x7fe45ea7fec9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe45d3efd4a in thread_sleep(timespec*) () at /lib64/libQtCore.so.4
#2  0x7fe45d3f06fd in QThread::msleep(unsigned long) () at
/lib64/libQtCore.so.4
#3  0x7fe460d5436f in net::DownloadThread::update() () at
/lib64/libktorrent.so.5
#4  0x7fe460d543c9 in net::NetworkThread::run() () at
/lib64/libktorrent.so.5
#5  0x7fe45d3f139c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#6  0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0
#7  0x7fe45c80b5fd in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fe3d6b57700 (LWP 19321)):
#0  0x7fe460d53a04 in net::UploadThread::waitForSocketsReady() () at
/lib64/libktorrent.so.5
#1  0x7fe460d53b06 in net::UploadThread::update() () at
/lib64/libktorrent.so.5
#2  0x7fe460d543c9 in net::NetworkThread::run() () at
/lib64/libktorrent.so.5
#3  0x7fe45d3f139c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#4  0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0
#5  0x7fe45c80b5fd in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fe3d6356700 (LWP 19323)):
#0  0x7fe45ea7fb20 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe45d3f1906 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQtCore.so.4
#2  0x7fe460d56cb2 in net::ReverseResolverThread::run() () at
/lib64/libktorrent.so.5
#3  0x7fe45d3f139c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#4  0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0
#5  0x7fe45c80b5fd in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fe4415ac700 (LWP 20802)):
#0  0x7fe45c805809 in syscall () at /lib64/libc.so.6
#1  0x7fe45d3efbd2 in QMutexPrivate::wait(int) () at /lib64/libQtCore.so.4
#2  0x7fe45d3ebfbd in QMutex::lock() () at /lib64/libQtCore.so.4
#3  0x7fe45fb3b498 in QHostInfoLookupManager::wasAborted(int) [clone
.part.2] () at /lib64/libQtNetwork.so.4
#4  0x7fe45fb3d797 in QHostInfoRunnable::run() () at
/lib64/libQtNetwork.so.4
#5  0x7fe45d3e46ca in QThreadPoolThread::run() () at /lib64/libQtCore.so.4
#6  0x7fe45d3f139c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#7  0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0
#8  0x7fe45c80b5fd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fe43affd700 (LWP 3616)):
#0  0x7fe45ea7fec9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe45d3f18e4 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQtCore.so.4
#2  0x7fe45d3e48a7 in QThreadPoolThread::run() () at /lib64/libQtCore.so.4
#3  

[Baloo] [Bug 366593] New: Information on Crash

2016-08-10 Thread Anthony N Malczanek via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366593

Bug ID: 366593
   Summary: Information on Crash
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: pinak.ah...@gmail.com
  Reporter: em...@anthonymalczanek.com

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Running the Install Media Creator tool with VirtualBox Manager open (no VMs
running) and Firefox open with three tabs that were displaying github READMEs.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7fa4445c3418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fa4445c501a in __GI_abort () at abort.c:89
#8  0x7fa445074ff1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=this@entry=0x7ffc7eb077c0,
msg=msg@entry=0x7fa4466d8d28 "Cannot construct placeholder type QDBusRawType")
at global/qlogging.cpp:781
#10 0x7fa4466b5552 in QDBusRawTypeHandler::construct () at
qdbusmetaobject.cpp:133
#11 0x7fa4452a89c0 in QMetaType::construct (copy=0x0, where=0x7ffc7eb078e0,
this=0x7ffc7eb07820) at
../../include/QtCore/../../src/corelib/kernel/qmetatype.h:2141
#12 (anonymous namespace)::customConstruct (d=0x7ffc7eb078e0, copy=0x0) at
kernel/qvariant.cpp:1019
#13 0x7fa4452a98bf in QVariant::QVariant (this=0x7ffc7eb078e0,
typeId=, copy=) at kernel/qvariant.cpp:1660
#14 0x7fa445275cf2 in QMetaProperty::read (this=this@entry=0x7ffc7eb07980,
object=object@entry=0x28ec7f0) at kernel/qmetaobject.cpp:3010
#15 0x7fa445295b0f in QObject::property (this=0x28ec7f0, name=0x2a2fdf8
"MountPoints") at kernel/qobject.cpp:3893
#16 0x7fa4462ac664 in Solid::Backends::UDisks2::DeviceBackend::checkCache
(this=0x2caed60, key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:185
#17 0x7fa4462ac883 in
Solid::Backends::UDisks2::DeviceBackend::propertyExists (this=0x2caed60,
key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:132
#18 0x7fa4462a45be in Solid::Backends::UDisks2::Device::propertyExists
(this=this@entry=0x2a2fe30, key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:126
#19 0x7fa4462a637f in Solid::Backends::UDisks2::Device::isMounted
(this=0x2a2fe30) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:818
#20 0x7fa4462bf711 in Solid::Backends::UDisks2::StorageAccess::isAccessible
(this=0x2922170) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:75
#21 0x7fa4462bf944 in Solid::Backends::UDisks2::StorageAccess::updateCache
(this=0x2922170) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:138
#22 Solid::Backends::UDisks2::StorageAccess::StorageAccess (this=0x2922170,
device=0x2a2fe30, __in_chrg=, __vtt_parm=) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:36
#23 0x7fa4462a4780 in
Solid::Backends::UDisks2::Device::createDeviceInterface (this=0x2a2fe30,
type=) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:174
#24 0x7fa44626e68f in Solid::Device::asDeviceInterface
(this=this@entry=0x7ffc7eb07cf0, type=@0x7ffc7eb07c80:
Solid::DeviceInterface::StorageAccess) at
../../../src/solid/devices/frontend/device.cpp:154
#25 0x00423116 in Solid::Device::as
(this=0x7ffc7eb07cf0) at /usr/include/KF5/Solid/solid/device.h:247
#26 Baloo::StorageDevices::createCacheEntry (this=this@entry=0x203a3d0,
dev=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/storagedevices.cpp:79
#27 0x004233a8 in Baloo::StorageDevices::slotSolidDeviceAdded
(this=0x203a3d0, udi=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/storagedevices.cpp:96
#28 0x7fa445296e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffc7eb07e50,
r=0x203a3d0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#29 QMetaObject::activate (sender=0x203a160, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc7eb07e50)
at kernel/qobject.cpp:3698
#30 0x7fa4452977d7 in QMetaObject::activate (sender=,
m=m@entry=0x7fa4464fbe60 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc7eb07e50)
at kernel/qobject.cpp:3578
#31 0x7fa44626ebb2 in Solid::DeviceNotifier::deviceAdded (this=, _t1=...) at ./moc_devicenotifier.cpp:136
#32 0x7fa445296fca in QMetaObject::activate (sender=sender@entry=0x203c200,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffc7eb07f80) 

[drkonqi] [Bug 366056] drqonki chrashing after attempting to send a bug

2016-07-28 Thread Stanislav N via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366056

Stanislav N <stanis...@nevolin.info> changed:

   What|Removed |Added

Version|unspecified |5.7.1

-- 
You are receiving this mail because:
You are watching all bug changes.


[drkonqi] [Bug 366056] New: drqonki chrashing after attempting to send a bug

2016-07-24 Thread Stanislav N via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366056

Bug ID: 366056
   Summary: drqonki chrashing after attempting to send a bug
   Product: drkonqi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: stanis...@nevolin.info

I tried to send a bug about kwin crashing, but drkonqi crashed itself.

Reproducible: Didn't try




Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb822a3e940 (LWP 9216))]

Thread 3 (Thread 0x7fb7fe648700 (LWP 9257)):
#0  0x7fb81f3ffd50 in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#1  0x7fb81f3ffe75 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#2  0x7fb81be12f7d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#3  0x7fb81be1396b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7fb81be13b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7fb81f40024b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7fb81f3af5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7fb81f20e343 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7fb822b10559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#9  0x7fb81f21299a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7fb81cac75ca in start_thread () at /lib64/libpthread.so.0
#11 0x7fb81e605ead in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fb805f62700 (LWP 9234)):
#0  0x7fb81e5fa32d in poll () at /lib64/libc.so.6
#1  0x7fb818a78f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fb818a7ab79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fb809b22da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fb81f21299a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fb81cac75ca in start_thread () at /lib64/libpthread.so.0
#6  0x7fb81e605ead in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fb822a3e940 (LWP 9216)):
[KCrash Handler]
#6  0x7fb8213ebf54 in KNotification::flags() const () at
/lib64/libKF5Notifications.so.5
#7  0x7fb82140b797 in NotifyByAudio::onAudioFinished() () at
/lib64/libKF5Notifications.so.5
#8  0x7fb821410e45 in NotifyByAudio::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libKF5Notifications.so.5
#9  0x7fb81f3d8b92 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#10 0x7fb81cd255d5 in Phonon::MediaObject::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libphonon4qt5.so.4
#11 0x7fb81f3d9bd9 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#12 0x7fb81fc43c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#13 0x7fb81fc490ef in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#14 0x7fb81f3b07aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#15 0x7fb81f3b284f in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#16 0x7fb81f4001b3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#17 0x7fb81be13703 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#18 0x7fb81be13ab0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#19 0x7fb81be13b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#20 0x7fb81f40022f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#21 0x7fb81f3af5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#22 0x7fb81fe49380 in QDialog::exec() () at /lib64/libQt5Widgets.so.5
#23 0x7fb8218fbcdb in KMessageBox::createKMessageBox(QDialog*,
QDialogButtonBox*, QIcon const&, QString const&, QStringList const&, QString
const&, bool*, QFlags, QString const&, QMessageBox::Icon)
() at /lib64/libKF5WidgetsAddons.so.5
#24 0x7fb8218fc826 in KMessageBox::createKMessageBox(QDialog*,
QDialogButtonBox*, QMessageBox::Icon, QString const&, QStringList const&,
QString const&, bool*, QFlags, QString const&) () at
/lib64/libKF5WidgetsAddons.so.5
#25 0x7fb8218fd5aa in KMessageBox::questionYesNoCancelInternal(QDialog*,
QString const&, QString const&, KGuiItem const&, KGuiItem const&, KGuiItem
const&, QString const&, QFlags) () at
/lib64/libKF5WidgetsAddons.so.5
#26 0x55a079971662 in ReportAssistantDialog::closeEvent(QCloseEvent*) ()
#27 0x7fb81fc89940 in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#28 0x7fb81fc43c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at 

[okular] [Bug 316130] Feature request: facing pages in presentation mode

2016-06-30 Thread N . Zou via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=316130

--- Comment #3 from N. Zou <nd...@yahoo.com> ---
As original filer of this request I feel that I should help clarify this
request.  The gist of it is that this request can be fulfilled using existing
control settings.  My original rationale is the same as that described by
Claus, maximizing utilization of screen real estate for wide screens.  But this
can be done by hiding the page navigation panel.  It's even easier if you  map
shortcut keys.  So now if I want to read two pages full screen with no extra
panels. I just do F10 (mapped to facing pages), F11 (mapped to full screen), F8
(mapped to hide navigation bar). Voila, I have 2 pages filling the entire
screen.  Hope this helps.

So basically this request is unnecessary and should remain closed.

-- 
You are receiving this mail because:
You are watching all bug changes.


[kate] [Bug 363767] New: KWrite crashes during the opening of a file txt

2016-05-31 Thread nmrk . n via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363767

Bug ID: 363767
   Summary: KWrite crashes during the opening of a file txt
   Product: kate
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: nmr...@free.fr

Application: kwrite (4.14.3)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.15-desktop-2.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed:
Kwrite plante lors de l'ouverture d'un fichier texte.
KWrite crashes during the opening of a file txt

The crash can be reproduced every time.

-- Backtrace:
Application: KWrite (kwrite), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f06cb75e780 (LWP 28565))]

Thread 2 (Thread 0x7f06a97c4700 (LWP 28566)):
#0  0x7f06ca00867f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f06bc15b73a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQtScript.so.4
#2  0x7f06bc15b769 in  () at /lib64/libQtScript.so.4
#3  0x7f06ca0035bd in start_thread () at /lib64/libpthread.so.0
#4  0x7f06c8d7b62d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f06cb75e780 (LWP 28565)):
[KCrash Handler]
#5  0x7f06ca8f9141 in KSycocaEntry::name() const () at
/lib64/libkdecore.so.5
#6  0x7f06ad6a838f in Kate::TextBuffer::load(QString const&, bool&, bool&,
bool) () at /lib64/libkatepartinterfaces.so.4
#7  0x7f06ad71c5b6 in KateBuffer::openFile(QString const&, bool) () at
/lib64/libkatepartinterfaces.so.4
#8  0x7f06ad71232c in KateDocument::openFile() () at
/lib64/libkatepartinterfaces.so.4
#9  0x7f06bf32dbda in KParts::ReadOnlyPartPrivate::openLocalFile() () at
/usr/lib64/libkparts.so.4
#10 0x7f06bf32fe2e in KParts::ReadOnlyPart::openUrl(KUrl const&) () at
/usr/lib64/libkparts.so.4
#11 0x7f06ad6fe1ae in KateDocument::openUrl(KUrl const&) () at
/lib64/libkatepartinterfaces.so.4
#12 0x7f06b3552616 in KWriteApp::init() () at
/usr/lib64/libkdeinit4_kwrite.so
#13 0x7f06b3552f17 in KWriteApp::KWriteApp(KCmdLineArgs*) () at
/usr/lib64/libkdeinit4_kwrite.so
#14 0x7f06b3551843 in kdemain () at /usr/lib64/libkdeinit4_kwrite.so
#15 0x0040819a in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) ()
#16 0x00409021 in handle_launcher_request(int, char const*) [clone
.isra.15] ()
#17 0x0040972a in handle_requests(int) ()
#18 0x00405303 in main ()

Possible duplicates by query: bug 359754, bug 356473, bug 350099, bug 348977.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2016-05-02 Thread Alberto N . via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356225

--- Comment #89 from Alberto N. <alberto.cartag...@gmail.com> ---
A workaround that is finally working for me, with a prerequisite, only one
panel in total among all the monitors. It's rather simple but try it if it's
your case.

System Settings -> Window management -> Window Rules
You just need a rule that applies to "Panel" and forces it to screen 1 (or
whatever your prefer).

If only there was a way of differentiating panels!! You could force your panels
in the screen you wanted, but I haven't found so yet. 

Thanks everyone for fighting this annoying bug, it's really disturbing that
it's happening in a so-called mature environment, it's like we're back to
justify our users that something simple that works in win and mac is almost
impossible in KDE again :(

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2016-04-09 Thread Alberto N . via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356225

Alberto N. <alberto.cartag...@gmail.com> changed:

   What|Removed |Added

 CC||alberto.cartag...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[kdeconnect] [Bug 337685] SFTP: Filesystem expose doesn't work

2016-03-13 Thread Stanislav N via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=337685

Stanislav N <stanis...@nevolin.info> changed:

   What|Removed |Added

 CC||stanis...@nevolin.info

--- Comment #15 from Stanislav N <stanis...@nevolin.info> ---
The same problem.
/usr/libexec/gdm-x-session[2331]: fusermount: entry for
/home/wizard/.config/kdeconnect/5290a060de937612/kdeconnect_sftp/5290a060de937612
not found in /etc/mtab

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 358238] New: Templates don't act as "templates"

2016-01-19 Thread Drew N via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358238

Bug ID: 358238
   Summary: Templates don't act as "templates"
   Product: digikam
   Version: 3.5.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata-Template
  Assignee: digikam-de...@kde.org
  Reporter: n1xim.em...@gmail.com

When using digiKam to apply Rights Management information using the "Template"
function it becomes impossible to edit fields using the quick editor.
Additionally, those fields do not appear in the full Metadata editor, so there
is no other way to edit them. If the "Template" function is not for templates,
then please change the name. If it is for templates then make it apply
templates which are the starting point for further editing and make locking
those templates a configurable option.

Reproducible: Always

Steps to Reproduce:
1. Select Image
2. Apply "Information" Metadata Template
3. Attempt to edit a field

Actual Results:  
Get angry when nothing happens, scream loudly, give up and wonder when
Lightroom will become available for LINUX.

Expected Results:  
The template acts as just that, a TEMPLATE to start further customizing of the
data fields available without having to type EVERYTHING in by hand.

Additionally, when setting the template to "Do Not Change" (presumably
available so one can hand edit things???) it instead CLEARS ALL OF THE
TEMPLATE-ABLE METADATA. What??

-- 
You are receiving this mail because:
You are watching all bug changes.


<    1   2   3