[ark] [Bug 358304] Ark do not open ISO files properly.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358304

--- Comment #4 from cameron...@poczta.fm ---
When I mount them in the console (mount iso where) it does it correctly and I
can see and copy what's inside the ISOs.

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

[Systemd KCM] [Bug 358308] New: Ability to start multiple services at once

[Alexander Potashev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358308

Bug ID: 358308
   Summary: Ability to start multiple services at once
   Product: Systemd KCM
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: rthoms...@gmail.com
  Reporter: aspotas...@gmail.com

Please implement ability to start multiple services at once. Currently I cannot
select multiple systemd units from the list, thus I cannot start or stop more
than one service at a time.

Reproducible: Always

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

[valgrind] [Bug 357338] disInstr(arm64): unhandled instruction 0x5E140020

[Tom Hughes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357338

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu
Summary|Unhandled instruction for   |disInstr(arm64): unhandled
   |SHA instructions libcrypto  |instruction 0x5E140020
   |Boring SSL  |

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Elvis Angelaccio via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358171

--- Comment #25 from Elvis Angelaccio  ---
(In reply to AJslye from comment #20)
>  I'll need to test some more, but today's update in Arch to plasma-framework
> 5.18.0-2 seems to have fixed this issue. I wonder what they patched or back
> ported?

You can see it here:
https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/plasma-framework=1b876fdcb66e690f466b413276fa468acdd6cf8b

It's a patch for another unrelated bug.

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

[kmail2] [Bug 352036] Regression: kMail 5.0.0 cannot open links contained in mails

[Gunter Ohrner via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352036

--- Comment #16 from Gunter Ohrner  ---
(In reply to Chris Samuel from comment #15)
> (In reply to Gunter Ohrner from comment #14)
> > Seems to work for me now at least with the following software stack:
> It's sort of better, but I wouldn't consider it fixed - what is opened is
> actually (for example using the link for this bug in the email that was
> triggered by your comment):
> 
> /home/chris/.cache/kioexec/krun/3830_0_show_bug.cgi
> 
> rather than the proper URL, consequently the page is not rendered correctly.

I'm currently not observing this.


> > I will reopen the bug if it re-appears - if any of you still see this with
> > the latest Frameworks and PIM releases, please notify me.
> I'm on the latest version from Kubuntu (via their backports PPA which was
> updated only a few days ago) which is:

I'm also using Kubuntu and currently am experimenting with the KDE Applications
Staging PPA:

https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/

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

[ark] [Bug 358304] Ark do not open ISO files properly.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358304

--- Comment #5 from cameron...@poczta.fm ---
I even tried to upgrade shared-mime-info to 1.5, but with no positive result.

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

[Akonadi] [Bug 355743] akonadiconsole shows now enties in the 'Browser' tab

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355743

--- Comment #2 from kram...@web.de ---
Same here, Arch Linux,
Akonadiconsole V. 0.99
Using:
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

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

[valgrind] [Bug 358213] helgrind/drd bar_bad testcase hangs with new glibc pthread barrier implementation

[Mark Wielaard via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358213

Mark Wielaard  changed:

   What|Removed |Added

  Attachment #96738|0   |1
is obsolete||

--- Comment #4 from Mark Wielaard  ---
Created attachment 96765
  --> https://bugs.kde.org/attachment.cgi?id=96765=edit
pthread_barrier-vs-newer-glibc-implementation-drd-helgrind

Simplest option to solve the drd issue is to do like in the helgrind case and
have two variants of the exp files. One of which will have
pthread_barrier_destroy hang, and so then drd will just not see that it wasn't
a barrier. Which isn't ideal, but since it is the last test in the batch it
seems it doesn't impact things too much.

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

[valgrind] [Bug 358213] helgrind/drd bar_bad testcase hangs with new glibc pthread barrier implementation

[Mark Wielaard via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358213

Mark Wielaard  changed:

   What|Removed |Added

Summary|helgrind bar_bad testcase   |helgrind/drd bar_bad
   |hangs with new glibc|testcase hangs with new
   |pthread barrier |glibc pthread barrier
   |implementation  |implementation

--- Comment #3 from Mark Wielaard  ---
The problem fixing this for drd is that DRD_(barrier_destroy) is called after
pthread_barrier_destroy. But that call might now hang and then bar_bad invokes
a watchdog to exit the program, so the post handler is never called.

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

[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=321190

--- Comment #82 from Martin Gräßlin  ---
Could we please stop on this bug report. It won't be added back. There won't be
new arguments, so please just let go.

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

[valgrind] [Bug 356393] valgrind (vex) crashes because isZeroU happened

[Florian Krohm via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356393

Florian Krohm  changed:

   What|Removed |Added

 CC||flor...@eich-krohm.de

--- Comment #4 from Florian Krohm  ---
(In reply to Darshit Shah from comment #0)
> vex: the `impossible' happened:
>isZeroU
> vex storage: T total 983714392 bytes allocated
> vex storage: P total 640 bytes allocated
> 
> valgrind: the 'impossible' happened:
>LibVEX called failure_exit().
> 
> host stacktrace:
> ==16723==at 0x38083FA8: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x380840C4: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x38084301: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x3808432A: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x3809F6C2: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x38148008: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x3815516D: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x38159292: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x38159EC6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x3815BDD8: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x3815CE26: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x38145E0C: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x380A1C4B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x380D295B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x380D45BF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> ==16723==by 0x380E3936: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
> 
> sched status:
>   running_tid=1
> 
> Thread 1: status = VgTs_Runnable (lwpid 16723)
> ==16723==at 0x5EA6F40: ecp_nistz256_avx2_select_w7 (in
> /usr/lib/libcrypto.so.1.0.0)
> ==16723==by 0x5E765CF: EC_POINT_mul (in /usr/lib/libcrypto.so.1.0.0)
> ==16723==by 0x5E75416: EC_POINT_new (in /usr/lib/libcrypto.so.1.0.0)
> ==16723==by 0x5E7EE89: EC_KEY_generate_key (in
> /usr/lib/libcrypto.so.1.0.0)
> ==16723==by 0x5B422A4: ssl3_send_client_key_exchange (in
> /usr/lib/libssl.so.1.0.0)
> ==16723==by 0x5B45F67: ssl3_connect (in /usr/lib/libssl.so.1.0.0)
> ==16723==by 0x5B50E9B: ssl23_connect (in /usr/lib/libssl.so.1.0.0)
> ==16723==by 0x452B2F: ssl_connect_with_timeout_callback (openssl.c:506)
> ==16723==by 0x44DDF3: run_with_timeout (utils.c:2046)
> ==16723==by 0x4529A9: ssl_connect_wget (openssl.c:559)
> ==16723==by 0x429A0F: establish_connection (http.c:2144)
> ==16723==by 0x425BAE: gethttp (http.c:3055)
> ==16723==by 0x4243C5: http_loop (http.c:3971)
> ==16723==by 0x43FE0E: retrieve_url (retr.c:817)
> ==16723==by 0x4365C2: main (main.c:1868)
> 
> Valgrind crashed with the following message when trying to test GNU Wget.
> The issue is triggered only by two specific tests that require Wget to
> connect to a proxy server over HTTPS. It does not happen during normal
> connections to HTTPS servers. Also, the issue occurs only when compiled with
> OpenSSL. With GnuTLS there are no problems.
> 
> P.S.: I'm using Valgrind 3.11 on Arch Linux. The version option is not
> available in the form. The issue seems to be a regression since it doesn't
> come up on an older version (3.7.0) during the CI builds on Travis.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. git clone http://git.savannah.gnu.org/r/wget.git
> 2. cd wget
> 3. ./bootstrap && ./configure --enable-valgrind-tests --with-ssl=openssl
> 4. make check
> 
> Actual Results:  
> The output present above

I just built wget according those instructions on my x86-64. With stock
valgrind 3.11.0 I do not get any errors:

Testsuite summary for wget 1.17.1.11-b305

# TOTAL: 85
# PASS:  71
# SKIP:  14
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

and

Testsuite summary for wget 1.17.1.11-b305

# TOTAL: 28
# PASS:  28
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

Perhaps it's one of those skipped tests that is failing:

SKIP: Test-ftp-iri.px
SKIP: Test-ftp-iri-fallback.px
SKIP: Test-ftp-iri-recursive.px
SKIP: Test-ftp-iri-disabled.px
SKIP: Test-idn-headers.px
SKIP: Test-idn-meta.px
SKIP: Test-idn-cmd.px
SKIP: Test-idn-cmd-utf8.px
SKIP: Test-idn-robots.px
SKIP: Test-idn-robots-utf8.px
SKIP: Test-iri.px
SKIP: Test-iri-percent.px
SKIP: Test-iri-forced-remote.px
SKIP: 

[krita] [Bug 358309] New: cant reset to default brushes

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358309

Bug ID: 358309
   Summary: cant reset to default brushes
   Product: krita
   Version: 2.9.10
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: atharvak...@gmail.com

By mistake i deleted the brush presets and there is no way to get it back.

Reproducible: Always

Steps to Reproduce:
1.Delete the brust presets
2.
3.



There should be an option int the settings to reset the brush settings

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[AJslye via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358171

--- Comment #26 from AJslye  ---
(In reply to Elvis Angelaccio from comment #25)
> (In reply to AJslye from comment #20)
> >  I'll need to test some more, but today's update in Arch to plasma-framework
> > 5.18.0-2 seems to have fixed this issue. I wonder what they patched or back
> > ported?
> 
> You can see it here:
> https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/
> plasma-framework=1b876fdcb66e690f466b413276fa468acdd6cf8b
> 
> It's a patch for another unrelated bug.

Yes, I see that now. The strange thing was I could log out and back in right
after the update without issue, it wasn't until I rebooted the laptop in the
morning that the issue reappeared.

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

[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=321190

--- Comment #83 from 1...@gmx-topmail.de ---
If only you could list reasonable grounds, the discussion would be over.

This is requested many times again and again, and you only say "it is mine and
I can do whatever I want".

It is sad that you fear viewpoints that differ from your opinion.

I'd really like to know why this is a red flag for you.

If middle click to close is so evil, then why it is possible to configure KDE
that way at other places? Nowadays it is usual default behavior to close
something by middle-clicking on it.

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

[kdevelop] [Bug 355685] Kdevelop C++ parser crash

[Kevin Funk via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355685

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||4.7.3

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

[Akonadi] [Bug 355743] akonadiconsole shows now enties in the 'Browser' tab

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355743

kram...@web.de changed:

   What|Removed |Added

 CC||kram...@web.de

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

[kmix] [Bug 358310] New: Crash on startup

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358310

Bug ID: 358310
   Summary: Crash on startup
   Product: kmix
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: lopez_more...@yahoo.com.br

Application: kmixctrl (4.6)

Qt Version: 5.5.1
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

Just starting the machine. kde environment has reported some crashes also.

The crash can be reproduced every time.

-- Backtrace:
Application: KMixCtrl (kmixctrl), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fabd6e5c840 (LWP 3069))]

Thread 2 (Thread 0x7fabc01cd700 (LWP 3095)):
#0  0x7fabd6782c1d in poll () at /lib64/libc.so.6
#1  0x7fabcbb5c422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fabcbb5e00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fabc252a3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fabd498b32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fabce8fc0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fabd678b04d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fabd6e5c840 (LWP 3069)):
[KCrash Handler]
#6  0x7fabce49f5b6 in  () at /usr/lib64/pulseaudio/libpulsecommon-7.0.so
#7  0x7fabce49ffc2 in pa_fdsem_before_poll () at
/usr/lib64/pulseaudio/libpulsecommon-7.0.so
#8  0x7fabce4b6697 in  () at /usr/lib64/pulseaudio/libpulsecommon-7.0.so
#9  0x7fabd5d241b4 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0
#10 0x7fabd5d2458a in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#11 0x7fabd6a6ef9f in  () at /usr/lib64/libkdeinit5_kmixctrl.so
#12 0x7fabd6a6f4b5 in  () at /usr/lib64/libkdeinit5_kmixctrl.so
#13 0x7fabd6a7e409 in  () at /usr/lib64/libkdeinit5_kmixctrl.so
#14 0x7fabd6a870b6 in  () at /usr/lib64/libkdeinit5_kmixctrl.so
#15 0x7fabd6a88398 in  () at /usr/lib64/libkdeinit5_kmixctrl.so
#16 0x7fabd6a8843d in  () at /usr/lib64/libkdeinit5_kmixctrl.so
#17 0x7fabd6a7900f in kdemain () at /usr/lib64/libkdeinit5_kmixctrl.so
#18 0x7fabd66c7b05 in __libc_start_main () at /lib64/libc.so.6
#19 0x004007ee in _start ()

Reported using DrKonqi

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

[kdevelop] [Bug 358311] New: broken highlighting

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358311

Bug ID: 358311
   Summary: broken highlighting
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@milianw.de

Sometimes the highlighting of files is severely broken as shown in the attached
screenshot.

This may be related to:

- missing translations of DUChain cursor/range locations
- improper revision locking
- delay between reading content from editor and actually parsing it

This may be triggered by:

- pasting content
- switching branches

In general, hard to reproduce, but when it hits you, you'll notice. F5 is the
only rescue in such situations.

Reproducible: Sometimes

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

[kate] [Bug 358307] New: Kate does not store configured SQL connection

[Andreas Blochberger via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358307

Bug ID: 358307
   Summary: Kate does not store configured SQL connection
   Product: kate
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: ablochber...@atoss-csd.de

Kate does not store any SQL connections. Event when a connection is created, it
does not show up on the drop down combo. It shows up in the "SQL" menu as radio
menu item

Version 15.12.1
KDE Frameworks 5.18.0
Qt 5.5.1 (kompiliert gegen 5.5.1)



Reproducible: Always

Steps to Reproduce:
Steps to reproduce:
1. Enable SQL module
2. Create a new SQL connection
3. New connection works (but there is no drop down combo anymore to select it)
4. Restart kate
-> Configured SQL connection is gone (looks like it was never saved

Actual Results:  
No SQL connection configured

Expected Results:  
Saved SQL connection

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

[valgrind] [Bug 357833] Valgrind is broken on recent linux kernel

[Mark Wielaard via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357833

Mark Wielaard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #8 from Mark Wielaard  ---
(In reply to Ivo Raisr from comment #7)
> Hi Mark, Thank you for providing the fix also for Solaris.
> It works ok on Solaris 12, regression tests passed.

Thanks for testing!

This has now been committed as valgrind svn r15766.

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

[kmail2] [Bug 352036] Regression: kMail 5.0.0 cannot open links contained in mails

[Chris Samuel via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352036

--- Comment #15 from Chris Samuel  ---
(In reply to Gunter Ohrner from comment #14)

> Seems to work for me now at least with the following software stack:

It's sort of better, but I wouldn't consider it fixed - what is opened is
actually (for example using the link for this bug in the email that was
triggered by your comment):

/home/chris/.cache/kioexec/krun/3830_0_show_bug.cgi

rather than the proper URL, consequently the page is not rendered correctly.

> I will reopen the bug if it re-appears - if any of you still see this with
> the latest Frameworks and PIM releases, please notify me.

I'm on the latest version from Kubuntu (via their backports PPA which was
updated only a few days ago) which is:

KMail 5.0.2
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

They don't appear to have KMail 5.0.3 yet, when was that released?

thanks!
Chris

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

[trojita] [Bug 358208] Remember last-used location for attachment storage and downloads

[Jan Kundrát via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358208

Jan Kundrát  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/troj
   ||ita/379fe2a8eb01eae06d77836
   ||de2689bc061fa729a

--- Comment #5 from Jan Kundrát  ---
Git commit 379fe2a8eb01eae06d77836de2689bc061fa729a by Jan Kundrát.
Committed on 21/01/2016 at 12:03.
Pushed by gerrit into branch 'master'.

GUI: remember last dir when adding attachments
Change-Id: Id54a718a77105ae4deffa31f87b3c0a98fa325f1

M  +3-1src/Gui/ComposeWidget.cpp

http://commits.kde.org/trojita/379fe2a8eb01eae06d77836de2689bc061fa729a

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

[kdevelop] [Bug 358311] broken highlighting

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358311

--- Comment #1 from Milian Wolff  ---
Created attachment 96766
  --> https://bugs.kde.org/attachment.cgi?id=96766=edit
broken highlighting

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

[kdevelop] [Bug 358311] broken highlighting

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358311

Milian Wolff  changed:

   What|Removed |Added

   Keywords||release_blocker
 Ever confirmed|0   |1
   Priority|NOR |VHI
   Target Milestone|--- |5.0.0
 Status|UNCONFIRMED |CONFIRMED

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Robbi3 via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358171

--- Comment #27 from Robbi3  ---
Same experience here, I thought it was fixed with latest update, after few
reboots, log- in issue still exists..

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

[ark] [Bug 358304] Ark do not open ISO files properly.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358304

--- Comment #3 from cameron...@poczta.fm ---
When I open those images with file-roller it shows them as empty, but they are
not !!

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

[valgrind] [Bug 356393] valgrind (vex) crashes because isZeroU happened

[Oleksii Serdiuk via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356393

Oleksii Serdiuk  changed:

   What|Removed |Added

 CC||conta...@oleksii.name

--- Comment #3 from Oleksii Serdiuk  ---
I'm getting the same crash on Kubuntu 15.10 with Vlagrind 3.11.0 while trying
to analyze the application that uses libcurl:

vex: the `impossible' happened:
   isZeroU
vex storage: T total 15579834320 bytes allocated
vex storage: P total 640 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().

host stacktrace:
==6282==at 0x38083F98: show_sched_status_wrk (m_libcassert.c:343)
==6282==by 0x380840B4: report_and_quit (m_libcassert.c:415)
==6282==by 0x380842F1: panic (m_libcassert.c:491)
==6282==by 0x380842F1: vgPlain_core_panic_at (m_libcassert.c:496)
==6282==by 0x3808431A: vgPlain_core_panic (m_libcassert.c:501)
==6282==by 0x3809F6B2: failure_exit (m_translate.c:740)
==6282==by 0x38148078: vpanic (main_util.c:231)
==6282==by 0x381551DD: isZeroU.isra.16.part.17 (ir_opt.c:1226)
==6282==by 0x38159302: isZeroU (ir_opt.c:1525)
==6282==by 0x38159302: fold_Expr (ir_opt.c:2308)
==6282==by 0x38159F36: subst_and_fold_Stmt (ir_opt.c:2585)
==6282==by 0x38159F36: cprop_BB (ir_opt.c:2794)
==6282==by 0x3815BE48: cheap_transformations (ir_opt.c:6414)
==6282==by 0x3815CE96: do_iropt_BB (ir_opt.c:6608)
==6282==by 0x38145E7C: LibVEX_Translate (main_main.c:916)
==6282==by 0x380A1C3B: vgPlain_translate (m_translate.c:1765)
==6282==by 0x380D294B: handle_chain_me (scheduler.c:1076)
==6282==by 0x380D45AF: vgPlain_scheduler (scheduler.c:1420)
==6282==by 0x380E3926: thread_wrapper (syswrap-linux.c:102)
==6282==by 0x380E3926: run_a_thread_NORETURN (syswrap-linux.c:155)
==6282==by 0x380E3DFA: vgModuleLocal_start_thread_NORETURN
(syswrap-linux.c:324)
==6282==by 0x3810C60D: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==6282==by 0xDEADBEEFDEADBEEE: ???
==6282==by 0xDEADBEEFDEADBEEE: ???
==6282==by 0xDEADBEEFDEADBEEE: ???

sched status:
  running_tid=8

[...]

Thread 8: status = VgTs_Runnable (lwpid 6351)
==6282==at 0x9AF5980: ecp_nistz256_avx2_select_w7 (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==6282==by 0x9AD4CEF: EC_POINT_mul (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==6282==by 0x9AD3B36: EC_POINT_new (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==6282==by 0x9ADD029: EC_KEY_generate_key (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==6282==by 0x11775D94: ssl3_send_client_key_exchange (in
/lib/x86_64-linux-gnu/libssl.so.1.0.0)
==6282==by 0x11779857: ssl3_connect (in
/lib/x86_64-linux-gnu/libssl.so.1.0.0)
==6282==by 0x11782F3D: ssl23_connect (in
/lib/x86_64-linux-gnu/libssl.so.1.0.0)
==6282==by 0xDC4FE83: ossl_connect_step2 (in
/usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0)
==6282==by 0xDC50999: ossl_connect_common (in
/usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0)
==6282==by 0xDC5433F: Curl_ssl_connect_nonblocking (in
/usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0)
==6282==by 0xDC1118C: Curl_http_connect (in
/usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0)
==6282==by 0xDC222C0: Curl_protocol_connect (in
/usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0)
==6282==by 0xDC3636D: multi_runsingle (in
/usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0)
==6282==by 0xDC36F5C: curl_multi_perform (in
/usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0)
==6282==[...]

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

[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=321190

1...@gmx-topmail.de changed:

   What|Removed |Added

 CC||1...@gmx-topmail.de

--- Comment #81 from 1...@gmx-topmail.de ---
Why does KDE allow to configure the the middle click action to close for the
task bar and the title bar of every window?
Why are here so much emotions?
Why do you say "I don't think I have to justify the decision. The feature had
been added by me 
(9551c94e7c460efb3b0fd9ccb60472311ff0bf16) in the first place and it has been 
removed by me (f2b7ad693e8c4ef59093287473fb07a3098775bc)."?

Is this a private feud?

Why hurt this feature? In contrast to all the other middle-click-to-close
functions?

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[AJslye via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358171

--- Comment #24 from AJslye  ---
It looks like the update yesterday of plasma-framework 5.18.0-2 didn't fix the
issue after all.
After a reboot this morning, the problem persists, it took 4 attempts before I
was able to log in.
SDDM disappears showing the VT output underneath and reloads itself instead of
starting Plasma.

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

[kdevelop] [Bug 355685] Kdevelop C++ parser crash

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355685

Milian Wolff  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||elop/f78c39655cb3d5dacca43f
   ||de60c7e748efb10820
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #16 from Milian Wolff  ---
Git commit f78c39655cb3d5dacca43fde60c7e748efb10820 by Milian Wolff.
Committed on 21/01/2016 at 12:41.
Pushed by mwolff into branch '4.7'.

Don't access declaration without holding the DUChain lock.

This hopefully fixes a crash in the declaration builder.

M  +9-6languages/cpp/cppduchain/declarationbuilder.cpp

http://commits.kde.org/kdevelop/f78c39655cb3d5dacca43fde60c7e748efb10820

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

[krita] [Bug 358247] "Tile leaked" critical message when closing Krita

[Boudewijn Rempt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358247

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Boudewijn Rempt  ---
Hi Samuel,

That's more of an informational warning for us developers. Somehow krita
managed to leak memory, but unless you remember exactly what you did in the
session that gave this output, there isn't much we can do about it. I'll make
the warning less scary.

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

[plasmashell] [Bug 358246] Plasma crash -konqueror, writer and kmail loaded and being used

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358246

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from David Edmundson  ---


*** This bug has been marked as a duplicate of bug 357895 ***

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

[plasmashell] [Bug 357895] Regression: KDE Plasma with KF 5.18 crash, if mouse repeatedly hovers over panel

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357895

--- Comment #23 from David Edmundson  ---
*** Bug 358246 has been marked as a duplicate of this bug. ***

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

[kopete] [Bug 357694] Kopete crashed when looking at settings

[Andreas Blochberger via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357694

Andreas Blochberger  changed:

   What|Removed |Added

 CC||ablochber...@atoss-csd.de

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

[okular] [Bug 356285] Not enough space for page number

[Gandalf Lechner via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356285

Gandalf Lechner  changed:

   What|Removed |Added

 CC||gandalflech...@gmail.com

--- Comment #2 from Gandalf Lechner  ---
same problem here - using kubuntu 15.10, fully updated

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

[ark] [Bug 358304] Ark do not open ISO files properly.

[Elvis Angelaccio via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358304

--- Comment #1 from Elvis Angelaccio  ---
Does it happen with any iSO file? Can you provide at least one link to an ISO
that Ark cannot open?

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

[plasmashell] [Bug 358297] New: Plasma crashing incessantly on almost any action.

[Alex via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358297

Bug ID: 358297
   Summary: Plasma crashing incessantly on almost any action.
   Product: plasmashell
   Version: 5.5.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: a...@e-dimensionz.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
Plasma crashing incessantly on almost any action.  Clicking on taskbar item,
clicking menu, opening an app, receiving a message, etc, etc

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fbd64eea7c0 (LWP 20681))]

Thread 13 (Thread 0x7fbd51329700 (LWP 20684)):
#0  0x7fbd5f5fa8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fbd636c8bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fbd636ca74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fbd53aa47e9 in QXcbEventReader::run (this=0x2407760) at
qxcbconnection.cpp:1229
#4  0x7fbd5fcf0a6e in QThreadPrivate::start (arg=0x2407760) at
thread/qthread_unix.cpp:331
#5  0x7fbd5eddc6aa in start_thread (arg=0x7fbd51329700) at
pthread_create.c:333
#6  0x7fbd5f605eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fbd4a634700 (LWP 20686)):
#0  0x7fbd5c3900e8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fbd5c3902fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbd5ff2850b in QEventDispatcherGlib::processEvents
(this=0x7fbd440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#3  0x7fbd5fecf50a in QEventLoop::exec (this=this@entry=0x7fbd4a633de0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7fbd5fcebac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#5  0x7fbd62599c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fbd5fcf0a6e in QThreadPrivate::start (arg=0x24e1e00) at
thread/qthread_unix.cpp:331
#7  0x7fbd5eddc6aa in start_thread (arg=0x7fbd4a634700) at
pthread_create.c:333
#8  0x7fbd5f605eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fbd3dca2700 (LWP 20687)):
#0  0x7fbd5c3d4869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fbd5c38f789 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbd5c39011b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbd5c3902fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbd5ff2850b in QEventDispatcherGlib::processEvents
(this=0x7fbd380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fbd5fecf50a in QEventLoop::exec (this=this@entry=0x7fbd3dca1de0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fbd5fcebac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fbd62599c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fbd5fcf0a6e in QThreadPrivate::start (arg=0x2825480) at
thread/qthread_unix.cpp:331
#9  0x7fbd5eddc6aa in start_thread (arg=0x7fbd3dca2700) at
pthread_create.c:333
#10 0x7fbd5f605eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fbd37fff700 (LWP 20688)):
#0  0x7fbd5f5f649d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fbd5c3d34e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbd5c38fcd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbd5c390190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbd5c3902fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbd5ff2850b in QEventDispatcherGlib::processEvents
(this=0x7fbd38c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7fbd5fecf50a in QEventLoop::exec (this=this@entry=0x7fbd37ffede0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7fbd5fcebac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7fbd62599c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fbd5fcf0a6e in QThreadPrivate::start (arg=0x2a29f90) at
thread/qthread_unix.cpp:331
#10 0x7fbd5eddc6aa in start_thread (arg=0x7fbd37fff700) at
pthread_create.c:333
#11 0x7fbd5f605eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 

[krita] [Bug 358055] Krita canvas unresponsive sporadically, using tablet support.

[Boudewijn Rempt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358055

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Boudewijn Rempt  ---
Could it actually be the same thing as
https://bugs.kde.org/show_bug.cgi?id=358130 ?

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

[plasmashell] [Bug 358294] Windows just got the upper hand on kde5

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358294

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||k...@davidedmundson.co.uk
 Resolution|--- |DUPLICATE

--- Comment #6 from David Edmundson  ---
>which even i hate so much i wish it died

Even though it has the exact same feature you require with a different name.

See linked report.

Also I do not expect to read messages with that tone on bugzilla, I understand
venting, however please understand that it will not acheive the intended
result.

*** This bug has been marked as a duplicate of bug 341143 ***

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=341143

David Edmundson  changed:

   What|Removed |Added

 CC||kamijoutouma...@gmail.com

--- Comment #165 from David Edmundson  ---
*** Bug 358294 has been marked as a duplicate of this bug. ***

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

[amarok] [Bug 305554] Lyrics applet doesn't display correctly

[Lukas Jirkovsky via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=305554

Lukas Jirkovsky  changed:

   What|Removed |Added

 CC||l.jirkov...@gmail.com

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

[krita] [Bug 358247] "Tile leaked" critical message when closing Krita

[Boudewijn Rempt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358247

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/call |http://commits.kde.org/krit
   |igra/fc8bbab0383a338753f153 |a/30a1d0a280ca69e3ca86274c6
   |51d59a0126d0e6d6d8  |0d4ba57bbafbac6

--- Comment #4 from Boudewijn Rempt  ---
Git commit 30a1d0a280ca69e3ca86274c60d4ba57bbafbac6 by Boudewijn Rempt.
Committed on 21/01/2016 at 09:27.
Pushed by rempt into branch 'master'.

M  +3-4krita/image/tiles3/kis_tile_data_store.cc

http://commits.kde.org/krita/30a1d0a280ca69e3ca86274c60d4ba57bbafbac6

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

[ark] [Bug 358304] New: Ark do not open ISO files properly.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358304

Bug ID: 358304
   Summary: Ark do not open ISO files properly.
   Product: ark
   Version: 15.08.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kdemail.net
  Reporter: cameron...@poczta.fm
CC: rak...@freebsd.org

When it opens any ISO image there is only README.TXT file listed which is
actually not inside the ISO files.

Reproducible: Always

Steps to Reproduce:
1. Open ISO image file.
2.
3.

Actual Results:  
Shows only ghost README.TXT file inside, but there is no README.TXT file
inside.

Expected Results:  
Should list all the files inside this ISO.

openSUSE Leap 42.1 x64
plasma5 5.4.3
shared-mime-info 1.2-3.3

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

[konsole] [Bug 358299] New: can't see terminal lines

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358299

Bug ID: 358299
   Summary: can't see terminal lines
   Product: konsole
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: araalepogl...@gmail.com

When I open the terminal i can't see any thing but scattered dots on the top
left of the terminal.

Reproducible: Always

Steps to Reproduce:
1.open terminal
2.screen size indicator
3.scattered dots on the top left

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

[plasmashell] [Bug 358240] Legacy system tray icons are shown as white squares.

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358240

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
  Component|System Tray |XembedSNIProxy

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

[kopete] [Bug 357694] Kopete crashed when looking at settings

[Andreas Blochberger via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357694

--- Comment #1 from Andreas Blochberger  ---
Created attachment 96763
  --> https://bugs.kde.org/attachment.cgi?id=96763=edit
New crash information added by DrKonqi

kopete (1.7.2) on KDE Platform 4.14.15 using Qt 4.8.6

- What I was doing when the application crashed:
1. Open settings
2. Close settings

Or
1. Open chat window
2. Close chat window

-- Backtrace (Reduced):
#6  0x7f7966829569 in KHTMLPart::begin(KUrl const&, int, int) () from
/usr/lib/libkhtml.so.5
#7  0x7f796702a971 in ChatMessagePart::writeTemplate() () from
/usr/lib/libkopetechatwindow_shared.so.1
#8  0x7f7967031f30 in ChatMessagePart::changeStyle() () from
/usr/lib/libkopetechatwindow_shared.so.1
#9  0x7f797d3cad01 in QObject::event (this=0x22bcde0, e=) at
kernel/qobject.cpp:1222
#10 0x7f797c476cdc in QApplicationPrivate::notify_helper
(this=this@entry=0x1a26b10, receiver=receiver@entry=0x22bcde0,
e=e@entry=0x2792ea0) at kernel/qapplication.cpp:4570

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

[plasmashell] [Bug 358283] VD: Make user-added plasmoid icons the same size of the system tray icons

[Martin Riethmayer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358283

Martin Riethmayer  changed:

   What|Removed |Added

 CC||rip...@freakmail.de

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

[kdialog] [Bug 358301] New: Segmentation fault while saving a file in Chromium

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358301

Bug ID: 358301
   Summary: Segmentation fault while saving a file in Chromium
   Product: kdialog
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: franklin_mcw...@hotmail.com

I have a Segmentation fault while saving an image file in Chromium. I select
the file, than right click > "Save as", and the popup KDialog window crashes
before I can click "Save". 

h@~ $ uname -a
Linux h 4.3.0-1-amd64 #1 SMP Debian 4.3.3-5 (2016-01-04) x86_64 GNU/Linux

Debug

Application: KDialog (kdialog), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc140aea900 (LWP 10097))]

Thread 4 (Thread 0x7fc12f567700 (LWP 10098)):
#0  0x7fc13d89552d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fc139b641cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc139b642dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc13ed883a6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7fc13ed562e1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7fc13ed56655 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7fc13ec45559 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7fc13ed36343 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7fc13ec47e4c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7fc13b80f0a4 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7fc13d89e06d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7fc12e2a6700 (LWP 10102)):
#0  0x7fc13d8972d3 in select () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fc13ed3272f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7fc13ec47e4c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7fc13b80f0a4 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7fc13d89e06d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7fc12daa5700 (LWP 10105)):
#0  0x7fc13d89552d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fc139b641cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc139b642dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc13ed883a6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7fc13ed562e1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7fc13ed56655 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7fc13ec45559 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7fc13ed36343 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7fc13ec47e4c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7fc13b80f0a4 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7fc13d89e06d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fc140aea900 (LWP 10097)):
[KCrash Handler]
#6  0x7fc11715f795 in QMetaObject::className() const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc1186487bf in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7fc1185e2e77 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7fc1409c3a0a in ?? () from /lib64/ld-linux-x86-64.so.2
#10 0x7fc1409c3af3 in ?? () from /lib64/ld-linux-x86-64.so.2
#11 0x7fc1409c7c58 in ?? () from /lib64/ld-linux-x86-64.so.2
#12 0x7fc1409c38c4 in ?? () from /lib64/ld-linux-x86-64.so.2
#13 0x7fc1409c744b in ?? () from /lib64/ld-linux-x86-64.so.2
#14 0x7fc13ba2502b in ?? () from /lib/x86_64-linux-gnu/libdl.so.2
#15 0x7fc1409c38c4 in ?? () from /lib64/ld-linux-x86-64.so.2
#16 0x7fc13ba255dd in ?? () from /lib/x86_64-linux-gnu/libdl.so.2
#17 0x7fc13ba250c1 in dlopen () from /lib/x86_64-linux-gnu/libdl.so.2
#18 0x7fc11e46c7af in ?? () from /usr/lib/libvlccore.so.8
#19 0x7fc11e4508ab in ?? () from /usr/lib/libvlccore.so.8
#20 0x7fc11e450bd8 in ?? () from /usr/lib/libvlccore.so.8
#21 0x7fc11e450b34 in ?? () from /usr/lib/libvlccore.so.8
#22 0x7fc11e4510b4 in ?? () from /usr/lib/libvlccore.so.8
#23 0x7fc11e4516aa in ?? () from /usr/lib/libvlccore.so.8
#24 0x7fc11e3d771d in libvlc_InternalInit () from /usr/lib/libvlccore.so.8
#25 0x7fc11e1a8a8b in libvlc_new () from /usr/lib/libvlc.so.5
#26 0x7fc11e6faf6b in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_vlc.so
#27 

[plasmashell] [Bug 358300] Plasma crashed during xdg-utils-1.1.1 unit testing

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358300

--- Comment #2 from David Edmundson  ---
Can you link to the test you were running? Would love it if we had a way to
reliably reproduce this bug.

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

[Breeze] [Bug 356037] Confusing indication of active tab (Konsole)

[Nick Cross via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356037

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[krunner] [Bug 344328] krunner is not visible when using multiple monitors

[Vytautas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344328

Vytautas  changed:

   What|Removed |Added

 CC||v...@azuolas.org

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

[plasmashell] [Bug 358298] New: Quick share plasmoid don't work as share

[SinClaus via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358298

Bug ID: 358298
   Summary: Quick share plasmoid don't work as share
   Product: plasmashell
   Version: 5.5.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Icon Applet
  Assignee: plasma-b...@kde.org
  Reporter: tomsk_interf...@vtomske.ru

Quick share plasmoid returns error while try to upload picture for share, and
it don't have any config options for setting other share server.

Reproducible: Always

Steps to Reproduce:
1. Try to move any picture file to plasmoid and select "Imgur" for public link.

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

[konsole] [Bug 358299] can't see terminal lines

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358299

--- Comment #1 from araalepogl...@gmail.com ---
Created attachment 96762
  --> https://bugs.kde.org/attachment.cgi?id=96762=edit
there are very small dots on the top left, when i tyoe i can see the dots
moving.

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

[kmail2] [Bug 317177] HTML emails CSS should not be applied to the header in th UI

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=317177

1...@gmx-topmail.de changed:

   What|Removed |Added

 CC||1...@gmx-topmail.de

--- Comment #7 from 1...@gmx-topmail.de ---
The bug is still present/reappeared in kmail2 5.0.2

eg every amazon order confirmation changes the header layout.

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

[plasmashell] [Bug 358300] Plasma crashed during xdg-utils-1.1.1 unit testing

[Alexey Chernov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358300

--- Comment #3 from Alexey Chernov <4er...@gmail.com> ---
They are triggered too fast one by one, but I'm trying to find the reproducing
one, so I hope to detect it and write here.

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

[kmail2] [Bug 358041] spamassassin filter deletes every incoming mail

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358041

--- Comment #1 from 1...@gmx-topmail.de ---
I changed the spamassassin ruleset to use "spamc" together with the daemonized
version of spamassassin. What a performance boost! The time to scan one mail
decreased from >10s to <1s.
Maybe this fixes the problem, too, that mails are not processed at all (maybe
because of a timeout?)

However, kmail should not sort out mails where no spamassassin header is set at
all.

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

[plasmashell] [Bug 358300] New: Plasma crashed during xdg-utils-1.1.1 unit testing

[Alexey Chernov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358300

Bug ID: 358300
   Summary: Plasma crashed during xdg-utils-1.1.1 unit testing
   Product: plasmashell
   Version: 5.5.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: 4er...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.3.3 x86_64

-- Information about the crash:
- What I was doing when the application crashed:
I've been testing xdg-utils-1.1.1 package before installing it, it interacts
with DE during this and one of these test cases crashed Plasma.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2749e2e7c0 (LWP 2137))]

Thread 7 (Thread 0x7f272df0b700 (LWP 2142)):
#0  0x7f274140edbd in poll () from /lib/libc.so.6
#1  0x7f2747acc152 in _xcb_conn_wait () from /usr/X11R6/lib64/libxcb.so.1
#2  0x7f2747ace2e9 in xcb_wait_for_event () from
/usr/X11R6/lib64/libxcb.so.1
#3  0x7f272fe8aaf9 in QXcbEventReader::run (this=0xfee0f0) at
qxcbconnection.cpp:1229
#4  0x7f27420081e0 in QThreadPrivate::start (arg=0xfee0f0) at
thread/qthread_unix.cpp:331
#5  0x7f27407703e4 in start_thread () from /lib/libpthread.so.0
#6  0x7f2741417d0d in clone () from /lib/libc.so.6

Thread 6 (Thread 0x7f27271cf700 (LWP 2153)):
#0  0x7f274140edbd in poll () from /lib/libc.so.6
#1  0x7f273ca31fe4 in g_main_context_iterate.isra () from
/usr/lib/libglib-2.0.so.0
#2  0x7f273ca320ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f27422471fb in QEventDispatcherGlib::processEvents
(this=0x7f2728c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f27421ec622 in QEventLoop::exec (this=this@entry=0x7f27271cedf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f2742002693 in QThread::exec (this=this@entry=0x10ed1e0) at
thread/qthread.cpp:503
#6  0x7f27464c2235 in QQmlThreadPrivate::run (this=0x10ed1e0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f27420081e0 in QThreadPrivate::start (arg=0x10ed1e0) at
thread/qthread_unix.cpp:331
#8  0x7f27407703e4 in start_thread () from /lib/libpthread.so.0
#9  0x7f2741417d0d in clone () from /lib/libc.so.6

Thread 5 (Thread 0x7f271dd38700 (LWP 2170)):
#0  0x7f2740775f5f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/libpthread.so.0
#1  0x7f2724998a8a in radeon_drm_cs_emit_ioctl () from
/usr/X11/lib/dri/r600_dri.so
#2  0x7f27249982b7 in impl_thrd_routine () from
/usr/X11/lib/dri/r600_dri.so
#3  0x7f27407703e4 in start_thread () from /lib/libpthread.so.0
#4  0x7f2741417d0d in clone () from /lib/libc.so.6

Thread 4 (Thread 0x7f2718fd2700 (LWP 2171)):
#0  0x7f274140edbd in poll () from /lib/libc.so.6
#1  0x7f273ca31fe4 in g_main_context_iterate.isra () from
/usr/lib/libglib-2.0.so.0
#2  0x7f273ca320ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f27422471fb in QEventDispatcherGlib::processEvents
(this=0x7f27140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f27421ec622 in QEventLoop::exec (this=this@entry=0x7f2718fd1df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f2742002693 in QThread::exec (this=this@entry=0x13cafc0) at
thread/qthread.cpp:503
#6  0x7f27464c2235 in QQmlThreadPrivate::run (this=0x13cafc0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f27420081e0 in QThreadPrivate::start (arg=0x13cafc0) at
thread/qthread_unix.cpp:331
#8  0x7f27407703e4 in start_thread () from /lib/libpthread.so.0
#9  0x7f2741417d0d in clone () from /lib/libc.so.6

Thread 3 (Thread 0x7f2713454700 (LWP 2173)):
#0  0x7f273ca82c70 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1  0x7f273ca31375 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7f273ca31f13 in g_main_context_iterate.isra () from
/usr/lib/libglib-2.0.so.0
#3  0x7f273ca320ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f27422471fb in QEventDispatcherGlib::processEvents
(this=0x7f270c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f27421ec622 in QEventLoop::exec (this=this@entry=0x7f2713453df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f2742002693 in QThread::exec (this=this@entry=0x1458f90) at
thread/qthread.cpp:503
#7  0x7f27464c2235 in QQmlThreadPrivate::run (this=0x1458f90) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f27420081e0 in QThreadPrivate::start (arg=0x1458f90) at
thread/qthread_unix.cpp:331
#9  0x7f27407703e4 in start_thread () from /lib/libpthread.so.0
#10 0x7f2741417d0d in clone () from 

[krita] [Bug 358247] "Tile leaked" critical message when closing Krita

[Samuel Frichou via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358247

--- Comment #3 from Samuel Frichou  ---
Thanks, I'll keep an eye out, to see if I can find what is the exact
manipulation.

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

[yakuake] [Bug 189919] Add a favorite commands feature to aid with repetitive typing

[mistermaker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=189919

mistermaker  changed:

   What|Removed |Added

 CC||chaz.sew...@gmail.com

--- Comment #5 from mistermaker  ---
This would be a very useful feature. Yes there are history and alias built into
shells but the problem is not everyone uses yakuake for a single machine. I
work in a data center with thousands of machines and am constantly having to
enter the same command on may different machines over ssh, history and aliases
are useless in this case. Adding a right-click menu tree that custom commands
could be added to would be very useful. Also if features like key-press
emulation and/or input rate limits so that commands are not garbled on slow
console connection would be helpful for this type of feature. This kind of
functionality is built into the right-click menu of terminator but I prefer the
drop down functionality and look of yakuake.

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

[Breeze] [Bug 358302] New: Highlighted checkbox or radio button becomes visually inverted

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358302

Bug ID: 358302
   Summary: Highlighted checkbox or radio button becomes visually
inverted
   Product: Breeze
   Version: 5.4.3
  Platform: openSUSE RPMs
   URL: https://imgur.com/auLTWSm
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: QtQuickControls
  Assignee: k...@davidedmundson.co.uk
  Reporter: linus.kardell+kdeb...@gmail.com

When a checkbox or radio button is highlighted it's color becomes inverted, so
it looks like it's checked when it's unchecked and vice versa. Thus an checked
highlighted looks like an unchecked non-highlighted and vice versa.

Reproducible: Always

Steps to Reproduce:
1. Go to somewhere where you can highlight checkboxes or radio buttons.
2. Check one of them
3. Highlight one of them

Actual Results:  
They look nearly identical.

Expected Results:  
The checked one looks checked and the unchecked one looks unchecked

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

[plasmashell] [Bug 358294] Windows just got the upper hand on kde5

[Michael Fox via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358294

--- Comment #7 from Michael Fox  ---
It's not even the same feature with a different name. If it was i wouldn't be
so damn annoyed like half of your userbase. Your like the pot calling the
kettle (in this case the kettle is activities and VD) black. When they aren't
even 2 sides of the same coin at all.

If you want something that is literally the same feature with a different name
refer to https://bugs.kde.org/show_bug.cgi?id=358294#c3

I mean come on now thats just rediculous.

I could see if you had merged activities and VD into one thing but you didn't. 
Also what makes activities annoying is the fact that activities is actually
harder to use than VD's it's less user freindly. Merging VD into activites (in
the right way) would have greatly reduced the annoyance of your userbase.
Instead you decided to completely remove a few features from VD that almoust
everyone uses, when it would have been smarter to just merge activites and VD
(if you actually beleive that its the "same feature with a different name").
Almoust all of your userbase has completely and utterly bashed and destroyed
KDE5 all over the internet and yet you still say "its the same feature so we
wont fix it".
If its the same feature then there is ABSOLUTELY no reason for there to be
Activities and VD as both do "some" of what a virtual desktop does, so they
might as well be merged and called VD.

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

[dolphin] [Bug 353490] Dolphin crashed while opening a folder containing a git repo

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353490

boblovgre...@gmail.com changed:

   What|Removed |Added

 CC||boblovgre...@gmail.com

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

[kde] [Bug 358305] New: acestream & viber

[Alexandr via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358305

Bug ID: 358305
   Summary: acestream & viber
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: vetra...@mail.ru

Application: kdeconnectd (0.1)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 3.16.0-59-generic x86_64
Distribution: Ubuntu 14.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Hi, Linux 14.04, the package is installed according to the instructions
http://forum.torrentstream.org/index.php?topic=2967.0 from the repository,
after installing Viber stops working (it starts and then
closes). Remove a package acestream-full restores
Viber.

The crash can be reproduced every time.

-- Backtrace:
Application: kdeconnect (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4d7197f7c0 (LWP 2061))]

Thread 2 (Thread 0x7f4d5f538700 (LWP 2072)):
[KCrash Handler]
#6  0x7f4d69b7dc8e in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7  0x7f4d69b770e2 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#8  0x7f4d69b775d2 in dbus_message_unref () from
/lib/x86_64-linux-gnu/libdbus-1.so.3
#9  0x7f4d6e2df099 in q_dbus_message_unref (message=) at
qdbus_symbols_p.h:296
#10 ~QDBusArgumentPrivate (this=, __in_chrg=) at
qdbusargument.cpp:66
#11 QDBusArgument::~QDBusArgument (this=0xe8f310, __in_chrg=) at
qdbusargument.cpp:348
#12 0x7f4d6e2bbbce in qMetaTypeDeleteHelper (t=0xe941d0) at
../../include/QtCore/../../src/corelib/kernel/qmetatype.h:134
#13 0x7f4d6fa78083 in clear (d=0xe08ca0) at kernel/qvariant.cpp:290
#14 0x7f4d6e2aae2c in node_destruct (this=, to=, from=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:431
#15 free (this=, data=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:757
#16 QList::~QList (this=0xe8f310, __in_chrg=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:732
#17 0x7f4d6e2bf40f in QDBusMessage::~QDBusMessage (this=0xe8f310,
__in_chrg=) at qdbusmessage.cpp:537
#18 0x7f4d6e2bc1b6 in ~QDBusCallDeliveryEvent (this=0xe59bc0,
__in_chrg=) at qdbusintegrator_p.h:93
#19 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0xe59bc0,
__in_chrg=) at qdbusintegrator_p.h:93
#20 0x7f4d6fa57b46 in QCoreApplicationPrivate::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xe3b770) at
kernel/qcoreapplication.cpp:1593
#21 0x7f4d6fa57fe3 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1470
#22 0x7f4d6fa81f83 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=0x7f4d58001350) at
kernel/qeventdispatcher_glib.cpp:287
#24 0x7f4d6c13fe04 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f4d6c140048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f4d6c1400ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f4d6fa817a1 in QEventDispatcherGlib::processEvents
(this=0x7f4d580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#28 0x7f4d6fa530af in QEventLoop::processEvents
(this=this@entry=0x7f4d5f537e20, flags=...) at kernel/qeventloop.cpp:149
#29 0x7f4d6fa533a5 in QEventLoop::exec (this=this@entry=0x7f4d5f537e20,
flags=...) at kernel/qeventloop.cpp:204
#30 0x7f4d6f94fc5f in QThread::exec (this=) at
thread/qthread.cpp:537
#31 0x7f4d6f95232f in QThreadPrivate::start (arg=0xe58da0) at
thread/qthread_unix.cpp:349
#32 0x7f4d6c61f182 in start_thread (arg=0x7f4d5f538700) at
pthread_create.c:312
#33 0x7f4d6f30847d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f4d7197f7c0 (LWP 2061)):
#0  0x7f4d6f2f982d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4d6c180c10 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4d6c13fb14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4d6c13ff7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f4d6c1400ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f4d6fa817be in QEventDispatcherGlib::processEvents (this=0xca5920,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f4d704e3be6 in QGuiEventDispatcherGlib::processEvents
(this=, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#7  0x7f4d6fa530af in QEventLoop::processEvents
(this=this@entry=0x7ffe4a266820, flags=...) at kernel/qeventloop.cpp:149
#8  0x7f4d6fa533a5 in QEventLoop::exec 

[k3b] [Bug 358306] New: K3b not able to record ISO images.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358306

Bug ID: 358306
   Summary: K3b not able to record ISO images.
   Product: k3b
   Version: 2.0.80
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Image Formats
  Assignee: k...@kde.org
  Reporter: cameron...@poczta.fm
CC: mich...@jabster.pl, tr...@kde.org

K3b not able to record ISO images. It goes through MD5 verification but when I
hit record it stops with an error saying it can't.

Reproducible: Always

Steps to Reproduce:
1. Open ISO image with K3b.
2. Try to record it on an empty disk.
3.

Actual Results:  
K3b not able to record ISO images.

Expected Results:  
Should record any ISO.

I tried even through console but it gives no messages while hitting record. I
tried on k3b-kf5 version, but it is the same story :(

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

[amarok] [Bug 358225] Amarok does not react when clicking on play

[Myriam Schweingruber via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358225

--- Comment #5 from Myriam Schweingruber  ---
(In reply to second_adress from comment #4)
> phonon-backend-gstreamer 4.8.0-2.4.2
> KDE Platform Version 4.14.9
> KIO-Client: 2.0
>  I hope this is helpful. What do you mean with desktop? Or how can I get
> that information?

Well, not everybody uses Amarok on the same platform, it also runs on other
desktops :-) In your case it is plasma 4.

You need to install the bad and ugly plugins for gstreamer 1.0

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

[KScreen] [Bug 353052] Disconnecting secondary screen leaves primary screen with huge virtual resolution

[Robin Green via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353052

Robin Green  changed:

   What|Removed |Added

 CC||gree...@greenrd.org

--- Comment #2 from Robin Green  ---
Issue still present in kscreen 5.5.3.

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

[ark] [Bug 358304] Ark do not open ISO files properly.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358304

--- Comment #2 from cameron...@poczta.fm ---
It happens with all ISO files, so choose any ISO you want.

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

[krita] [Bug 358247] "Tile leaked" critical message when closing Krita

[Boudewijn Rempt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358247

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/call
   ||igra/fc8bbab0383a338753f153
   ||51d59a0126d0e6d6d8
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Boudewijn Rempt  ---
Git commit fc8bbab0383a338753f15351d59a0126d0e6d6d8 by Boudewijn Rempt.
Committed on 21/01/2016 at 08:14.
Pushed by rempt into branch 'calligra/2.9'.

Make the developer warning about tile leaks less threatening

M  +3-4krita/image/tiles3/kis_tile_data_store.cc

http://commits.kde.org/calligra/fc8bbab0383a338753f15351d59a0126d0e6d6d8

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

[valgrind] [Bug 357338] Unhandled instruction for SHA instructions libcrypto Boring SSL

[satyanarayana koneru via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357338

satyanarayana koneru  changed:

   What|Removed |Added

 CC||satyakoneru.ii...@gmail.com

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

[plasmashell] [Bug 358300] Plasma crashed during xdg-utils-1.1.1 unit testing

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358300

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Edmundson  ---


*** This bug has been marked as a duplicate of bug 342763 ***

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

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=342763

David Edmundson  changed:

   What|Removed |Added

 CC||4er...@gmail.com

--- Comment #138 from David Edmundson  ---
*** Bug 358300 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 317177] HTML emails CSS should not be applied to the header in th UI

[Laurent Montel via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=317177

Laurent Montel  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #8 from Laurent Montel  ---
I confirm it
I need to separate it from message.

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

[plasmashell] [Bug 358303] New: Desktop Folder View does not respect custom Desktop location

[Clinton Ignatov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358303

Bug ID: 358303
   Summary: Desktop Folder View does not respect custom Desktop
location
   Product: plasmashell
   Version: 5.5.3
  Platform: Ubuntu Packages
   URL: http://tinypic.com/r/2j0o4g2/9
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: clintontheg...@gmail.com
CC: plasma-b...@kde.org

I've set my Desktop path to my home folder in Applications -> Locations. It
graciously migrated my shortcuts to my new desktop folder.

However, now I see .desktop extensions on all my shortcuts. This is likely
since I must set my Location in the Plasma Folder View Desktop to "Home"
instead of the default option "Show the Desktop Folder" which persists in
showing icons from ~/Desktop. It should, instead, respect the custom Desktop
folder I have set.

Reproducible: Always

Steps to Reproduce:
1.Change your Desktop folder to your Home directory in Applications ->
Locations
2.Change to Folder View for your Plasma Desktop

Actual Results:  
Nothing is on the desktop. It reflects anything copied into ~/Desktop

Expected Results:  
I would see the contents of my home directory.

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

[kmail2] [Bug 358312] New: The shortcut "M" does not move messages

[Rigo Wenning via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358312

Bug ID: 358312
   Summary: The shortcut "M" does not move messages
   Product: kmail2
   Version: 5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: r...@w3.org

Moving messages with the keyboard does not work. The shortcut "M" calls the
dialog. One can select the folder. On carriage return, the dialog window
disappears. In 4.14 the messages disappeared. Now nothing happens. If one uses
drag & drop it works. The message is then moved correctly

Reproducible: Always

Steps to Reproduce:
1.Hit key m
2.select folder 
3.hit carriage return

Actual Results:  
dialog disappears, messages are not moved but remain untouched

Expected Results:  
messages should be moved to the destination folder

Moving messages via drag & drop of messages to target folder works

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

[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=321190

--- Comment #84 from Martin Gräßlin  ---
The discussion is over, I won't implement it and I won't approve any change
which would implement it. If you expect reasoning for that: sorry I don't feel
like I want to.

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

[kmail2] [Bug 358312] The shortcut "M" does not move messages

[Rigo Wenning via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358312

--- Comment #1 from Rigo Wenning  ---
Shift-Delete works and "move to trash" via "del-key" works too

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

[Spectacle] [Bug 357846] cursor barely visible for rectangle region

[Boudhayan Gupta via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357846

Boudhayan Gupta  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kscr
   ||eengenie/16018caea515baefd4
   ||a61e8a8b1624183283e9f6
   Version Fixed In||16.04

--- Comment #6 from Boudhayan Gupta  ---
Git commit 16018caea515baefd4a61e8a8b1624183283e9f6 by Boudhayan Gupta.
Committed on 21/01/2016 at 15:43.
Pushed by bgupta into branch 'master'.

Create a new preferences dialog and handling system.

Tunables include:
* Default save options as before
* Dynamic save button
* Remember last rectangular selection
* Use light mask colour for rectangular selection
FIXED-IN: 16.04

M  +4-1src/CMakeLists.txt
M  +14   -7src/Gui/KSMainWindow.cpp
M  +1-1src/Gui/KSMainWindow.h
M  +7-2src/Gui/ScreenClipper.cpp
A  +134  -0src/Gui/SettingsDialog/GeneralOptionsPage.cpp [License: LGPL
(v2+)]
C  +18   -27   src/Gui/SettingsDialog/GeneralOptionsPage.h [from:
src/Gui/KSSaveConfigDialog.h - 056% similarity]
R  +18   -19   src/Gui/SettingsDialog/SaveOptionsPage.cpp [from:
src/Gui/KSSaveConfigDialog.cpp - 085% similarity]
C  +15   -25   src/Gui/SettingsDialog/SaveOptionsPage.h [from:
src/Gui/KSSaveConfigDialog.h - 064% similarity]
A  +71   -0src/Gui/SettingsDialog/SettingsDialog.cpp [License: LGPL
(v2+)]
C  +17   -26   src/Gui/SettingsDialog/SettingsDialog.h [from:
src/Gui/KSSaveConfigDialog.h - 059% similarity]
C  +10   -36   src/Gui/SettingsDialog/SettingsPage.cpp [from:
src/Gui/KSSaveConfigDialog.h - 052% similarity]
R  +13   -28   src/Gui/SettingsDialog/SettingsPage.h [from:
src/Gui/KSSaveConfigDialog.h - 055% similarity]
M  +39   -0src/SpectacleConfig.cpp
M  +9-0src/SpectacleConfig.h

http://commits.kde.org/kscreengenie/16018caea515baefd4a61e8a8b1624183283e9f6

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

[kdevelop] [Bug 358296] Kdevelop crashes when trying to scp a file by rightclick --> run external script

[Kevin Funk via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358296

--- Comment #2 from Kevin Funk  ---
I presume you only get this crash in case you don't have any editor tabs open?

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

[kdeplasma-addons] [Bug 358200] tiny size on panel with KF 5.18

[David Rosca via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358200

David Rosca  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-framework/f688c904a81c72
   ||d077580ab942b874f398fbd7d4
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from David Rosca  ---
Git commit f688c904a81c72d077580ab942b874f398fbd7d4 by David Rosca.
Committed on 21/01/2016 at 14:35.
Pushed by drosca into branch 'master'.

AppletQuickItem: Don't try to set initial size bigger than parent size

Trying to set initial size bigger than parent size only results
to item being resized down to fit in parent later.

REVIEW: 126822

M  +8-4src/plasmaquick/appletquickitem.cpp

http://commits.kde.org/plasma-framework/f688c904a81c72d077580ab942b874f398fbd7d4

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

[valgrind] [Bug 358213] helgrind/drd bar_bad testcase hangs with new glibc pthread barrier implementation

[Mark Wielaard via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358213

--- Comment #5 from Mark Wielaard  ---
Note that patch is missing the drd/test/Makefile.am addition of the two extra
exp file:

diff --git a/drd/tests/Makefile.am b/drd/tests/Makefile.am
index 2885391..cfd74d0 100644
--- a/drd/tests/Makefile.am
+++ b/drd/tests/Makefile.am
@@ -81,8 +81,10 @@ EXTRA_DIST =\
atomic_var.stderr.exp   \
atomic_var.vgtest   \
bar_bad.stderr.exp  \
+   bar_bad.stderr.exp-nohang   \
bar_bad.vgtest  \
bar_bad_xml.stderr.exp  \
+   bar_bad_xml.stderr.exp-nohang   \
bar_bad_xml.vgtest  \
bar_trivial.stderr.exp  \
bar_trivial.stdout.exp  \

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

[kmail2] [Bug 277007] KMail2 full search of emails does not work

[Josep via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=277007

Josep  changed:

   What|Removed |Added

 CC||j...@ieec.cat

--- Comment #40 from Josep  ---
Just the same, with the same configuration as Robert Scott (kmail 4.14.1,
Debian Jessie, all KDE packages installed through package system). Searchs
finish almost instantly, but always with empty results. Tried selecting search
folder manually, include and don't include subfolders and several other
options, but the search was always instantaneous and empty.

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

[valgrind] [Bug 356393] valgrind (vex) crashes because isZeroU happened

[Florian Krohm via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356393

--- Comment #5 from Florian Krohm  ---
This is the guilty code:

case Iop_Xor8:
case Iop_Xor16:
case Iop_Xor32:
case Iop_Xor64:
case Iop_XorV128:
case Iop_XorV256://   < selecting this case
   /* Xor8/16/32/64/V128(t,t) ==> 0, for some IRTemp t */
   if (sameIRExprs(env, e->Iex.Binop.arg1, e->Iex.Binop.arg2)) { 
// <=== false
  e2 = mkZeroOfPrimopResultType(e->Iex.Binop.op);
  break;
   }
   /* XorV128(t,0) ==> t */
   if (e->Iex.Binop.op == Iop_XorV128) {
  if (isZeroV128(e->Iex.Binop.arg2)) {
 e2 = e->Iex.Binop.arg1;
 break;
  }
  //Disabled because there's no known test case right now.
  //if (isZeroV128(e->Iex.Binop.arg1)) {
  //   e2 = e->Iex.Binop.arg2;
  //   break;
  //}
   } else {
  /* Xor8/16/32/64(0,t) ==> t */
  if (isZeroU(e->Iex.Binop.arg1)) { //  <=== arriving here

BANG. isZeroU cannot handle Iop_XorV256  hence the assert.

This patch is likely going to fix it (still testing):
Index: VEX/priv/ir_opt.c
===
--- VEX/priv/ir_opt.c(revision 3206)
+++ VEX/priv/ir_opt.c(working copy)
@@ -2292,8 +2292,15 @@
   e2 = mkZeroOfPrimopResultType(e->Iex.Binop.op);
   break;
}
+   /* XorV256(t,0) ==> t */
+   if (e->Iex.Binop.op == Iop_XorV256) {
+  if (isZeroV256(e->Iex.Binop.arg2)) {
+ e2 = e->Iex.Binop.arg1;
+ break;
+  }
+   }
/* XorV128(t,0) ==> t */
-   if (e->Iex.Binop.op == Iop_XorV128) {
+   else if (e->Iex.Binop.op == Iop_XorV128) {
   if (isZeroV128(e->Iex.Binop.arg2)) {
  e2 = e->Iex.Binop.arg1;
  break;

but the code is UGLY. Comments are out of date and the Boolean IRops And/Or/Xor
are handled differently. We really should keep as much code in common as
possible. 
Extending isZeroU and isOneU to also handle V128 and V256 values makes sense to
me.Even if the function name then no longer exactly describes the set of
allowed values. Or we can change the function name as there are only aboout 10
invocations. So the ripple is acceptable IMHO.

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

[kontact] [Bug 351686] After using Knotes, Kontakt crashes after reopening following to riduction to icon

[sederic via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=351686

sederic  changed:

   What|Removed |Added

 CC||sebastian.end...@online.de

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

[Akonadi] [Bug 358313] New: Akonadi 15.12.1 - IMAP resource: read status sometimes wrong

[Till Schäfer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358313

Bug ID: 358313
   Summary: Akonadi 15.12.1 - IMAP resource: read status sometimes
wrong
   Product: Akonadi
   Version: GIT (master)
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: till2.schae...@uni-dortmund.de
CC: kdepim-b...@kde.org, vkra...@kde.org

I have noticed, that i often have several mails marked as read on the imap
server are marked as unread in akonadi or the other way round. (verified over
akonadi console, not only in kmail)  Sometimes even complete directories get
marked unread. 

Pressing F5 to update the folder does not resolve the situation in both cases.
Also akonadictl fsck and vaccuum do not resolve the issue.  The only workaround
i have found so far is do delete the akonadi cache in akonadiconsole and
re-sync the folder afterward.

This bug occurred since the migration to the KF5 version of akonadi. It was not
present in KDE4. 

Maybe this bug is also related to Bug 355966, which is causing my imap resource
to crash every few hours or so.

Reproducible: Always

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

[kmail2] [Bug 310896] Sent messages re-appearing outbox folder as unread mail

[Josep via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=310896

Josep  changed:

   What|Removed |Added

 CC||j...@ieec.cat

--- Comment #6 from Josep  ---
I have the same problem in Debian Jessie with kmail 4.14.1, but it just started
to happen a few weeks ago. Any message I send, reappears almost immediately in
the outbox, though the message is sent correctly (the receiver gets it and a
copy appears in the "Sent" folder and there are no error notifications). In the
.xsession-errors I do get messages like:

akonadi_maildispatcher_agent(3681) OutboxQueue::Private::addIfComplete: Item
345559 does not have the required attribute Address. 

and

void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&)
Notification source "akonadi_maildispatcher_agent_3681_dcz5O2" now serving: ()

but I cannot confirm if they are related.

As I mentioned before, a few weeks ago it was not happening. More or less at
the same time, I had changed the configuration of the SMTP server (postfix) to
add some additional restrictions on sender addresses (
reject_unauthenticated_sender_login_mismatch, reject_non_fqdn_sender) but since
the messages are being sent correctly I doubt this is the problem.

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

[plasmashell] [Bug 358300] Plasma crashed during xdg-utils-1.1.1 unit testing

[Alexey Chernov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358300

--- Comment #4 from Alexey Chernov <4er...@gmail.com> ---
Unfortunately, I didn't manage to reproduce it with running unit tests again —
seems that it was caused my some collision when I tried to close windows it
opened during tests while it kept opening more windows. I tried to repeat this
as well, but never managed to get this crash again.

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

[Akonadi] [Bug 355966] akonadi 15.12.1: imap resource crashed while running in background

[Till Schäfer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355966

Till Schäfer  changed:

   What|Removed |Added

Version|unspecified |GIT (master)
Summary|akonadi 15.08.3: imap   |akonadi 15.12.1: imap
   |resource crashed while  |resource crashed while
   |running in background   |running in background

--- Comment #1 from Till Schäfer  ---
still valid for 15.12.1

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

[Breeze] [Bug 356343] Rendering issue after upgrade to kwin 5.5

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356343

k...@stieler.org changed:

   What|Removed |Added

 CC||k...@stieler.org

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

[krunner] [Bug 358316] New: KRunner becomes frozen and is shown when app with incorrect .desktop file is started

[Alexey Chernov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358316

Bug ID: 358316
   Summary: KRunner becomes frozen and is shown when app with
incorrect .desktop file is started
   Product: krunner
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: 4er...@gmail.com

KRunner hangs and is shown until the application is closed when it was used to
start the applications with absent service is defined in X-DBUS-ServiceName
item of its .desktop file (for reproduce scenario see bug #358315 for
Skrooge-2.2.0 with such a typo in this field). When the application is closed,
"KDEInit couldn't launch " error message is shown and KRunner
continues to run normally.

Reproducible: Always

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

[kmail2] [Bug 358312] The shortcut "M" does not move messages

[Henri via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358312

Henri  changed:

   What|Removed |Added

 CC||cer...@luukku.com

--- Comment #2 from Henri  ---
Works for me. Using kmail5-15.12.0-1.2.x86_64, openSUSE TW, Plasma 5.5.2, Qt
5.5.1.

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

[trojita] [Bug 350606] Fragile tests: IDLE depends on build node load

[Jan Kundrát via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350606

Jan Kundrát  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[plasmashell] [Bug 358317] xembedsniproxy crashes when clicking on empty fcitx icon

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358317

--- Comment #2 from David Edmundson  ---
Urgh, thanks.

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

[plasmashell] [Bug 358318] Plasma crahed after login

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358318

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from David Edmundson  ---
#19 0x7fd36c6a2e4b in brw_clear (ctx=0x1f23608, mask=0) at
../../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:264

This is crashing in your graphic driver which we can't do much about.

Please upgrade/downgrade your version of mesa. See information (including a
workaround) in the linked report

*** This bug has been marked as a duplicate of bug 349519 ***

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

[plasmashell] [Bug 358317] xembedsniproxy crashes when clicking on empty fcitx icon

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358317

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[skrooge] [Bug 358315] Typo in .desktop file leads to KRunner freeze

[Alexey Chernov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358315

--- Comment #1 from Alexey Chernov <4er...@gmail.com> ---
Created attachment 96768
  --> https://bugs.kde.org/attachment.cgi?id=96768=edit
Patch fixing the typo and certain problem.

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

[plasmashell] [Bug 358319] New: Tray icons disappear

[sederic via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358319

Bug ID: 358319
   Summary: Tray icons disappear
   Product: plasmashell
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: sebastian.end...@online.de

Sometimes some icons in the tray area (bottom right in the panel) are hidden
and there is a gap. Sometimes they appear after killing and relaunching
plasmashell and sometimes other icons disappear. On my laptop the volume
control often disappears, on a firend's laptop the network icon disappears.

Reproducible: Sometimes

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

[plasmashell] [Bug 358319] Tray icons disappear

[sederic via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358319

sederic  changed:

   What|Removed |Added

 CC||sebastian.end...@online.de

--- Comment #1 from sederic  ---
Created attachment 96769
  --> https://bugs.kde.org/attachment.cgi?id=96769=edit
The missing tray icons are highlighted

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

[plasmashell] [Bug 358317] New: xembedsniproxy crashes when clicking on empty fcitx icon

[Wolfgang Bauer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358317

Bug ID: 358317
   Summary: xembedsniproxy crashes when clicking on empty fcitx
icon
   Product: plasmashell
   Version: 5.5.3
  Platform: openSUSE RPMs
   URL: https://bugzilla.opensuse.org/show_bug.cgi?id=954623
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: XembedSNIProxy
  Assignee: plasma-b...@kde.org
  Reporter: wba...@tmo.at
CC: k...@davidedmundson.co.uk
Depends on: 358227

+++ This bug was initially created as a clone of Bug #358227 +++

While the original crash is fixed now, we noticed a new problem:
When fcitx is installed/active, a new, empty, icon now shows up in the system
tray (this probably caused the original crash already) in addition to fcitx's
normal icon (which seems to be SNI as it is also shown when xembedsniproxy is
not running).

If you click on this icon, xembedsniproxy crashes again.

Konsole output:
kde.xembedsniproxy: trying to dock window  12582932
kde.xembedsniproxy: adding damage watch for  12582932
kde.xembedsniproxy: Resizing window 12582932 "" from w*h QSize(-1, -1)
QXcbConnection: XCB error: 3 (BadWindow), sequence: 850, resource id: 12582932,
major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 856, resource id: 12582932,
major code: 7 (ReparentWindow), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 857, resource id: 12582932,
major code: 142 (Unknown), minor code: 1
QXcbConnection: XCB error: 3 (BadWindow), sequence: 858, resource id: 12582932,
major code: 6 (ChangeSaveSet), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 859, resource id: 12582932,
major code: 25 (SendEvent), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 860, resource id: 12582932,
major code: 12 (ConfigureWindow), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 864, resource id: 12582932,
major code: 12 (ConfigureWindow), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 865, resource id: 12582932,
major code: 8 (MapWindow), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 866, resource id: 12582932,
major code: 61 (ClearArea), minor code: 0
kde.xembedsniproxy: No xembed icon for 12582932 ""
kde.xembedsniproxy: Received click 1 with passed x*y 1008 998

Program received signal SIGSEGV, Segmentation fault.

Backtrace:
#0  0x0040eaf8 in SNIProxy::sendClick(unsigned char, int, int)
(this=0x62a6e0, mouseButton=mouseButton@entry=1 '\001', x=1008, y=998)
at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/sniproxy.cpp:438
#1  0x0040eb6e in SNIProxy::Activate(int, int) (this=,
x=, y=)
at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/sniproxy.cpp:384
#2  0x00410d2d in StatusNotifierItemAdaptor::Activate(int, int)
(this=, x=, y=)
at
/usr/src/debug/plasma-workspace-5.5.3/build/xembed-sni-proxy/statusnotifieritemadaptor.cpp:81
#3  0x00411231 in
StatusNotifierItemAdaptor::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) (_o=_o@entry=0x71dfb0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=6, _a=_a@entry=0x7fffd2e0)
at
/usr/src/debug/plasma-workspace-5.5.3/build/xembed-sni-proxy/statusnotifieritemadaptor.moc:166
#4  0x004117ab in
StatusNotifierItemAdaptor::qt_metacall(QMetaObject::Call, int, void**)
(this=0x71dfb0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fffd2e0)
at
/usr/src/debug/plasma-workspace-5.5.3/build/xembed-sni-proxy/statusnotifieritemadaptor.moc:266
#5  0x77b7fda4 in  () at /usr/lib64/libQt5DBus.so.5
#6  0x77b84372 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x77b84e83 in  () at /usr/lib64/libQt5DBus.so.5
#8  0x77b8692e in  () at /usr/lib64/libQt5DBus.so.5
#9  0x7618c4f6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#10 0x7615bc2d in QCoreApplication::notify(QObject*, QEvent*) ()
at /usr/lib64/libQt5Core.so.5
#11 0x7615b935 in QCoreApplication::notifyInternal(QObject*, QEvent*)
()
at /usr/lib64/libQt5Core.so.5
#12 0x7615daf7 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#13 0x761b3303 in  () at /usr/lib64/libQt5Core.so.5
#14 0x726cba04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#15 0x726cbc48 in  () at /usr/lib64/libglib-2.0.so.0
#16 0x726cbcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#17 0x761b277c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#18 0x76159803 in
QEventLoop::exec(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#19 0x76161396 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#20 0x0040a9da in 

[plasmashell] [Bug 358227] xembedsniproxy crashes when fcitx is started

[Wolfgang Bauer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358227

Wolfgang Bauer  changed:

   What|Removed |Added

 Blocks||358317

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

[plasmashell] [Bug 358317] xembedsniproxy crashes when clicking on empty fcitx icon

[Wolfgang Bauer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358317

--- Comment #1 from Wolfgang Bauer  ---
It seems the original fix was not enough.

(In reply to Wolfgang Bauer from comment #0)
> #0  0x0040eaf8 in SNIProxy::sendClick(unsigned char, int, int)
> (this=0x62a6e0, mouseButton=mouseButton@entry=1 '\001', x=1008, y=998)
> at
> /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/sniproxy.cpp:438

This line still uses clientGeom without checking for null.
If clientGeom was null in SNIProxy::SNIProxy() (which caused the original
crash, that was fixed by adding a check in line 163), it will also be null
here.

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