[plasmashell] [Bug 388249] KWin should query org.freedesktop.locale1 for the default keyboard layout

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
  Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/kwi
   |sma-workspace/361ee31606fb4 |n/eb69e87288d37fdb13eca32ca
   |d770356e7adde8c45369cca0aab |807ed8279f912af
 Resolution|--- |FIXED

--- Comment #9 from Fabian Vogt  ---
Git commit eb69e87288d37fdb13eca32ca807ed8279f912af by Fabian Vogt.
Committed on 15/01/2018 at 07:56.
Pushed by fvogt into branch 'master'.

Manually take XKB_DEFAULT_{RULES,MODEL,LAYOUT,VARIANT,OPTIONS} into account

Summary:
As kwin_wayland can have the CAP_SYS_NICE capability, libxkbcommon does not
read environment variables (see secure_getenv).
So process them here, in the same way xkb_context_sanitize_rule_names would.

Test Plan: kwin_wayland has the capability set, keyboard layout is applied
correctly.

Reviewers: #plasma, graesslin

Subscribers: kwin, plasma-devel, #kwin

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D9873

M  +34   -1xkb.cpp

https://commits.kde.org/kwin/eb69e87288d37fdb13eca32ca807ed8279f912af

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

[systemsettings] [Bug 388994] New: Save button to save the current Look and Feel preferences

[Baltasar]

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

Bug ID: 388994
   Summary: Save button to save the current Look and Feel
preferences
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bort...@kde-espana.es
  Target Milestone: ---

Hello:

I thing it would be great to have a button to save the current state of your
plasma desktop in the Look and Feel section: wallpaper, widgets, bars,colors,
etc.

It would be nice because if you try another Look and Feel theme you lost the
changes of the current Plasma Desktop and sometimes you can lost information
(the note widget dissapear, for example).

Best Regards

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

[kate] [Bug 388993] New: Kate or one of its plugins opens a 'helloworld test' in firefox at desktop startup

[T R T]

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

Bug ID: 388993
   Summary: Kate or one of its plugins opens a 'helloworld test'
in firefox at desktop startup
   Product: kate
   Version: 17.12.0
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: trial...@protonmail.com
  Target Milestone: ---

When I logged in, firefox started with this link:
https://cgit.kde.org/?p=kate.git=tree=addons%2Fkate%2Fhelloworld
I've never used kate and only started it once out of curiosity a few months
ago. So, I never installed any plugin either.

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

[Discover] [Bug 388990] Discover fails to install flatpak application

[Mustafa Muhammad]

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

--- Comment #1 from Mustafa Muhammad  ---
OK, the problem is probably in flatpak, it didn't install it from console too:

mustafa@mustafa-pc:~$ flatpak install flathub org.telegram.desktop
Installing: org.telegram.desktop/x86_64/stable from flathub
[] 1 metadata, 0 content objects fetched; 569 B transferred
in 1 se
error: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error deploying: Key file
does not start with a group

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

[plasmashell] [Bug 388992] New: Taskbar edit causes Wayland to crash.

[Scott]

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

Bug ID: 388992
   Summary: Taskbar edit causes Wayland to crash.
   Product: plasmashell
   Version: 5.11.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: davis.scot...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.5)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed: Clicking the show desktop icon
does nothing, clicking the edit taskbar causes the taskbar and KDE to crash. My
kernel is not tainted and I have not done anything other that using wayland and
installing a few packages. I just installed Arch less than 12 hours ago. 

- Unusual behavior I noticed: Show desktop fails and some strange display
artifacts sometime appears. I am using Wayland and I believe this to be highly
relevant.

The crash can be reproduced every time.

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

Thread 15 (Thread 0x7f1b7912e700 (LWP 7134)):
[KCrash Handler]
#5  0x7f1c60893c81 in wl_proxy_create_wrapper () at
/usr/lib/libwayland-client.so.0
#6  0x7f1bbf3e236d in  () at /usr/lib/libEGL_mesa.so.0
#7  0x7f1bbf3cf7cf in  () at /usr/lib/libEGL_mesa.so.0
#8  0x7f1bbfcf8792 in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#9  0x7f1bbfcf6c3e in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#10 0x7f1c62ab9a19 in QOpenGLContext::makeCurrent(QSurface*) () at
/usr/lib/libQt5Gui.so.5
#11 0x7f1c65ecfb86 in  () at /usr/lib/libQt5Quick.so.5
#12 0x7f1c65ed7846 in  () at /usr/lib/libQt5Quick.so.5
#13 0x7f1c65ed6a5b in  () at /usr/lib/libQt5Quick.so.5
#14 0x7f1c65ed6e54 in  () at /usr/lib/libQt5Quick.so.5
#15 0x7f1c62093b2d in  () at /usr/lib/libQt5Core.so.5
#16 0x7f1c6124908c in start_thread () at /usr/lib/libpthread.so.0
#17 0x7f1c6199be1f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f1b7992f700 (LWP 7133)):
#0  0x7f1c6124f39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1c6209500c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1c65ed69ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1c65ed6e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1c62093b2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1c6124908c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1c6199be1f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f1b7bfff700 (LWP 7132)):
#0  0x7f1c6198d3d8 in read () at /usr/lib/libc.so.6
#1  0x7f1c5c282801 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1c5c23cafc in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f1c5c23cfc6 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f1c5c23d13e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f1c622dc6b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f1c6227e82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f1c6208e78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f1c65298a19 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f1c62093b2d in  () at /usr/lib/libQt5Core.so.5
#10 0x7f1c6124908c in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f1c6199be1f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f1b7b7fe700 (LWP 6534)):
#0  0x7f1c6124f39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1c6209500c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1c65ed69ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1c65ed6e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1c62093b2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1c6124908c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1c6199be1f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f1b9f114700 (LWP 1084)):
#0  0x7f1c6124f39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1c6209500c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1c65ed69ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1c65ed6e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1c62093b2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1c6124908c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1c6199be1f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 

[kdeconnect] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[David Mattatall]

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

David Mattatall  changed:

   What|Removed |Added

   Keywords||reproducible

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

[kdeconnect] [Bug 388991] New: KDE Connect 1.2 segfaults/crashes.

[David Mattatall]

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

Bug ID: 388991
   Summary: KDE Connect 1.2 segfaults/crashes.
   Product: kdeconnect
   Version: 1.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: davidsm...@davidsmind.com
  Target Milestone: ---

With 64-bit gentoo on an I5 CPU.

KDE connect is one of my favorite plasma applications, however for the past
half a year say it will segfault after 5-10 minutes of starting up, and that's
a bummer! 

The segfault's always look like this. [32953.332329] kdeconnectd[2576]:
segfault at 18 ip 7fd09a067ab3 sp 7ffc75359c78 error 4 in
libQt5Core.so.5.9.3[7fd099f54000+484000] 

Typically in this situation I'll just go to an earlier version, but only one is
present in portage. 

I'm wondering if there is some known issue and if there is something I can do
to trace the code to help reveal what is going on exactly. 


System info:

Portage 2.3.13 (python 3.5.4-final-0,
default/linux/amd64/17.1/desktop/plasma/systemd, gcc-6.4.0, glibc-2.25-r9,
4.9.72-gentoo x86_64) 
= 
 System Settings 
= 
System uname:
Linux-4.9.72-gentoo-x86_64-Intel-R-_Core-TM-_i5-4670K_CPU_@_3.40GHz-with-gentoo-2.4.1
 
KiB Mem:32906896 total,   2375100 free 
KiB Swap:8191996 total,   8191996 free 
Timestamp of repository gentoo: Sun, 14 Jan 2018 23:00:01 + 
Head commit of repository gentoo: fb5fbc676a05bb8f14c154e79c577d50894e81a4 
sh bash 4.4_p12 
ld GNU ld (Gentoo 2.29.1 p3) 2.29.1 
app-shells/bash:  4.4_p12::gentoo 
dev-java/java-config: 2.2.0-r3::gentoo 
dev-lang/perl:5.24.3::gentoo 
dev-lang/python:  2.7.14-r1::gentoo, 3.4.5-r1::gentoo, 3.5.4-r1::gentoo 
dev-util/cmake:   3.9.6::gentoo 
dev-util/pkgconfig:   0.29.2::gentoo 
sys-apps/baselayout:  2.4.1-r2::gentoo 
sys-apps/openrc:  0.34.11::gentoo 
sys-apps/sandbox: 2.10-r4::gentoo 
sys-devel/autoconf:   2.13::gentoo, 2.69-r4::gentoo 
sys-devel/automake:   1.11.6-r2::gentoo, 1.15.1-r1::gentoo 
sys-devel/binutils:   2.29.1-r1::gentoo 
sys-devel/gcc:6.4.0-r1::gentoo 
sys-devel/gcc-config: 1.8-r1::gentoo 
sys-devel/libtool:2.4.6-r3::gentoo 
sys-devel/make:   4.2.1::gentoo 
sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers) 
sys-libs/glibc:   2.25-r9::gentoo 
Repositories: 

gentoo 
location: /usr/portage 
sync-type: rsync 
sync-uri: rsync://rsync.gentoo.org/gentoo-portage 
priority: -1000 
sync-rsync-extra-opts: 

ago 
location: /var/lib/layman/ago 
masters: gentoo 
priority: 50 

steam-overlay 
location: /var/lib/layman/steam-overlay 
masters: gentoo 
priority: 50 

ACCEPT_KEYWORDS="amd64" 
ACCEPT_LICENSE="* -@EULA" 
CBUILD="x86_64-pc-linux-gnu" 
CFLAGS="-march=core-avx2 -O2 -pipe" 
CHOST="x86_64-pc-linux-gnu" 
CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config
/usr/share/gnupg/qualified.txt" 
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release
/etc/php/apache2-php7.1/ext-active/ /etc/php/cgi-php7.1/ext-active/
/etc/php/cli-php7.1/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/splash
/etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d
/etc/texmf/updmap.d /etc/texmf/web2c" 
CXXFLAGS="-march=core-avx2 -O2 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FCFLAGS="-O2 -pipe" 
FEATURES="assume-digests binpkg-logs candy clean-logs
config-protect-if-modified distlocks fixlafiles merge-sync multilib-strict news
parallel-fetch parallel-install preserve-libs protect-owned sandbox sfperms
strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv
usersandbox usersync xattr" 
FFLAGS="-O2 -pipe" 
GENTOO_MIRRORS="http://gentoo.gossamerhost.com
rsync://gentoo.gossamerhost.com/gentoo-distfiles/
rsync://mirror.the-best-hosting.net/gentoo-distfiles
http://mirror.the-best-hosting.net http://gentoo.mirrors.tera-byte.com/; 
LANG="en_US.utf8" 
LDFLAGS="-Wl,-O1 -Wl,--as-needed" 
LINGUAS="en ja" 
MAKEOPTS="-j5 --load-average" 
PKGDIR="/usr/portage/packages" 
PORTAGE_CONFIGROOT="/" 
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--omit-dir-times --compress --force --whole-file --delete --stats
--human-readable --timeout=180 --exclude=/distfiles --exclude=/local
--exclude=/packages --exclude=/.git" 
PORTAGE_TMPDIR="/tmp" 
USE="X a52 aac acl acoustid acpi activities alsa amd64 bash-completion berkdb
bluetooth branding btrfs bzip2 cairo cdda cddb cdr chromecast cli client-libs
crypt cups curl cxx dbus declarative dos dri dts dvd dvdr emboss encode
equalizer exif facebook fat 

[Discover] [Bug 388990] New: Discover fails to install flatpak application

[Mustafa Muhammad]

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

Bug ID: 388990
   Summary: Discover fails to install flatpak application
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Flatpak Backend
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
CC: jgrul...@redhat.com
  Target Milestone: ---

Discover fails to install an application, I tested Telegram, I started Discover
from terminal and got this log:

mustafa@mustafa-pc:~$ plasma-discover 
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x21e4ee0)
Failed to install "org.telegram.desktop" :
"GDBus.Error:org.freedesktop.DBus.Error.Failed: Error deploying: Key file does
not start with a group"

Using Neon dev git-unstable, Discover version 5.11.90
With flatpak backend installed

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

[kdeplasma-addons] [Bug 366527] Touch events cannot launch applications

[Eike Hein]

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

--- Comment #7 from Eike Hein  ---
The comment Kai linked should also resolve this indeed.

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

[krita] [Bug 388989] Configuration window too large in Hi-DPI mode

[bugzilla_noreply]

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

--- Comment #1 from gst...@zoho.com ---
current workaround is to use keyboard for navigation
possible fixes could include a slider for DPI scaling, smaller default window
size for popups, or enabling resizing of the popup window

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

[krita] [Bug 388989] New: Configuration window too large in Hi-DPI mode

[bugzilla_noreply]

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

Bug ID: 388989
   Summary: Configuration window too large in Hi-DPI mode
   Product: krita
   Version: 3.3.3
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: gst...@zoho.com
  Target Milestone: ---

Created attachment 109868
  --> https://bugs.kde.org/attachment.cgi?id=109868=edit
screenshot demonstrating issue on Surface Pro 2

'OK', 'Cancel' and 'Restore Defaults' buttons in the 'Configure Krita' popup
window are cut off at the bottom when 'Enable Hi-DPI support' is used
this is on a Surface Pro 2, system scaling set to 150%

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

[kmail2] [Bug 388573] Draft message is confused about mail transport

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kma
   ||iltransport/424f0273dbebd11
   ||5da6812e0b680fb911f282cd4
   Version Fixed In||5.7.2

--- Comment #4 from Laurent Montel  ---
Git commit 424f0273dbebd115da6812e0b680fb911f282cd4 by Laurent Montel.
Committed on 15/01/2018 at 06:04.
Pushed by mlaurent into branch 'Applications/17.12'.

Fix Bug 388573 - Draft message is confused about mail transport

FIXED-IN: 5.7.2

M  +1-1src/kmailtransport/widgets/transportcombobox.cpp

https://commits.kde.org/kmailtransport/424f0273dbebd115da6812e0b680fb911f282cd4

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

[kig] [Bug 388241] Cannot use python scripting when compiling from source

[Maurizio Paolini]

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

--- Comment #8 from Maurizio Paolini  ---
This problem seems to appear when compiling from git sources when compiled
against boost-devel-1.63.0 or later.
In this version of boost the file /usr/include/boost/python/object_core.hpp
contains an assert at line 425:

---
inline api::object_base::~object_base()
{
assert( Py_REFCNT(m_ptr) > 0 );
Py_DECREF(m_ptr);
}
---

that fails.  It took long to track the problem because the kig package compiled
in a rpm fedora package is compiled with build flag -DNDEBUG which disables
asserts.  Can you reproduce the problem bu opening the kig file provided as
attachment?

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

[kig] [Bug 388241] Cannot use python scripting when compiling from source

[Maurizio Paolini]

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

--- Comment #7 from Maurizio Paolini  ---
Created attachment 109867
  --> https://bugs.kde.org/attachment.cgi?id=109867=edit
kig file exposing the problem

This kig file contains a very simple python script depending upon
a numeric label:

def calc( arg1 ):
x = arg1.coordinate().x
return DoubleObject (x)

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

[neon] [Bug 388988] New: boincmgr will not run after update of kchart

[bugzilla_noreply]

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

Bug ID: 388988
   Summary: boincmgr will not run after update of kchart
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: rol...@logikalsolutions.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 109866
  --> https://bugs.kde.org/attachment.cgi?id=109866=edit
gui error log

I have 2 systems with the exact same install of KDE Neon. One the I7 I applied
all updates including the kchart update which prompted me for OK to remove
kdiagram. On the I5 I have not installed that update.

boincmgr will not run on the I7, but does on the I5. It appears boincmgr is
dependent on kdiagram and this wasn't taken into account with the kchart
update.

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

[digikam] [Bug 388977] Error during upgrading core database schema from v8 to v9

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Created attachment 109865
  --> https://bugs.kde.org/attachment.cgi?id=109865=edit
dbconfig.xml

Replace the dbconfig.xml under /usr/share/digikam/database/ with this one. If
the entries in the database is in a clean state, the schema update should work
fine with MySQL-5.7.

Maik

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

[Discover] [Bug 388987] New: Discover crashes after system update

[Richard Ullger]

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

Bug ID: 388987
   Summary: Discover crashes after system update
   Product: Discover
   Version: 5.11.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: rull...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.11.5)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Updated Arch Linux system (4 packages selected for update) from within Discover
by clicking on Update and selecting Update All. Update completed and Discover
reported there were no updates. Discover crashed.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb7e573f800 (LWP 1587))]

Thread 8 (Thread 0x7fb7a3177700 (LWP 1600)):
#0  0x7fb7db3bbba9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fb7db374a36 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7fb7db374fc6 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fb7db37513e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fb7e16cb6b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fb7e166d82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fb7e147d78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fb7e1482b2d in  () at /usr/lib/libQt5Core.so.5
#8  0x7fb7dd58e08c in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fb7e0d8ae1f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fb7b289a700 (LWP 1594)):
#0  0x7fb7db37447b in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fb7db374f4e in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fb7db37513e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fb7e16cb6b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fb7e166d82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fb7e147d78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fb7e1482b2d in  () at /usr/lib/libQt5Core.so.5
#7  0x7fb7dd58e08c in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fb7e0d8ae1f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fb7b373b700 (LWP 1593)):
#0  0x7fb7db3ba7fb in  () at /usr/lib/libglib-2.0.so.0
#1  0x7fb7db374afc in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7fb7db374fc6 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fb7db37513e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fb7e16cb6b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fb7e166d82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fb7e147d78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fb7e1482b2d in  () at /usr/lib/libQt5Core.so.5
#8  0x7fb7dd58e08c in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fb7e0d8ae1f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fb7b930b700 (LWP 1592)):
#0  0x7fb7e16cb468 in  () at /usr/lib/libQt5Core.so.5
#1  0x7fb7db374a2a in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7fb7db374fc6 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fb7db37513e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fb7e16cb6b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fb7e166d82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fb7e147d78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fb7e46adbcb in  () at /usr/lib/libQt5Quick.so.5
#8  0x7fb7e1482b2d in  () at /usr/lib/libQt5Core.so.5
#9  0x7fb7dd58e08c in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fb7e0d8ae1f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fb7c3fff700 (LWP 1591)):
#0  0x7fb7e0d7c3d8 in read () at /usr/lib/libc.so.6
#1  0x7fb7db3ba801 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fb7db374afc in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fb7db374fc6 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fb7db37513e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fb7e16cb6b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fb7e166d82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fb7e147d78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fb7e207ea19 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7fb7e1482b2d in  () at /usr/lib/libQt5Core.so.5
#10 

[Discover] [Bug 388986] New: [Crash] Discover crashes when user manually triggers check for update

[Raghavendra kamath]

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

Bug ID: 388986
   Summary: [Crash] Discover crashes when user manually triggers
check for update
   Product: Discover
   Version: 5.11.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: raghavendr.ra...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.11.5)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I had a already updated arch linux system, I triggered check for update action
via settings >  more  > check for update

Discover crashe. I also tried the shortcut Ctrl + R and the crash was
reproducible.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8a003f4800 (LWP 4069))]

Thread 10 (Thread 0x7f89b8885700 (LWP 4081)):
#0  0x7f89f82526dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f89fc141ec1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f89fc13dd91 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f89fc140b2d in  () at /usr/lib/libQt5Core.so.5
#4  0x7f89f824c08c in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f89fba48e1f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f89bbfff700 (LWP 4078)):
#0  0x7f89f825239d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f89fc14200c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f89ff3ed9ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f89ff3ede54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f89fc140b2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f89f824c08c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f89fba48e1f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f89c13f7700 (LWP 4077)):
#0  0x7f89fba3e91b in poll () at /usr/lib/libc.so.6
#1  0x7f89f6033023 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f89f603313e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f89fc3896b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f89fc32b82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f89fc13b78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f89fc140b2d in  () at /usr/lib/libQt5Core.so.5
#7  0x7f89f824c08c in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f89fba48e1f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f89c3fff700 (LWP 4076)):
#0  0x7f89f82526dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f89fc141ec1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f89fc13dd91 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f89fc140b2d in  () at /usr/lib/libQt5Core.so.5
#4  0x7f89f824c08c in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f89fba48e1f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f89d0a99700 (LWP 4075)):
#0  0x7f89fba3e91b in poll () at /usr/lib/libc.so.6
#1  0x7f89f6033023 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f89f603313e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f89fc3896b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f89fc32b82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f89fc13b78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f89fc140b2d in  () at /usr/lib/libQt5Core.so.5
#7  0x7f89f824c08c in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f89fba48e1f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f89d193a700 (LWP 4074)):
#0  0x7f89fba3e91b in poll () at /usr/lib/libc.so.6
#1  0x7f89f6033023 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f89f603313e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f89fc3896b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f89fc32b82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f89fc13b78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f89fc140b2d in  () at /usr/lib/libQt5Core.so.5
#7  0x7f89f824c08c in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f89fba48e1f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f89d3bee700 (LWP 4073)):
#0  0x7f89f6032a10 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#1  0x7f89f6032fc6 in  () at 

[krita] [Bug 388985] New: Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta

[David Warner]

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

Bug ID: 388985
   Summary: Pen Pressure not detected on Surface Pro 4 in Krita
4.0 Beta
   Product: krita
   Version: 4.0.0-beta.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: blen...@gmail.com
  Target Milestone: ---

I installed Krita 4, build 36 on my Surface Pro 4. So far I have no pressure
variance with my pen. I have tried both the Win Tab and Windows Ink base
setting in Krita with no success. All other apps like Sketchbook, Leonardo, and
Ink work fine as did Krita 3.3.2 and 3.3.3

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

[Discover] [Bug 388916] Install button doesn't disable or become something else during installation of Snap app

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #2 from Nate Graham  ---
Hmm, even with that commit, the Install button still doesn't change or
deactivate, so you can still click it multiple times.

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

[Discover] [Bug 388968] Discover shows version as "Stable" for Flatpak packages even if release information with version numbers is available in AppStream

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #5 from Nate Graham  ---
Verified!

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

[storageservicemanager] [Bug 388944] Don't return an empty icon if there's no decoration

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||aleix...@kde.org

--- Comment #2 from Aleix Pol  ---
Tracked here on the store.kde.org side: https://phabricator.kde.org/T7754

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

[Discover] [Bug 388916] Install button doesn't disable or become something else during installation of Snap app

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dis
   ||cover/3193c6f19b96425278915
   ||f045a3ee662cb6093bc
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Aleix Pol  ---
Git commit 3193c6f19b96425278915f045a3ee662cb6093bc by Aleix Pol.
Committed on 15/01/2018 at 02:14.
Pushed by apol into branch 'master'.

Report progress on snaps

M  +8-1libdiscover/backends/SnapBackend/SnapTransaction.cpp

https://commits.kde.org/discover/3193c6f19b96425278915f045a3ee662cb6093bc

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

[Discover] [Bug 388968] Discover shows version as "Stable" for Flatpak packages even if release information with version numbers is available in AppStream

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dis
   ||cover/61f520f9cf1da96eeb163
   ||45d197f46ebef859eb3
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Aleix Pol  ---
Git commit 61f520f9cf1da96eeb16345d197f46ebef859eb3 by Aleix Pol.
Committed on 15/01/2018 at 01:53.
Pushed by apol into branch 'master'.

Extract the version number from the AppStream information

M  +10   -5libdiscover/backends/FlatpakBackend/FlatpakResource.cpp

https://commits.kde.org/discover/61f520f9cf1da96eeb16345d197f46ebef859eb3

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

[Discover] [Bug 388968] Discover shows version as "Stable" for Flatpak packages even if release information with version numbers is available in AppStream

[Aleix Pol]

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

--- Comment #3 from Aleix Pol  ---
Related: https://github.com/ximion/appstream/issues/164

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

[Breeze] [Bug 388984] New: regression: breeze icons 5.41.0 uncompilable

[Uwe Stöhr]

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

Bug ID: 388984
   Summary: regression: breeze icons 5.41.0 uncompilable
   Product: Breeze
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: uwesto...@web.de
CC: kain...@gmail.com
  Target Milestone: ---

Using MSVC 2015 I can no longer compile the breeze icons 5.41.0. Version 5.40.0
worked.

I get:

[13/26] Building CXX object CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj
[14/26] Linking CXX executable bin\qrcAlias.exe
FAILED: bin/qrcAlias.exe
cmd.exe /C "cd . && C:\Perl\c\bin\c++.exe -std=c++0x -fno-operator-names
-fno-exceptions -Wall -Wextra -Wcast-align -Wch
ar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=r
eturn-type -Wvla -Wdate-time -fdiagnostics-color=always -O3 -DNDEBUG  -mwindows
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj
 CMakeFiles/qrcAlias.dir/qrcAlias_autogen/mocs_compilation.cpp.obj  -o
bin\qrcAlias.exe -Wl,--out-implib,lib\libqrcAlias
.dll.a -Wl,--major-image-version,0,--minor-image-version,0 
C:/Qt/Qt5.9.3/5.9.3/msvc2015_64/lib/Qt5Core.lib C:/Qt/Qt5.9.
3/5.9.3/msvc2015_64/lib/qtmain.lib -lkernel32 -luser32 -lgdi32 -lwinspool
-lshell32 -lole32 -loleaut32 -luuid -lcomdlg32
 -ladvapi32 && cd ."
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x55): undefined
reference to `_imp___ZN7QString11reallocDa
taEjb'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0xa4): undefined
reference to `_imp___ZN7QString6appendERKS
_'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0xbc): undefined
reference to `_imp___ZN5QFileC1ERK7QString
'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x110): undefined
reference to `_imp___ZN5QFile4openE6QFlag
sIN9QIODevice12OpenModeFlagEE'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x136): undefined
reference to `_imp___ZN9QIODevice8readLin
eEx'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x17a): undefined
reference to `_imp___ZN7QString16fromAsci
i_helperEPKci'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x1b5): undefined
reference to `_imp___ZN10QArrayData10deal
locateEPS_jj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x1ff): undefined
reference to `_imp___ZNK14QMessageLogger5
debugEv'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x20f): undefined
reference to `_imp___ZNK5QFile8fileNameEv
'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x22b): undefined
reference to `_imp___ZN6QDebug9putStringE
PK5QCharj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x259): undefined
reference to `_imp___ZN7QString15fromUtf8
_helperEPKci'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x264): undefined
reference to `_imp___ZN11QTextStreamlsERK
7QString'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x29f): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x2cd): undefined
reference to `_imp___ZN6QDebugD1Ev'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x2d2): undefined
reference to `_imp___ZN10QArrayData11shar
ed_nullE'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x315): undefined
reference to `_imp___ZN10QArrayData10deal
locateEPS_jj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x335): undefined
reference to `_imp___ZN10QArrayData10deal
locateEPS_jj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x35c): undefined
reference to `_imp___ZN10QArrayData10deal
locateEPS_jj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x3a3): undefined
reference to `_imp___ZNK14QMessageLogger5
debugEv'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x3c7): undefined
reference to `_imp___ZN7QString15fromUtf8
_helperEPKci'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x3d2): undefined
reference to `_imp___ZN11QTextStreamlsERK
7QString'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x40d): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x41f): undefined
reference to `_imp___ZN6QDebug9putStringE
PK5QCharj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x44a): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x481): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x48f): undefined
reference to `_imp___ZNK5QFile8fileNameEv
'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x4c1): undefined
reference to `_imp___ZN11QTextStreamlsEc'

[storageservicemanager] [Bug 388944] Don't return an empty icon if there's no decoration

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

Summary|Use Generic Icon for|Don't return an empty icon
   |Missing App Icons   |if there's no decoration
Product|Discover|storageservicemanager
 Ever confirmed|0   |1
  Component|discover|general
 Status|UNCONFIRMED |CONFIRMED
   Assignee|aleix...@kde.org|mon...@kde.org

--- Comment #1 from Aleix Pol  ---
At the moment we are getting such a thing:
https://cn.pling.com/cache/100x100/img/default.png

Will see how to fix it in the store...

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

[cantor] [Bug 386865] AutoMoc warnings with plot2dassistant, plot3dassistant, antor_advancedplotassistant and cantorpart

[Uwe Stöhr]

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

--- Comment #3 from Uwe Stöhr  ---
> The first two warning should be gone now. Do you still get a warning for
> cantor_part after my fix?

I can no longer compile cantor because the compilation of the breeze icons
fails:

[13/26] Building CXX object CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj
[14/26] Linking CXX executable bin\qrcAlias.exe
FAILED: bin/qrcAlias.exe
cmd.exe /C "cd . && C:\Perl\c\bin\c++.exe -std=c++0x -fno-operator-names
-fno-exceptions -Wall -Wextra -Wcast-align -Wch
ar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=r
eturn-type -Wvla -Wdate-time -fdiagnostics-color=always -O3 -DNDEBUG  -mwindows
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj
 CMakeFiles/qrcAlias.dir/qrcAlias_autogen/mocs_compilation.cpp.obj  -o
bin\qrcAlias.exe -Wl,--out-implib,lib\libqrcAlias
.dll.a -Wl,--major-image-version,0,--minor-image-version,0 
C:/Qt/Qt5.9.3/5.9.3/msvc2015_64/lib/Qt5Core.lib C:/Qt/Qt5.9.
3/5.9.3/msvc2015_64/lib/qtmain.lib -lkernel32 -luser32 -lgdi32 -lwinspool
-lshell32 -lole32 -loleaut32 -luuid -lcomdlg32
 -ladvapi32 && cd ."
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x55): undefined
reference to `_imp___ZN7QString11reallocDa
taEjb'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0xa4): undefined
reference to `_imp___ZN7QString6appendERKS
_'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0xbc): undefined
reference to `_imp___ZN5QFileC1ERK7QString
'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x110): undefined
reference to `_imp___ZN5QFile4openE6QFlag
sIN9QIODevice12OpenModeFlagEE'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x136): undefined
reference to `_imp___ZN9QIODevice8readLin
eEx'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x17a): undefined
reference to `_imp___ZN7QString16fromAsci
i_helperEPKci'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x1b5): undefined
reference to `_imp___ZN10QArrayData10deal
locateEPS_jj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x1ff): undefined
reference to `_imp___ZNK14QMessageLogger5
debugEv'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x20f): undefined
reference to `_imp___ZNK5QFile8fileNameEv
'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x22b): undefined
reference to `_imp___ZN6QDebug9putStringE
PK5QCharj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x259): undefined
reference to `_imp___ZN7QString15fromUtf8
_helperEPKci'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x264): undefined
reference to `_imp___ZN11QTextStreamlsERK
7QString'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x29f): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x2cd): undefined
reference to `_imp___ZN6QDebugD1Ev'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x2d2): undefined
reference to `_imp___ZN10QArrayData11shar
ed_nullE'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x315): undefined
reference to `_imp___ZN10QArrayData10deal
locateEPS_jj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x335): undefined
reference to `_imp___ZN10QArrayData10deal
locateEPS_jj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x35c): undefined
reference to `_imp___ZN10QArrayData10deal
locateEPS_jj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x3a3): undefined
reference to `_imp___ZNK14QMessageLogger5
debugEv'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x3c7): undefined
reference to `_imp___ZN7QString15fromUtf8
_helperEPKci'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x3d2): undefined
reference to `_imp___ZN11QTextStreamlsERK
7QString'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x40d): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x41f): undefined
reference to `_imp___ZN6QDebug9putStringE
PK5QCharj'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x44a): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x481): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x48f): undefined
reference to `_imp___ZNK5QFile8fileNameEv
'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x4c1): undefined
reference to `_imp___ZN11QTextStreamlsEc'

CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x4ed): undefined
reference to `_imp___ZN6QDebugD1Ev'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x4f2): undefined
reference to `_imp___ZN10QArrayData11shar
ed_nullE'
CMakeFiles/qrcAlias.dir/qrcAlias.cpp.obj:qrcAlias.cpp:(.text+0x503): undefined
reference to 

[kde] [Bug 388983] Systemsettings crashes setting "Default Web shotcut"

[Tony]

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

Tony  changed:

   What|Removed |Added

Product|systemsettings  |kde
  Component|general |general

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

[systemsettings] [Bug 388983] Systemsettings crashes setting "Default Web shotcut"

[Tony]

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

Tony  changed:

   What|Removed |Added

Product|kde |systemsettings
   Platform|unspecified |openSUSE RPMs
  Component|general |general

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

[kde] [Bug 388983] New: Systemsettings crashes setting "Default Web shotcut"

[Tony]

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

Bug ID: 388983
   Summary: Systemsettings crashes setting "Default Web shotcut"
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jodr...@live.com
  Target Milestone: ---

Application: kdeinit5 (5.11.90)

Qt Version: 5.10.0
Frameworks Version: 5.42.0
Operating System: Linux 4.14.11-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Trying to chage the default web shortcut for konsole to duck duck go.

-Steps to reproduce:
Open a konsole window
Right click, select "search for", open the "Web Shortcuts"
Either Click "OK" or "Cancel", no changes are necesary, even if you do they are
not saved.

Doing the same from Systemsettings>Shortcuts>Web Shortcuts as well as running
the module directly from Krunner does not trigger the crash.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f11d2a17700 (LWP 4007)):
#0  0x7f11edd3df2b in __GI___poll (fds=0x7f11cc002de0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f11ea4de149 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f11cc002de0, timeout=, context=0x7f11cc000be0)
at gmain.c:4187
#2  g_main_context_iterate (context=context@entry=0x7f11cc000be0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3881
#3  0x7f11ea4de25c in g_main_context_iteration (context=0x7f11cc000be0,
may_block=1) at gmain.c:3947
#4  0x7f11ee2f257b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f11ee2994aa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f11ee0c08da in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f11e67afbd5 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#8  0x7f11ee0c58d0 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f11ec3b7558 in start_thread (arg=0x7f11d2a17700) at
pthread_create.c:465
#10 0x7f11edd486df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f11d9a27700 (LWP 4006)):
#0  0x7f11edd3df2b in __GI___poll (fds=fds@entry=0x7f11d9a26d48,
nfds=nfds@entry=1, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f11ef10d387 in poll (__timeout=-1, __nfds=1, __fds=0x7f11d9a26d48)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x559db22df120, cond=cond@entry=0x559db22df160,
vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:479
#3  0x7f11ef10f17a in xcb_wait_for_event (c=0x559db22df120) at xcb_in.c:693
#4  0x7f11dca358d9 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#5  0x7f11ee0c58d0 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f11ec3b7558 in start_thread (arg=0x7f11d9a27700) at
pthread_create.c:465
#7  0x7f11edd486df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f11efcbd780 (LWP 4005)):
[KCrash Handler]
#6  0x0031 in ?? ()
#7  0x7f11d10764ee in qDeleteAll::const_iterator>
(end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320
#8  qDeleteAll > (c=...) at
/usr/include/qt5/QtCore/qalgorithms.h:328
#9  ProvidersModel::~ProvidersModel (this=0x559db23dedf0, __in_chrg=) at
/usr/src/debug/kio-5.41.0git.20180114T135246~017eb3f1/src/urifilters/ikws/ikwsopts.cpp:43
#10 0x7f11d1076559 in ProvidersModel::~ProvidersModel (this=0x559db23dedf0,
__in_chrg=) at
/usr/src/debug/kio-5.41.0git.20180114T135246~017eb3f1/src/urifilters/ikws/ikwsopts.cpp:44
#11 0x7f11ee2c6b8b in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#12 0x7f11ec977d0c in QWidget::~QWidget() () from
/usr/lib64/libQt5Widgets.so.5
#13 0x7f11e2c21141 in KCModule::~KCModule (this=0x559db23ea330,
__in_chrg=) at
/usr/src/debug/kconfigwidgets-5.41.0git.20180105T234114~72a795a/src/kcmodule.cpp:178
#14 0x7f11d1085d37 in FilterOptions::~FilterOptions (this=0x559db23ea330,
__in_chrg=) at
/usr/src/debug/kio-5.41.0git.20180114T135246~017eb3f1/src/urifilters/ikws/ikwsopts.h:35
#15 FilterOptions::~FilterOptions (this=0x559db23ea330, __in_chrg=) at
/usr/src/debug/kio-5.41.0git.20180114T135246~017eb3f1/src/urifilters/ikws/ikwsopts.h:35
#16 0x7f11d14a417e in qDeleteAll::const_iterator>
(end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320
#17 qDeleteAll > (c=...) at

[bindings] [Bug 388980] heaps of missing and broken libraries for TortoiseHg

[Scott Kitterman]

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

Scott Kitterman  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||k...@kitterman.com

--- Comment #1 from Scott Kitterman  ---
qscintilla2 in Neon needs to be recompiled.  This is a downstream packaging
issue.

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

[gwenview] [Bug 388982] New: Main image view does not automatically refresh on file changes

[ned]

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

Bug ID: 388982
   Summary: Main image view does not automatically refresh on file
changes
   Product: gwenview
   Version: 17.04.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: naught...@gmail.com
  Target Milestone: ---

Gwenview's main image view does not update when a file is modified. The
thumbnail bar thumbnails do update.

Perhaps there is a reason for this behaviour, but it would be good to at least
have an option in the settings to allow auto refresh (and I think that that
should be the default behaviour).

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

[kblackbox] [Bug 363660] Grid visibility is poor

[bugzilla_noreply]

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

--- Comment #4 from key...@gmail.com ---
I made it an option because I was worried the new behavior would be undesirable
or annoying for players used to the current behavior. I can remove the option
if it make more sense to always have the cursor on.

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

[Discover] [Bug 378339] Crash on remove chars in search text box

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #21 from Aleix Pol  ---
Seems to be happening still. Also on System Settings, so possibly a Kirigami
issue.

As pointed out by Christoph Feck:
https://bugs.kde.org/buglist.cgi?bug_severity=crash=---=QQuickItemPrivate%3A%3AdeliverKeyEvent_type=allwordssubstr

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

[neon] [Bug 382694] [SLIMBOOK] oem-config-prepare Desktop shortcut doesn't work correctly

[Harald Sitter]

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

--- Comment #9 from Harald Sitter  ---
So it would seem. Mind you, grub theming is still broken so the ISO continues
to not meet UX expectations of plasma 
https://build.neon.kde.org/view/openqa%20%E2%9B%B7/job/openqa_xenial_useredition_installation_oem/25/testReport/junit/(root)/003_first_start/038_unmatched_needle/

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

[digikam] [Bug 388981] Ability to set "Reference Album" for Find Duplicates

[bugzilla_noreply]

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

firndel...@live.com changed:

   What|Removed |Added

 CC||firndel...@live.com

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

[digikam] [Bug 388981] New: Ability to set "Reference Album" for Find Duplicates

[bugzilla_noreply]

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

Bug ID: 388981
   Summary: Ability to set "Reference Album" for Find Duplicates
   Product: digikam
   Version: 5.7.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Searches-Similarity
  Assignee: digikam-bugs-n...@kde.org
  Reporter: firndel...@live.com
  Target Milestone: ---

Currently the only thing I can get Find Duplicates to do is compare all images
to all other images within a directory (or set of multiple selected
directories), or to compare a single image to a set of albums/directories.

Based on the Restriction options to Include/Exclude the "Reference Album[s]" I
at first thought there was a way to select a reference set and find all
duplicates of that reference set within a target set.

Specifically, I imported a folder of images and wanted to see if any of them
were duplicates after importing as I had not yet set up the fingerprints. I
didn't want to search every image in my collection against every other, just
every image I had just import against the rest of the collection--still a long
task but much shorter! 

After a lot of troubleshooting there didn't seem to be a way to do this. If
there was a way to do it, there was at the very least no clear way to tell what
the "Reference Album" was currently set to other than the (usually empty)
window of "Reference Images" containing already suspected duplicates. This is,
for me at least, a really important feature for making Find Duplicates and
other Similarity Searches more useable--searching either one image at a time or
checking an entire set against itself are both very wasteful tasks compared to
what I find myself actually wanting to do with the feature!

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

[kile] [Bug 388348] livePreview can not find tex file

[balabi]

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

--- Comment #9 from balabi  ---
(In reply to Michel Ludwig from comment #8)
> Git commit 306a7322bbbf6413f59ccda3089164575907b6b8 by Michel Ludwig.
> Committed on 13/01/2018 at 06:05.
> Pushed by mludwig into branch 'master'.
> 
> Use the correct path list separator on Windows
> Related: bug 385840
> 
> M  +2-2src/dialogs/texdocumentationdialog.cpp
> M  +4-8src/kileconstants.h
> M  +5-5src/kileinfo.cpp
> M  +7-7src/kilelauncher.cpp
> M  +5-5src/livepreview.cpp
> M  +2-2src/quickpreview.cpp
> 
> https://commits.kde.org/kile/306a7322bbbf6413f59ccda3089164575907b6b8

Thank you so much! Is the binary for windows updated?

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

[Discover] [Bug 388281] Discover Update Crash

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
Should we reopen bug 378339? Either the commit there was not sufficient to fix
the issue, or it is not really a duplicate (see KF5 version).

Note that we also have related search crashes in systemsettings since its
switch to the new kirigami UI.

https://bugs.kde.org/buglist.cgi?bug_severity=crash=---=QQuickItemPrivate%3A%3AdeliverKeyEvent_type=allwordssubstr

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

[bindings] [Bug 388980] New: heaps of missing and broken libraries for TortoiseHg

[Eddie]

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

Bug ID: 388980
   Summary: heaps of missing and broken libraries for TortoiseHg
   Product: bindings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: pykde
  Assignee: kde-bindi...@kde.org
  Reporter: eddie.dha...@gmail.com
  Target Milestone: ---

TortoiseHg, GUI for mercurial (link =
https://bitbucket.org/tortoisehg/targz/downloads/tortoisehg-4.4.2.tar.gz) works
perfectly fine on other distros but not on KDE neon. I haven't tried Kubuntu
though.

The first error:
No module named Qsci

Upon trying to fix that up:
`sudo apt-get install python-qscintilla2`
it gives the following error:
`python-qscintilla2: Depends: sip-api-11.2`
`E: Unable to correct problems, you have held broken packages.`

Upon trying to fix that up:
`sudo apt-get install sip-api-11.2` it gives the following error:
`E: Package 'sip-api-11.2' has no installation candidate`
although according to `aptitude search sip-api` the version of the `sip-api`
required is available.

The version of `python-sip` is `4.19.6` and I don't know the relationship
between `python-sip` and the `sip-api`.

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

[plasmashell] [Bug 388937] plasmashell crash when I open Kdevelop or Ark

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

--- Comment #1 from Christoph Feck  ---
If this is reproducible, please install debug symbols to generate a better
backtrace. For more information, please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[korganizer] [Bug 358106] [REGRESSION] Allow week to start on Monday

[sparhawk]

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

--- Comment #17 from sparhawk  ---
I think the fact that it's not customisable is arguably a feature (if a poor
one). However, there is definitely a bug present, because the hard-coded days
are incorrect. See my comments above.

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

[korganizer] [Bug 358106] [REGRESSION] Allow week to start on Monday

[bugzilla_noreply]

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

--- Comment #16 from liv...@penserpouragir.org ---
I use a workaround but maybe this is not a bug, just a feature.
The different countries officially begin the week by a different day, Sunday in
north America, Monday in Europa ... if I well remember what I readied.
So just set the LOCALE for the format you need. In general "French Canadian"
Locales, I have french ones for Hours and Orders. And it is better now.
All this cam be setuped in KDE : System settings > regionals parameters >
Formats (free translation).
Once I changed more specificals Locales, and OpenOffice had accents problems. 
A bit tricky but seems a feature a bit underdocumented.
Hope it will help

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

[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[bugzilla_noreply]

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

steffen.he...@gmail.com changed:

   What|Removed |Added

 CC||steffen.he...@gmail.com

--- Comment #22 from steffen.he...@gmail.com ---
Same issue here with "An authentication error occurred: SSL handshake failed
(6)". I use digikam-5.8.0-01-x86-64.appimage (Ubuntu Linux 17.04
4.10.0-42-generic #46-Ubuntu SMP Mon Dec 4 14:38:01 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux).

Strange is that I don't get this error with another laptop with Ubuntu Linux
16.04.03 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux...

I tried with deleting all cifing file under .local or .config, but the issue is
the same.

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

[clazy] [Bug 388925] Segmentation fault in OldStyleConnect::fixits() calling Expr::getBestDynamicClassType()

[Tom Isaacson]

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

--- Comment #5 from Tom Isaacson  ---
I've made some small changes but nothing to do with this crash - line 450 is:
const auto record = expr ? expr->getBestDynamicClassType() : nullptr;

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

[clazy] [Bug 388925] Segmentation fault in OldStyleConnect::fixits() calling Expr::getBestDynamicClassType()

[Sergio Martins]

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

--- Comment #4 from Sergio Martins  ---
weird, I don't have a line 450 in oldstyleconnect.cpp, which commit is this ?

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

[clazy] [Bug 388979] New: Allow to add classes to UnusedNonTrivialVariable::isInterestingType

[Albert Astals Cid]

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

Bug ID: 388979
   Summary: Allow to add classes to
UnusedNonTrivialVariable::isInterestingType
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: aa...@kde.org
CC: smart...@kde.org
  Target Milestone: ---

Some projects may have their own classes that they may want to lookout in the
"declared but not used" scenario, i.e. for poppler i did a run with Object and
found quite a few.

I guess easier would be an environment variable?

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

[kblackbox] [Bug 363660] Grid visibility is poor

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #3 from Albert Astals Cid  ---
I'm not really a kblackbox player, but i'm reviewing the patch because i don't
think anyone else will.

Do we really need this to be an option?

I think it really makes sense to always have the highlight follow the mouse,
no?

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

[plasma4] [Bug 330356] Panel auto-hide stops working after using desktop for a while.

[bugzilla_noreply]

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

--- Comment #18 from bk...@gnu.org ---
It has been *FOUR* years now. This still happens on a regular basis and this
bug is still marked, "UNCONFIRMED". My "System Settings" says Version 5.8.8, so
I assume that is the KDE version, too, but the Frameworks is 5.36.0. So I do
not know what the KDE version is. I've rebooted a few times, but to no avail.

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

[krunner] [Bug 388902] Segfault while searching apps

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

Product|plasmashell |krunner
   Assignee|k...@davidedmundson.co.uk|k...@privat.broulik.de
  Component|general |bookmarks
   Target Milestone|1.0 |---

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

[plasmashell] [Bug 384236] Crash in KIO::DropJob::setApplicationActions

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

Summary|plasmashell crash (and  |Crash in
   |restart)|KIO::DropJob::setApplicatio
   ||nActions

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

[plasmashell] [Bug 388886] plasmashell crashed when trying to unminimize konsole

[David Edmundson]

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

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 384236 ***

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

[plasmashell] [Bug 384236] plasmashell crash (and restart)

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||bsmith7...@live.com

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

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

[krita] [Bug 388976] [Gradient Map Filter] color mapping issue

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
I can reproduce it on the appimage, but not my local build, which makes it near
impossible for me to figure out what is going on...

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

[Discover] [Bug 388978] New: Sometimes searching crashes Discover

[Mustafa Muhammad]

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

Bug ID: 388978
   Summary: Sometimes searching crashes Discover
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.11.90)

Qt Version: 5.9.3
Frameworks Version: 5.42.0
Operating System: Linux 4.13.0-26-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
- What I was doing when the application crashed:
Searching in Discover, I opened a new report because this is an up to date neon
dev (from git)

The crash can be reproduced sometimes.

-- Backtrace:
Application: Discover (plasma-discover), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fece67358c0 (LWP 5014))]

Thread 9 (Thread 0x7fec97dd3700 (LWP 5045)):
#0  0x7fece1bc024d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc9316f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ede74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fecdc8ee330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7fec98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7fec97dd2d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#8  0x7fece25ca709 in QThreadPrivate::start (arg=0x2a19f90) at
thread/qthread_unix.cpp:368
#9  0x7fecde7776ba in start_thread (arg=0x7fec97dd3700) at
pthread_create.c:333
#10 0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7feca60e0700 (LWP 5024)):
#0  0x7fece1bc470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc8ee38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7fec9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7feca60dfd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x2d78db0) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7feca60e0700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7feca7d96700 (LWP 5021)):
#0  0x7fecdc932a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fecdc8ee23d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7feca8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7feca7d95d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x2c264d0) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7feca7d96700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fecadfa0700 (LWP 5020)):
#0  0x7fece1bc470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc8ee38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7feca80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7fecadf9fd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x3d96820) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7fecadfa0700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fecb9a12700 (LWP 5019)):
#0  __GI___pthread_getspecific (key=3) at pthread_getspecific.c:30
#1  

[digikam] [Bug 388977] New: Error during upgrading core database schema from v8 to v9

[Thomas]

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

Bug ID: 388977
   Summary: Error during upgrading core database schema from v8 to
v9
   Product: digikam
   Version: 5.8.0
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Database-Mysql
  Assignee: digikam-bugs-n...@kde.org
  Reporter: thfl...@gmail.com
  Target Milestone: ---

The problem is that this syntax is obsolete since mysql 5.7. From mysql
documentation https://dev.mysql.com/doc/refman/5.6/en/alter-table.html:
> As of MySQL 5.6.17, the IGNORE clause is deprecated and its use generates a > 
> warning. IGNORE is removed in MySQL 5.7.

the required console output:
digikam.coredb: Core database: makeUpdates  8  to  9
digikam.dbengine: Failure executing query:
 "" 
Error messages: "QMYSQL: Unable to execute query" "You have an error in your
SQL syntax; check the manual that corresponds to your MySQL server version for
the right syntax to use near 'IGNORE TABLE AlbumRoots\n
   ADD UNIQUE (iden' at line 1" 1064 2 
Bound values:  ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV9" ]
Statement [ "ALTER IGNORE TABLE AlbumRoots\n   
ADD UNIQUE (identifier(127), specificPath(128)),\n 
  ENGINE InnoDB;" ]
digikam.coredb: Core database: schema update to V 9 failed!
digikam.coredb: Core database: cannot process schema initialization
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  16748412928
digikam.general: Allowing a cache size of 200 MB
QThreadStorage: Thread 0x7ff8652ab100 exited after QThreadStorage 11 destroyed

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

[krita] [Bug 388976] New: [Gradient Map Filter] color mapping issue

[David REVOY]

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

Bug ID: 388976
   Summary: [Gradient Map Filter] color mapping issue
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Filters
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Created attachment 109864
  --> https://bugs.kde.org/attachment.cgi?id=109864=edit
[Test file: a PNG with a character painted with greyscale]

Hi!

I have issue with the Gradient map filter being not really WYSIWYG in my tests.

To reproduce:
=
1. Open the test file in attachment: Spring-greyscale-painting.png
2. Open the filter: Filter > Map > Gradient Map
3. Pick a gradient in the presets (eg: GPS Fire Blueish)

Result:
===
https://www.peppercarrot.com/extras/temp/2018-01-14_screenshot_220324_net.jpg
The color of the gradient doesn't map to the picture only a low percent of the
gradient are mapped to the full artwork.

Note:
=
Reproduced on compiled source, appimage4.0beta1 ; but Wolthera couldn't
reproduce (IRC discution).

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

[gwenview] [Bug 306835] Make selecting directory in directory tree to automatically enter Browse mode

[Henrik Fehlauer]

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

--- Comment #5 from Henrik Fehlauer  ---
Thanks for looking into it.

Yup, ContextManager::currentDirUrlChanged(const QUrl&) still has the correct
URL. Seems like switching to Browse mode was never implemented explicitly for
clicking on a folder in the sidebar and this only worked because of
b55420b2ac3d's side effect, i.e. an empty selection in
MainWindow::openSelectedDocuments().

The fact that it works for slow DirListers is another indicator that currently
we rely on unpredictable timing / signal emission behaviour.

One more thing: It would be nice if clicking on the same folder you have open
in View mode would switch to Browse mode (currently it does nothing at all, see
the early return in MainWindow::openDirUrl).

I couldn't come up with anything better than your suggestion of just triggering
the switch manually. Although I wonder whether triggering the action should be
done in MainWindow::openDirUrl instead (most of the other actions are triggered
in this class). Do you want to submit a Diff or do you want me to do it?

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

[systemsettings] [Bug 388975] New: System Settings crashed when typing in upper left search box

[Bill]

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

Bug ID: 388975
   Summary: System Settings crashed when typing in upper left
search box
   Product: systemsettings
   Version: 5.11.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@notjustbill.com
  Target Milestone: ---

Application: systemsettings5 (5.11.5)

Qt Version: 5.9.3
Frameworks Version: 5.41.0
Operating System: Linux 4.10.0-42-generic x86_64
Distribution: KDE neon User Edition 5.11

-- Information about the crash:
- What I was doing when the application crashed: Searching for screen lock
settings in search box, while using remote input feature of KDEconnect from an
android device.  Able to restart System Settings and complete my search in the
same manner with no further crashes.

The crash does not seem to be reproducible.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7651c0a8c0 (LWP 25440))]

Thread 5 (Thread 0x7f761f629700 (LWP 25446)):
#0  0x7f764d90470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f764789f38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f764789f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f764e22b6cb in QEventDispatcherGlib::processEvents
(this=0x7f76180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f764e1d3e2a in QEventLoop::exec (this=this@entry=0x7f761f628ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f764dffc8f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f764c0b1d25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f764e001709 in QThreadPrivate::start (arg=0x1145570) at
thread/qthread_unix.cpp:368
#8  0x7f76497286ba in start_thread (arg=0x7f761f629700) at
pthread_create.c:333
#9  0x7f764d9103dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f76291ff700 (LWP 25445)):
#0  0x7f764dff8b49 in
std::__atomic_base::compare_exchange_strong
(__m2=std::memory_order_relaxed, __m1=std::memory_order_release, __p2=0x0,
__p1=@0x7f76291fea88: 0x1, this=0xe4d460) at
/usr/include/c++/5/bits/atomic_base.h:752
#1  std::atomic::compare_exchange_strong
(__m2=std::memory_order_relaxed, __m1=std::memory_order_release, __p2=0x0,
__p1=@0x7f76291fea88: 0x1, this=0xe4d460) at /usr/include/c++/5/atomic:462
#2  QAtomicOps::testAndSetRelease
(currentValue=, newValue=0x0, expectedValue=0x1,
_q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:299
#3  QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=, this=0xe4d460) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:264
#4  QBasicMutex::fastTryUnlock (current=, this=0xe4d460) at
thread/qmutex.h:104
#5  QMutex::unlock (this=this@entry=0xe4d460) at thread/qmutex.cpp:337
#6  0x7f764e22b5f1 in QMutexLocker::unlock (this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:213
#7  QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:207
#8  QThreadData::canWaitLocked (this=0xe4d430) at
../../include/QtCore/5.9.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253
#9  postEventSourcePrepare (s=0x7f76240012d0, timeout=0x7f76291feb14) at
kernel/qeventdispatcher_glib.cpp:259
#10 0x7f764789e91d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f764789f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f764789f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f764e22b6cb in QEventDispatcherGlib::processEvents
(this=0x7f76240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#14 0x7f764e1d3e2a in QEventLoop::exec (this=this@entry=0x7f76291fece0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#15 0x7f764dffc8f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#16 0x7f764c0b1d25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#17 0x7f764e001709 in QThreadPrivate::start (arg=0xe4d110) at
thread/qthread_unix.cpp:368
#18 0x7f76497286ba in start_thread (arg=0x7f76291ff700) at
pthread_create.c:333
#19 0x7f764d9103dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f76357fc700 (LWP 25443)):
#0  QTimerInfoList::timerWait (this=0x7f7630002ed0, tm=...) at
kernel/qtimerinfo_unix.cpp:413
#1  0x7f764e22b43e in timerSourcePrepareHelper (timeout=0x7f76357fbb04,
src=) at kernel/qeventdispatcher_glib.cpp:132
#2  timerSourcePrepare 

[KBibTeX] [Bug 387638] kbibtex for kde5 crashes at start in fc27

[Thomas Fischer]

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

Thomas Fischer  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Thomas Fischer  ---
(In reply to Amaro from comment #4)
> Figured it out. Had to remove the optional packages qoauth and qoauth-devel 
> 2.0.0-4.fc27, recompiled kbibtex for kf5 and it works.
You comment pointed me to a potential issue due to the different names of the
Qt5-based QtOAuth library on Gentoo Linux and Fedora. Please see attachment
109863 for details. Before testing this patch, please install qoauth-qt5-devel
and dependencies.

> Minor aspect is that
> installation creates a non-standard /usr/lib64/plugins directory solely for
> kbibtexpart.so even though all other plugins for qt5 are in
> /usr/lib64/qt5/plugins, had to create a symbolic link there.
The install path for the parts plugin comes from the variable
KDE_INSTALL_PLUGINDIR which is use even in core KDE apps like Dolphin's part.
I assume that official Fedora packages for KDE redefine KDE_INSTALL_PLUGINDIR
to point to /usr/lib64/qt5/plugins, whereas the default is /usr/lib64/plugins.
Simply try to set the environment variable
KDE_INSTALL_PLUGINDIR=/usr/lib64/qt5/plugins before running cmake and make.

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

[Discover] [Bug 388974] Make search field sticky

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[KBibTeX] [Bug 387638] kbibtex for kde5 crashes at start in fc27

[Thomas Fischer]

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

--- Comment #5 from Thomas Fischer  ---
Created attachment 109863
  --> https://bugs.kde.org/attachment.cgi?id=109863=edit
First check of qtoauth-qt5, only then for qtoauth

It may be an issue that during configuration (cmake phase), KBibTeX is
configured to look for the 'qtoauth' library instead of 'qtoauth-qt5'.
For some Linux distributions like Gentoo, 'qtoauth' is the Qt5 variant and
there is no Qt4 variant. For other distributions like Fedora, there exists both
a 'qtoauth' variant (Qt4) and a 'qtoauth-qt5' variant (Qt5). Just checking for
'qtoauth' as done without this patch may work in Gentoo but fail on Fedora as
it will try to make use of a Qt4-based library in a Qt5-based program (at
least, this is the working thesis).

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

[plasma4] [Bug 302015] weather widget should also show temperature when in panel

[Friedrich W . H . Kossebau]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

   Version Fixed In||5.12.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kde
   ||plasma-addons/ad04c42b28d1b
   ||197553490cb6e892e8d5f28d331
 Resolution|--- |FIXED

--- Comment #1 from Friedrich W. H. Kossebau  ---
Git commit ad04c42b28d1b197553490cb6e892e8d5f28d331 by Friedrich W. H.
Kossebau.
Committed on 14/01/2018 at 20:27.
Pushed by kossebau into branch 'master'.

[weather] Show optionally temperature next to icon in compact mode

Summary:
Adds the logic for showing an alternative component for the compact
presentation, where the temperature is shown next to the icon with the
weather status (done in flow of layout).

Adds also the matching configuration logic to allow the user to enable that
alternative display.
Related: bug 367751
FIXED-IN: 5.12.0

Reviewers: #plasma, broulik

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D9872

M  +7-0applets/weather/package/contents/config/config.qml
M  +38   -11   applets/weather/package/contents/ui/CompactRepresentation.qml
A  +115  -0applets/weather/package/contents/ui/IconAndTextItem.qml
[License: GPL (v2+)]
A  +69   -0applets/weather/package/contents/ui/configAppearance.qml
[License: GPL (v2+)]
M  +20   -2applets/weather/weatherapplet.cpp
M  +7-0applets/weather/weatherapplet.h

https://commits.kde.org/kdeplasma-addons/ad04c42b28d1b197553490cb6e892e8d5f28d331

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

[plasmashell] [Bug 367751] Add the possibility to show the temperature in the panel

[Friedrich W . H . Kossebau]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

   Version Fixed In||5.12.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kde
   ||plasma-addons/ad04c42b28d1b
   ||197553490cb6e892e8d5f28d331

--- Comment #3 from Friedrich W. H. Kossebau  ---
Git commit ad04c42b28d1b197553490cb6e892e8d5f28d331 by Friedrich W. H.
Kossebau.
Committed on 14/01/2018 at 20:27.
Pushed by kossebau into branch 'master'.

[weather] Show optionally temperature next to icon in compact mode

Summary:
Adds the logic for showing an alternative component for the compact
presentation, where the temperature is shown next to the icon with the
weather status (done in flow of layout).

Adds also the matching configuration logic to allow the user to enable that
alternative display.
Related: bug 302015
FIXED-IN: 5.12.0

Reviewers: #plasma, broulik

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D9872

M  +7-0applets/weather/package/contents/config/config.qml
M  +38   -11   applets/weather/package/contents/ui/CompactRepresentation.qml
A  +115  -0applets/weather/package/contents/ui/IconAndTextItem.qml
[License: GPL (v2+)]
A  +69   -0applets/weather/package/contents/ui/configAppearance.qml
[License: GPL (v2+)]
M  +20   -2applets/weather/weatherapplet.cpp
M  +7-0applets/weather/weatherapplet.h

https://commits.kde.org/kdeplasma-addons/ad04c42b28d1b197553490cb6e892e8d5f28d331

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

[Discover] [Bug 388974] New: Make search field sticky

[soee]

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

Bug ID: 388974
   Summary: Make search field sticky
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: kont...@soee.pl
  Target Milestone: ---

Atm. if our Discover window is small the left column content will be
scrollable. If we scroll down the content search field won't be visible. Maybe
search field could be sticky and stay always visible in the left column.

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

[Discover] [Bug 387041] "Reason" and "Change Log" are identical

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dis
   ||cover/fad964d9a0b92fbcf51d5
   ||fcbfc4de52d55b86437
   Version Fixed In||5.12.0
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #9 from Nate Graham  ---
Git commit fad964d9a0b92fbcf51d5fcbfc4de52d55b86437 by Nathaniel Graham.
Committed on 14/01/2018 at 20:25.
Pushed by ngraham into branch 'master'.

Remove redundant changeLog field

Summary:
FIXED-IN: 5.12.0

For Debian packages, PackageKit manufactures the `updateText` and `updates`
fields from the package's changelog. PackageKit gives us the `updateText` and
`updates` fields, but also includes the original text used to synthesize them
in a field called `changeLog`.

So we should only display `updateText` and `updates`, since `changeLog` is just
the the raw information used to synthesize them, and if we show it too, there's
duplicate information.

For more information about this, see
https://github.com/hughsie/PackageKit/issues/227

Test Plan:
**This change needs testing from people who are not using Debian-based distros
to make sure it didn't break anything for them!**

I tested in KDE Neon, a Debian-based distro. Before:
{F5644556}

After:
{F5644557}

Other entries still show up and are not affected.

Reviewers: apol, #discover_software_store

Reviewed By: apol, #discover_software_store

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D9850

M  +0-1libdiscover/backends/PackageKitBackend/PackageKitResource.cpp

https://commits.kde.org/discover/fad964d9a0b92fbcf51d5fcbfc4de52d55b86437

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

[krita] [Bug 388973] New: Switching from brush to eraser not working with a graphics tablet

[Lee taylor]

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

Bug ID: 388973
   Summary: Switching from brush to eraser not working with a
graphics tablet
   Product: krita
   Version: 3.3.3
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: lee.jg.tay...@hotmail.co.uk
  Target Milestone: ---

OS: Windows 10 64-bit

Tablet: Wacom Intuos 5

Krita: 3.3.3

Hello,

I have selected a brush and configured the brush settings. This works fine.

When I turn my pen upside-down to enable the eraser this does not work.

I have to select the eraser manually. 

After using the eraser I then have to select the brush manually.

I noticed this issue after installing a users brush pack. 'David Revoy- Brush
set '.

Regards,
Lee

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

[i18n] [Bug 244293] cryptic info about temperature in weather widget

[Friedrich W . H . Kossebau]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 CC||kosse...@kde.org

--- Comment #6 from Friedrich W. H. Kossebau  ---
This seems still a valid report for latest version of the Plasma Weather applet
from kdeplasma-addons.

While the po file is now to be found at kde-workspace module, so e.g. for
master
https://websvn.kde.org/trunk/l10n-kf5/pl/messages/kde-workspace/plasma_applet_org.kde.plasma.weather.po?view=markup
,
it still has "N" for "H"(igh) and "W" for "L"(ow):

250 #: package/contents/ui/TopPanel.qml:86
251 #, kde-format
252 msgctxt "High & Low temperature"
253 msgid "H: %1 L: %2"
254 msgstr "N: %1 W: %2"

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

[KBibTeX] [Bug 388892] Formatting error when saving file ( switching " and } )

[Thomas Fischer]

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

Thomas Fischer  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Thomas Fischer  ---
(In reply to Arnout Boelens from comment #0)
> Unfortunately I have not yet been able to consistently reproduce this bug,
> but every once in a while, when saving a bib file the characters " and } get
> switched around. Unfortunately when a bibtex label is written "{ label "}
> instead of "{ label }" latex does not successfully compile the document.
> I'll report back when I find how to consistently reproduce this issue.

This is the first time I hear of this problem. I am looking forward to a
concrete example case to reproduce this issue.

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

[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load

[Thomas Lübking]

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

--- Comment #124 from Thomas Lübking  ---
Impossible. nvidia and nouveau are incompatible on the kernel layer and act on
the same HW. It's no way near the optimus condition.

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

[frameworks-qqc2-desktop-style] [Bug 388941] Strange Visual Effect with Search Bar

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Ever confirmed|0   |1
  Component|discover|general
   Assignee|aleix...@kde.org|notm...@gmail.com
 Status|UNCONFIRMED |CONFIRMED
Version|unspecified |5.42.0
 CC||k...@davidedmundson.co.uk
Product|Discover|frameworks-qqc2-desktop-sty
   ||le

--- Comment #1 from Aleix Pol  ---
Correct, that's an issue in the Desktop style.

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

[frameworks-qqc2-desktop-style] [Bug 388941] Non-transparent corners in Text Field

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||aleix...@kde.org
Summary|Strange Visual Effect with  |Non-transparent corners in
   |Search Bar  |Text Field

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

[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load

[Ryein Goddard]

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

--- Comment #123 from Ryein Goddard  ---
It would be cool if we could dynamically load the nvidia binary 
driver(like nvidia prime but switching with the open and closed driver 
quickly) when ever we want so we can have the best of both worlds and 
not even worry about any of those things.  Screen tearing is probably 
the one thing I hate about KDE/Plasma right now compared with other 
solutions that for whatever reason do not have this issue.


On 01/14/2018 12:22 PM, Mahendra Tallur wrote:
> https://bugs.kde.org/show_bug.cgi?id=322060
>
> --- Comment #120 from Mahendra Tallur  ---
> Hi again,
>
> I would like to raise a different but likely connected issue :
>
> on my setup, either setting USLEEP or triple buffering does fix the tearing
> issue. With either, performance is wonderful in 3D games (1060 GTX + i3 CPU).
>
> However, what boggles me is the responsiveness and smoothness of kwin itself 
> (I
> mean the desktop : resizing windows, raising menus etc.) is inconsistent. The
> same animation can be butter smooth then the next time appears jerky. It's
> actually always happened as long as I can remember when using kwin and Nvidia
> cards.
>
> It seems slightly better with triple buffer, but as I don't want to add input
> lag in games...
>
> I kinda supposed it was a standard behaviour, but I noticed that even old
> machines with Intel HD Graphics would show a perfectly constant 60 FPS in 
> kwin.
> I tried to remove my Nvidia and use the built-in Intel HD and the desktop felt
> perfect. It even seemed to feel smoother with the Nouveau driver.
>
> I'm pretty sure all this is also related to the difficulty to work with the
> proprietary driver. As you devs are aware of the vsync issue, what's your
> opinion on the "desktop smoothness" issue ?
>
> Thanks again :-)
> Best regards & happy new year :)
>

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

[dolphin] [Bug 388611] log polluted w/ 'Empty filename passed to function'

[Henrik Fehlauer]

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

--- Comment #9 from Henrik Fehlauer  ---
I have worked on fixes for plasma-framework and kinit, will post them for
review in the next days. I think those will prevent the Plasma and startup
related occurrences.

@Michael: I'm not sure why you still get the error in Dolphin and Kate after
upgrading to KF 5.42. Did you relogin after your latest "zypper dup"? Does it
also occur on a fresh user account without any custom settings?

Try setting a breakpoint on QMessageLogger::warning in gdb and obtain a
backtrace, so we get an idea where it still fails for you. (Let me know if you
need help with that.)

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

[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load

[Thomas Lübking]

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

--- Comment #122 from Thomas Lübking  ---
Comment #120 sounds more like a client related issue anyway - resizing
(QtQuick) GL contexts is PITA - at least on nvidia but OPenGL wasn't drafted
for this behavior anyway.

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

[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load

[Martin Flöser]

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

--- Comment #121 from Martin Flöser  ---

> As you devs are aware of the vsync issue, what's your
> opinion on the "desktop smoothness" issue ?
> 
Honestly, I stopped caring about nvidia specific problems years ago. To me
Nvidia stopped to matter the day I switched my developer systems to Wayland.
They run Intel as NVIDIA doesn't support gbm. Due to that even if I wanted to,
I would not be able to install an Nvidia card and test issues.

Nowadays my opinion is that it is the choice of the consumers to decide whether
they want nvidia with all that problems or not. They as consumers can bring
nvidia to fix issues, but not we devs. Every crash in the Nvidia driver gets
closer with please report to Nvidia. If all users do, it might change
something.

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

[kwin] [Bug 388969] Active Screen Corners and Edges - toggle checkbox and schortcut

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Flöser  ---
A game normally locks the mouse and only operates with relative positions. If
your game would do that, this would be a none issue.

In general we do not expose options to workaround incorrect behavior of other
applications.

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

[kdevelop] [Bug 388972] New: Support using same class/fn/etc name in different projects

[Vitaliy]

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

Bug ID: 388972
   Summary: Support using same class/fn/etc name in different
projects
   Product: kdevelop
   Version: 5.2.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: silverunicorn2...@yandex.ru
  Target Milestone: ---

Currently, it seems to treat all non-local names session-scoped. That is
probably handy for large multi-project systems, but that also effectively
prevents working with several versions/branches of the same project in a single
session.

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

[kdevelop] [Bug 388971] New: Syntax highlighting doesn’t work sometimes

[Vitaliy]

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

Bug ID: 388971
   Summary: Syntax highlighting doesn’t work sometimes
   Product: kdevelop
   Version: 5.2.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: silverunicorn2...@yandex.ru
  Target Milestone: ---

Created attachment 109862
  --> https://bugs.kde.org/attachment.cgi?id=109862=edit
Screenshot with missing syntax highlighting.

See the screenshot.
1. Syntax (or semantic?) highlighting is absent for some functions, e.g. Lua
auxlib functions (it was absent for other Lua functions as well before some
magic that I don’t remember exactly). Autocompletion and argument list works
for them, however.
2. Those for which highlighting works are described as “Invalid type” (followed
by “Type: Function”!) in the tooltip.

There may be several reasons for that.
a. I have several versions of Lua, one in `/usr/include` and others in
subdirectories.
b. Lua uses weird syntax for functions, like
`LUALIB_API int (luaL_callmeta) (lua_State *L, int obj, const char *e);`
(notice the parentheses, like in pointer declaration).
c. Lua uses `#include` inside `extern "C"`.

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

[plasmashell] [Bug 388939] plasmashell 5.11.5 segfaults every couple of minutes

[Paul Konecny]

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

Paul Konecny  changed:

   What|Removed |Added

 CC||p...@konecny.at

--- Comment #3 from Paul Konecny  ---
Created attachment 109861
  --> https://bugs.kde.org/attachment.cgi?id=109861=edit
Backtrace with debug symbols

This is my backtrace with debug symbols for arch.
I hope this helps.
Cheers!

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

[plasmashell] [Bug 388901] Plasmashell segfaulting regularly

[Maxim Vasilchuk]

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

Maxim Vasilchuk  changed:

   What|Removed |Added

 CC|mvasilc...@gmail.com|

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

[okular] [Bug 388288] some thumbnail of pdf not shown in dolphin, some are shown

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde
   |graphics-thumbnailers/cfc2e |graphics-thumbnailers/4530c
   |2c32b5525691b5ba1b6eaf91071 |07cb53263d95600e4249074049b
   |e4a0c8be|bf07e1ac

--- Comment #10 from Albert Astals Cid  ---
Git commit 4530c07cb53263d95600e4249074049bbf07e1ac by Albert Astals Cid.
Committed on 14/01/2018 at 18:52.
Pushed by aacid into branch 'master'.

gs thumbnailer: Make it work when gs spits out warning messages

Reviewers: #kde_applications, #dolphin, elvisangelaccio

Reviewed By: elvisangelaccio

Subscribers: elvisangelaccio, ngraham

Differential Revision: https://phabricator.kde.org/D9834

M  +13   -2ps/gscreator.cpp

https://commits.kde.org/kdegraphics-thumbnailers/4530c07cb53263d95600e4249074049bbf07e1ac

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

[okular] [Bug 388288] some thumbnail of pdf not shown in dolphin, some are shown

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kde
   ||graphics-thumbnailers/cfc2e
   ||2c32b5525691b5ba1b6eaf91071
   ||e4a0c8be
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #9 from Albert Astals Cid  ---
Git commit cfc2e2c32b5525691b5ba1b6eaf91071e4a0c8be by Albert Astals Cid.
Committed on 14/01/2018 at 18:51.
Pushed by aacid into branch 'Applications/17.12'.

gs thumbnailer: Make it work when gs spits out warning messages

Reviewers: #kde_applications, #dolphin, elvisangelaccio

Reviewed By: elvisangelaccio

Subscribers: elvisangelaccio, ngraham

Differential Revision: https://phabricator.kde.org/D9834

M  +13   -2ps/gscreator.cpp

https://commits.kde.org/kdegraphics-thumbnailers/cfc2e2c32b5525691b5ba1b6eaf91071e4a0c8be

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

[korganizer] [Bug 358106] [REGRESSION] Allow week to start on Monday

[davidblunkett]

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

davidblunkett  changed:

   What|Removed |Added

 CC||dav1dblunk...@hotmail.com

--- Comment #15 from davidblunkett  ---
Still a problem in 5.5.3 - I wish to start the week on Sunday but can't and
I've no wish to change my regional settings to a foreign country to acheive
this (even if I knew how).

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

[korganizer] [Bug 374803] How to change start of the week from Monday to Sunday?

[davidblunkett]

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

--- Comment #10 from davidblunkett  ---
Still can't appear to do this in v5.5.3.

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

[korganizer] [Bug 388850] Error whiloe trying to modify calender item [llconflict]

[davidblunkett]

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

davidblunkett  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|FIXED   |---

--- Comment #2 from davidblunkett  ---
I can confirm this problem is _still_ here in v5.5.3.

Same error llconflict if I make changes in the dialogue if I have previously
pressed "apply"

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

[korganizer] [Bug 388849] korganizer has problems syncing with google calender

[davidblunkett]

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

davidblunkett  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from davidblunkett  ---
I can confirm that upgrading to v5.5.3 has fixed this problem - thanks

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

[plasmashell] [Bug 388970] Plasma panel crashes when trying to add wiget

[David Edmundson]

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

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 381630 ***

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

[plasmashell] [Bug 381630] Crash in wl_proxy_create_wrapper in QtWayland after window destruction

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||espe...@junta.no

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

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

[plasmashell] [Bug 388901] Plasmashell segfaulting regularly

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||adne...@live.com

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

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

[plasmashell] [Bug 386356] Memory usage widget crashes plasmashell process.

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

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


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

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

[plasmashell] [Bug 388924] Plasmashell crasshing

[David Edmundson]

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

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 388901 ***

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

[plasmashell] [Bug 388901] Plasmashell segfaulting regularly

[David Edmundson]

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

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

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

[plasmashell] [Bug 388901] Plasmashell segfaulting regularly

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||tesfab...@gmail.com

--- Comment #9 from Antonio Rojas  ---
*** Bug 388965 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 388965] Plasmashell crashes randomly

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||aro...@archlinux.org

--- Comment #2 from Antonio Rojas  ---


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

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

[plasmashell] [Bug 388970] New: Plasma panel crashes when trying to add wiget

[Espen Fossen]

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

Bug ID: 388970
   Summary: Plasma panel crashes when trying to add wiget
   Product: plasmashell
   Version: 5.11.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: espe...@junta.no
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.5)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.9-1-macbook x86_64
Distribution: "Arch Linux"

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

* Open laptop after suspend
* Unlock user (allready logged inn Wayland session)
* Unlock Widgets on main Plasma panel
* Click hamburger menu 
* Click add Widgets, and then i crashes.

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

Thread 21 (Thread 0x7f19df3fe700 (LWP 7155)):
[KCrash Handler]
#5  0x7f1ae938ec81 in wl_proxy_create_wrapper () at
/usr/lib/libwayland-client.so.0
#6  0x7f1a479ce36d in  () at /usr/lib/libEGL_mesa.so.0
#7  0x7f1a479bb7cf in  () at /usr/lib/libEGL_mesa.so.0
#8  0x7f1ad0499792 in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#9  0x7f1ad0497c3e in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#10 0x7f1aeb5b4a19 in QOpenGLContext::makeCurrent(QSurface*) () at
/usr/lib/libQt5Gui.so.5
#11 0x7f1aee9cab86 in  () at /usr/lib/libQt5Quick.so.5
#12 0x7f1aee9d2846 in  () at /usr/lib/libQt5Quick.so.5
#13 0x7f1aee9d1a5b in  () at /usr/lib/libQt5Quick.so.5
#14 0x7f1aee9d1e54 in  () at /usr/lib/libQt5Quick.so.5
#15 0x7f1aeab8eb2d in  () at /usr/lib/libQt5Core.so.5
#16 0x7f1ae9d4408c in start_thread () at /usr/lib/libpthread.so.0
#17 0x7f1aea496e1f in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f19d700 (LWP 7154)):
#0  0x7f1ae9d4a39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1aeab9000c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1aee9d19ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1aee9d1e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1aeab8eb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1ae9d4408c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1aea496e1f in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f19f172c700 (LWP 7153)):
#0  0x7f1aea48c91b in poll () at /usr/lib/libc.so.6
#1  0x7f1ae4d38053 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1ae4d3816e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f1aeadd76b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f1aead7982b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f1aeab8978e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f1aedd93a19 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f1aeab8eb2d in  () at /usr/lib/libQt5Core.so.5
#8  0x7f1ae9d4408c in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f1aea496e1f in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f19f1f2d700 (LWP 7149)):
#0  0x7f1ae9d4a6dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1aeab8fec1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1aeab8bd91 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f1aeab8eb2d in  () at /usr/lib/libQt5Core.so.5
#4  0x7f1ae9d4408c in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f1aea496e1f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f1a193fb700 (LWP 7148)):
#0  0x7f1ae9d4a6dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1aeab8fec1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1aeab8bd91 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f1aeab8eb2d in  () at /usr/lib/libQt5Core.so.5
#4  0x7f1ae9d4408c in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f1aea496e1f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f1a188fa700 (LWP 7119)):
#0  0x7f1ae9d4a39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1aeab9000c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1aee9d19ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1aee9d1e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1aeab8eb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1ae9d4408c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1aea496e1f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f19f36fe700 (LWP 

[konsole] [Bug 387808] When session is restored, hidden menubars become visible

[Kurt Hindenburg]

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

--- Comment #1 from Kurt Hindenburg  ---
command line options are not restored - is there any reason you're not using
configure konsole->General->Show menubar by default?

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

[konsole] [Bug 388003] Application crash when changing KDE theme

[Kurt Hindenburg]

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

--- Comment #4 from Kurt Hindenburg  ---
I little concerning that you're able to download/change to a non working theme.

Should this be closed or reassigned to another group?

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

[konsole] [Bug 387833] konsole scrollback functionality often vanishes

[Kurt Hindenburg]

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

--- Comment #1 from Kurt Hindenburg  ---
Do you have the ability to try a later Konsole version?  Also have you changed
the scrollback option?

The 2GB issue was fixed in 17.08 - are you hitting that limit?

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