[systemsettings] [Bug 357688] New: DPI is always reported to 96 on High Res Display

[Kai-Uwe Behrmann via KDE Bugzilla]

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

Bug ID: 357688
   Summary: DPI is always reported to 96 on High Res Display
   Product: systemsettings
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_fonts
  Assignee: unassigned-b...@kde.org
  Reporter: k...@gmx.de
CC: unassigned-b...@kde.org

The plasma 5 systemsettings fontsettings panel has a checkbox for forcing a DPI
value for fonts and a accompanying DPI value field. So far so good.

On a MacBook-pro with retina display this field is always set to 96 DPI, which
is wrong. This setting forces me to adjust the value manually to 192 doubling
the size to obtain a reasonable desktop. The correct physical DPI value is 227.

After some research for other non Qt based applications, I found that 96 is
always reported by Xinerama on this machine, with all other values like size
and so on computed to match 96 DPI. However XRandR reports the size in
millimeter correctly. Based on this information and the desktops pixel size,
the DPI can be computed correctly.

Reproducible: Always

Steps to Reproduce:
1. install KDE Plasma 5 on MacBookPro Retina
2. see the too small desktop windows rendering
3. go to systemsettings -> font settings -> force DPI box

Actual Results:  
see 96 DPI in the fonts force DPI value box

Expected Results:  
see the xrandr reported DPI value in the fonts force DPI value box

// Here some code showing the correct DPI values by using the XRandR API.
// Hope this helps.
// cc -Wall -g -pedantic XRandRfl.cxx -o XRandRfl -lX11 `pkg-config --libs
xrandr`
#include 
#include 

int main(int argc, char ** argv)
{
  Display * display = XOpenDisplay(":0.0");
  int screen = DefaultScreen( display );
  Window w = RootWindow(display, screen);
  XRRScreenResources * res = XRRGetScreenResources(display, w);
  for(int i=0; i < res->noutput; ++i)
  {
XRROutputInfo * output_info = XRRGetOutputInfo( display, res,
res->outputs[i]);
if(output_info->crtc)
{
  XRRCrtcInfo * crtc_info = XRRGetCrtcInfo( display, res,
output_info->crtc );
  unsigned int pixel_width = crtc_info->width,
   pixel_height = crtc_info->height;
  float xdpi = pixel_width * 25.4f / (float)output_info->mm_width,
ydpi = pixel_height * 25.4f / (float)output_info->mm_height;
  printf( "[%d] %upx x %upx  Dimensions: %limm x %limm  DPI: %.02f x
%.02f\n",
  i, pixel_width, pixel_height,
  output_info->mm_width, output_info->mm_height,
  xdpi, ydpi );
}
XRRFreeOutputInfo( output_info );
  }
  XRRFreeScreenResources(res);
  XCloseDisplay( display );

  return 0;
}

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

[plasmashell] [Bug 356727] panel disappears when dragging it to other monitor

[Iven Hsu via KDE Bugzilla]

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

Iven Hsu  changed:

   What|Removed |Added

 CC||ive...@gmail.com

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

[systemsettings] [Bug 357689] New: Automatically start searching when given user input

[Paulo Fidalgo via KDE Bugzilla]

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

Bug ID: 357689
   Summary: Automatically start searching when given user input
   Product: systemsettings
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: paulo.fidalgo...@gmail.com

When I open the system settings it would be great if I start typing and it
automatically search for items.

This could be done by setting the autofocus in the search bar I supose.

Also there's a missing shortcut to search.

Reproducible: Always

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

[systemsettings] [Bug 357688] DPI is always reported to 96 on High Res Display

[Kai-Uwe Behrmann via KDE Bugzilla]

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

Kai-Uwe Behrmann  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

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

[step] [Bug 357690] New: Anchor

[Stergios Nastopoulos via KDE Bugzilla]

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

Bug ID: 357690
   Summary: Anchor
   Product: step
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ks.vladi...@gmail.com
  Reporter: ste...@ath.forthnet.gr

Anchor object looks like a big red square on the screen, covering the objects
underneath

Reproducible: Always

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

[akregator] [Bug 114397] akregator does not start automatically when kontact starts

[Daniel Hornung via KDE Bugzilla]

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

Daniel Hornung  changed:

   What|Removed |Added

  Component|general |kontact plugin
 CC||daniel.horn...@gmx.de

--- Comment #14 from Daniel Hornung  ---
Still confirmed in Kontact/Akregator 4.14.10, Debian Testing.

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

[kmail2] [Bug 357681] KMail crashed when trying to drag-select list of recent addresses in Settings dialog

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
I can't reproduce but 4.14.1 is a very old version.
Could you re-test on new version ? (last version is 4.14.11 or 5.1.1)

Thanks

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

[konsole] [Bug 357063] New konsole uses desktop for background; echoing command input/out NOT displaying

[Jaroslav Reznik via KDE Bugzilla]

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

Jaroslav Reznik  changed:

   What|Removed |Added

 CC||jrez...@redhat.com

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

[konsole] [Bug 356223] konsole crashes when external monitor is unplugged

[brancaleone via KDE Bugzilla]

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

brancaleone  changed:

   What|Removed |Added

 CC||cedric.devill...@gmail.com

--- Comment #1 from brancaleone  ---
I can confirm the same issue. also on opensuse Leap 42.1 and packages from
KDE:Frameworks5.
Framework version is 5.17 and plasma is 5.5.2

I also noted that a running program in one of the konsole session (weechat irc
client) is still running after konsole "crash".

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

[kio] [Bug 356227] Dolphin in plasma 5 doesn't have thumbnails for .kra, .ora, .psd files

[Raghavendra kamath via KDE Bugzilla]

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

--- Comment #6 from Raghavendra kamath  ---
Boudewijn Rempt, has upstreamed the krita and ora thumbnailers , you can see
the review request here -> https://git.reviewboard.kde.org/r/126674/ and here->
https://git.reviewboard.kde.org/r/126675/

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

[systemsettings] [Bug 357688] DPI is always reported to 96 on High Res Display

[Kai-Uwe Behrmann via KDE Bugzilla]

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

Kai-Uwe Behrmann  changed:

   What|Removed |Added

 CC||k...@gmx.de

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

[ktorrent] [Bug 357691] New: In List of active downloads: If i select several downloads, Right-Mouse-Properties, Change Location after finished: the finished downloads are still stored in the old loca

[peter via KDE Bugzilla]

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

Bug ID: 357691
   Summary: In List of active downloads: If i select several
downloads, Right-Mouse-Properties, Change Location
after finished: the finished downloads are still
stored in the old location !!
   Product: ktorrent
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: swift6...@gmail.com

Reproducible: Always

Steps to Reproduce:
1. In List of active downloads: Select several downloads
2. Right-Mouse-Properties
3. Change Location after finished


Actual Results:  
the finished downloads are still stored in the OLD location !!

Expected Results:  
store the downloaded files in the NEW location

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

[ktorrent] [Bug 357691] In List of active downloads: If i select several downloads, Right-Mouse-Properties, Change Location after finished: the finished downloads are still stored in the old location

[peter via KDE Bugzilla]

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

peter  changed:

   What|Removed |Added

 CC||swift6...@gmail.com

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

[plasmashell] [Bug 357703] Mouse hover does not show any popup dialogs

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #5 from Martin Klapetek  ---
Ok, can you also please check

System Settings -> Workspace/Desktop Behaviour -> Workspace/Workspace Behaviour
-> Show Informational Tips

..if that is enabled?

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

[kdevplatform] [Bug 356826] EnvironmentWidget: Support cloning existing environment

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/57801dfb75d5e8b705
   ||a0d6e37af8f1a72aeb7af3
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Kevin Funk  ---
Git commit 57801dfb75d5e8b705a0d6e37af8f1a72aeb7af3 by Kevin Funk, on behalf of
Mikhail Ivchenko.
Committed on 08/01/2016 at 19:02.
Pushed by kfunk into branch '5.0'.

EnvironmentWidget: Add support for cloning envs
FIXED-IN: 5.0.0

Test Plan: Tests passed. Button works as expected.

Reviewers: kfunk

Reviewed By: kfunk

Subscribers: kdevelop-devel

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

M  +15   -0shell/settings/environmentgroupmodel.cpp
M  +1-0shell/settings/environmentgroupmodel.h
M  +17   -0shell/settings/environmentwidget.cpp
M  +1-0shell/settings/environmentwidget.h
M  +7-0shell/settings/environmentwidget.ui

http://commits.kde.org/kdevplatform/57801dfb75d5e8b705a0d6e37af8f1a72aeb7af3

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

[trojita] [Bug 357678] Hide MIME type tab bar when only one option exists

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #6 from Thomas Lübking  ---
Depends.
If that's limited to one sender: likely.

Otherwise it might be a bug in the IMAP server (I took your concern as
indicator that this happens on a more regular base. If I get malformatted spam,
I don't care. It's going /dev/null - malformatted or not ;-)

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[Dotan Cohen via KDE Bugzilla]

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

Dotan Cohen  changed:

   What|Removed |Added

 CC||kde-2011...@dotancohen.com

--- Comment #61 from Dotan Cohen  ---
It seems like this bug could be split into two feature requests:

1) About 75% of the people here, including the OP, seem to be asking for ISO
8601 support*. This specifies, among other things, a date format of -MM-DD.

2) About 25% of the people here seem to be asking for freely-configurable date,
time, and other locale items support.

In my opinion, this bug should concentrate on adding ISO 8601 support, and
another bug should be opened for freely-configurable locale support.

* https://en.wikipedia.org/wiki/ISO_8601

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

[plasmashell] [Bug 357703] Mouse hover does not show any popup dialogs

[Raman Gupta via KDE Bugzilla]

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

--- Comment #4 from Raman Gupta  ---
(In reply to Martin Klapetek from comment #3)
> Ok; do you use multi-screen setup?

Yes. Three monitors.

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

[plasmashell] [Bug 357703] Mouse hover does not show any popup dialogs

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

   Assignee|mklape...@kde.org   |k...@davidedmundson.co.uk
  Component|Digital Clock   |general
 CC||bhus...@gmail.com

--- Comment #3 from Martin Klapetek  ---
Ok; do you use multi-screen setup?

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

[systemsettings] [Bug 357705] New: Collapsing of the Date and Time Setting Panel after having made a change

[via KDE Bugzilla]

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

Bug ID: 357705
   Summary: Collapsing of the Date and Time Setting Panel after
having made a change
   Product: systemsettings
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: sanga...@gmail.com

Application: kcmshell4 (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-38-generic x86_64
Distribution: Linux Mint 17.2 Rafaela

-- Information about the crash:
- What I was doing when the application crashed: I tried to change the look of
my digital date and time
Meanwhile the Browser was open (Mozilla Firefox) and I was copying file from my
external HDD to my laptop.

The crash does not seem to be reproducible.

-- Backtrace:
Application: KDE beállítómodul (kcmshell4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f74d1dae7c0 (LWP 22434))]

Thread 3 (Thread 0x7f74b01f5700 (LWP 22538)):
#0  0x7f74d16e312d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f74cc2a4fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f74cc2a530a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f74b06fe336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f74cc2c9f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f74ccdd0182 in start_thread (arg=0x7f74b01f5700) at
pthread_create.c:312
#6  0x7f74d16f047d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f74aed55700 (LWP 22539)):
#0  __tls_get_addr (ti=0x7f74d0632a50) at dl-tls.c:772
#1  0x7f74d01ca044 in get_thread_data () at thread/qthread_unix.cpp:188
#2  QThreadData::current () at thread/qthread_unix.cpp:219
#3  0x7f74d02faaf5 in postEventSourcePrepare (s=0x7f74a0001350,
timeout=0x7f74aed54c24) at kernel/qeventdispatcher_glib.cpp:263
#4  0x7f74cc2a468d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f74cc2a4f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f74cc2a50ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f74d02fa7be in QEventDispatcherGlib::processEvents
(this=0x7f74a8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#8  0x7f74d02cc0af in QEventLoop::processEvents
(this=this@entry=0x7f74aed54de0, flags=...) at kernel/qeventloop.cpp:149
#9  0x7f74d02cc3a5 in QEventLoop::exec (this=this@entry=0x7f74aed54de0,
flags=...) at kernel/qeventloop.cpp:204
#10 0x7f74d01c8c5f in QThread::exec (this=this@entry=0x29b6290) at
thread/qthread.cpp:537
#11 0x7f74d02ad823 in QInotifyFileSystemWatcherEngine::run (this=0x29b6290)
at io/qfilesystemwatcher_inotify.cpp:265
#12 0x7f74d01cb32f in QThreadPrivate::start (arg=0x29b6290) at
thread/qthread_unix.cpp:349
#13 0x7f74ccdd0182 in start_thread (arg=0x7f74aed55700) at
pthread_create.c:312
#14 0x7f74d16f047d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f74d1dae7c0 (LWP 22434)):
[KCrash Handler]
#6  0x028deb50 in ?? ()
#7  0x7f74d02e2a69 in QObject::connect (sender=sender@entry=0x2becb00,
signal=0x7f74d03a796d "timeout()", signal@entry=0x7f74d03a796c "2timeout()",
receiver=receiver@entry=0x24cc5e0, method=0x7f74c0509efd "load()",
method@entry=0x7f74c0509efc "1load()", type=Qt::AutoConnection,
type@entry=Qt::AutoCompatConnection) at kernel/qobject.cpp:2583
#8  0x7f74d02ea98c in QSingleShotTimer::QSingleShotTimer (this=0x2becb00,
msec=5000, receiver=0x24cc5e0, member=0x7f74c0509efc "1load()") at
kernel/qtimer.cpp:300
#9  0x7f74d02eaa4e in QTimer::singleShot (msec=msec@entry=5000,
receiver=receiver@entry=0x24cc5e0, member=member@entry=0x7f74c0509efc
"1load()") at kernel/qtimer.cpp:363
#10 0x7f74c0508e73 in KclockModule::save (this=0x24cc5e0) at
../../../kcontrol/dateandtime/main.cpp:113
#11 0x7f74d13d8327 in KCModuleProxy::save (this=this@entry=0x243d770) at
../../kutils/kcmoduleproxy.cpp:280
#12 0x7f74d13d45a8 in KCMultiDialogPrivate::apply (this=) at
../../kutils/kcmultidialog.cpp:300
#13 0x7f74d02e187a in QMetaObject::activate (sender=0x242ebd0,
m=m@entry=0x7f74d13a78a0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe61ff4b00)
at kernel/qobject.cpp:3539
#14 0x7f74d1054aff in KPushButton::authorized (this=,
_t1=0x246add0) at ./kpushbutton.moc:142
#15 0x7f74d02e187a in QMetaObject::activate (sender=sender@entry=0x242ebd0,
m=m@entry=0x7f74d013a2a0 ,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe61ff4c30)
at kernel/qobject.cpp:3539
#16 0x7f74cfcb5172 in QAbstractButton::clicked 

[plasmashell] [Bug 356994] Task manager shows windows from wrong screen or not at all in dual monitor setup

[Florian Sievert via KDE Bugzilla]

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

Florian Sievert  changed:

   What|Removed |Added

 CC||ca...@phobeus.de

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

[kdenlive] [Bug 356643] "Clip Properties" shows properties for proxy instead of the clip, when clip is proxied

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 356643] "Clip Properties" shows properties for proxy instead of the clip, when clip is proxied

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

   Version Fixed In||15.12

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

[kdenlive] [Bug 353019] Chroma key effect not working -- leaving burned image of keyed clip in monitor

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|15.11.80 - "Blue Screen"|Chroma key effect not
   |effect not working --   |working -- leaving burned
   |leaving burned image of |image of keyed clip in
   |keyed clip in monitor   |monitor

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

[kdenlive] [Bug 351512] Freeze when importing clips without a clip monitor

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #6 from Jean-Baptiste Mardelle  ---
Git commit c547b82146c55683ae69f1aecee437a6f4d8057f by Jean-Baptiste Mardelle.
Committed on 08/01/2016 at 17:46.
Pushed by mardelle into branch 'master'.

Attempt to fix freeze when clip monitor is disabled

M  +4-1src/monitor/monitor.cpp
M  +4-0src/renderer.cpp

http://commits.kde.org/kdenlive/c547b82146c55683ae69f1aecee437a6f4d8057f

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

[trojita] [Bug 357676] HTML-only email rendered as plain text

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #4 from Thomas Lübking  ---
No.
You can try to grep the relevant data from the full log, but you won't like
doing that.

What's the problem about adding a subdir, copy the mail there, open the dir,
dump the log and then removing the dir again? That's not nearly as troublesome.

I assume Jan requires it to figure whether trojita messes network replies or
the server returns the html part as text/plain.
I'd expect the latter and the question is then whether trojita would better
post-inspect the content-type field to "fix" that - however, there's no point
in doing that if there's actually a bug in reply handling, so please provide
the log data.

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

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

[Alvin via KDE Bugzilla]

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

Alvin  changed:

   What|Removed |Added

 CC||i...@alvin.be

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

[plasmashell] [Bug 357703] Wording of "Workspace Behavior, Show Informational Tips" ambiguous

[Raman Gupta via KDE Bugzilla]

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

Raman Gupta  changed:

   What|Removed |Added

   Severity|normal  |task
Summary|Mouse hover does not show   |Wording of "Workspace
   |any popup dialogs   |Behavior, Show
   ||Informational Tips"
   ||ambiguous

--- Comment #6 from Raman Gupta  ---
(In reply to Martin Klapetek from comment #5)
> System Settings -> Workspace/Desktop Behaviour -> Workspace/Workspace
> Behaviour -> Show Informational Tips

Ah, well that fixed it.

I remember turning that off because the wording sounded like it was
tutorial-type stuff like when one is first starting to learn KDE ("tips"). I
didn't notice any immediate difference from turning it off so I left it off and
subsequently forgot about it.

I guess "informational tips" is supposed to be a nicer way to say "tooltips"
but "tips" as a separate word means something other than what tooltip means.

Some additional explanation in that dialog about what "informational tips" are
would be useful.

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

[plasmashell] [Bug 357703] Wording of "Workspace Behavior, Show Informational Tips" ambiguous

[Raman Gupta via KDE Bugzilla]

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

--- Comment #7 from Raman Gupta  ---
And: why would *anyone* want to turn that off anyway?? i.e. why is that even an
option?

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

[plasmashell] [Bug 356994] Task manager shows windows from wrong screen or not at all in dual monitor setup

[Florian Sievert via KDE Bugzilla]

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

--- Comment #2 from Florian Sievert  ---
I am also observing this issue on my dual head setting on a Fedora 23 system
with latest updates (KF 5.18, plasma 5.5.1). The filter for the screen seems to
be completely ignored for the second screen. When I am moving a firefox task
from the first screen to the second one, it is disappearing from the task bar
on the first screen. (expected). If I move it back to the first screen, it is
still shown on the second, but added to the first. This is making the feature
totally broken currently.

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

[kdevplatform] [Bug 356825] EnvironmentWidget: Support editing existing environment

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/99793ab082e85bc0fd
   ||1a2d09f41882dfb12fbc07
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.0.0

--- Comment #1 from Kevin Funk  ---
Git commit 99793ab082e85bc0fd1a2d09f41882dfb12fbc07 by Kevin Funk, on behalf of
Sergey Popov.
Committed on 08/01/2016 at 18:39.
Pushed by kfunk into branch '5.0'.

Add feature to edit existing environment group
FIXED-IN: 5.0.0

Test Plan: Tests passed and implemented feature works as expected.

Reviewers: kfunk

Subscribers: kdevelop-devel

Projects: #kdevelop

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

M  +3-3shell/settings/environmentgroupmodel.cpp
M  +5-0shell/settings/environmentgroupmodel.h
M  +12   -5shell/settings/environmentwidget.cpp
M  +1-1shell/settings/environmentwidget.h
M  +2-2shell/settings/environmentwidget.ui

http://commits.kde.org/kdevplatform/99793ab082e85bc0fd1a2d09f41882dfb12fbc07

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[Ancoron via KDE Bugzilla]

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

--- Comment #62 from Ancoron  ---
I would agree to that, but don't forget the ISO-8601 time format.

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

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

[RJVB via KDE Bugzilla]

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

--- Comment #10 from RJVB  ---
I've got the log, but a priori it just shows a crash while dlopen'ing
kdevclangsupport without any further explanation as to what the gdb backtrace
above already shows.

I rebuilt kdevclangsupport against the clang 3.5.1 version I grabbed from
Debian/Exp. a year ago and built via a PPA of my own. And that one seems to
work, contrary to Ubuntu's current 3.6.0 release and both the 3.6.2 and the
3.7.1 builds from the LLVM apt servers. Those last 2 fail in the same way,
which leads me to think it must be some incompatibility in the way they build
their stuff and I built KF5/KDevelop.
This particular issue is too resource demanding to continue to look into it.
I'll see if I can reproduce the crash-on-exit issue, now that I managed to work
around the crash-on-startup :)

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

[skrooge] [Bug 356391] For 2.2.0, Operations Date field format does not follow Skrooge Date configuration setting

[Stephane MANKOWSKI via KDE Bugzilla]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|ASSIGNED|RESOLVED

--- Comment #1 from Stephane MANKOWSKI  ---
Hi,

I can't fix this because with the date format options, we can have following
dates:
31/12/2015  => OK. Not problem to parse this kind of
date
Jeudi 31 décembre 2015  => KO. I don't know how to parse this kind of date. And
do you really want to enter dates in this format?
Yesterday  => KO
2015/31/12 => OK but not aligned with the partial date
entering (example: 12 for the previous 12, 30/12 for the previous 30 of
December)

That's why I won't fix this bug.
The option in settings is only for "Display". Not for entering.

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

[konqueror] [Bug 357711] New: konqueror crashed -- session autosave related [QPointer::operator->]

[Raúl via KDE Bugzilla]

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

Bug ID: 357711
   Summary: konqueror crashed -- session autosave related
[QPointer::operator->]
   Product: konqueror
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: rasas...@gmail.com

Application: konqueror (4.14.13)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.3.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

I opened konqueror from krunner. Iit restored a previously saved session. I
always kill konqueror so session is saved. The session is quite big with a ~15
tabs window and another singled tab window.
After the session was successfully restored konqueror "idled"* in the
background for some minutes and it crashed.
* I say idled but it actually takes some CPU as some opened webs require
javascript running in background
I have had some other similar crashed also related with autosave but
unfortunately I'm unable to explain how they are reproduced.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f92a7262900 (LWP 7333))]

Thread 6 (Thread 0x7f9285604700 (LWP 7735)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f928af18a4d in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f928b9a3514 ) at
/build/qtwebkit-B2cRei/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/FastMalloc.cpp:2575
#2  0x7f928af18aa9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0x7f928b9a3514 ) at
/build/qtwebkit-B2cRei/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/FastMalloc.cpp:1771
#3  0x7f929fde6284 in start_thread (arg=0x7f9285604700) at
pthread_create.c:333
#4  0x7f92a6b8774d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f9244602700 (LWP 7757)):
#0  0x7f92a6b7e86d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f929f70c1cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f929f70c2dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f92a45b93a6 in QEventDispatcherGlib::processEvents
(this=0x7f923c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x7f92a45872e1 in QEventLoop::processEvents
(this=this@entry=0x7f9244601cd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f92a4587655 in QEventLoop::exec (this=this@entry=0x7f9244601cd0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f92a4476559 in QThread::exec (this=) at
thread/qthread.cpp:538
#7  0x7f92a4478e4c in QThreadPrivate::start (arg=0x1be0d70) at
thread/qthread_unix.cpp:352
#8  0x7f929fde6284 in start_thread (arg=0x7f9244602700) at
pthread_create.c:333
#9  0x7f92a6b8774d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f92430ac700 (LWP 7787)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f92a4479394 in QWaitConditionPrivate::wait (time=3,
this=0x1e77be0) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=this@entry=0x1f04f00,
mutex=mutex@entry=0x1e86848, time=3) at thread/qwaitcondition_unix.cpp:158
#3  0x7f92a446bff7 in QThreadPoolThread::run (this=0x1f04ef0) at
concurrent/qthreadpool.cpp:142
#4  0x7f92a4478e4c in QThreadPrivate::start (arg=0x1f04ef0) at
thread/qthread_unix.cpp:352
#5  0x7f929fde6284 in start_thread (arg=0x7f92430ac700) at
pthread_create.c:333
#6  0x7f92a6b8774d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f924246e700 (LWP 7801)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f928ac3c191 in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x7f9284d73398) at
/build/qtwebkit-B2cRei/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x7f928af48fe6 in WTF::wtfThreadEntryPoint (param=0x1fa8be0) at
/build/qtwebkit-B2cRei/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x7f929fde6284 in start_thread (arg=0x7f924246e700) at
pthread_create.c:333
#4  0x7f92a6b8774d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f9241532700 (LWP 7826)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f92a4479394 in QWaitConditionPrivate::wait (time=3,
this=0x1e6d5d0) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait 

[dolphin] [Bug 357712] New: Dolphin sometimes crashes when right-clicking icons

[Jesse Talavera-Greenberg via KDE Bugzilla]

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

Bug ID: 357712
   Summary: Dolphin sometimes crashes when right-clicking icons
   Product: dolphin
   Version: 15.08.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: jessetalav...@aol.com

Application: dolphin (15.08.2)

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

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

Testing out a custom service menu.  Also crashes when I try to configure it
under Configure Dolphin

- Custom settings of the application:

Custom service menu

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb686c3c800 (LWP 5747))]

Thread 4 (Thread 0x7fb67a63e700 (LWP 5778)):
#0  0x7fb6995f98dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb6903961ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb6903962fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb69466b50b in QEventDispatcherGlib::processEvents
(this=0x7fb6740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fb69461250a in QEventLoop::exec (this=this@entry=0x7fb67a63ddc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fb69442eac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fb694433a6e in QThreadPrivate::start (arg=0x1d017d0) at
thread/qthread_unix.cpp:331
#7  0x7fb690acc6aa in start_thread (arg=0x7fb67a63e700) at
pthread_create.c:333
#8  0x7fb699604eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fb67962f700 (LWP 5783)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7fb694434c46 in QWaitConditionPrivate::wait_relative (time=3,
this=0x1e0fed0) at thread/qwaitcondition_unix.cpp:126
#2  QWaitConditionPrivate::wait (time=3, this=0x1e0fed0) at
thread/qwaitcondition_unix.cpp:134
#3  QWaitCondition::wait (this=this@entry=0x1e10550,
mutex=mutex@entry=0x1e10480, time=3) at thread/qwaitcondition_unix.cpp:208
#4  0x7fb6944306f3 in QThreadPoolThread::run (this=0x1e10540) at
thread/qthreadpool.cpp:127
#5  0x7fb694433a6e in QThreadPrivate::start (arg=0x1e10540) at
thread/qthread_unix.cpp:331
#6  0x7fb690acc6aa in start_thread (arg=0x7fb67962f700) at
pthread_create.c:333
#7  0x7fb699604eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fb678e2e700 (LWP 5784)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7fb694434c46 in QWaitConditionPrivate::wait_relative (time=3,
this=0x213b240) at thread/qwaitcondition_unix.cpp:126
#2  QWaitConditionPrivate::wait (time=3, this=0x213b240) at
thread/qwaitcondition_unix.cpp:134
#3  QWaitCondition::wait (this=this@entry=0x1df6470,
mutex=mutex@entry=0x1e10480, time=3) at thread/qwaitcondition_unix.cpp:208
#4  0x7fb6944306f3 in QThreadPoolThread::run (this=0x1df6460) at
thread/qthreadpool.cpp:127
#5  0x7fb694433a6e in QThreadPrivate::start (arg=0x1df6460) at
thread/qthread_unix.cpp:331
#6  0x7fb690acc6aa in start_thread (arg=0x7fb678e2e700) at
pthread_create.c:333
#7  0x7fb699604eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb686c3c800 (LWP 5747)):
[KCrash Handler]
#6  QBasicAtomicPointer::load
(this=0x6a) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:254
#7  QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x1f81d20)
at tools/qsharedpointer.cpp:1330
#8  0x7fb6951772d5 in QWeakPointer::QWeakPointer
(ptr=0x1f81d20, this=) at
../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:696
#9  QWeakPointer::assign (ptr=0x1f81d20, this=0x7fb69564bb00
) at
../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:692
#10 QPointer::operator= (p=0x1f81d20, this=0x7fb69564bb00
) at
../../include/QtCore/../../src/corelib/kernel/qpointer.h:67
#11 QWidgetWindow::handleMouseEvent (this=this@entry=0x1ec6fb0,
event=event@entry=0x7ffdb435ea70) at kernel/qwidgetwindow.cpp:453
#12 0x7fb69517952b in QWidgetWindow::event (this=0x1ec6fb0,
event=0x7ffdb435ea70) at kernel/qwidgetwindow.cpp:210
#13 0x7fb6951199dc in QApplicationPrivate::notify_helper
(this=this@entry=0x1751f10, receiver=receiver@entry=0x1ec6fb0,
e=e@entry=0x7ffdb435ea70) at kernel/qapplication.cpp:3716
#14 0x7fb69511eea6 in QApplication::notify (this=0x7ffdb435fe30,
receiver=0x1ec6fb0, e=0x7ffdb435ea70) at 

[kaffeine] [Bug 357709] New: kaffeine videos flickering ubuntu 15.10

[hans via KDE Bugzilla]

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

Bug ID: 357709
   Summary: kaffeine videos flickering ubuntu 15.10
   Product: kaffeine
   Version: 1.2.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: christophpfis...@gmail.com
  Reporter: hans.lei...@gmx.de

with (k)ubuntu 15.10 it is not possible to look television or see a video. all
is flickering. Same kaffeine version with (k)ubuntu 14.04.3 works fine.
Platform is Intel i5 with hd4600 grafics.

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

[plasmashell] [Bug 357687] Icons-Only Task Manager has button shapes

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Eike Hein  ---
Outlines or not is a theme thing, not an applet thing.

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

[kontact] [Bug 357707] New: Kontact crashed while reading news in akregator

[Andreas Hencke via KDE Bugzilla]

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

Bug ID: 357707
   Summary: Kontact crashed while reading news in akregator
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: andreas.hen...@outlook.com

Application: kontact (4.14.3)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 3.19.0-43-generic x86_64
Distribution: Ubuntu 14.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I closed some sub windows in akregator as kontact crashed.

Akgregator was pretty slow closing the windows

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbb0db8c800 (LWP 3548))]

Thread 6 (Thread 0x7fbaee302700 (LWP 3549)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbb0893381d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fbb08933859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fbb05054182 in start_thread (arg=0x7fbaee302700) at
pthread_create.c:312
#4  0x7fbb0b10747d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7fbaad9e7700 (LWP 3550)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbb0867420d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fbb08962fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fbb05054182 in start_thread (arg=0x7fbaad9e7700) at
pthread_create.c:312
#4  0x7fbb0b10747d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fba9db31700 (LWP 3574)):
#0  0x7fbb04b723ef in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fbb04b749bb in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbb04b74f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbb04b750ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbb0b8807be in QEventDispatcherGlib::processEvents
(this=0x7fba980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7fbb0b8520af in QEventLoop::processEvents
(this=this@entry=0x7fba9db30de0, flags=...) at kernel/qeventloop.cpp:149
#6  0x7fbb0b8523a5 in QEventLoop::exec (this=this@entry=0x7fba9db30de0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7fbb0b74ec5f in QThread::exec (this=) at
thread/qthread.cpp:537
#8  0x7fbb0b75132f in QThreadPrivate::start (arg=0xf5bc00) at
thread/qthread_unix.cpp:349
#9  0x7fbb05054182 in start_thread (arg=0x7fba9db31700) at
pthread_create.c:312
#10 0x7fbb0b10747d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fba97b8e700 (LWP 3587)):
#0  0x7ffcd5daec28 in ?? ()
#1  0x7fbb0db8e210 in ?? ()
#2  0x0001 in ?? ()
#3  0x00010b747244 in ?? ()
#4  0x7fba90002f30 in ?? ()
#5  0x7fba97b8dbe8 in ?? ()
#6  0x7fba97b8db80 in ?? ()
#7  0x7fff in ?? ()
#8  0x7fba97b8dbf0 in ?? ()
#9  0x7fbb0b11592d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#10 0x7fbb0b7a5ad7 in do_gettime (frac=0x7fba97b8db30, sec=0x7fba97b8db28)
at tools/qelapsedtimer_unix.cpp:127
#11 qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#12 0x7fbb0b881f05 in updateCurrentTime (this=0x1) at
kernel/qeventdispatcher_unix.cpp:354
#13 QTimerInfoList::timerWait (this=0x1, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#14 0x7fbb0b88067c in timerSourcePrepareHelper (src=,
timeout=0x7fba97b8dbe4) at kernel/qeventdispatcher_glib.cpp:143
#15 0x7fbb0b880725 in timerSourcePrepare (source=,
timeout=) at kernel/qeventdispatcher_glib.cpp:176
#16 0x7fbb04b7468d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7fbb04b74f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7fbb04b750ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7fbb0b8807be in QEventDispatcherGlib::processEvents
(this=0x7fba98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#20 0x7fbb0b8520af in QEventLoop::processEvents
(this=this@entry=0x7fba97b8dda0, flags=...) at kernel/qeventloop.cpp:149
#21 0x7fbb0b8523a5 in QEventLoop::exec (this=this@entry=0x7fba97b8dda0,
flags=...) at kernel/qeventloop.cpp:204
#22 0x7fbb0b74ec5f in QThread::exec (this=this@entry=0x1d0b3b0) at
thread/qthread.cpp:537
#23 0x7fbb0b833823 in QInotifyFileSystemWatcherEngine::run (this=0x1d0b3b0)
at io/qfilesystemwatcher_inotify.cpp:265
#24 

[konsole] [Bug 347540] Cannot start Konsole in Kubuntu 15.04

[via KDE Bugzilla]

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

gotokrik...@gmail.com changed:

   What|Removed |Added

 CC||gotokrik...@gmail.com

--- Comment #10 from gotokrik...@gmail.com ---
This bug is annoying and it is still around on my Debian Sid

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

[kmail2] [Bug 355195] date and time are ambiguous when replying to and forwarding messages (no timezone information)

[kolAflash via KDE Bugzilla]

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

--- Comment #2 from kolAflash  ---
Thanks for the comment Ben!

Actually I'd prefer to see the timezone offset (e.g. +0800). Especially because
I'm mailing with people in different timezones, this seems to be the better way
instead of recalculating everything to my local timezone without any attached
timezone information.

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

[kdenlive] [Bug 357710] wipe transition uses incorrect shape size when using a png lumas file

[Roberto Castagnola via KDE Bugzilla]

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

Roberto Castagnola  changed:

   What|Removed |Added

Summary|wipe transition use |wipe transition uses
   |incorrect shape size when   |incorrect shape size when
   |using a png lumas file  |using a png lumas file

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

[kdenlive] [Bug 357710] New: wipe transition use incorrect shape size when using a png lumas file

[Roberto Castagnola via KDE Bugzilla]

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

Bug ID: 357710
   Summary: wipe transition use incorrect shape size when using a
png lumas file
   Product: kdenlive
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: roberto.castagn...@gmail.com

If I use a png lumas file with a different aspect ratio than the project one,
the shape of transition is resized keeping the aspect-ratio of the png file, so
I get 2 bar on left and right of the clip where the transition is not applied.
I will attach a simple test project in dv_pal format where I have created a
black and a white clip color, starting with the balck clip and ending with the
white one. During the transition, using file radial.png found into kdenlive
package, the black clip is resized leaving 2 white bars on left and right.
If I convert the file to pgm format:
   convert -strip radial.png radial.pgm
the transition covers all the clip size as expected
(I have to use -strip option to strip comment, or the transition doesn't work:
maybe I shall open an other bug for this?)

Furthermore, if I enable 'Use GPU processing' option, kdenlive crashes when
using png file, but not when using pgm file


Reproducible: Always




kdenlive version: 15.12.0
mlt version: 0.9.8

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

[plasmashell] [Bug 357638] Plasma 5.5.3 crash when right clicking the Application Launcher

[Eike Hein via KDE Bugzilla]

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

--- Comment #1 from Eike Hein  ---
The backtrace is quite clear, but I'm not sure how that situation arises. Do
you use your Application Menu in some unusual way like on the desktop? Can you
say whether the entry is is in a regular category subdialog, or somewhere more
specific in the menu?

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

[kdevplatform] [Bug 134854] show read-only files in "File List" and editor tabs

[Kevin Funk via KDE Bugzilla]

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

--- Comment #6 from Kevin Funk  ---
Steps to reproduce:
- Open a file
- Tools -> [x] Read Only Mode

What happens:
- No indicator

Should happen:
- [read only] in KDevelop caption

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

[krita] [Bug 357708] New: krita fails to build against qt built with OpenGLES support

[Heiko Becker via KDE Bugzilla]

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

Bug ID: 357708
   Summary: krita fails to build against qt built with OpenGLES
support
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: heire...@exherbo.org

My qt is built with -opengl es2 and it's causing krita to fail during build
probably due to missing some include dirs for that case:

"var/tmp/paludis/build/media-gfx-krita-scm/work/krita-scm/krita/ui/opengl/kis_opengl_image_textures.cpp:
In member function 'void KisOpenGLImageTextures::updateTextureFormat()':
/var/tmp/paludis/build/media-gfx-krita-scm/work/krita-scm/krita/ui/opengl/kis_opengl_image_textures.cpp:511:49:
error: 'GL_RGBA16F_ARB' was not declared in this scope
 m_texturesInfo.internalFormat = GL_RGBA16F_ARB;
 ^
/var/tmp/paludis/build/media-gfx-krita-scm/work/krita-scm/krita/ui/opengl/kis_opengl_image_textures.cpp:515:49:
error: 'GL_RGBA_FLOAT16_ATI' was not declared in this scope
 m_texturesInfo.internalFormat = GL_RGBA_FLOAT16_ATI;
..."

Full log uploaded here (too big to attach):
https://gist.github.com/raw/df51984619a907d7f03c

If I compile qt with -opengl desktop krita compiles fine.

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

[plasma-nm] [Bug 357459] NM Connection Editor crashes adding new OpenVPN entry

[Achim Herwig via KDE Bugzilla]

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

Achim Herwig  changed:

   What|Removed |Added

 CC||achim.her...@wodca.de

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

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

[Kevin Funk via KDE Bugzilla]

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

--- Comment #11 from Kevin Funk  ---
For the record: Distro-provided Clang/LLVM works fine for me on Ubuntu Wily.
I'm sure I tried both the 3.6 and 3.7 versions at some point, without problems.

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

[krita] [Bug 357708] krita fails to build against qt built with OpenGLES support

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||b...@valdyas.org
 Resolution|--- |LATER

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

Krita requires desktop opengl, I'm afraid, so what you're trying isn't going to
work. Patches are welcome, it's something we'll need to do when we want to port
to Android, but it's more a todo than a bug...

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

[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev
   |platform/7cf9810c44b75d4123 |platform/596d64310d7a01ba24
   |b6f65150400a1d0296c0ea  |326c802e29b799443095f6
 Resolution|--- |FIXED

--- Comment #22 from Kevin Funk  ---
Git commit 596d64310d7a01ba24326c802e29b799443095f6 by Kevin Funk.
Committed on 08/01/2016 at 21:15.
Pushed by kfunk into branch '5.0'.

OutputView: Remove output rewriting feature

Just show the plain output to the users, as he would see when invoking
the build tool inside the terminal.

Don't rewrite the output, always show the full output. I don't think
there's a reason to support rewriting the output altogether, it's only
misleading for the user.

As discussed in bug 354143
Related: bug 194403
FIXED-IN: 5.0.0

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

M  +0-2outputview/filtereditem.cpp
M  +0-1outputview/filtereditem.h
M  +19   -40   outputview/outputfilteringstrategies.cpp
M  +4-8outputview/outputformats.cpp
M  +2-4outputview/outputformats.h
M  +1-1outputview/outputmodel.cpp
M  +0-32   outputview/tests/test_filteringstrategy.cpp
M  +0-2outputview/tests/test_filteringstrategy.h

http://commits.kde.org/kdevplatform/596d64310d7a01ba24326c802e29b799443095f6

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

[krita] [Bug 357706] New: Krita crashes when KDE exits

[via KDE Bugzilla]

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

Bug ID: 357706
   Summary: Krita crashes when KDE exits
   Product: krita
   Version: 2.9.10
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: jeffrey.rol...@gmail.com

Application: krita (2.9.10)
KDE Platform Version: 4.14.15
Qt Version: 4.8.7
Operating System: Linux 4.4.0-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
I had loaded Krita but had not yet started editing anything. I logged out of
KDE to test something else, whereupon Krita (and only Krita) crashed.

-- Backtrace:
Application: Krita (krita), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4c2dfe1840 (LWP 22799))]

Thread 3 (Thread 0x7f4bf3fff700 (LWP 23287)):
#0  0x7f4c2631d07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4c2bcc26b6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#2  0x7f4c2cd4f8dc in ?? () from /usr/lib/libQtGui.so.4
#3  0x7f4c2bcc214c in ?? () from /usr/lib/libQtCore.so.4
#4  0x7f4c263174a4 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f4c2b3e313d in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f4bf27fc700 (LWP 23288)):
#0  0x7f4c2b3dbe23 in select () from /usr/lib/libc.so.6
#1  0x7f4c2bdff5af in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timeval const*) () from /usr/lib/libQtCore.so.4
#2  0x7f4c2be0529f in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timeval*) () from /usr/lib/libQtCore.so.4
#3  0x7f4c2be05768 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/libQtCore.so.4
#4  0x7f4c2bdd0dc1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/libQtCore.so.4
#5  0x7f4c2bdd1135 in
QEventLoop::exec(QFlags) () from
/usr/lib/libQtCore.so.4
#6  0x7f4c2bcbf859 in QThread::exec() () from /usr/lib/libQtCore.so.4
#7  0x7f4c2bdb0f13 in ?? () from /usr/lib/libQtCore.so.4
#8  0x7f4c2bcc214c in ?? () from /usr/lib/libQtCore.so.4
#9  0x7f4c263174a4 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f4c2b3e313d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f4c2dfe1840 (LWP 22799)):
[KCrash Handler]
#6  0x7f4c2b32d5f8 in raise () from /usr/lib/libc.so.6
#7  0x7f4c2b32ea7a in abort () from /usr/lib/libc.so.6
#8  0x7f4c2bcb752d in qt_message_output(QtMsgType, char const*) () from
/usr/lib/libQtCore.so.4
#9  0x7f4c2bcb76b1 in ?? () from /usr/lib/libQtCore.so.4
#10 0x7f4c2bcb7fd1 in qFatal(char const*, ...) () from
/usr/lib/libQtCore.so.4
#11 0x7f4c2c87cc7e in QWidgetPrivate::QWidgetPrivate(int) () from
/usr/lib/libQtGui.so.4
#12 0x7f4c2c8c6b7a in QDesktopWidget::QDesktopWidget() () from
/usr/lib/libQtGui.so.4
#13 0x7f4c2c832911 in QApplication::desktop() () from
/usr/lib/libQtGui.so.4
#14 0x7f4c2c8863cf in QWidget::saveGeometry() const () from
/usr/lib/libQtGui.so.4
#15 0x7f4c2d969230 in KisMainWindow::~KisMainWindow() () from
/usr/lib/libkritaui.so.14
#16 0x7f4c2d969889 in KisMainWindow::~KisMainWindow() () from
/usr/lib/libkritaui.so.14
#17 0x7f4c2d9827a9 in KisPart::~KisPart() () from /usr/lib/libkritaui.so.14
#18 0x7f4c2d982969 in KisPart::~KisPart() () from /usr/lib/libkritaui.so.14
#19 0x7f4c2b32ff88 in __run_exit_handlers () from /usr/lib/libc.so.6
#20 0x7f4c2b32ffd5 in exit () from /usr/lib/libc.so.6
#21 0x7f4c2b31a617 in __libc_start_main () from /usr/lib/libc.so.6
#22 0x004034c9 in _start ()

Possible duplicates by query: bug 262341, bug 251460.

Reported using DrKonqi

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

[kdevelop] [Bug 194403] ability to configure verbosity of compiler output is lost

[Kevin Funk via KDE Bugzilla]

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

--- Comment #7 from Kevin Funk  ---
Git commit 596d64310d7a01ba24326c802e29b799443095f6 by Kevin Funk.
Committed on 08/01/2016 at 21:15.
Pushed by kfunk into branch '5.0'.

OutputView: Remove output rewriting feature

Just show the plain output to the users, as he would see when invoking
the build tool inside the terminal.

Don't rewrite the output, always show the full output. I don't think
there's a reason to support rewriting the output altogether, it's only
misleading for the user.

As discussed in bug 354143
Related: bug 354143
FIXED-IN: 5.0.0

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

M  +0-2outputview/filtereditem.cpp
M  +0-1outputview/filtereditem.h
M  +19   -40   outputview/outputfilteringstrategies.cpp
M  +4-8outputview/outputformats.cpp
M  +2-4outputview/outputformats.h
M  +1-1outputview/outputmodel.cpp
M  +0-32   outputview/tests/test_filteringstrategy.cpp
M  +0-2outputview/tests/test_filteringstrategy.h

http://commits.kde.org/kdevplatform/596d64310d7a01ba24326c802e29b799443095f6

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

[plasmashell] [Bug 357717] New: Plasma crashed when trying to open the Application Menu

[Jesse Talavera-Greenberg via KDE Bugzilla]

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

Bug ID: 357717
   Summary: Plasma crashed when trying to open the Application
Menu
   Product: plasmashell
   Version: 5.4.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jessetalav...@aol.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
Opening an application from the Application Menu.  No idea how or why it
happened.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa5323d7800 (LWP 2071))]

Thread 6 (Thread 0x7fa516fca700 (LWP 2091)):
#0  __GI___pthread_getspecific (key=3) at pthread_getspecific.c:32
#1  0x7fa529909e10 in g_thread_self () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa5298e32ed in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa52d46a50b in QEventDispatcherGlib::processEvents
(this=0x7fa518c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fa52d41150a in QEventLoop::exec (this=this@entry=0x7fa516fc9da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fa52d22dac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fa52faa1c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa52d232a6e in QThreadPrivate::start (arg=0x123e970) at
thread/qthread_unix.cpp:331
#8  0x7fa52c31e6aa in start_thread (arg=0x7fa516fca700) at
pthread_create.c:333
#9  0x7fa52cb47eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fa50bbb9700 (LWP 2109)):
#0  0x7fa52cb3c8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa5298e31ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa5298e32fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa52d46a50b in QEventDispatcherGlib::processEvents
(this=0x7fa5040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fa52d41150a in QEventLoop::exec (this=this@entry=0x7fa50bbb8da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fa52d22dac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fa52faa1c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa52d232a6e in QThreadPrivate::start (arg=0x1566ae0) at
thread/qthread_unix.cpp:331
#8  0x7fa52c31e6aa in start_thread (arg=0x7fa50bbb9700) at
pthread_create.c:333
#9  0x7fa52cb47eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fa509b6e700 (LWP 2114)):
#0  0x7fa52d2e2ff2 in qt_gettime () at tools/qelapsedtimer_unix.cpp:163
#1  0x7fa52d467f99 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7fa4fc002ed0) at kernel/qtimerinfo_unix.cpp:84
#2  0x7fa52d468505 in QTimerInfoList::timerWait (this=0x7fa4fc002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:381
#3  0x7fa52d4698ee in timerSourcePrepareHelper (timeout=0x7fa509b6dbe4,
src=) at kernel/qeventdispatcher_glib.cpp:127
#4  timerSourcePrepare (source=, timeout=0x7fa509b6dbe4) at
kernel/qeventdispatcher_glib.cpp:160
#5  0x7fa5298e277d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fa5298e311b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fa5298e32fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fa52d46a50b in QEventDispatcherGlib::processEvents
(this=0x7fa4fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#9  0x7fa52d41150a in QEventLoop::exec (this=this@entry=0x7fa509b6dda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#10 0x7fa52d22dac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#11 0x7fa52faa1c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7fa52d232a6e in QThreadPrivate::start (arg=0x163b020) at
thread/qthread_unix.cpp:331
#13 0x7fa52c31e6aa in start_thread (arg=0x7fa509b6e700) at
pthread_create.c:333
#14 0x7fa52cb47eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fa503fff700 (LWP 2119)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa531e31194 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa531e311d9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa52c31e6aa in start_thread (arg=0x7fa503fff700) at
pthread_create.c:333
#4  0x7fa52cb47eed in clone () at

[kdelibs] [Bug 162211] Copying to an external causes lots of missing files

[Alex via KDE Bugzilla]

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

--- Comment #89 from Alex  ---
I lost the files when copying from hdd to hdd. Without using the USB drives.
Today checked on 2 PCs Archlinux in Konqueror, Krusader, Dolphin bug not
reproduced.
Previously, he consistently played. Now it is fixed.

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

[Breeze] [Bug 344425] Cannot select fields using the mouse

[André Marcelo Alvarenga via KDE Bugzilla]

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

--- Comment #20 from André Marcelo Alvarenga  ---
Please, reopen this bug report.
I can reproduce this bug in Plasma 5.5.3 (Qt 5.5.1 and Frameworks 5.17).

Distro: Manjaro Linux 15.12

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

[kate] [Bug 354482] scrolling quickly with the mouse wheel jumps and can even scroll backwards

[Denis Akimkin via KDE Bugzilla]

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

Denis Akimkin  changed:

   What|Removed |Added

 CC||akimkin.de...@gmail.com

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

[kopete] [Bug 353245] Support of OMEMO in Kopete

[Benedikt Geißler via KDE Bugzilla]

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

Benedikt Geißler  changed:

   What|Removed |Added

 CC||benedi...@openaliasbox.org

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

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

[Danny Tamez via KDE Bugzilla]

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

--- Comment #163 from Danny Tamez  ---
I read this before going to bed last night.   I dreamed I was in the not too
distant future and I upgraded my desktop.  When the upgrade concluded I
rebooted my laptop.  To my amazement all functionality and features had been
completely removed except for and in favor of activities.  I was really
confused but found that it was not a big deal as the 4 remaining KDE users were
absolutely in love with the new streamlined interface.  
I woke up in a cold sweat. Alas, it was but a dream.  But wow, it felt so real!

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

[plasmashell] [Bug 357717] Plasma crashed when trying to open the Application Menu

[David Edmundson via KDE Bugzilla]

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

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

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

[plasmashell] [Bug 355751] Reload plasma

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||jessetalav...@aol.com

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

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

[kdevelop] [Bug 274246] Lot of kdevelop 'defunct' processes exceed ulimit setting

[Aaron Williams via KDE Bugzilla]

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

Aaron Williams  changed:

   What|Removed |Added

 CC||aar...@doofus.org

--- Comment #29 from Aaron Williams  ---
I am seeing this happening with 4.7.1 on OpenSUSE 13.2 with a large project I
am working on. One thing to note is that I have well over 100 files, .c, .h and
.dts (device tree) files open in my project.

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

[kinfocenter] [Bug 357718] New: KInfoCenter Crashed When Closing

[via KDE Bugzilla]

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

Bug ID: 357718
   Summary: KInfoCenter Crashed When Closing
   Product: kinfocenter
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: kerryla...@islandnet.com

Application: kinfocenter (5.5.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
I had just finished viewing information using KInfoCenter and I was informed of
a crash.

-- Backtrace:
Application: KDE Info Center (kinfocenter), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0bacdc8780 (LWP 29929))]

Thread 4 (Thread 0x7f0b99fb4700 (LWP 29931)):
#0  0x7f0ba9895c1d in poll () at /lib64/libc.so.6
#1  0x7f0ba2d7c422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f0ba2d7e00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f0b9c93b3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f0ba9f8d32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f0ba624c0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0ba989e04d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f0b8ba9e700 (LWP 10744)):
#0  0x7f0ba9895c1d in poll () at /lib64/libc.so.6
#1  0x7f0ba5817e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0ba5817f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0baa1bfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f0baa166d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f0ba9f8861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f0ba8c78df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f0ba9f8d32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f0ba624c0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f0ba989e04d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f0b89132700 (LWP 10839)):
#0  0x7f0ba9891ced in read () at /lib64/libc.so.6
#1  0x7f0ba19e2073 in  () at /usr/lib64/tls/libnvidia-tls.so.358.16
#2  0x7f0ba5858b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f0ba5817999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f0ba5817df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f0ba5817f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f0baa1bfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f0baa166d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f0ba9f8861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f0ba8c78df8 in  () at /usr/lib64/libQt5Qml.so.5
#10 0x7f0ba9f8d32f in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f0ba624c0a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f0ba989e04d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f0bacdc8780 (LWP 29929)):
[KCrash Handler]
#6  0x7f0ba97ee187 in raise () at /lib64/libc.so.6
#7  0x7f0ba97ef538 in abort () at /lib64/libc.so.6
#8  0x7f0ba9f7b7ce in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f0baa694092 in  () at /usr/lib64/libQt5Gui.so.5
#10 0x7f0baa72b3c6 in  () at /usr/lib64/libQt5Gui.so.5
#11 0x7f0baa6c4c3f in QCursor::QCursor(QCursor const&) () at
/usr/lib64/libQt5Gui.so.5
#12 0x7f0ba915b9c9 in QQuickItem::cursor() const () at
/usr/lib64/libQt5Quick.so.5
#13 0x7f0ba91dba1b in QQuickMouseArea::setCursorShape(Qt::CursorShape) ()
at /usr/lib64/libQt5Quick.so.5
#14 0x7f0ba92a170b in QQuickMouseArea::qt_metacall(QMetaObject::Call, int,
void**) () at /usr/lib64/libQt5Quick.so.5
#15 0x7f0ba8be1b68 in QQmlVMEMetaObject::metaCall(QMetaObject::Call, int,
void**) () at /usr/lib64/libQt5Qml.so.5
#16 0x7f0ba8bfb737 in QQmlPropertyPrivate::writeBinding(QObject*,
QQmlPropertyData const&, QQmlContextData*, QQmlJavaScriptExpression*,
QV4::Value const&, bool, QFlags) () at
/usr/lib64/libQt5Qml.so.5
#17 0x7f0ba8c65823 in
QQmlBinding::update(QFlags) () at
/usr/lib64/libQt5Qml.so.5
#18 0x7f0ba8c65dae in
QQmlBinding::expressionChanged(QQmlJavaScriptExpression*) () at
/usr/lib64/libQt5Qml.so.5
#19 0x7f0ba8c423b7 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () at /usr/lib64/libQt5Qml.so.5
#20 0x7f0ba8be9844 in QQmlData::signalEmitted(QAbstractDeclarativeData*,
QObject*, int, void**) () at /usr/lib64/libQt5Qml.so.5
#21 0x7f0baa198543 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#22 0x7f0ba91632d8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib64/libQt5Quick.so.5
#23 0x7f0ba9163245 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at 

[plasmashell] [Bug 357719] New: Plasma Crashed While Application Menu Was Being Used

[via KDE Bugzilla]

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

Bug ID: 357719
   Summary: Plasma Crashed While Application Menu Was Being Used
   Product: plasmashell
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kerryla...@islandnet.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
I clicked on the application menu portion of the panel to select an
application, when it crashed and Plasma restarted.

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

Thread 44 (Thread 0x7fd8e61fb700 (LWP 1687)):
#0  0x7fd8fd809c1d in poll () at /lib64/libc.so.6
#1  0x7fd8f9eeae64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fd8f9eeaf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fd8fe133d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fd8fe0dad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd8fdefc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fd901207df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fd8fdf0132f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fd8fd0130a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fd8fd81204d in clone () at /lib64/libc.so.6

Thread 43 (Thread 0x7fd8d9bc9700 (LWP 1717)):
#0  0x7fd8fd809c1d in poll () at /lib64/libc.so.6
#1  0x7fd8f9eeae64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fd8f9eeaf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fd8fe133d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fd8fe0dad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd8fdefc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fd901207df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fd8fdf0132f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fd8fd0130a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fd8fd81204d in clone () at /lib64/libc.so.6

Thread 42 (Thread 0x7fd8d3fff700 (LWP 1722)):
#0  0x7fd8fd809c1d in poll () at /lib64/libc.so.6
#1  0x7fd8f9eeae64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fd8f9eeaf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fd8fe133d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fd8fe0dad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd8fdefc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fd901207df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fd8fdf0132f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fd8fd0130a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fd8fd81204d in clone () at /lib64/libc.so.6

Thread 41 (Thread 0x7fd8d29a3700 (LWP 1726)):
#0  0x7fd8fd01705f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd9039cc86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fd9039cc899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fd8fd0130a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd8fd81204d in clone () at /lib64/libc.so.6

Thread 40 (Thread 0x7fd84bd4d700 (LWP 1728)):
#0  0x7fd8fd805ced in read () at /lib64/libc.so.6
#1  0x7fd8f59b9073 in  () at /usr/lib64/tls/libnvidia-tls.so.358.16
#2  0x7fd8f9f2bb60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fd8f9eea999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fd8f9eeadf8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7fd8f9eeaf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7fd8fe133d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7fd8fe0dad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7fd8fdefc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7fd901d9f282 in  () at /usr/lib64/libQt5Quick.so.5
#10 0x7fd8fdf0132f in  () at /usr/lib64/libQt5Core.so.5
#11 0x7fd8fd0130a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7fd8fd81204d in clone () at /lib64/libc.so.6

Thread 39 (Thread 0x7fd8498d1700 (LWP 1784)):
#0  0x7fd8fd01705f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd8fdf0234b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fd901e1225b in  () at /usr/lib64/libQt5Quick.so.5
#3  

[kdevelop] [Bug 119929] sort variables list alphabetically

[Piotr Mierzwinski via KDE Bugzilla]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #15 from Piotr Mierzwinski  ---
The same happen when we unfold QStringList contains more than 10 items. I aware
that QStringList is vector variation contains strings instead of numbers. It
was only next example.
This issue probably happens because there are sorting strings (presenting
indexes) and not numbers.

Some solution for this could be adding 0 to the left side of indexes, making
that them length (as string) would be equal. I mean left padding every indexes
shortest than one longest (counting number of digits). I think, example will
show the best what I mean.
There is QStringList contains 12 strings. This vector/list would be presented
in Variable view like this.

myStrList
 |-[00] aa
 |-[01] bb
 |-[02] cc
 |-[03] dd
 |-[04] ee
 |-[05] ff
 |-[06] gg
 |-[07] hh
 |-[08] ii
 |-[09] jj
 |-[10] kk
  \-[11] ll

Thanks leading "0", change of sorting would not broke the order of items.

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

[systemsettings] [Bug 345234] Adding/Removing fonts shows wait dialog forever

[Ongun Kanat via KDE Bugzilla]

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

--- Comment #14 from Ongun Kanat  ---
I still have the issue. KAuth 5.17.0-1 package of ArchLinux have been already
installed on my pc. Did you tried instaling fonts with the System option after
the commit went upstream (I know it's a silly question though), since
installing with Personal option works but System option causes dialog wait
forever. I removed the configs releated to kcmfontinst in the folder ~/.config
,hoping it might fix things, but I couldn't achieve further improvements.

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

[telepathy] [Bug 357714] New: authentication to jabber server not working

[Fabian via KDE Bugzilla]

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

Bug ID: 357714
   Summary: authentication to jabber server not working
   Product: telepathy
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: auth-handler
  Assignee: kde-telepathy-b...@kde.org
  Reporter: fab...@web2.0-apps.de

If I try to connect to my jabber server I get the ktp-auth-handler dialog over
and over again, but I'm quite sure it's not an actual problem with the
(initial) authentication.

Sometimes I can connect to the jabber server, I see the contacts and there
online/offline status. If I delete the account and recreate it, the contact
list is loaded. Sometimes I can chat. But most of the time I still get the
ktp-auth-handler dialog over and over again.

This the ktp-debugger mission log for a authentification attemp:
08.01.2016 22:08:26.667670 - [mcd] mcd_connection_reconnect: 0x17dfe10
08.01.2016 22:08:26.667788 - [mcd] _mcd_connection_attempt: called for
0x17dfe10, account gabble/jabber/fabian_40leo_2eorg0
08.01.2016 22:08:26.667850 - [mcd] _mcd_account_dup_parameters: called
08.01.2016 22:08:26.668016 - [mcd] _mcd_account_set_connection_status:
gabble/jabber/fabian_40leo_2eorg0: 1 because 1
08.01.2016 22:08:26.668072 - [mcd] mcd_account_freeze_properties:
gabble/jabber/fabian_40leo_2eorg0
08.01.2016 22:08:26.668133 - [mcd] _mcd_account_set_connection_status: changing
connection status from 2 to 1
08.01.2016 22:08:26.668185 - [mcd] _mcd_account_set_connection_status: changing
connection status reason from 2 to 1
08.01.2016 22:08:26.668246 - [mcd] mcd_account_changed_property: called:
Connection
08.01.2016 22:08:26.668303 - [mcd] mcd_account_changed_property: First changed
property
08.01.2016 22:08:26.668462 - [mcd] mcd_account_changed_property: called:
ConnectionStatus
08.01.2016 22:08:26.668518 - [mcd] mcd_account_changed_property: called:
ConnectionStatusReason
08.01.2016 22:08:26.668567 - [mcd] mcd_account_changed_property: called:
ConnectionError
08.01.2016 22:08:26.668627 - [mcd] mcd_account_changed_property: called:
ConnectionErrorDetails
08.01.2016 22:08:26.668697 - [mcd] mcd_account_thaw_properties:
gabble/jabber/fabian_40leo_2eorg0
08.01.2016 22:08:26.668744 - [mcd] emit_property_changed: called
08.01.2016 22:08:26.668863 - [mcd] mcd_account_connection_proceed_with_reason:
gabble/jabber/fabian_40leo_2eorg0 wants to connect and we're online - go for it
08.01.2016 22:08:26.668910 - [mcd] _mcd_connection_connect: called for
0x17dfe10, account gabble/jabber/fabian_40leo_2eorg0
08.01.2016 22:08:26.668956 - [mcd] _mcd_connection_connect_with_params: Trying
connect account: gabble/jabber/fabian_40leo_2eorg0
08.01.2016 22:08:26.669013 - [mcd] _mcd_account_set_connection_status:
gabble/jabber/fabian_40leo_2eorg0: 1 because 1
08.01.2016 22:08:26.669060 - [mcd] mcd_account_freeze_properties:
gabble/jabber/fabian_40leo_2eorg0
08.01.2016 22:08:26.669106 - [mcd] mcd_account_thaw_properties:
gabble/jabber/fabian_40leo_2eorg0
08.01.2016 22:08:26.693840 - [mcd] request_connection_cb: created
/org/freedesktop/Telepathy/Connection/gabble/jabber/fabian_40leo_2eorg_2fkde_2dtelepathy_2d603496
08.01.2016 22:08:26.694664 - [mcd] _mcd_connection_set_tp_connection: new
connection is 0x17e14f0
08.01.2016 22:08:26.695439 - [mcd] mcd_account_changed_property: called:
Connection
08.01.2016 22:08:26.695480 - [mcd] mcd_account_changed_property: First changed
property
08.01.2016 22:08:26.695791 - [mcd] on_connection_status_changed: status_changed
called from tp (2)
08.01.2016 22:08:26.696222 - [mcd] _mcd_connection_update_client_caps: Sending
client caps to connection
08.01.2016 22:08:26.696746 - [mcd] mcd_connection_early_get_statuses_cb:
/org/freedesktop/Telepathy/Connection/gabble/jabber/fabian_40leo_2eorg_2fkde_2dtelepathy_2d603496:
Early Get(Statuses) succeeded
08.01.2016 22:08:26.696788 - [mcd] presence_get_statuses_cb: account
gabble/jabber/fabian_40leo_2eorg0:
08.01.2016 22:08:26.696842 - [mcd] presence_get_statuses_cb:   offline
08.01.2016 22:08:26.696897 - [mcd] presence_get_statuses_cb:   chat
08.01.2016 22:08:26.696949 - [mcd] presence_get_statuses_cb:   xa
08.01.2016 22:08:26.697000 - [mcd] presence_get_statuses_cb:   unknown
08.01.2016 22:08:26.697052 - [mcd] presence_get_statuses_cb:   error
08.01.2016 22:08:26.697104 - [mcd] presence_get_statuses_cb:   hidden
08.01.2016 22:08:26.697155 - [mcd] presence_get_statuses_cb:   available
08.01.2016 22:08:26.697206 - [mcd] presence_get_statuses_cb:   away
08.01.2016 22:08:26.697259 - [mcd] presence_get_statuses_cb:   dnd
08.01.2016 22:08:26.697313 - [mcd] _mcd_connection_set_presence: Setting status
'available' of type 2 ('available' was requested)
08.01.2016 22:08:26.697474 - [mcd] _mcd_dispatcher_add_connection: 0x1795e20:
0x17dfe10

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

[RJVB via KDE Bugzilla]

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

--- Comment #12 from RJVB  ---
(In reply to Kevin Funk from comment #11)
> For the record: Distro-provided Clang/LLVM works fine for me on Ubuntu Wily.

The crash I saw with Ubuntu's Clang 3.6 was different from the one I saw with
the LLVM-provided builds. Ubuntu only provide an early 3.6.0 for "Trusty", it's
not at all impossible there's a real bug in there.

Here's a wild thought: when I tried to rebuild that year old 3.5.1 LLVM
toolchain earlier today using gcc-5.3 instead of gcc-4.8 I ran into a build
failure. Gcc 5 didn't accept access to a private member of a template class in
one of LLVM's headers (in one of the class ctors...), code that is accepted
without issues by gcc-4.8 . Not that it seems likely, but suppose that is
caused by a difference in default C++ flavour in gcc-5, couldn't that also lead
to subtle incompatibilities between libraries built with an older g++ and a
host application built with g++5?

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

[valgrind] [Bug 353192] Debug info/data section not detected on AMD64

[Patrick Collins via KDE Bugzilla]

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

Patrick Collins  changed:

   What|Removed |Added

 CC||pscoll...@google.com

--- Comment #4 from Patrick Collins  ---
I was bitten by this as well. I ended up with program headers that looked like
this:

Program Headers:
  Type   Offset VirtAddr   PhysAddr
 FileSizMemSiz  Flags  Align
  LOAD   0x 0x 0x
 0x005eabf4 0x005eabf4  R**W**E20
  LOAD   0x0060 0x0080 0x0080
 0x0003b3f0 0x0004efe8  RW 20
  DYNAMIC0x0060f460 0x0080f460 0x0080f460
 0x0180 0x0180  RW 8
  NOTE   0x01c8 0x01c8 0x01c8
 0x0024 0x0024  R  4
  GNU_EH_FRAME   0x0057c050 0x0057c050 0x0057c050
 0x0001600c 0x0001600c  R  4
  GNU_STACK  0x 0x 0x
 0x 0x  RW 10
  GNU_RELRO  0x0060 0x0080 0x0080
 0x00011000 0x00011000  R  1

where the W flag in section 00 was caused by a combination of unusual
__attribute__((__section__(foo))) annotations in GCC. I am also on Ubuntu, with
amd64. I think this is properly called a bug, at least on amd64, because there
is nothing in any standard that prevents .text sections from being mmaped with
rwx permissions. 


As far as I can tell, moving amd64 to the same bucket as x86 and accepting r.x
permissions would be harmless, since Valgrind will only try to read in debug
symbols for a particular section if it finds *both* a section marked as
executable *and* a .debug entry that corresponds to that section. I assume the
rationale here is that if users are trying to treat a writeable section as a
text section, then they're probably doing something wrong --- but this won't
change existing behavior unless the user also provides debug info corresponding
to that section (in which case they probably really do want to treat that
section as text-like).

At the very least, emitting a warning when --trace-symbtab is turned on would
be helpful, because this was very difficult to track down.

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

[valgrind] [Bug 353192] Debug info/data section not detected on AMD64

[Patrick Collins via KDE Bugzilla]

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

--- Comment #5 from Patrick Collins  ---
And if it's useful, I can put together a compileable example that displays this
behavior. Please let me know.

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

[ark] [Bug 357593] Allow choosing panel position (docking)

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Priority|NOR |LO
 Status|UNCONFIRMED |CONFIRMED

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

[konqueror] [Bug 357711] konqueror crashed -- session autosave related [QPointer::operator->]

[Raúl via KDE Bugzilla]

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

Raúl  changed:

   What|Removed |Added

 CC||rasas...@gmail.com

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

[konqueror] [Bug 357711] konqueror crashed -- session autosave related [QPointer::operator->]

[Raúl via KDE Bugzilla]

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

--- Comment #1 from Raúl  ---
Created attachment 96533
  --> https://bugs.kde.org/attachment.cgi?id=96533=edit
New crash information added by DrKonqi

konqueror (4.14.13) on KDE Platform 4.14.14 using Qt 4.8.7

- What I was doing when the application crashed:

I opnen konqueror again (same as above). This time I got to open a pair of new
tabs. I browsed in one of then, closed and the konqueror crashed.

-- Backtrace (Reduced):
#6  0x7f9ab9042b2c in QPointer::operator-> (this=) at /usr/include/qt4/QtCore/qpointer.h:74
#7  KHTMLPart::saveState (this=0x54457d00, stream=...) at
../../khtml/khtml_part.cpp:5403
#8  0x7f9ab9042f93 in KHTMLPart::saveState (this=,
stream=...) at ../../khtml/khtml_part.cpp:5467
#9  0x7f9ab9042f93 in KHTMLPart::saveState (this=,
stream=...) at ../../khtml/khtml_part.cpp:5467
#10 0x7f9ab9042f93 in KHTMLPart::saveState (this=,
stream=...) at ../../khtml/khtml_part.cpp:5467

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

[lokalize] [Bug 357713] New: Filter feature for project view

[Karl Ove Hufthammer via KDE Bugzilla]

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

Bug ID: 357713
   Summary: Filter feature for project view
   Product: lokalize
   Version: 2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: project management
  Assignee: sha...@ukr.net
  Reporter: k...@huftis.org

It would be nice if it would be possible to define a per-project (regexp)
filter for hiding folders and files in the project view. Use cases:

Use case 1: Hiding all ‘playground-*’ folders for a KDE translation project.
Since it is usually no reason to translate them, having them (and their bad
translations statistics) shown in the project view only adds noise.

Use case 2: For projects that keep translation files for all languages together
in the *same* folder (one or several folders), one could hide all files not
belonging to the target language. Typically, the files would be named
appname.langcode.po (e.g. foo.nn.po, foo.da.po, bar.nn.po, bar.da.po). So by
adding a filter for showing only files ending in langcode.po(t), one would have
a list of files to translate.

Base on the two use cases, I think two types of filters are needed, one for
‘Hide folders/files matching:’ and one for ‘Only show folders/files matching:’
(and it would be possible to use both filter types at the same time). To
deactivate a filter one would leave it empty.

Reproducible: Always

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

[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers

[an999 via KDE Bugzilla]

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

an999  changed:

   What|Removed |Added

 CC||arminn...@gmail.com

--- Comment #40 from an999  ---
seems like we have to wait 10 years for a fix

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

[plasmashell] [Bug 357638] Plasma 5.5.3 crash when right clicking the Application Launcher

[Till Schäfer via KDE Bugzilla]

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

--- Comment #2 from Till Schäfer  ---
i used the default kickoff from the task bar. I browsed the category "computer"
and then right clicked on the systemsettings symbol.

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

[plasmashell] [Bug 357638] Plasma 5.5.3 crash when right clicking the Application Launcher

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

  Component|Application Menu (Kicker)   |Application Launcher
   ||(Kickoff)
   Assignee|h...@kde.org|k...@davidedmundson.co.uk

--- Comment #3 from Eike Hein  ---
Move to correct product.

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

[systemsettings] [Bug 336089] Font preview - rendering problem

[Ongun Kanat via KDE Bugzilla]

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

Ongun Kanat  changed:

   What|Removed |Added

 CC||ongun.ka...@gmail.com

--- Comment #39 from Ongun Kanat  ---
I have the same bad font rendering issue with UXA rendering mode of the Intel
driver. SNA works correctly.

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

[systemsettings] [Bug 336089] Font preview - rendering problem

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #40 from Thomas Lübking  ---
Sure it's this bug?
Can you provide screenshots of UXA and SNA rendered fonts?

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

[ark] [Bug 357594] It should be possible to edit/create archives with comments

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[ark] [Bug 357658] Ark-15.12.0: default actions for clicking files: easy misconception of settings dialog

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #6 from Elvis Angelaccio  ---
All right, I'm confirming this report then.

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

[Breeze] [Bug 357661] Invisible monochrome icon in 'system tray'

[Sudhir Khanger via KDE Bugzilla]

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

Sudhir Khanger  changed:

   What|Removed |Added

 CC||sud...@sudhirkhanger.com

--- Comment #2 from Sudhir Khanger  ---
This is duplicate of #356380.

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

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

[Breeze] [Bug 356849] ownCloud Icon is hardly visible when using breeze dark-desktop and light-icon theme

[Sudhir Khanger via KDE Bugzilla]

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

Sudhir Khanger  changed:

   What|Removed |Added

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

--- Comment #2 from Sudhir Khanger  ---
Border is again white and icon is visible. So I am closing this bug.

I do have to say that empty icons with only border around them have very low
visibility. I have to pressure my eyes to be able to tell which icon it might
be. And 70-80% icons have some white inside them so the ones that are empty
look poor and are hardly visible.

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

[plasmashell] [Bug 353520] Crash when startup

[via KDE Bugzilla]

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

ad1r...@hotmail.fr changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from ad1r...@hotmail.fr ---
oki same here

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

[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage

[H . H . via KDE Bugzilla]

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

H.H.  changed:

   What|Removed |Added

 CC||cyberb...@gmx.de

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

[trojita] [Bug 357678] Hide MIME type tab bar when only one option exists

[Luke-Jr via KDE Bugzilla]

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

--- Comment #5 from Luke-Jr  ---
a) I assume because the sender formatted it that way...

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

[dolphin] [Bug 357693] New: Preview scans files opened for read/write resulting in an endless scan, locking up CPU/Desktop

[via KDE Bugzilla]

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

Bug ID: 357693
   Summary: Preview scans files opened for read/write resulting in
an endless scan, locking up CPU/Desktop
   Product: dolphin
   Version: 15.12.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: tuxfus...@gmail.com

A video file being created on the hard disk while Dolphin-Preview active is
being scanned for a thumbnail, every second although the creation is a minute
or hour long process resulting in thousands of thumbnail scans on one file. The
used up CPU and IO resources for scanning, extend the actual creation length of
the file as less resources are available, resulting in even more thumbnail
scans, as the overall process takes longer.


Reproducible: Always

Steps to Reproduce:
1.  create a huge video file, for instance recode video a to video b. Let
resulting file be a modern hd file and let it have 5 to 10 gigabytes of data (
maybe smaller files also effected)
2. Have dolphin open, showing that folder. Preview Enabled.
3. As video b is constantly "growing" as it is being generated, dolphin or
better the thumbnail.so re-scans the file every second, resulting in huge CPU
usage.
4. Let the recode continue as long as it takes( this can be hours, depending),
dolphin will try to generate new thumbnails for hours, in bad situations.


Actual Results:  
high cpu usage, desktop lock up/not reacting for seconds , every few seconds

Expected Results:  
nothing, until read/write operation finished on the file

installed thumbnail software version:

local/ffmpegthumbs 15.12.0-1
FFmpeg-based thumbnail creator for video files
local/ffmpegthumbs-git r91.c06602f-1
FFmpeg-based thumbnail creator for video files
local/kdegraphics-thumbnailers 15.12.0-1
Thumbnailers for various graphics file formats

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

[trojita] [Bug 357678] Hide MIME type tab bar when only one option exists

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #2 from Thomas Lübking  ---
Hah? This would be a multipart message w/ only one part, would it?
(I do absolutely not get this in singlepart mails)

Might be a misconfigured server (along bug #357676) if this is the "regular"
case for you?

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

[kwin] [Bug 348156] Add a feature to unredirect all fullscreen windows except some selected

[via KDE Bugzilla]

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

--- Comment #21 from jeremy9...@gmail.com ---
(In reply to Thomas Lübking from comment #20)
> The checkbox is already there (this is how scripts are triggered)
> Please understand that everybody wants "his" feature to activate by sheer
> will, but we lack a brain interface.
That's not what I meant. I mean a checkbox easily discoverable, like the one
"unredirect windows" or even easier to find and use because the scripts are in
their own windows and for a "normal" user it's not really obvious that in order
to play game in good condition he need to activate a script in this particular
window.

> Sorry, I don't follow. It is *exactly* what's described in the "X11
> workaround" section (and the rest is irrelevant to the topic) - 
The suggestion of Martin is "When a fullscreen game starts, it can create a
“sub-session” on a new virtual terminal and become the logind- session
controller for that session. Etc...". It seems that is not really easy to do
and not exactly the same thing that simply disabling compositing. But
nevermind, it's not important here.

> the only question is "who activates the block" and *obviously* the ideal 
> solution
> would be the client in question would just say "make me uncomposited".
As you know, that's the point of this _NET_WM_BYPASS_COMPOSITOR (bug 349910).
But unfortunately not every software that can take benefit of it will use it,
therefore the blacklist.
By the way I see that you have submitted a review request
https://git.reviewboard.kde.org/r/126561/ Does this mean that it will be
implemented ?

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

[frameworks-ktexteditor] [Bug 256561] Katepart scrolls per paragraph rather than what is set globally (e.g. 3 lines)

[Michael D via KDE Bugzilla]

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

--- Comment #19 from Michael D  ---
Any status on this?

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

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

[Seth Izenzon via KDE Bugzilla]

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

Bug ID: 357694
   Summary: Kopete crashed when looking at settings
   Product: kopete
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kopete-bugs-n...@kde.org
  Reporter: izen...@gmail.com

Application: kopete (1.7.3)
KDE Platform Version: 4.14.14
Qt Version: 4.8.6
Operating System: Linux 4.2.0-23-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
When looking at the settings where you see all your contacts Kopete Crashed. I
am only using it because Teepathy (KDE contact messager) has that bug where it
won't Auth to Google and other's like it via xmmp still.

The crash can be reproduced every time.

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2905485840 (LWP 24046))]

Thread 5 (Thread 0x7f28eaa3b700 (LWP 24047)):
#0  0x7f290174b49d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f28fcb414e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f28fcafdcd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f28fcafe190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f28fcafe2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f28fcafe339 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f28fcb24965 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f28fd3f36aa in start_thread (arg=0x7f28eaa3b700) at
pthread_create.c:333
#8  0x7f290175aeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f28e9a39700 (LWP 24049)):
#0  0x7f290174f8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f28fcafe1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f28fcafe572 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f28eaf4c4c6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f28fcb24965 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f28fd3f36aa in start_thread (arg=0x7f28e9a39700) at
pthread_create.c:333
#6  0x7f290175aeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f28d8e5b700 (LWP 24054)):
#0  0x7f290174f8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f28fcafe1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f28fcafe2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2902ee720e in QEventDispatcherGlib::processEvents
(this=0x7f28d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f2902eb50d1 in QEventLoop::processEvents
(this=this@entry=0x7f28d40013b0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f2902eb5445 in QEventLoop::exec (this=0x7f28d40013b0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f28dad7d9a3 in QCA::SyncThread::run() () from
/usr/lib/x86_64-linux-gnu/libqca.so.2
#7  0x7f2902da6d1c in QThreadPrivate::start (arg=0x2c9ff00) at
thread/qthread_unix.cpp:349
#8  0x7f28fd3f36aa in start_thread (arg=0x7f28d8e5b700) at
pthread_create.c:333
#9  0x7f290175aeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f28d3fff700 (LWP 24055)):
#0  0x7f28fcafb2ca in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f28fcafdb4a in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f28fcafe190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f28fcafe2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2902ee720e in QEventDispatcherGlib::processEvents
(this=0x7f28cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x7f2902eb50d1 in QEventLoop::processEvents
(this=this@entry=0x7f28d3ffece0, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f2902eb5445 in QEventLoop::exec (this=this@entry=0x7f28d3ffece0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f2902da44f9 in QThread::exec (this=) at
thread/qthread.cpp:538
#8  0x7f28db1b9b2a in ?? () from /usr/lib/kde4/kopete_jabber.so
#9  0x7f2902da6d1c in QThreadPrivate::start (arg=0x2722010) at
thread/qthread_unix.cpp:349
#10 0x7f28fd3f36aa in start_thread (arg=0x7f28d3fff700) at
pthread_create.c:333
#11 0x7f290175aeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f2905485840 (LWP 24046)):
[KCrash Handler]
#6  QWidget::testAttribute (attribute=, this=) at
/usr/include/qt4/QtGui/qwidget.h:1044
#7  QWidget::underMouse (this=0x0) at /usr/include/qt4/QtGui/qwidget.h:997
#8  

[dolphin] [Bug 357693] Preview scans files opened for read/write resulting in an endless scan, locking up CPU/Desktop

[via KDE Bugzilla]

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

tuxfus...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from tuxfus...@gmail.com ---
Removing ffmpegthumbs-git r91.c06602f-1  fixed the issue. Created files (copy,
encoded) are not touched, or only every 10 seconds which is okay. This request
was false alert on my side.

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

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Seth Izenzon via KDE Bugzilla]

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

Seth Izenzon  changed:

   What|Removed |Added

 CC||izen...@gmail.com

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

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Seth Izenzon via KDE Bugzilla]

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

--- Comment #47 from Seth Izenzon  ---
Created attachment 96523
  --> https://bugs.kde.org/attachment.cgi?id=96523=edit
New crash information added by DrKonqi

kopete (1.7.3) on KDE Platform 4.14.14 using Qt 4.8.6

- What I was doing when the application crashed:

I was playing with settings in Kopete and I closed a chat window and it
crashed.

-- Backtrace (Reduced):
#7  0x7f82929c43c5 in QObject::disconnect (sender=0x3177df0,
signal=0x3394e19 "destroyed()", signal@entry=0x7f828af92293 "2destroyed()",
receiver=receiver@entry=0x307c4e0, method=0x339b349
"slotManagedTopLevelWidgetDestroyed()", method@entry=0x7f828af92eb8
"1slotManagedTopLevelWidgetDestroyed()") at kernel/qobject.cpp:2911
#8  0x7f828af780d9 in KParts::PartManager::~PartManager (this=0x307c4e0,
__in_chrg=) at ../../kparts/partmanager.cpp:132
#9  0x7f828af782a9 in KParts::PartManager::~PartManager (this=0x307c4e0,
__in_chrg=) at ../../kparts/partmanager.cpp:143
#10 0x7f82929c7201 in QObjectPrivate::deleteChildren
(this=this@entry=0x313e260) at kernel/qobject.cpp:1935
#11 0x7f82929c98a4 in QObject::~QObject (this=0x312eb50,
__in_chrg=) at kernel/qobject.cpp:954

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

[rekonq] [Bug 357695] New: Constant crashes

[via KDE Bugzilla]

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

Bug ID: 357695
   Summary: Constant crashes
   Product: rekonq
   Version: 2.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: adj...@gmail.com
  Reporter: kubuntug...@suremail.info

Application: rekonq (2.4.2)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.0-23-generic x86_64
Distribution: Ubuntu 15.10

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

Browsing web pages in general. Doesn't matter what URL, it just eventually
crashes no matter what page I'm visiting or what type of content it has. And
I'm using a disposable email for this report and will never make another report
because you've made it so effing difficult. You should not be requiring
accounts in order to report bugs. You're basically doing everything wrong, and
I'm about to give up on Ubuntu altogether because you've been heading the wrong
direction since about 6.10.

The crash can be reproduced every time.

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

Thread 19 (Thread 0x7fb3727d8700 (LWP 15551)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb388cf88cd in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fb38978b6b4 ) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/FastMalloc.cpp:2575
#2  0x7fb388cf8929 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0x7fb38978b6b4 ) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/FastMalloc.cpp:1771
#3  0x7fb3804cf6aa in start_thread (arg=0x7fb3727d8700) at
pthread_create.c:333
#4  0x7fb3898a7eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fb32bfff700 (LWP 15553)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7fb388d2b6ca in WTF::ThreadCondition::timedWait (this=0x7fb371f4d4a0,
mutex=0x7fb371f4d478, absoluteTime=846610069.27490234) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/ThreadingPthreads.cpp:400
#2  0x7fb388a1ac05 in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x7fb371f4d398) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/JavaScriptCore/heap/BlockAllocator.cpp:89
#3  0x7fb388d2b066 in WTF::wtfThreadEntryPoint (param=0x1c89820) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/ThreadingPthreads.cpp:196
#4  0x7fb3804cf6aa in start_thread (arg=0x7fb32bfff700) at
pthread_create.c:333
#5  0x7fb3898a7eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7fb32adcd700 (LWP 15554)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb3881138d4 in WebCore::IconDatabase::syncThreadMainLoop() () at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/SegmentedVector.h:129
#2  0x7fb388113b19 in WebCore::IconDatabase::iconDatabaseSyncThread() () at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/SegmentedVector.h:129
#3  0x7fb388d2b066 in WTF::wtfThreadEntryPoint (param=0x1f7f630) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/ThreadingPthreads.cpp:196
#4  0x7fb3804cf6aa in start_thread (arg=0x7fb32adcd700) at
pthread_create.c:333
#5  0x7fb3898a7eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7fb32a4cc700 (LWP 1)):
#0  0x7fb38989c8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb3811d51ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb3811d52fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb383c5520e in QEventDispatcherGlib::processEvents
(this=0x7fb328c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fb383c230d1 in QEventLoop::processEvents
(this=this@entry=0x7fb32a4cbd90, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fb383c23445 in QEventLoop::exec (this=this@entry=0x7fb32a4cbd90,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fb383b124f9 in QThread::exec (this=) at
thread/qthread.cpp:538
#7  0x7fb383b14d1c in QThreadPrivate::start (arg=0x1e0c6b0) at
thread/qthread_unix.cpp:349
#8  0x7fb3804cf6aa in start_thread (arg=0x7fb32a4cc700) at
pthread_create.c:333
#9  0x7fb3898a7eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fb328a75700 (LWP 15557)):
#0  0x7fb38989849d in read () at 

[kdevelop] [Bug 341352] Quickly copy filename to clipboard (with variations)

[Kevin Funk via KDE Bugzilla]

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

--- Comment #3 from Kevin Funk  ---
Hint: Relevant code location: kdevplatform.git:sublime/container.cpp
(Container::contextMenu)

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

[kdevplatform] [Bug 347351] commit fails when no git user/email are configured

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

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

--- Comment #1 from Kevin Funk  ---
Is this just about the CI failure? If yes, I fixed this a while ago...

Do we need changes to handle this case in a normal KDevelop run?

(I don't think so, you already get the output in the terminal view afaik, so
the user knows what's going wrong).

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

[digikam] [Bug 357723] New: Digikam Crashes while assigning a label to mutiple pictures

[via KDE Bugzilla]

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

Bug ID: 357723
   Summary: Digikam Crashes while assigning a label to mutiple
pictures
   Product: digikam
   Version: 4.14.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: thedur...@gmail.com

Application: digikam (4.14.0)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.3.3-4-default x86_64
Distribution: "openSUSE Tumbleweed (20151124) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: Digikam Crashes while
assigning the 'Rejected' label to mutiple pictures. It doesn't seam to be just
rejected but accepted and any other label.
 It only seems to do it in subfolders and only the first time I try to tag the
image. After I restart the program after it crashes I can change the label.

If I  pick a color first it doesn't crash any more for those pictures, any
other picture will make it crash if I don't change the color first.

The last time it crashed I ran it in Konsole and it spat out this:
"Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/5609_p0.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/5609_p1.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/5609_p1.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/5609_p2.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/5609_p0.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/5609_p1.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/5609_p2.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/5609_p0.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/16626557_p0.jpg"
"user.xdg.tags" 
Could not delete xattr for "/mnt/data/WALLPAPERS/Vertical/16626557_p0.jpg"
"user.xdg.comment" 
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/kate/.kde4/socket-Bernkastel/kdeinit4__0
QMYSQLResult::cleanup: unable to free statement handle
digikam: Fatal IO error: client killed
QSocketNotifier: Invalid socket 37 and type 'Read', disabling..."

- Custom settings of the application: I am using MySQL database instead of
SQLite. I am using MariaDB 10.0.22.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd310a0e9c0 (LWP 1231))]

Thread 14 (Thread 0x7fd2f237f700 (LWP 1233)):
#0  0x7fd306d6507f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd30a070754 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x005f6cac in  ()
#3  0x7fd30a07023c in  () at /usr/lib64/libQtCore.so.4
#4  0x7fd306d5f4a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7fd309509bdd in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fd2f1b7e700 (LWP 1234)):
#0  0x7fd30951615f in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7fd309501242 in poll () at /lib64/libc.so.6
#2  0x7fd30164c264 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fd30164c36c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fd30a1a426e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7fd30a1743e1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fd30a1746f5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7fd30a06da59 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7fd30a1554c3 in  () at /usr/lib64/libQtCore.so.4
#9  0x7fd30a07023c in  () at /usr/lib64/libQtCore.so.4
#10 0x7fd306d5f4a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fd309509bdd in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fd2f137d700 (LWP 1248)):
#0  0x7fd306d6507f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd30a070754 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7fd30e77f5d2 in  () at /usr/lib64/libdigikamcore.so.4.14.0
#3  0x7fd30a07023c in  () at /usr/lib64/libQtCore.so.4
#4  0x7fd306d5f4a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7fd309509bdd in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fd2174d7700 (LWP 1300)):
#0  0x7fd30950124d in poll () at /lib64/libc.so.6
#1  0x7fd21fbdfae8 in  () at /usr/lib64/libusb-1.0.so.0
#2  0x7fd306d5f4a4 in start_thread () at /lib64/libpthread.so.0
#3  0x7fd309509bdd in clone 

[digikam] [Bug 357723] Digikam Crashes while assigning a label to mutiple pictures

[via KDE Bugzilla]

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

--- Comment #2 from thedur...@gmail.com ---
I was playing around with how many and how many sub-directories down and it
almost seems random but has to be 2 or more. It'll do it to PNG, JPG and CR2
(canon raw) files.

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

[choqok] [Bug 357588] should use NetworkManager online status

[Mehrdad Momeny via KDE Bugzilla]

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

Mehrdad Momeny  changed:

   What|Removed |Added

   Target Milestone|1.6 |---
 Ever confirmed|1   |0
   Priority|NOR |LO
 Status|CONFIRMED   |UNCONFIRMED

--- Comment #2 from Mehrdad Momeny  ---
Well, I tried this here, (logging into KDE while the networking is disabled and
clicking on Update Timelines menu option to update) but in both cases, it does
not show connection error as a popup message box. just report it in a message
in Choqok window's status bar.
And I do remember that we had only one message showing in start-up time, and it
was eliminated some time ago. and upon re-checking the source codes, I see only
message box errors in cases where user is interacting with the app. (e.g.
posting a tweet)

While the idea of checking if system is connected looks nice, I don't think it
worth the hassle, considering that every module in Choqok is now contacting
directly something on the network to load some stuff.

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

[Baloo] [Bug 357723] Digikam Crashes while assigning a label to mutiple pictures

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|general |General
   Assignee|digikam-de...@kde.org   |m...@vhanda.in
Product|digikam |Baloo
 CC||caulier.gil...@gmail.com,
   ||pinak.ah...@gmail.com
Version|4.14.0  |unspecified

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