[konqueror] [Bug 384376] Konqueror crashing on start of Plasma Desktop

2019-06-27 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=384376

--- Comment #27 from Patrick Carabin  ---
Created attachment 121193
  --> https://bugs.kde.org/attachment.cgi?id=121193=edit
New crash information added by DrKonqi

kdeinit5 (5.0.97) using Qt 5.9.5

- What I was doing when the application crashed:
At startup, konqueror crashes WHEN IT WAS OPEN AT the previous SHUTDOWN 
- Unusual behavior I noticed:
Once, i CLOSED konqueror BEFORE SHUTDOWN. At next statup, Konqueror did NOT
start automatically. The manual start of konqueror was correct... 
At the NEXT START ( WITHOUT having stopped konqueror manually), konqueror
CRASHED AGAIN.
- Custom settings of the application:

-- Backtrace (Reduced):
#7  0xb28822d4 in KonqView::url() const () at
/usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so
#8  0xb28bab99 in KonqMainWindow::isPreloaded() const () at
/usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so
#9  0xb28f2af0 in KonqSessionManager::saveCurrentSessionToFile(KConfig*,
QList const&) () at
/usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so
#10 0xb28f2d7a in KonqSessionManager::autoSaveSession() () at
/usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so
#11 0xb2906e09 in  () at /usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so

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

[kde] [Bug 408356] New: Konqueror crasches at login in Kubuntu

2019-06-05 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=408356

Bug ID: 408356
   Summary: Konqueror crasches at login in Kubuntu
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

Application: kdeinit5 (5.0.97)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-51-generic i686
Distribution: Ubuntu 18.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
just logging in. It happens at each login.
- Unusual behavior I noticed:
It seems the tabs in konqueror are duplicated after each crash.

The crash can be reproduced every time.

-- Backtrace:
Application: Konqueror (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb422a700 (LWP 3898))]

Thread 19 (Thread 0x92347b40 (LWP 4168)):
#0  0xb7f25d09 in __kernel_vsyscall ()
#1  0xb664d810 in futex_wait_cancelable (private=, expected=0,
futex_word=0xf35f94) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#2  0xb664d810 in __pthread_cond_wait_common (abstime=0x0, mutex=0xf35f54,
cond=0xf35f6c) at pthread_cond_wait.c:502
#3  0xb664d810 in __pthread_cond_wait (cond=0xf35f6c, mutex=0xf35f54) at
pthread_cond_wait.c:655
#4  0xa51bbdac in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#5  0xa5189de9 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#6  0xa518a37f in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#7  0xa518b464 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#8  0xa51873b8 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#9  0xb66473bd in start_thread (arg=0x92347b40) at pthread_create.c:463
#10 0xb70a9e16 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

Thread 18 (Thread 0x96ceeb40 (LWP 4161)):
#0  0xb7f25d09 in __kernel_vsyscall ()
#1  0xb70b7012 in __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/i386/lowlevellock.S:97
#2  0xb70b89fb in ___fprintf_chk (fp=0xb7189ce0 <_IO_2_1_stderr_>, flag=1,
format=0xa41634b0 "[%s] %s\n") at fprintf_chk.c:30
#3  0xa414a933 in event_logv_ () at /usr/lib/i386-linux-gnu/libevent-2.1.so.6
#4  0xa414a9e0 in event_warn () at /usr/lib/i386-linux-gnu/libevent-2.1.so.6
#5  0xa414c264 in  () at /usr/lib/i386-linux-gnu/libevent-2.1.so.6
#6  0xa414146e in event_base_loop () at
/usr/lib/i386-linux-gnu/libevent-2.1.so.6
#7  0xa5156df1 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#8  0xa5152c74 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#9  0xa51720f8 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#10 0xa518baa1 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#11 0xa51873b8 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#12 0xb66473bd in start_thread (arg=0x96ceeb40) at pthread_create.c:463
#13 0xb70a9e16 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

Thread 17 (Thread 0x974efb40 (LWP 4160)):
#0  0xb7f25d09 in __kernel_vsyscall ()
#1  0xb709f43b in __GI___poll (fds=0xf88cf0, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
#2  0xb2ce0323 in  () at /usr/lib/i386-linux-gnu/libpulse.so.0
#3  0xb2cd1234 in pa_mainloop_poll () at /usr/lib/i386-linux-gnu/libpulse.so.0
#4  0xb2cd1949 in pa_mainloop_iterate () at
/usr/lib/i386-linux-gnu/libpulse.so.0
#5  0xb2cd19dc in pa_mainloop_run () at /usr/lib/i386-linux-gnu/libpulse.so.0
#6  0xb2ce0261 in  () at /usr/lib/i386-linux-gnu/libpulse.so.0
#7  0xb2c6ca3e in  () at
/usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#8  0xb66473bd in start_thread (arg=0x974efb40) at pthread_create.c:463
#9  0xb70a9e16 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

Thread 16 (Thread 0x97cf0b40 (LWP 4159)):
#0  0xb7f25d09 in __kernel_vsyscall ()
#1  0xb664d810 in futex_wait_cancelable (private=, expected=0,
futex_word=0x97cf00b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#2  0xb664d810 in __pthread_cond_wait_common (abstime=0x0, mutex=0x97cf0070,
cond=0x97cf0088) at pthread_cond_wait.c:502
#3  0xb664d810 in __pthread_cond_wait (cond=0x97cf0088, mutex=0x97cf0070) at
pthread_cond_wait.c:655
#4  0xa51bbdac in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#5  0xa517f30c in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#6  0xa517f341 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#7  0xa51566e3 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#8  0xa5152c74 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#9  0xa51720f8 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#10 0xa518baa1 in  () at /usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5
#11 0xa51873b8 in  () at

[kmail2] [Bug 405005] In KMAIL ( I do not see any KMAIL2 ) There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP

2019-03-02 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=405005

Patrick Carabin  changed:

   What|Removed |Added

 CC||patrick.cara...@gmail.com

--- Comment #2 from Patrick Carabin  ---
STEPS TO REPRODUCE
1. Kmail unable to connect to GMAIL server
2. By mistake, click seems to remove the menus
3. Idiotic message appears 1 ms ( 0,001 sec) telling it removes the menus, and
(may be) telling how to get the menus back[impossible to read, it disappears]
4. dpkg-reconfigure kmail SHOULD correct the problem, but DOES NOT
5. PURGE kmail and pim, and reinstall : does NOT solve the problem

OBSERVED RESULT
the menus DO NOT reappear: KMAIL unusable

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma:

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

[kmail2] [Bug 405005] In KMAIL ( I do not see any KMAIL2 ) There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP

2019-03-02 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=405005

--- Comment #1 from Patrick Carabin  ---
N: Impossible de trouver le paquet kmail2
version : ii  kmail  
4:17.12.3-0ubuntu1

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

[kmail2] [Bug 405005] In KMAIL ( I do not see any KMAIL2 ) There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP

2019-03-02 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=405005

Patrick Carabin  changed:

   What|Removed |Added

Summary|There is a STUPID OPTION to |In KMAIL ( I do not see any
   |suppress the menu, and NO   |KMAIL2 ) There is a STUPID
   |WAY BACK: dpkg-reconfigure  |OPTION to suppress the
   |does NOT repair, Uninstall  |menu, and NO WAY BACK:
   |+ Reinstall does NOT HELP   |dpkg-reconfigure does NOT
   ||repair, Uninstall +
   ||Reinstall does NOT HELP

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

[kmail2] [Bug 405005] New: There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP

2019-03-02 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=405005

Bug ID: 405005
   Summary: There is a STUPID OPTION to suppress the menu, and NO
WAY BACK: dpkg-reconfigure does NOT repair, Uninstall
+ Reinstall does NOT HELP
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 376969] New: crash after trying to change the hight of the characters to display the full needed info

2017-02-26 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=376969

Bug ID: 376969
   Summary: crash after trying to change the hight of the
characters to display the full needed info
   Product: systemsettings
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-64-generic i686
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
i tried to change the Ctrl-F1 into another key ( Crtl-1 ), which was impossible
because the place did not display ( bad shape of the frame ), tried to change
the shape of the character so it could become visible, which did NOT work. The
i halted systemsettings5 , and it crashed.
- Unusual behavior I noticed:
bad shape of the frames, which i observed in ALL the installations i made since
severl months.

-- Backtrace:
Application: Configuration du système (systemsettings5), signal: Segmentation
fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb246c800 (LWP 2402))]

Thread 4 (Thread 0xa9b85b40 (LWP 5582)):
#0  0xb4a1c5d5 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb4a1d024 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb4a1d254 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb6185964 in QEventDispatcherGlib::processEvents (this=0xa9200470,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0xb612a7a3 in QEventLoop::processEvents (this=0xa9b851d4, flags=...) at
kernel/qeventloop.cpp:128
#5  0xb612abfa in QEventLoop::exec (this=0xa9b851d4, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb5f50f1d in QThread::exec (this=0xb9e1570) at thread/qthread.cpp:503
#7  0xb5418aff in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#8  0xb5f5643b in QThreadPrivate::start (arg=0xb9e1570) at
thread/qthread_unix.cpp:331
#9  0xb4b65295 in start_thread (arg=0xa9b85b40) at pthread_create.c:333
#10 0xb5c83eee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 3 (Thread 0xab4b4b40 (LWP 4720)):
#0  0xb4a1c564 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb4a1d024 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb4a1d254 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb6185964 in QEventDispatcherGlib::processEvents (this=0xaab00470,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0xb612a7a3 in QEventLoop::processEvents (this=0xab4b41d4, flags=...) at
kernel/qeventloop.cpp:128
#5  0xb612abfa in QEventLoop::exec (this=0xab4b41d4, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb5f50f1d in QThread::exec (this=0xa0364a8) at thread/qthread.cpp:503
#7  0xb5418aff in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#8  0xb5f5643b in QThreadPrivate::start (arg=0xa0364a8) at
thread/qthread_unix.cpp:331
#9  0xb4b65295 in start_thread (arg=0xab4b4b40) at pthread_create.c:333
#10 0xb5c83eee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 2 (Thread 0xb202eb40 (LWP 2407)):
#0  0xb7718c31 in __kernel_vsyscall ()
#1  0xb5c79d0f in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0xb4bdf41d in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#3  0xb4be159b in xcb_wait_for_event () from
/usr/lib/i386-linux-gnu/libxcb.so.1
#4  0xb2174273 in QXcbEventReader::run (this=0x9c799d0) at
qxcbconnection.cpp:1253
#5  0xb5f5643b in QThreadPrivate::start (arg=0x9c799d0) at
thread/qthread_unix.cpp:331
#6  0xb4b65295 in start_thread (arg=0xb202eb40) at pthread_create.c:333
#7  0xb5c83eee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 1 (Thread 0xb246c800 (LWP 2402)):
[KCrash Handler]
#7  0x0016 in ?? ()
#8  0xb61613af in QObject::disconnect (sender=0x9e10138, signal=, receiver=0x9f00ac8, method=0x9efc159
"slotManagedTopLevelWidgetDestroyed()") at kernel/qobject.cpp:2932
#9  0xaebd455c in KParts::PartManager::~PartManager() () from
/usr/lib/i386-linux-gnu/libKF5Parts.so.5
#10 0xaebd474a in KParts::PartManager::~PartManager() () from
/usr/lib/i386-linux-gnu/libKF5Parts.so.5
#11 0xb615b7c0 in QObjectPrivate::deleteChildren (this=0x9eb1ff8) at
kernel/qobject.cpp:1946
#12 0xb6164d9c in QObject::~QObject (this=0x9eb1d80, __in_chrg=)
at kernel/qobject.cpp:1024
#13 0xaebcc5b8 in KParts::Part::~Part() () from
/usr/lib/i386-linux-gnu/libKF5Parts.so.5
#14 0xaebce18e in KParts::ReadOnlyPart::~ReadOnlyPart() () from
/usr/lib/i386-linux-gnu/libKF5Parts.so.5
#15 0xaee15cb1 in KHTMLPart::~KHTMLPart() () from
/usr/lib/i386-linux-gnu/libKF5KHtml.so.5
#16 0xaee15dfa in KHTMLPart::~KHTMLPart() () from

[kde] [Bug 373926] New: Baloo - Segmentation fault

2016-12-19 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=373926

Bug ID: 373926
   Summary: Baloo - Segmentation fault
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-53-generic i686
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I just started the PC and Logged ON
It's every day the same...

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  0xb5c8c1fa in mdb_txn_begin () from /usr/lib/i386-linux-gnu/liblmdb.so.0
#8  0xb74fc2e9 in Baloo::Transaction::Transaction (this=0xbfbfdc9c, db=...,
type=Baloo::Transaction::ReadOnly) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:53
#9  0xb74fc3e0 in Baloo::Transaction::Transaction (this=0xbfbfdc9c,
db=0xb7518240 <(anonymous namespace)::Q_QGS_s_db::innerFunction()::holder>,
type=Baloo::Transaction::ReadOnly) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:62
#10 0x0806551f in Baloo::FileContentIndexerProvider::size (this=0xbfbfe5bc) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/filecontentindexerprovider.cpp:40
#11 0x0805ed54 in Baloo::FileIndexScheduler::scheduleIndexing (this=0xbfbfe598)
at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:121
#12 0x0805ef75 in Baloo::FileIndexScheduler::powerManagementStatusChanged
(this=0xbfbfe598, isOnBattery=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:177
#13 0x0805f7b6 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (Baloo::FileIndexScheduler::*)(bool)>::call
(arg=0xbfbfdee4, o=0xbfbfe598, f=) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501
#14 QtPrivate::FunctionPointer::call
(arg=0xbfbfdee4, o=0xbfbfe598, f=) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520
#15 QtPrivate::QSlotObject, void>::impl (which=1, this_=0x901c080, r=0xbfbfe598,
a=0xbfbfdee4, ret=0x0) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:143
#16 0xb7212080 in QtPrivate::QSlotObjectBase::call (a=0xbfbfdee4, r=0xbfbfe598,
this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#17 QMetaObject::activate (sender=0xbfbfe5c4, signalOffset=3,
local_signal_index=0, argv=0xbfbfdee4) at kernel/qobject.cpp:3698
#18 0xb721295d in QMetaObject::activate (sender=0xbfbfe5c4, m=0x8094c70
, local_signal_index=0,
argv=0xbfbfdee4) at kernel/qobject.cpp:3578
#19 0x08077fd9 in Baloo::PowerStateMonitor::powerManagementStatusChanged
(this=0xbfbfe5c4, _t1=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/obj-i686-linux-gnu/src/file/moc_powerstatemonitor.cpp:135
#20 0x0807d964 in Baloo::PowerStateMonitor::slotPowerManagementStatusChanged
(this=0xbfbfe5c4, conserveResources=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:63
#21 0x0807daf0 in
Baloo::PowerStateMonitor::::operator()
(watch=0x9002378, __closure=) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:53
#22 QtPrivate::FunctorCall,
QtPrivate::List, void,
Baloo::PowerStateMonitor::PowerStateMonitor(QObject*)::
>::call (arg=0xbfbfe084, f=...) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495
#23
QtPrivate::Functor,
1>::call, void> (arg=0xbfbfe084,
f=...) at /usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552
#24
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x9031e90, r=0x9002378, a=0xbfbfe084, ret=0x0) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:192
#25 0xb7212080 in QtPrivate::QSlotObjectBase::call (a=0xbfbfe084, r=0x9002378,
this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#26 QMetaObject::activate (sender=0x9002378, signalOffset=3,
local_signal_index=0, argv=0xbfbfe084) at kernel/qobject.cpp:3698
#27 0xb721295d in QMetaObject::activate (sender=0x9002378, m=0xb768db7c
, local_signal_index=0,
argv=0xbfbfe084) at kernel/qobject.cpp:3578
#28 0xb765aac9 in

[kde] [Bug 373626] New: Baloo crashes at login

2016-12-13 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=373626

Bug ID: 373626
   Summary: Baloo crashes at login
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-53-generic i686
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I reloaded the computer
No other app is running now ( even not konsole )

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  0xb5c591fa in mdb_txn_begin () from /usr/lib/i386-linux-gnu/liblmdb.so.0
#8  0xb74c92e9 in Baloo::Transaction::Transaction (this=0xbf9dc65c, db=...,
type=Baloo::Transaction::ReadOnly) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:53
#9  0xb74c93e0 in Baloo::Transaction::Transaction (this=0xbf9dc65c,
db=0xb74e5240 <(anonymous namespace)::Q_QGS_s_db::innerFunction()::holder>,
type=Baloo::Transaction::ReadOnly) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:62
#10 0x0806551f in Baloo::FileContentIndexerProvider::size (this=0xbf9dcf7c) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/filecontentindexerprovider.cpp:40
#11 0x0805ed54 in Baloo::FileIndexScheduler::scheduleIndexing (this=0xbf9dcf58)
at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:121
#12 0x0805ef75 in Baloo::FileIndexScheduler::powerManagementStatusChanged
(this=0xbf9dcf58, isOnBattery=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:177
#13 0x0805f7b6 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (Baloo::FileIndexScheduler::*)(bool)>::call
(arg=0xbf9dc8a4, o=0xbf9dcf58, f=) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501
#14 QtPrivate::FunctionPointer::call
(arg=0xbf9dc8a4, o=0xbf9dcf58, f=) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520
#15 QtPrivate::QSlotObject, void>::impl (which=1, this_=0x8eba188, r=0xbf9dcf58,
a=0xbf9dc8a4, ret=0x0) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:143
#16 0xb71df080 in QtPrivate::QSlotObjectBase::call (a=0xbf9dc8a4, r=0xbf9dcf58,
this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#17 QMetaObject::activate (sender=0xbf9dcf84, signalOffset=3,
local_signal_index=0, argv=0xbf9dc8a4) at kernel/qobject.cpp:3698
#18 0xb71df95d in QMetaObject::activate (sender=0xbf9dcf84, m=0x8094c70
, local_signal_index=0,
argv=0xbf9dc8a4) at kernel/qobject.cpp:3578
#19 0x08077fd9 in Baloo::PowerStateMonitor::powerManagementStatusChanged
(this=0xbf9dcf84, _t1=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/obj-i686-linux-gnu/src/file/moc_powerstatemonitor.cpp:135
#20 0x0807d964 in Baloo::PowerStateMonitor::slotPowerManagementStatusChanged
(this=0xbf9dcf84, conserveResources=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:63
#21 0x0807daf0 in
Baloo::PowerStateMonitor::::operator()
(watch=0x8edfb20, __closure=) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:53
#22 QtPrivate::FunctorCall,
QtPrivate::List, void,
Baloo::PowerStateMonitor::PowerStateMonitor(QObject*)::
>::call (arg=0xbf9dca44, f=...) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495
#23
QtPrivate::Functor,
1>::call, void> (arg=0xbf9dca44,
f=...) at /usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552
#24
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x8eba258, r=0x8edfb20, a=0xbf9dca44, ret=0x0) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:192
#25 0xb71df080 in QtPrivate::QSlotObjectBase::call (a=0xbf9dca44, r=0x8edfb20,
this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#26 QMetaObject::activate (sender=0x8edfb20, signalOffset=3,
local_signal_index=0, argv=0xbf9dca44) at kernel/qobject.cpp:3698
#27 0xb71df95d in QMetaObject::activate (sender=0x8edfb20, m=0xb765ab7c
, local_signal_index=0,
argv=0xbf9dca44) at kernel/qobject.cpp:3578
#28 0xb7627ac9 in

[kde] [Bug 373422] New: Baloo stops at startup

2016-12-08 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=373422

Bug ID: 373422
   Summary: Baloo stops at startup
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-53-generic i686
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I just logged in. I did NOT ask to run Baloo...
- Unusual behavior I noticed:
I installed KUbuntu this WE - since then, Baloo start and crashes each time i
log in

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  0xb5c141fa in mdb_txn_begin () from /usr/lib/i386-linux-gnu/liblmdb.so.0
#8  0xb74842e9 in Baloo::Transaction::Transaction (this=0xbfec487c, db=...,
type=Baloo::Transaction::ReadOnly) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:53
#9  0xb74843e0 in Baloo::Transaction::Transaction (this=0xbfec487c,
db=0xb74a0240 <(anonymous namespace)::Q_QGS_s_db::innerFunction()::holder>,
type=Baloo::Transaction::ReadOnly) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:62
#10 0x0806551f in Baloo::FileContentIndexerProvider::size (this=0xbfec519c) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/filecontentindexerprovider.cpp:40
#11 0x0805ed54 in Baloo::FileIndexScheduler::scheduleIndexing (this=0xbfec5178)
at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:121
#12 0x0805ef75 in Baloo::FileIndexScheduler::powerManagementStatusChanged
(this=0xbfec5178, isOnBattery=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:177
#13 0x0805f7b6 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (Baloo::FileIndexScheduler::*)(bool)>::call
(arg=0xbfec4ac4, o=0xbfec5178, f=) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501
#14 QtPrivate::FunctionPointer::call
(arg=0xbfec4ac4, o=0xbfec5178, f=) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520
#15 QtPrivate::QSlotObject, void>::impl (which=1, this_=0x9fd1e98, r=0xbfec5178,
a=0xbfec4ac4, ret=0x0) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:143
#16 0xb719a080 in QtPrivate::QSlotObjectBase::call (a=0xbfec4ac4, r=0xbfec5178,
this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#17 QMetaObject::activate (sender=0xbfec51a4, signalOffset=3,
local_signal_index=0, argv=0xbfec4ac4) at kernel/qobject.cpp:3698
#18 0xb719a95d in QMetaObject::activate (sender=0xbfec51a4, m=0x8094c70
, local_signal_index=0,
argv=0xbfec4ac4) at kernel/qobject.cpp:3578
#19 0x08077fd9 in Baloo::PowerStateMonitor::powerManagementStatusChanged
(this=0xbfec51a4, _t1=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/obj-i686-linux-gnu/src/file/moc_powerstatemonitor.cpp:135
#20 0x0807d964 in Baloo::PowerStateMonitor::slotPowerManagementStatusChanged
(this=0xbfec51a4, conserveResources=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:63
#21 0x0807daf0 in
Baloo::PowerStateMonitor::::operator()
(watch=0x9f686a8, __closure=) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:53
#22 QtPrivate::FunctorCall,
QtPrivate::List, void,
Baloo::PowerStateMonitor::PowerStateMonitor(QObject*)::
>::call (arg=0xbfec4c64, f=...) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495
#23
QtPrivate::Functor,
1>::call, void> (arg=0xbfec4c64,
f=...) at /usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552
#24
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x9fb58c8, r=0x9f686a8, a=0xbfec4c64, ret=0x0) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:192
#25 0xb719a080 in QtPrivate::QSlotObjectBase::call (a=0xbfec4c64, r=0x9f686a8,
this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#26 QMetaObject::activate (sender=0x9f686a8, signalOffset=3,
local_signal_index=0, argv=0xbfec4c64) at kernel/qobject.cpp:3698
#27 0xb719a95d in QMetaObject::activate (sender=0x9f686a8, m=0xb7615b7c
,

[kde] [Bug 373397] New: Baloo crashed at startup

2016-12-07 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=373397

Bug ID: 373397
   Summary: Baloo crashed at startup
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-53-generic i686
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I just logged in 
- Unusual behavior I noticed:
The screen still stays bad ( instead of filling the screen like during
installation ), I get a square with difficult to read text), since i told i
have a LAPTOP, and it was IMPOSSIBLE to UNDO it.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  0xb5bef1fa in mdb_txn_begin () from /usr/lib/i386-linux-gnu/liblmdb.so.0
#8  0xb745f2e9 in Baloo::Transaction::Transaction (this=0xbfda776c, db=...,
type=Baloo::Transaction::ReadOnly) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:53
#9  0xb745f3e0 in Baloo::Transaction::Transaction (this=0xbfda776c,
db=0xb747b240 <(anonymous namespace)::Q_QGS_s_db::innerFunction()::holder>,
type=Baloo::Transaction::ReadOnly) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:62
#10 0x0806551f in Baloo::FileContentIndexerProvider::size (this=0xbfda808c) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/filecontentindexerprovider.cpp:40
#11 0x0805ed54 in Baloo::FileIndexScheduler::scheduleIndexing (this=0xbfda8068)
at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:121
#12 0x0805ef75 in Baloo::FileIndexScheduler::powerManagementStatusChanged
(this=0xbfda8068, isOnBattery=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:177
#13 0x0805f7b6 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (Baloo::FileIndexScheduler::*)(bool)>::call
(arg=0xbfda79b4, o=0xbfda8068, f=) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501
#14 QtPrivate::FunctionPointer::call
(arg=0xbfda79b4, o=0xbfda8068, f=) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520
#15 QtPrivate::QSlotObject, void>::impl (which=1, this_=0x950c810, r=0xbfda8068,
a=0xbfda79b4, ret=0x0) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:143
#16 0xb7175080 in QtPrivate::QSlotObjectBase::call (a=0xbfda79b4, r=0xbfda8068,
this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#17 QMetaObject::activate (sender=0xbfda8094, signalOffset=3,
local_signal_index=0, argv=0xbfda79b4) at kernel/qobject.cpp:3698
#18 0xb717595d in QMetaObject::activate (sender=0xbfda8094, m=0x8094c70
, local_signal_index=0,
argv=0xbfda79b4) at kernel/qobject.cpp:3578
#19 0x08077fd9 in Baloo::PowerStateMonitor::powerManagementStatusChanged
(this=0xbfda8094, _t1=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/obj-i686-linux-gnu/src/file/moc_powerstatemonitor.cpp:135
#20 0x0807d964 in Baloo::PowerStateMonitor::slotPowerManagementStatusChanged
(this=0xbfda8094, conserveResources=false) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:63
#21 0x0807daf0 in
Baloo::PowerStateMonitor::::operator()
(watch=0x94f4a08, __closure=) at
/build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:53
#22 QtPrivate::FunctorCall,
QtPrivate::List, void,
Baloo::PowerStateMonitor::PowerStateMonitor(QObject*)::
>::call (arg=0xbfda7b54, f=...) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495
#23
QtPrivate::Functor,
1>::call, void> (arg=0xbfda7b54,
f=...) at /usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552
#24
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x94d60b0, r=0x94f4a08, a=0xbfda7b54, ret=0x0) at
/usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:192
#25 0xb7175080 in QtPrivate::QSlotObjectBase::call (a=0xbfda7b54, r=0x94f4a08,
this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#26 QMetaObject::activate (sender=0x94f4a08, signalOffset=3,
local_signal_index=0, argv=0xbfda7b54) at kernel/qobject.cpp:3698
#27

[systemsettings] [Bug 373325] New: Impossible to UNDO an ugly screen ( Laptop selection made an horrible and difficult to use screen on my Toshiba Laptop )

2016-12-05 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=373325

Bug ID: 373325
   Summary: Impossible to UNDO an ugly screen ( Laptop selection
made an horrible and difficult to use screen on my
Toshiba Laptop )
   Product: systemsettings
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: krdb
  Assignee: kdelibs-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

Because I have a Laptop, i selected the «Laptop» option. Catastrophe! 
While asking to «Undo» or «restore default», I still keep a difficult-to-read
screen ), square instead of rectangular-full-screen. Please correct the «undo»
fuction which is NOT WORKING.

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

[kwin] [Bug 94470] unilaterally violate the NETWM spec to support inner xinerama struts

2016-12-05 Thread Patrick Carabin 
https://bugs.kde.org/show_bug.cgi?id=94470

Patrick Carabin <patrick.cara...@gmail.com> changed:

   What|Removed |Added

 CC||patrick.cara...@gmail.com

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