date:20160327

[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor

2016-03-27 Thread via KDE Bugzilla

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

--- Comment #43 from alfa...@gmx.de ---

> Do you mean the slight lag of like couple pixels? About the same as Window
> drag?
Yes, just a couple of pixels. A few days ago I've tested nouveau and noticed no
"lag" but as 3D performance is "non-existent", I've switched back to
proprietary driver :-)

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

[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor

2016-03-27 Thread Artur O . via KDE Bugzilla

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

--- Comment #42 from Artur O.  ---
(In reply to alfaflo from comment #41)
> (In reply to alfaflo from comment #38)
> > latest update (plasma 5.6 & qt 5.6) fixed it for me
> > by the way: plasma is now smooth like never before - thanks guys!
> > 
> > florian
> 
> An additional note: it seems that it's not fully gone. Compared to using
> noveau there's still a (very) little  "lag" but I think for daily use it's
> not a problem.

Do you mean the slight lag of like couple pixels? About the same as Window
drag?

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

[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor

2016-03-27 Thread via KDE Bugzilla

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

--- Comment #41 from alfa...@gmx.de ---
(In reply to alfaflo from comment #38)
> latest update (plasma 5.6 & qt 5.6) fixed it for me
> by the way: plasma is now smooth like never before - thanks guys!
> 
> florian

An additional note: it seems that it's not fully gone. Compared to using noveau
there's still a (very) little  "lag" but I think for daily use it's not a
problem.

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

[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor

2016-03-27 Thread via KDE Bugzilla

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

--- Comment #40 from alfa...@gmx.de ---
(In reply to alfaflo from comment #38)
> latest update (plasma 5.6 & qt 5.6) fixed it for me
> by the way: plasma is now smooth like never before - thanks guys!
> 
> florian

An additional note: it seems that it's not fully gone. Compared to using noveau
there's still a (very) little  "lag" but I think for daily use it's not a
problem.

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

[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities

2016-03-27 Thread Gilboa Davara via KDE Bugzilla

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

Gilboa Davara  changed:

   What|Removed |Added

 CC||gilb...@gmail.com

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

[plasmashell] [Bug 361073] New: Session Logout and Session Switch User (from application launcher) get wrong position on the dialog.

2016-03-27 Thread Artur O . via KDE Bugzilla

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

Bug ID: 361073
   Summary: Session Logout and Session Switch User (from
application launcher) get wrong position on the
dialog.
   Product: plasmashell
   Version: 5.6.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: commander.alch...@gmail.com
CC: plasma-b...@kde.org

Since the 5.6 update; 
session Logout dialog appears lower left of my primary monitor.
session switch user appears on the lower right of my primary monitor.

I have 3 monitors, (Portrait 1080x1920, Landscape 1920x1080, Landscape
1920x1080)
It seems that Logout appears trying to center between screen 0 and 1, while
switch user trying to center between them all and failing since the portrait
monitor is taller.

Reproducible: Always

Steps to Reproduce:
1. Have asymmetric screen setup, ie portrait and landscape screen setup. 
2. Click Leave - > Session Logout or Leave -> Session Switch User.
3. Dialog does not appear centered on primary monitor like it would before.

Actual Results:  
Wrong position.

Expected Results:  
Centered on primary monitor.

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

[frameworks-kitemmodels] [Bug 352369] KSelectionProxyModel bug

2016-03-27 Thread Stephen Kelly via KDE Bugzilla

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

Stephen Kelly  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kite
   ||mmodels/0cf75268b00decc0ecb
   ||e75ba905d7bc556dcca26
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #8 from Stephen Kelly  ---
Git commit 0cf75268b00decc0ecbe75ba905d7bc556dcca26 by Stephen Kelly.
Committed on 28/03/2016 at 05:09.
Pushed by skelly into branch 'master'.

KSPM: Recreate mapping on removal only if needed

Previously, the model would create a mapping for the wrong index while
processing removal.  Constrain the re-creation of the mapping by
determining at AboutToBe-time whether to re-create it.  This is
important because the mapping contains QPersistentModelIndexes to the
source model, and when post-processing the removal, that is already
invalidated.

M  +6-1src/kselectionproxymodel.cpp

http://commits.kde.org/kitemmodels/0cf75268b00decc0ecbe75ba905d7bc556dcca26

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

[krunner] [Bug 361072] New: krunner crashed when attempting to start konsole

2016-03-27 Thread Arthur Marsh via KDE Bugzilla

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

Bug ID: 361072
   Summary: krunner crashed when attempting to start konsole
   Product: krunner
   Version: 5.5.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: arthur.ma...@internode.on.net

Application: krunner (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.6.0-rc1 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
when attempting to start konsole via alt-F2 after restarting a KDE plasma
session following updates, krunner crashed and konsole did not start.

The crash can be reproduced sometimes.

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

Thread 12 (Thread 0x7f90bd959700 (LWP 23147)):
#0  0x0030004dfe4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00300340a382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f90bd958d00) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x00300340a382 in _xcb_conn_wait (c=c@entry=0x2522470,
cond=cond@entry=0x25224b0, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x00300340bff7 in xcb_wait_for_event (c=0x2522470) at
../../src/xcb_in.c:693
#4  0x7f90bddb8789 in QXcbEventReader::run() (this=0x25354c0) at
qxcbconnection.cpp:1230
#5  0x0030174a57fe in QThreadPrivate::start(void*) (arg=0x25354c0) at
thread/qthread_unix.cpp:331
#6  0x003000c07454 in start_thread (arg=0x7f90bd959700) at
pthread_create.c:334
#7  0x0030004e8edd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f90b4973700 (LWP 23151)):
#0  0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f90b79b3c43 in radeon_drm_cs_emit_ioctl (mtx=0x2618f40,
cond=0x2618f68) at ../../../../../../../include/c11/threads_posix.h:159
#2  0x7f90b79b3c43 in radeon_drm_cs_emit_ioctl (sema=0x2618f40) at
../../../../../../../src/gallium/auxiliary/os/os_thread.h:259
#3  0x7f90b79b3c43 in radeon_drm_cs_emit_ioctl
(param=param@entry=0x2618bf0) at
../../../../../../../src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:653
#4  0x7f90b79b3397 in impl_thrd_routine (p=) at
../../../../../../../include/c11/threads_posix.h:87
#5  0x003000c07454 in start_thread (arg=0x7f90b4973700) at
pthread_create.c:334
#6  0x0030004e8edd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f90b2fd8700 (LWP 23153)):
#0  0x00300408ea70 in g_mutex_lock (mutex=mutex@entry=0x7f90ac000990) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread-posix.c:1338
#1  0x003004049ae1 in g_main_context_query
(context=context@entry=0x7f90ac000990, max_priority=2147483647,
timeout=timeout@entry=0x7f90b2fd7cb4, fds=fds@entry=0x7f90ac003070,
n_fds=n_fds@entry=1) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3544
#2  0x00300404a2a7 in g_main_context_iterate
(context=context@entry=0x7f90ac000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3822
#3  0x00300404a43c in g_main_context_iteration (context=0x7f90ac000990,
may_block=may_block@entry=1) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3901
#4  0x0030176dca5b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f90ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x003017683d6a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f90b2fd7de0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x0030174a0854 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x0030476d5105 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x0030174a57fe in QThreadPrivate::start(void*) (arg=0x2956760) at
thread/qthread_unix.cpp:331
#9  0x003000c07454 in start_thread (arg=0x7f90b2fd8700) at
pthread_create.c:334
#10 0x0030004e8edd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f90a8d20700 (LWP 23289)):
#0  0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0030174a6a9b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x288ed90) at
thread/qwaitcondition_unix.cpp:136
#2  0x0030174a6a9b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x27d39b0, time=time@entry=18446744073709551615)
at thread/qwaitcondition_unix.cpp:208
#3  0x7f90b0ddb02b in

[plasmashell] [Bug 361071] New: Weather Forecast Widget - Cannot save configuration when loaded in system tray

2016-03-27 Thread aexoxea via KDE Bugzilla

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

Bug ID: 361071
Summary: Weather Forecast Widget - Cannot save configuration
when loaded in system tray
Product: plasmashell
Version: 5.6.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: aexoxea...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

(Apologies for placing in General; I'm not sure if this is a System Tray issue
or a Widget issue. Will try to get back to you in a timely fashion for any info
needed for re-assignment.)

The Weather Forecast Widget is listed as an "Extra Item" that can be activated
in the System Tray. However, it is not useful as there is no default weather
station configuration, and a new weather station cannot be set; you can bring
up the configuration dialog, search for and set a weather station, but the
"Apply" button is never activated and the weather station is not saved when you
select the "OK" button.

This also applies to other settings (the update frequency and units). You also
can't work around this by switching between the configuration modules, as the
usual 'unsaved changes' prompt never shows. It's as though you've changed
nothing, even though you have.

The Widget can be configured fine when added directly to a panel, or to the
desktop (both of which serve as workarounds), so it's just when activating it
as a System Tray Extra Item.

(If the Widget is not meant to be available as a System Tray Extra Item, then
I'm happy for this bug to be closed once the configuration that causes it to be
available there is removed; however, I will leave that to those who know
whether this is intended or not.)

Reproducible: Always

Steps to Reproduce:
1. Create a panel and add a System Tray to it.
2. Access the System Tray Settings, "Entries" module, and enable "Weather
Forecast". The Widget appears by default as a blank space in the System Tray.
3. Access Weather Forecast Settings for that Widget, either "Weather Station"
or "Units" modules, and change one or more settings. Note that the "Apply"
button does not activate.
4. Press the "OK" button. Note that the Widget does nothing.
5. Re-access Weather Forecast Settings for that Widget. Note that none of the
settings that you changed were saved.

Actual Results:
Widget is not configured and does nothing; re-opening the configuration dialog
shows changes not saved.

Expected Results:
Widget is configured and loads the weather for the specified weather station.

plasmashell logs various warnings when accessing the Weather Forecast Widget's
configuration dialog. There are two key differences to what happens when doing
this for the Widget in the System Tray vs. the Widget directly on the
panel/desktop, which may be relevant:

(1) The following warnings are logged for Widget in System Tray which are NOT
logged for Widget directly in Panel/Desktop:

plasmashell:
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/configWeatherStation.qml:63:
TypeError: Cannot read property 'nativeInterface' of null
plasmashell:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:75:
TypeError: Cannot read property 'configuration' of null

(2) The following warnings are logged for Widget directly in Panel/Desktop
which are NOT logged for Widget in System Tray:

plasmashell: Calling KPluginInfo::property("Name") is deprecated, use
KPluginInfo::name() in "/usr/lib/qt/plugins/plasma/dataengine/ion_noaa.so"
instead.
plasmashell: Calling KPluginInfo::property("Name") is deprecated, use
KPluginInfo::name() in "/usr/lib/qt/plugins/plasma/dataengine/ion_wettercom.so"
instead.
plasmashell: Calling KPluginInfo::property("Name") is deprecated, use
KPluginInfo::name() in "/usr/lib/qt/plugins/plasma/dataengine/ion_envcan.so"
instead.
plasmashell: init()
plasmashell:

1 2 >

1 - 100 of 168 matches

Mail list logo