[kwin] [Bug 480992] New: Kwin (wayland) crashes after idle for about one hour

2024-02-07 Thread Leandro Santiago da Silva
https://bugs.kde.org/show_bug.cgi?id=480992

Bug ID: 480992
   Summary: Kwin (wayland) crashes after idle for about one hour
Classification: Plasma
   Product: kwin
   Version: 5.27.10
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: leandrosansi...@gmail.com
  Target Milestone: ---

Created attachment 165641
  --> https://bugs.kde.org/attachment.cgi?id=165641=edit
energy settings

SUMMARY

Kwin_wayland Crashes on no activity. I've noticed that kwin logs to syslog when
Kwin tries to put my two screens to sleep. One screen is on a HDMI port and the
other on a Display Port.

The line I often see on `dmesg` is:

```
[272940.976297] traps: VizCompositorTh[2705470] trap invalid opcode
ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000]
```

The screens are configured in the KDE settings to go to sleep after 10min. They
never go though, instead flickering and finally turning on again.

This time though, after leaving the computer doing nothing for about one hour,
when I returned, Plasma was on a "reset" state, with no windows open. The
screen was unlocked though, so I suspect that the plasma session did not
restart (I did not have to unlock it or go back to SDDM).

The applications set on autostart did not restart.

Upon checking `dmesg`, unfortunately this is the best info I can get:

```
[229252.822425] traps: GlobalQueue[26][2674503] general protection fault
ip:7fe76a2c1ddd sp:7fe7015fefd8 error:0 in
libQt5Core.so.5.15.12[7fe76a09f000+2dd000]
[230033.962062] traps: VizCompositorTh[2567709] trap int3 ip:7fbe4111290d
sp:7fbded5fd2d0 error:0 in libcef.so[7fbe37a15000+9aec000]
[230644.965366] traps: VizCompositorTh[2556985] trap invalid opcode
ip:560a520d6d6e sp:7f2a2c9fe490 error:0 in signal-desktop[560a4d6b2000+7e36000]
[230725.867704] traps: VizCompositorTh[2687472] trap invalid opcode
ip:560a520d6d6e sp:7f2a2c9fe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000]
[232955.172067] traps: VizCompositorTh[2682322] trap int3 ip:7fbe4111290d
sp:7fbdecbfd090 error:0 in libcef.so[7fbe37a15000+9aec000]
[232993.119132] traps: VizCompositorTh[2688239] trap invalid opcode
ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000]
[269637.931822] traps: VizCompositorTh[2549760] trap invalid opcode
ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000]
[270246.887782] traps: VizCompositorTh[2959470] trap invalid opcode
ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000]
[272940.976097] traps: VizCompositorTh[2963805] trap invalid opcode
ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000]
[272940.976297] traps: VizCompositorTh[2705470] trap invalid opcode
ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000]
[272942.646675] traps: VizCompositorTh[2983487] trap invalid opcode
ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000]
[273551.878088] kwin_wayland[2279]: segfault at 0 ip 7f69ed36939a sp
73e2c930 error 4 in libkwin.so.5.27.10[7f69ed369000+327000] likely on
CPU 31 (core 15, socket 0)
[273551.878099] Code: 04 25 00 00 00 00 0f 0b 48 8b 04 25 00 00 00 00 0f 0b 8b
04 25 20 00 00 00 0f 0b 90 8b 04 25 20 00 00 00 0f 0b 90 f3 0f 1e fa <48> 8b 04
25 00 00 00 00 0f 0b 31 ff ff 15 14 ed 48 00 0f b7 04 25
[273551.882364] traps: VizCompositorTh[2983700] trap invalid opcode
ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000]
[273585.084529] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[273585.084533] Bluetooth: BNEP filters: protocol multicast
[273585.084537] Bluetooth: BNEP socket layer initialized
```

STEPS TO REPRODUCE
1. Configure  the screens to switch off after 10min, as in the attached image.
2. let the computer idle. In my case, I left two dolphin windows, each with an
embedded terminal (F4) open, doing some work (in my case, computing md5sum of
some large files). 
3. Go have breakfast and return after about 1 hour.
4. The workspace is empty, with no windows open. All previously running
processes were killed.

OBSERVED RESULT

Plasma workspace empty, no windows open. All previously opened windows were
killed.

EXPECTED RESULT

The screens should've been switched off. Maybe the screens would be locked,
asking for authentication to unlock.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 6.7.0-0-MANJARO (amd64)
KDE Plasma Version: 5.27.10 
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION

Kwin Info:

```
KWin Support Information:
The following information should be used when requesting support on e.g.
https://forum.kde.org.
It provides information about the currently running instance, which options are
used,
what OpenGL driver and which effects are running.
Please post the information provided underneath 

[valgrind] [Bug 339596] AMD64 xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

2022-08-22 Thread Leandro Nini
https://bugs.kde.org/show_bug.cgi?id=339596

Leandro Nini  changed:

   What|Removed |Added

 CC||drfiem...@email.it

--- Comment #28 from Leandro Nini  ---
Been hit by another unhandled instruction using valgrind-3.19.0 with the bextr
patch from bug #381819 applied:

vex amd64->IR: unhandled instruction bytes: 0x8F 0xC8 0x70 0xA3 0xCD 0x30 0xC4
0x41 0x79 0xD4
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=1
vex amd64->IR:   VEX=0 VEX.L=0 VEX.n=0x1 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0

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

[konqueror] [Bug 449489] New: Cannot drag'n'drop files to the directory view on the sidebar

2022-02-02 Thread Leandro Nini
https://bugs.kde.org/show_bug.cgi?id=449489

Bug ID: 449489
   Summary: Cannot drag'n'drop files to the directory view on the
sidebar
   Product: konqueror
   Version: 21.08.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: sidebar
  Assignee: stefano.cro...@alice.it
  Reporter: drfiem...@email.it
  Target Milestone: ---

The drop action is disabled in the sidebar so it is not possible to move/copy
files from the main view to a directory shown in the dir view.

Using KDE frameworks 5.88 and release-service 21.08.3 compiled from vanilla
sources.

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

[KScreen] [Bug 426609] kscreen2 kicks monitor out of power save mode

2022-01-03 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=426609

Leandro  changed:

   What|Removed |Added

 CC||leandro...@gmail.com

--- Comment #12 from Leandro  ---
(In reply to pqwoerituytrueiwoq from comment #11)

Unfortulately my monitor MSI MAG272QR doesn't have the option to turn off input
polling, it may be hardcoded into the firmware, and the upstream bug is still
opened.
Do you have any other workaround?

SYSTEM INFO
Operating System: Gentoo Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.12-gentoo-clang-lto-prjc-cpufreq (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: Radeon RX Vega

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

2021-12-15 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=425271

--- Comment #34 from Leandro Lucarella  ---
(In reply to David Edmundson from comment #32)
> We have some logic in xembedsniproxy that says "if our hidden window is
> shown, send it to the back again".  Clearly someone else is putting our
> window back again. Possibly a new kwin change.
> 
> Can you confirm that openbox --replace silences the issue?
> Can you also enable any debug in kwin and see if that shows anything?

Ah, interesting. I'm using i3, so no kwin for me. I'll try i3 --replace when
this happens to see if it changes anything.

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

[knotes] [Bug 445220] New: After boot notes are shown in the taskbar even when "Show note in taskbar" option is disabled

2021-11-09 Thread Leandro Juan
https://bugs.kde.org/show_bug.cgi?id=445220

Bug ID: 445220
   Summary: After boot notes are shown in the taskbar even when
"Show note in taskbar" option is disabled
   Product: knotes
   Version: 5.17.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: nargaroth_...@hotmail.com
CC: myr...@kde.org
  Target Milestone: ---

SUMMARY
After boot notes are shown in the taskbar even when "Show note in taskbar"
option is disabled.

STEPS TO REPRODUCE
1. Create some notes.
2. In Knotes' settings disable option "Show note in taskbar".
3. Reboot the system.

OBSERVED RESULT
Notes are shown in the taskbar.

EXPECTED RESULT
Notes are not shown in the taskbar.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 35
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.22.5
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Doing Knotes -> "Hide all notes" and then "Show all notes" several times solves
the issue, but has to be done manually after every boot.

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

2021-10-31 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=425271

--- Comment #29 from Leandro Lucarella  ---
For me this happens consistently with BackInTime, usually when it runs after
resuming from suspend. When it is doing a backup and the notification area icon
is shown, xembedsniproxy uses ~65% CPU (and xorg 100%).

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

2021-10-07 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=425271

Leandro Lucarella  changed:

   What|Removed |Added

 CC||luca-...@llucax.com

--- Comment #22 from Leandro Lucarella  ---
I can confirm too.

Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-8-amd64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

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

[kgpg] [Bug 429016] New: Problem displaying icon in dark theme

2020-11-12 Thread Leandro Vital
https://bugs.kde.org/show_bug.cgi?id=429016

Bug ID: 429016
   Summary: Problem displaying icon in dark theme
   Product: kgpg
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: leavit...@gmail.com
  Target Milestone: ---

Created attachment 133260
  --> https://bugs.kde.org/attachment.cgi?id=133260=edit
Problem displaying icon in dark theme

SUMMARY
Problem displaying the icon in the dark theme, the standard icon has the same
color tint.

My suggestion is to have an icon with different colors to better adapt to
different theme colors

I opened a problem in gitlab:
https://invent.kde.org/utilities/kgpg/-/issues/1


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Rawhide (KDE Plasma Prerelease)

KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

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

[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen

2020-11-07 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=392798

Leandro Lucarella  changed:

   What|Removed |Added

 CC||luca-...@llucax.com

--- Comment #16 from Leandro Lucarella  ---
This is bugging me too often. Is very hard for me to see a reason why you
wouldn't want to allow suspending, and in any case I think leaving the option
to the user to allow reboot and power-off too (even if is burried in some
"Advanced" setting somewhere) would make a lot of sense.

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

[frameworks-baloo] [Bug 426195] New: Plasma session crash after returning from wayland session.

2020-09-04 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=426195

Bug ID: 426195
   Summary: Plasma session crash after returning from wayland
session.
   Product: frameworks-baloo
   Version: 5.68.0
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: stefan.bru...@rwth-aachen.de
  Reporter: empathd...@gmail.com
  Target Milestone: ---

Application: baloo_file (5.68.0)

Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.4.0-45-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Just initiate the normal plasma session after endind the wayland session.

- Unusual behavior I noticed:
It crashes and most of the time I cannot generate bactracing in plasma session.

- Custom settings of the application:
None change on baloo_file_extractor or db mechanisms was done.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=16, buf=0x7fff4058baa0, fd=3) at
../sysdeps/unix/sysv/linux/read.c:26
[Current thread is 1 (Thread 0x7f3c08325c80 (LWP 8464))]

Thread 3 (Thread 0x7f3c0727c700 (LWP 8573)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x7f3c0bbb9859 in __GI_abort () at abort.c:79
#8  0x7f3c0b23ba83 in mdb_assert_fail (env=0x55e2ad710600,
expr_txt=expr_txt@entry=0x7f3c0b23e02f "rc == 0",
func=func@entry=0x7f3c0b23e978 <__func__.7221> "mdb_page_dirty",
line=line@entry=2127, file=0x7f3c0b23e010 "mdb.c") at mdb.c:1542
#9  0x7f3c0b2306d5 in mdb_page_dirty (mp=,
txn=0x55e2ad7109f0) at mdb.c:2114
#10 mdb_page_dirty (txn=0x55e2ad7109f0, mp=) at mdb.c:2114
#11 0x7f3c0b231966 in mdb_page_alloc (num=num@entry=1,
mp=mp@entry=0x7f3c0727aee8, mc=) at mdb.c:2308
#12 0x7f3c0b231ba3 in mdb_page_touch (mc=mc@entry=0x7f3c0727b420) at
mdb.c:2495
#13 0x7f3c0b2337c7 in mdb_cursor_touch (mc=mc@entry=0x7f3c0727b420) at
mdb.c:6523
#14 0x7f3c0b2368f9 in mdb_cursor_put (mc=mc@entry=0x7f3c0727b420,
key=key@entry=0x7f3c0727b810, data=data@entry=0x7f3c0727b820,
flags=flags@entry=0) at mdb.c:6657
#15 0x7f3c0b23976b in mdb_put (txn=0x55e2ad7109f0, dbi=5,
key=key@entry=0x7f3c0727b810, data=data@entry=0x7f3c0727b820,
flags=flags@entry=0) at mdb.c:9022
#16 0x7f3c0c7124c5 in Baloo::DocumentDB::put
(this=this@entry=0x7f3c0727b960, docId=,
docId@entry=2704142263366, list=...) at ./src/engine/documentdb.cpp:79
#17 0x7f3c0c743da7 in Baloo::WriteTransaction::replaceDocument
(this=0x55e2ad7ea340, doc=..., operations=operations@entry=...) at
./src/engine/writetransaction.cpp:232
#18 0x7f3c0c736b16 in Baloo::Transaction::replaceDocument
(this=this@entry=0x7f3c0727bc10, doc=..., operations=operations@entry=...) at
./src/engine/transaction.cpp:295
#19 0x55e2ac5d6cbc in Baloo::UnindexedFileIndexer::run
(this=0x55e2ad79ca20) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:60
#20 0x7f3c0c177f82 in QThreadPoolThread::run (this=0x55e2ad717f20) at
thread/qthreadpool.cpp:99
#21 0x7f3c0c1749d2 in QThreadPrivate::start (arg=0x55e2ad717f20) at
thread/qthread_unix.cpp:361
#22 0x7f3c0b29d609 in start_thread (arg=) at
pthread_create.c:477
#23 0x7f3c0bcb6103 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3c07d8f700 (LWP 8472)):
#0  0x7f3c0bca996f in __GI___poll (fds=0x7f3c29e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3c0ab8b1ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3c0ab8b2e3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3c0c394583 in QEventDispatcherGlib::processEvents
(this=0x7f3c0b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f3c0c33b4db in QEventLoop::exec (this=this@entry=0x7f3c07d8ed70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7f3c0c173785 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7f3c0c76aefa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f3c0c1749d2 in QThreadPrivate::start (arg=0x7f3c0c7edd80) at
thread/qthread_unix.cpp:361
#8  0x7f3c0b29d609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f3c0bcb6103 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f3c08325c80 (LWP 8464)):
#0  __GI___libc_read (nbytes=16, buf=0x7fff4058baa0, fd=3) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=3, buf=0x7fff4058baa0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f3c0abd389f in ?? () 

[frameworks-baloo] [Bug 420615] Baloo chashed after logging in into account

2020-08-31 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=420615

Leandro  changed:

   What|Removed |Added

 CC||empathd...@gmail.com

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

[plasmashell] [Bug 421204] New: Plasma crashed when changing sddm welcome screen

2020-05-08 Thread Leandro Alvarez
https://bugs.kde.org/show_bug.cgi?id=421204

Bug ID: 421204
   Summary: Plasma crashed when changing sddm welcome screen
   Product: plasmashell
   Version: 5.18.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: leandral...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.18.4)

Qt Version: 5.14.1
Frameworks Version: 5.69.0
Operating System: Linux 5.6.8-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

Since I installed Tumbleweed i haven't been able to see the sddm welcome screen
image, I always see a black bottom image in the login screen. I checked that
sddm service was running (it wasn't so I turned it on) re logged in but still
no changes, so I tried changing the sddm welcome image to see if that made the
trick. Then I saw the error in the desktop taskbar.

- Custom settings of the application:
The setting I changed is the sddm welcome window. I tried switching from Elarun
to Breeze image.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5833131440 (LWP 5291))]

Thread 27 (Thread 0x7f57c9ffb700 (LWP 6155)):
#0  0x7f58348cf795 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f58354531db in QWaitConditionPrivate::wait (deadline=...,
this=0x5619bbf48d30) at thread/qwaitcondition_unix.cpp:146
#2  QWaitCondition::wait (this=, mutex=0x7f582c00d430,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#3  0x7f5835453299 in QWaitCondition::wait (this=0x5619bb52c458,
mutex=0x7f582c00d430, time=) at
../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68
#4  0x7f58067d76b0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f58067d7a1a in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f58067cfcce in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f58067d7a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f58067cfcce in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f58067d7a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f58067cfcce in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f58067d7a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f58067cfcce in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f58067d7a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f58067cfcce in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7f58067d7a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7f58067cfcce in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7f58067d709b in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7f583544d698 in QThreadPrivate::start (arg=0x7f57b80034e0) at
thread/qthread_unix.cpp:342
#19 0x7f58348c8efa in start_thread () from /lib64/libpthread.so.0
#20 0x7f58350db3bf in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f57ca7fc700 (LWP 6154)):
#0  0x7f58348cf795 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f58354531db in QWaitConditionPrivate::wait (deadline=...,
this=0x5619bbf48d30) at thread/qwaitcondition_unix.cpp:146
#2  QWaitCondition::wait (this=, mutex=0x7f582c00d430,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#3  0x7f5835453299 in QWaitCondition::wait (this=0x5619bb52c458,
mutex=0x7f582c00d430, time=) at
../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68
#4  0x7f58067d76b0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f58067d7a1a in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f58067cfcce in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f58067d7a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f58067cfcce in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f58067d7a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f58067cfcce in

[systemsettings] [Bug 414361] New: Failure access Plasma Style and Application Style on System Settings menu

2019-11-21 Thread Leandro Arruda
https://bugs.kde.org/show_bug.cgi?id=414361

Bug ID: 414361
   Summary: Failure access Plasma Style and Application Style on
System Settings menu
   Product: systemsettings
   Version: 5.17.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: leandroarruda1...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.17.3)

Qt Version: 5.13.1
Frameworks Version: 5.64.0
Operating System: Linux 5.3.11-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
At access this main menus or change between the internally options of them, the
screen of setting options crashes and closes immediately.

KDE Plasma Version: 5.17.3
KDE Framework Version: 5.64.0
Qt Version: 5.13.1
Kernel Version: 5.3.11-1
Video Driver: Generic - MESA
OS Type: 64-bit
Arch: x86-64

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb694b06800 (LWP 37897))]

Thread 6 (Thread 0x7fb67f5a7700 (LWP 37920)):
#0  0x7fb6973bdbdf in poll () from /lib64/libc.so.6
#1  0x7fb69559a27e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fb69559a39f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fb69795d98b in QEventDispatcherGlib::processEvents
(this=0x7fb67436d370, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb6979060cb in QEventLoop::exec (this=this@entry=0x7fb67f5a6d80,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7fb69773e021 in QThread::exec (this=this@entry=0x560d27b88c00) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7fb696a383b5 in QQmlThreadPrivate::run (this=0x560d27b88c00) at
/usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/qml/ftw/qqmlthread.cpp:152
#7  0x7fb69773f1a2 in QThreadPrivate::start (arg=0x560d27b88c00) at
thread/qthread_unix.cpp:360
#8  0x7fb695f78f2a in start_thread () from /lib64/libpthread.so.0
#9  0x7fb6973c84af in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fb68a388700 (LWP 37901)):
#0  0x7fb695f7f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fb68b786315 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7fb68b769697 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7fb695f78f2a in start_thread () from /lib64/libpthread.so.0
#4  0x7fb6973c84af in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fb68ab89700 (LWP 37900)):
#0  0x7fb695f7f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fb68b786315 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7fb68b769697 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7fb695f78f2a in start_thread () from /lib64/libpthread.so.0
#4  0x7fb6973c84af in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fb691b04700 (LWP 37899)):
#0  0x7fb6973bdbdf in poll () from /lib64/libc.so.6
#1  0x7fb69559a27e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fb69559a39f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fb69795d98b in QEventDispatcherGlib::processEvents
(this=0x7fb684000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb6979060cb in QEventLoop::exec (this=this@entry=0x7fb691b03d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7fb69773e021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7fb697be64f6 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7fb69773f1a2 in QThreadPrivate::start (arg=0x7fb697c68d80) at
thread/qthread_unix.cpp:360
#8  0x7fb695f78f2a in start_thread () from /lib64/libpthread.so.0
#9  0x7fb6973c84af in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb692a33700 (LWP 37898)):
#0  0x7fb6973bdbdf in poll () from /lib64/libc.so.6
#1  0x7fb695f48742 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fb695f493fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fb692c4af90 in QXcbEventQueue::run (this=0x560d27aa32b0) at
qxcbeventqueue.cpp:228
#4  0x7fb69773f1a2 in QThreadPrivate::start (arg=0x560d27aa32b0) at
thread/qthread_unix.cpp:360
#5  0x7fb695f78f2a in start_thread () from /lib64/libpthread.so.0
#6  0x7fb6973c84af in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fb694b06800 (LWP 37897)):
[KCrash Handler]
#6  0x0065 in ?? ()
#7  0x7fb697938611 in QObject::property (this=0x560d280ef380,
name=name@entry=0x7fb67e997264 "gridUnit") at kernel/qobject.cpp:3974
#8  0x7fb67e9781e0 in 

[systemsettings] [Bug 413948] New: System's Preferences close

2019-11-08 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=413948

Bug ID: 413948
   Summary: System's Preferences close
   Product: systemsettings
   Version: 5.17.2
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: leandrovallejospu...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.17.2)

Qt Version: 5.13.1
Frameworks Version: 5.63.0
Operating System: Linux 5.0.0-32-generic x86_64
Distribution: KDE neon User Edition 5.17

-- Information about the crash:
- What I was doing when the application crashed:

I just opened the System's Preferences, and then when I select any option from
the main menu of the system settings, the window closes.

The crash can be reproduced every time.

-- Backtrace:
Application: Preferencias del sistema (systemsettings5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc07de66800 (LWP 24167))]

Thread 6 (Thread 0x7fc051d0f700 (LWP 24175)):
#0  0x7fc0793a3bf9 in __GI___poll (fds=0x7fc0480020a0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc0728175c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc0728176dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc079cf69db in QEventDispatcherGlib::processEvents
(this=0x7fc048000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc079c96eaa in QEventLoop::exec (this=this@entry=0x7fc051d0ed80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7fc079ab23ca in QThread::exec (this=) at
thread/qthread.cpp:531
#6  0x7fc077855cb5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fc079ab3b72 in QThreadPrivate::start (arg=0x55bfde3c15f0) at
thread/qthread_unix.cpp:360
#8  0x7fc074bd66db in start_thread (arg=0x7fc051d0f700) at
pthread_create.c:463
#9  0x7fc0793b088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fc05271e700 (LWP 24174)):
#0  0x7fc0793a3bf9 in __GI___poll (fds=0x55bfde3ab500, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc0728175c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc072817962 in g_main_loop_run () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc053adb0e6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7fc07283f195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc074bd66db in start_thread (arg=0x7fc05271e700) at
pthread_create.c:463
#6  0x7fc0793b088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fc052f1f700 (LWP 24173)):
#0  0x7fc0793a3bf9 in __GI___poll (fds=0x55bfde37f0b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc0728175c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc0728176dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc072817721 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc07283f195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc074bd66db in start_thread (arg=0x7fc052f1f700) at
pthread_create.c:463
#6  0x7fc0793b088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fc05e19f700 (LWP 24170)):
#0  0x7fc07285d649 in g_mutex_lock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc0728175af in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc0728176dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc079cf69db in QEventDispatcherGlib::processEvents
(this=0x7fc058000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc079c96eaa in QEventLoop::exec (this=this@entry=0x7fc05e19ed70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7fc079ab23ca in QThread::exec (this=) at
thread/qthread.cpp:531
#6  0x7fc07a16d0e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fc079ab3b72 in QThreadPrivate::start (arg=0x7fc07a3e4d80) at
thread/qthread_unix.cpp:360
#8  0x7fc074bd66db in start_thread (arg=0x7fc05e19f700) at
pthread_create.c:463
#9  0x7fc0793b088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fc06a359700 (LWP 24169)):
#0  0x7fc0793a3bf9 in __GI___poll (fds=0x7fc06a358ca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc07479a747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fc07479c36a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fc06d13ef00 in QXcbEventQueue::run (this=0x55bfddd4a8e0) at
qxcbeventqueue.cpp:228
#4  0x7fc079ab3b72 in 

[kde] [Bug 412864] Latte dock crashed when changing layout

2019-10-17 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=412864

--- Comment #2 from Leandro  ---
Created attachment 123277
  --> https://bugs.kde.org/attachment.cgi?id=123277=edit
New crash information added by DrKonqi

latte-dock (0.9.3) using Qt 5.13.1

- What I was doing when the application crashed:
I changed the layout to unity, then I configured it a little. After playing
around with the layout I switched back to default and the crash ocurred. 
Every time I try to switch to default latte crashes.

-- Backtrace (Reduced):
#5  0x55acadb617f6 in Latte::Corona::availableScreenRectWithCriteria(int,
QList, QList) const ()
#6  0x55acadc44a83 in
Latte::WindowSystem::Tracker::Windows::updateAvailableScreenGeometries() ()
[...]
#9  0x55acadb4ee63 in
Latte::Corona::availableScreenRectChangedFrom(Latte::View*) ()
[...]
#11 0x55acadb59b8b in
Latte::ViewPart::Effects::qt_metacall(QMetaObject::Call, int, void**) ()
#12 0x7f5b95ba1346 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData
const&, QVariant const&, QQmlContextData*, QFlags)
() at /usr/lib/libQt5Qml.so.5

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

[kde] [Bug 412864] Latte dock crashed when changing layout

2019-10-17 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=412864

Leandro  changed:

   What|Removed |Added

 CC||leandro.ff...@gmail.com

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

[kdepim] [Bug 413078] Can't change name of akonadi EWS resource (sort of)

2019-10-17 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=413078

--- Comment #1 from Leandro Lucarella  ---
Created attachment 123267
  --> https://bugs.kde.org/attachment.cgi?id=123267=edit
KMail folder view

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

[kdepim] [Bug 413078] Can't change name of akonadi EWS resource (sort of)

2019-10-17 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=413078

--- Comment #3 from Leandro Lucarella  ---
Created attachment 123269
  --> https://bugs.kde.org/attachment.cgi?id=123269=edit
KMail akonadi console

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

[kdepim] [Bug 413078] Can't change name of akonadi EWS resource (sort of)

2019-10-17 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=413078

--- Comment #2 from Leandro Lucarella  ---
Created attachment 123268
  --> https://bugs.kde.org/attachment.cgi?id=123268=edit
KMail accounts view

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

[kdepim] [Bug 413078] New: Can't change name of akonadi EWS resource (sort of)

2019-10-17 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=413078

Bug ID: 413078
   Summary: Can't change name of akonadi EWS resource (sort of)
   Product: kdepim
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: leandro.lucare...@quoscient.io
  Target Milestone: ---

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

SUMMARY

When adding an akonadi EWS resource, I change the name of the account to
something more meaningful than akonadi_ews_resource_1, but even when in Akonadi
Console and KMail settings is shown as expected, in the tree views of KMail,
Kontact and KOrganizer it still shows the akonadi_ews_resource_1 name.

STEPS TO REPRODUCE
1. Create a new EWS resource/account
2. Rename it to other than the generated default name
3. Open KMail/Korganizer/Kontact

OBSERVED RESULT

The generated default name is used as the account name/root folder.

EXPECTED RESULT

The chosen name is used as the account name/root folder.


SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.62.0
Kernel Version: 5.2.0-3-amd64
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz
Memory: 23.1 GiB of RAM

ADDITIONAL INFORMATION

kdepim-runtime 4:18.08.3-4

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

[kmail2] [Bug 412830] New: The key sequence 'U' is ambiguous

2019-10-10 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=412830

Bug ID: 412830
   Summary: The key sequence 'U' is ambiguous
   Product: kmail2
   Version: 5.9.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: luca-...@llucax.com
  Target Milestone: ---

SUMMARY

Out of the blue, without touching anyting (although it might have been after
some upgrade of some KDE component, not KMail), I started to get this message
when trying to use the 'U' shortcut to mark messages as unread:
The key sequence 'U' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.

I looked in the shortcuts configuration and there is nothing else bound to `U`,
not even in the global KDE shortcuts defined in the KDE Settings.

STEPS TO REPRODUCE
1. Open KMail
2. Select an e-mail
3. Press the "U" letter in the keyboard

OBSERVED RESULT
A dialog with this message is shown:
The key sequence 'U' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.

EXPECTED RESULT
The message is marked as unread.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian unstable, kde version 5:104 (from the debian package)
KDE Plasma Version: 5.14.5.1 (?). Is the version of the plasma-desktop package
KDE Frameworks Version: ?
Qt Version: ?

ADDITIONAL INFORMATION

If I remove the binding for 'U' from the shortcuts config and then press 'U',
there is no visible effect.

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-07-30 Thread Leandro Ramos
https://bugs.kde.org/show_bug.cgi?id=404990

Leandro Ramos  changed:

   What|Removed |Added

 CC||leandroe...@gmail.com

--- Comment #23 from Leandro Ramos  ---
Same issue here: Fedora Rawhide 31 - KMail 5.11.3
And here: Debian Buster - KMail 4.18

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

[krunner] [Bug 410126] New: Memory Leak when searching

2019-07-22 Thread Leandro Santucci
https://bugs.kde.org/show_bug.cgi?id=410126

Bug ID: 410126
   Summary: Memory Leak when searching
   Product: krunner
   Version: 5.16.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: santucci.sim...@gmail.com
  Target Milestone: ---

When i'm searching anything through the application and after stop, process
"/usr/bin/krunner" have too much memory usage...  

STEPS TO REPRODUCE
1. Search anything using krunner (1m+)
2. Stop
3. See memory usage of the application

I searched for 1 minute and process got more then 1Gb...


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.

[latte-dock] [Bug 395851] Right button is not working

2018-07-16 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=395851

--- Comment #5 from Leandro  ---
thank you very much...

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

[yakuake] [Bug 396023] New: Yakuake crashes on random text selection

2018-06-30 Thread Leandro Santiago da Silva
https://bugs.kde.org/show_bug.cgi?id=396023

Bug ID: 396023
   Summary: Yakuake crashes on random text selection
   Product: yakuake
   Version: 3.0.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: leandrosansi...@gmail.com
  Target Milestone: ---

Application: yakuake (3.0.5)

Qt Version: 5.11.1
Frameworks Version: 5.47.0
Operating System: Linux 4.14.51-1-lts x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

I have the habit to quicly select and unselecy text while reading them on my
laptop using the touchpad, and while I was doing it, yakuake crashed. I believe
I selected some text and unintentionally dragged it, and then yakuake crashed.

- Custom settings of the application:
I am using kwin_wayland.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3973f6f800 (LWP 906))]

Thread 3 (Thread 0x7f3953650700 (LWP 960)):
#0  0x7f396a4c2ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f395442c124 in  () at /usr/lib/dri/i965_dri.so
#2  0x7f395442be18 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f396a4bd075 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f396e4be53f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f395e926700 (LWP 935)):
#0  0x7f396e4b3ea9 in poll () at /usr/lib/libc.so.6
#1  0x7f39686a2523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f39686a263e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f396edd0054 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f396ed7b94c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f396ebc4a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f39709e5976 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f396ebceb45 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f396a4bd075 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f396e4be53f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f3973f6f800 (LWP 906)):
[KCrash Handler]
#6  0x7f396eda1e20 in QMimeData::text() const () at
/usr/lib/libQt5Core.so.5
#7  0x7f39527ad6ea in Konsole::TerminalDisplay::doDrag() () at
/usr/lib/libkonsoleprivate.so.18
#8  0x7f39527ae25b in
Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) () at
/usr/lib/libkonsoleprivate.so.18
#9  0x7f396fb302b8 in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#10 0x7f39527b5034 in Konsole::TerminalDisplay::event(QEvent*) () at
/usr/lib/libkonsoleprivate.so.18
#11 0x7f396faf0a74 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#12 0x7f396faf858a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#13 0x7f396ed7ccb9 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#14 0x7f396faf7871 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib/libQt5Widgets.so.5
#15 0x7f396fb4b5ec in  () at /usr/lib/libQt5Widgets.so.5
#16 0x7f396fb4e235 in  () at /usr/lib/libQt5Widgets.so.5
#17 0x7f396faf0a74 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#18 0x7f396faf8341 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#19 0x7f396ed7ccb9 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#20 0x7f396f322e34 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /usr/lib/libQt5Gui.so.5
#21 0x7f396f324df6 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /usr/lib/libQt5Gui.so.5
#22 0x7f396f2feb7c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#23 0x7f39620bd57d in  () at /usr/lib/libQt5WaylandClient.so.5
#24 0x7f396ed7b94c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#25 0x7f396ed83c46 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#26 0x55616091ac92 in  ()
#27 0x7f396e3e906b in __libc_start_main () at /usr/lib/libc.so.6
#28 0x55616091ad2a in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 395666.

Possible duplicates by query: bug 395666.

Reported using DrKonqi

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

[latte-dock] [Bug 395851] Right button is not working

2018-06-27 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=395851

--- Comment #2 from Leandro  ---
(In reply to Michail Vourlakos from comment #1)
> Are you building Latte yourself?

No, only user.

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

[latte-dock] [Bug 395851] New: Right button is not working

2018-06-25 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=395851

Bug ID: 395851
   Summary: Right button is not working
   Product: latte-dock
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: leandrinh...@gmail.com
  Target Milestone: ---

Hi, after update day 06/22/2018, the right button is not working, now I use KDE
5.12 and 4.15.0-23-generic on Dell vostro 5740 - 8gb ram - 128gb HD.

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

[yakuake] [Bug 395666] yakuake crashes on multiple touches on the touchscreen

2018-06-20 Thread Leandro Santiago da Silva
https://bugs.kde.org/show_bug.cgi?id=395666

--- Comment #1 from Leandro Santiago da Silva  ---
I mean, "whose screen supports up to 10 simultaneous touches" :-)

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

[yakuake] [Bug 395666] New: yakuake crashes on multiple touches on the touchscreen

2018-06-20 Thread Leandro Santiago da Silva
https://bugs.kde.org/show_bug.cgi?id=395666

Bug ID: 395666
   Summary: yakuake crashes on multiple touches on the touchscreen
   Product: yakuake
   Version: 3.0.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: leandrosansi...@gmail.com
  Target Milestone: ---

Application: yakuake (3.0.5)

Qt Version: 5.11.0
Frameworks Version: 5.47.0
Operating System: Linux 4.14.49-1-lts x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

I have a dell laptop which supports up to 10 touches. I am using kwin_wayland
and and tried touching with several (maybe 8) fingers when yakuake is in full
screen.

- Unusual behavior I noticed:
yakuake crashed

- Custom settings of the application:
kwin_wayland, yakuake in fullscreen

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f02bdb2d800 (LWP 14727))]

Thread 3 (Thread 0x7f029d22f700 (LWP 14730)):
#0  0x7f02b4085ffc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f029e00b0a4 in ?? () from /usr/lib/dri/i965_dri.so
#2  0x7f029e00ad98 in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7f02b4080075 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f02b808153f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f02a84ec700 (LWP 14728)):
#0  0x7f02b8072934 in read () from /usr/lib/libc.so.6
#1  0x7f02b22aaed1 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f02b2264ff8 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7f02b22654c6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7f02b226563e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7f02b8992e64 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#6  0x7f02b893e85c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#7  0x7f02b8787ac9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x7f02ba5a3976 in ?? () from /usr/lib/libQt5DBus.so.5
#9  0x7f02b8791b95 in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7f02b4080075 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7f02b808153f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f02bdb2d800 (LWP 14727)):
[KCrash Handler]
#6  0x7f02b8964d30 in QMimeData::text() const () from
/usr/lib/libQt5Core.so.5
#7  0x7f029c38c6ea in Konsole::TerminalDisplay::doDrag() () from
/usr/lib/libkonsoleprivate.so.18
#8  0x7f029c38d25b in
Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) () from
/usr/lib/libkonsoleprivate.so.18
#9  0x7f02b96ef058 in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#10 0x7f029c394034 in Konsole::TerminalDisplay::event(QEvent*) () from
/usr/lib/libkonsoleprivate.so.18
#11 0x7f02b96af984 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#12 0x7f02b96b746a in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#13 0x7f02b893fbc9 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#14 0x7f02b96b6781 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/usr/lib/libQt5Widgets.so.5
#15 0x7f02b970a38c in ?? () from /usr/lib/libQt5Widgets.so.5
#16 0x7f02b970cfd5 in ?? () from /usr/lib/libQt5Widgets.so.5
#17 0x7f02b96af984 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#18 0x7f02b96b725b in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#19 0x7f02b893fbc9 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#20 0x7f02b8ee7596 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /usr/lib/libQt5Gui.so.5
#21 0x7f02b8ee67f8 in
QGuiApplicationPrivate::processTouchEvent(QWindowSystemInterfacePrivate::TouchEvent*)
() from /usr/lib/libQt5Gui.so.5
#22 0x7f02b8ee94e6 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/libQt5Gui.so.5
#23 0x7f02b8ec0a5c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/libQt5Gui.so.5
#24 0x7f02abc80f7d in ?? () from /usr/lib/libQt5WaylandClient.so.5
#25 0x7f02b893e85c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#26 0x7f02b8946b56 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#27 0x5654f1d02c92 in ?? ()
#28 0x7f02b7fac06b in __libc_start_main () from 

[kwin] [Bug 394927] New: KWin crashes when, during 'expose' mode, I try to filter the windows by using a composite key combination

2018-06-01 Thread Leandro Santiago da Silva
https://bugs.kde.org/show_bug.cgi?id=394927

Bug ID: 394927
   Summary: KWin crashes when, during 'expose' mode, I try to
filter the windows by using a composite key
combination
   Product: kwin
   Version: 5.12.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: leandrosansi...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.12.5)

Qt Version: 5.11.0
Frameworks Version: 5.46.0
Operating System: Linux 4.14.41-1-lts x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

enabled 'expose', typed the keys ` and then a, in a pt_BR (abnt2) keyboard,
expecting to filter windows with the letter 'à' in the name.

- Unusual behavior I noticed:

KWin crashed and restarted.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0606c53840 (LWP 806))]

Thread 7 (Thread 0x7f05d3dd1700 (LWP 4304)):
#0  0x7f06065ecfa6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f06039f7d1b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f06039f920b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f06039a785c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f06037f0ac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f05fe0a6559 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f06037fab95 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f06065f753f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f05e4f70700 (LWP 1488)):
#0  0x7f06039f908e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#1  0x7f06039a785c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#2  0x7f06037f0ac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#3  0x7f05fe0a6559 in  () at /usr/lib/libQt5Qml.so.5
#4  0x7f06037fab95 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f06065f753f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f05d35d0700 (LWP 916)):
#0  0x7f05ff660ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0602920bbc in  () at /usr/lib/libQt5Script.so.5
#2  0x7f0602920bd9 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f06065f753f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f05d700 (LWP 895)):
#0  0x7f06065ecfa6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f06039f7d1b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f06039f920b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f06039a785c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f06037f0ac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f05fe0a6559 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f06037fab95 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f06065f753f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f05e67e7700 (LWP 868)):
#0  0x7f06037ed74c in QMutex::lock() () at /usr/lib/libQt5Core.so.5
#1  0x7f06039f908e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#2  0x7f06039a785c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#3  0x7f06037f0ac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#4  0x7f05fcf9d976 in  () at /usr/lib/libQt5DBus.so.5
#5  0x7f06037fab95 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f06065f753f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f05ecd67700 (LWP 846)):
#0  0x7f06065ecea9 in poll () at /usr/lib/libc.so.6
#1  0x7f0605516180 in  () at /usr/lib/libxcb.so.1
#2  0x7f0605517e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f05ede55f1a in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f06037fab95 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f06065f753f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f0606c53840 (LWP 806)):
[KCrash Handler]
#6  0x7f06039a8ac4 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#7  0x7f05e6c8171d in  () at

[kmail2] [Bug 392203] Managesieve doesn't work over pure TLS connection

2018-03-23 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=392203

Leandro Lucarella <luca-...@llucax.com> changed:

   What|Removed |Added

Summary|Managesieve doesn't work|Managesieve doesn't work
   |over pure TLS connectino|over pure TLS connection

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

[kmail2] [Bug 392203] New: Managesieve doesn't work over pure TLS connectino

2018-03-22 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=392203

Bug ID: 392203
   Summary: Managesieve doesn't work over pure TLS connectino
   Product: kmail2
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: sieve
  Assignee: kdepim-b...@kde.org
  Reporter: luca-...@llucax.com
  Target Milestone: ---

I couldn't find any way to configure manangesieve over a pure TLS connection
(no plain connection + STARTTLS command). There should be a way to configure
which type of encrypted channel to use with managesieve. Even when there is no
standard port for "sieves", users should be able to configure on it on any
custom port.

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

[systemsettings] [Bug 391843] New: Erro após clicar em temas do espaço de trabalho

2018-03-13 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=391843

Bug ID: 391843
   Summary: Erro após clicar em temas do espaço de trabalho
   Product: systemsettings
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: leanmendo...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.13.0-36-generic x86_64
Distribution: Ubuntu 16.04.4 LTS

-- Information about the crash:
Após aberto a configuração do sistema, clicou-se no icone temas do espaço de
trabalho o qual mostrou um erro inesperado do sistema. Foram feitas várias
tentativas sempre apresentando o mesmo comportamento anormal.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Configurações do Sistema (systemsettings5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8c76bee900 (LWP 23047))]

Thread 3 (Thread 0x7f8c559ea700 (LWP 23050)):
#0  0x7f8c7330074d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8c7025038c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8c7025049c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8c73c2d7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f8c73bd4b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8c739f1834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f8c7236f3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f8c739f67be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f8c707716ba in start_thread (arg=0x7f8c559ea700) at
pthread_create.c:333
#9  0x7f8c7330c41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f8c6472c700 (LWP 23048)):
#0  0x7f8c7330074d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8c70fe7c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f8c70fe98d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f8c670b0889 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f8c739f67be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8c707716ba in start_thread (arg=0x7f8c6472c700) at
pthread_create.c:333
#6  0x7f8c7330c41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f8c76bee900 (LWP 23047)):
[KCrash Handler]
#6  0x7f8c7323a428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f8c7323c02a in __GI_abort () at abort.c:89
#8  0x7f8c739e3f81 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f8c72627af1 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7f8c72630332 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7f8c72630733 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7f8c74b022b5 in QWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x7f8c72663871 in QQuickWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x7f8c750aa05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f8c750af516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7f8c73bd738b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f8c74afa4ac in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x7f8c74afb21d in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x7f8c74adef08 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#20 0x7f8c670e2200 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x7f8c70250197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f8c702503f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f8c7025049c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f8c73c2d7cf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f8c73bd4b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f8c73bdcbec in 

[systemsettings] [Bug 391842] New: Fechamento Inesperado Configuração do Sistema

2018-03-13 Thread Leandro
https://bugs.kde.org/show_bug.cgi?id=391842

Bug ID: 391842
   Summary: Fechamento Inesperado Configuração do Sistema
   Product: systemsettings
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: leanmendo...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.13.0-36-generic x86_64
Distribution: Ubuntu 16.04.4 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Após atualização do driver de video, foi tentado abrir a configuração do
sistema o qual fechou inesperadamente após ter sido chamado através do menu de
inicialização do kde a esquerda do painel inferior.

-- Backtrace:
Application: Configurações do Sistema (systemsettings5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbb9ddba900 (LWP 18004))]

Thread 3 (Thread 0x7fbb7c951700 (LWP 18007)):
#0  0x7fbb9a4cc74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbb9741c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbb9741c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbb9adf97eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fbb9ada0b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fbb9abbd834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fbb9953b3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fbb9abc27be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fbb9793d6ba in start_thread (arg=0x7fbb7c951700) at
pthread_create.c:333
#9  0x7fbb9a4d841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fbb8b8f8700 (LWP 18005)):
#0  0x7fbb9a4cc74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbb981b3c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fbb981b58d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fbb8e27c889 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fbb9abc27be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fbb9793d6ba in start_thread (arg=0x7fbb8b8f8700) at
pthread_create.c:333
#6  0x7fbb9a4d841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fbb9ddba900 (LWP 18004)):
[KCrash Handler]
#6  0x7fbb9a406428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fbb9a40802a in __GI_abort () at abort.c:89
#8  0x7fbb9abaff81 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fbb997f3af1 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7fbb997fc332 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7fbb997fc733 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7fbb9bcce2b5 in QWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x7fbb9982f871 in QQuickWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x7fbb9c27605c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7fbb9c27b516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fbb9ada338b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fbb9bcc64ac in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x7fbb9bcc721d in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x7fbb9bcaaf08 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#20 0x7fbb8e2ae200 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x7fbb9741c197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fbb9741c3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fbb9741c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fbb9adf97cf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7fbb9ada0b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7fbb9ada8bec in 

[kmail2] [Bug 391806] New: Sieve doesn't error on bad managesieve host

2018-03-13 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=391806

Bug ID: 391806
   Summary: Sieve doesn't error on bad managesieve host
   Product: kmail2
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: sieve
  Assignee: kdepim-b...@kde.org
  Reporter: luca-...@llucax.com
  Target Milestone: ---

If the configured managesieve host doesn't exist, there is no error reported to
the user. When going to Settings -> Manage Sieve Scripts, the progress circle
will just go on and on without reporting any errors. A simple typo in the host
name is very hard to pin point because of this!

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

[kio] [Bug 73547] sieve will not allow you to retry logging in on a bad password.

2018-03-13 Thread Leandro Lucarella
https://bugs.kde.org/show_bug.cgi?id=73547

Leandro Lucarella <luca-...@llucax.com> changed:

   What|Removed |Added

 CC||luca-...@llucax.com

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

[neon] [Bug 381183] latest libzip4 package breaks applications

2017-06-14 Thread Leandro Martins de Sá
https://bugs.kde.org/show_bug.cgi?id=381183

Leandro Martins de Sá <leandrosa.e...@gmail.com> changed:

   What|Removed |Added

 CC||leandrosa.e...@gmail.com

--- Comment #1 from Leandro Martins de Sá <leandrosa.e...@gmail.com> ---
Problem happened here too.
Thanks, this solved my problem with the workbench.

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

[kdevelop] [Bug 364816] New: KDevelop crashes on saving file on vim mode

2016-06-27 Thread Leandro Santiago da Silva via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364816

Bug ID: 364816
   Summary: KDevelop crashes on saving file on vim mode
   Product: kdevelop
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: leandrosansi...@gmail.com

Application: kdevelop (4.90.92)

Qt Version: 5.5.1
Frameworks Version: 5.22.0
Operating System: Linux 4.6.0-040600-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I just typed ESC, :x, and KDevelop suddenly crashed.

>From lastest ktexeditor, kdevplatform and kdevelop master branch.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5f947ab900 (LWP 3154))]

Thread 13 (Thread 0x7f5f41fa7700 (LWP 4848)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5fa5e51bd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f5fa5e51c19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f5faa2636fa in start_thread (arg=0x7f5f41fa7700) at
pthread_create.c:333
#4  0x7f5fb0e70b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f5f5dffb700 (LWP 4830)):
#0  __syscall_clock_gettime () at ../sysdeps/unix/syscall-template.S:66
#1  0x7f5fb0e7efb6 in __GI___clock_gettime (clock_id=1, tp=0x7f5f5dffaa10)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f5fb160ac16 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f5fb178f529 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5fb178fa95 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5fb1790e7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5fa93cd92d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f5fa93ce2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f5fa93ce4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f5fb1791a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f5fb1738dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f5fb15558a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f5fae63d3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f5fb155a84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f5faa2636fa in start_thread (arg=0x7f5f5dffb700) at
pthread_create.c:333
#15 0x7f5fb0e70b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f5f5effd700 (LWP 3297)):
#0  0x7f5fb0e64e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5fa93ce39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5fa93ce4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5fb1791a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5fb1738dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5fb15558a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5fb155a84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5faa2636fa in start_thread (arg=0x7f5f5effd700) at
pthread_create.c:333
#8  0x7f5fb0e70b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f5f5e7fc700 (LWP 3251)):
#0  __syscall_clock_gettime () at ../sysdeps/unix/syscall-template.S:66
#1  0x7f5fb0e7efb6 in __GI___clock_gettime (clock_id=1, tp=0x7f5f5e7fba30)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f5fb160ac16 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f5fb178f529 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5fb178fa95 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5fb1790e7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5fa93cd92d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f5fa93ce2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f5fa93ce4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f5fb1791a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f5fb1738dea in
QEventLoop::exec(QFlags) () from