[neon] [Bug 367519] Build fcitx-frontend-qt5 in neon

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #1 from Weng Xuetian  ---
Ping

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

[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #22 from Weng Xuetian  ---
Sorry for the noise.

Looks like the reverted plugin right now is not relevant to contact runner.
Can't reproduce it.

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

[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|FIXED   |---
 CC||wen...@gmail.com
 Status|RESOLVED|REOPENED

--- Comment #21 from Weng Xuetian  ---
IMHO, this need to be reopened since it's actually got reverted.

https://quickgit.kde.org/?p=kdepim-runtime.git=commit=acb496c86356d2b2fb6df23c108436db879a58ab

I wonder, if it is possible to make sure that krunner always load plugin in
main thread? It is quite possible that any krunner plugin need such assumption.

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

[Powerdevil] [Bug 366402] Closing the lid triggers Sleep

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #7 from Weng Xuetian  ---
well not all distro package latest systemd, so probably it will be skipped.

And you can also modify the logind.conf and set LidSwitchIgnoreInhibited=no

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

[neon] [Bug 367519] New: Build fcitx-frontend-qt5 in neon

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 367519
   Summary: Build fcitx-frontend-qt5 in neon
   Product: neon
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: wen...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

FYI: https://github.com/fcitx/fcitx-qt5/issues/17

Immodule in Qt5 need to use Private API of Qt5, from the information I have
neon has its own Qt package which is incompatible version for private API
comparing to the one in main repo.

Please consider package it since it is necessary for fcitx user to use input
method on Qt5 application.

Reproducible: Always

Steps to Reproduce:
run LANG=C sudo apt install fcitx-frontend-qt5 on neon

Actual Results:  
couldn't be installed because of incompatibility

Expected Results:  
neon has its own fcitx-frontend-qt5 build against neon's qt

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

[Powerdevil] [Bug 366402] Closing the lid triggers Sleep

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #5 from Weng Xuetian  ---
Just FYI:

https://github.com/systemd/systemd/issues/3897

Looks like the commit mentioned above will be reverted.

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

[KScreen] [Bug 358689] Support Qt 5.6 new highdpi environment variable

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #9 from Weng Xuetian  ---
(In reply to Martin Gräßlin from comment #8)
> (In reply to Weng Xuetian from comment #7)
> > This setting has nothing to do with X11, it's just for Qt itself.
> > 
> > you can set it like:
> > QT_SCREEN_SCALE_FACTORS=eDP1=2;eDP2=3
> > 
> > So when you move window among screen, the Qt's window will be rescaled to
> > the screen dpi automatically.
> 
> That cannot work on X11, sorry. That's just Qt's "I don't know how to
> multi-screen on X11". The problems here are:
> * a window is not connected with an output, it has a position within the X
> screen space
> * QWindow allows to set the QScreen, but this does not influence whether the
> window is sown on the screen
> * DPI for multi-screen on common X-Servers is broken. As soon as there are
> two screens, the X-Server does report a default 96 pdi AFAIK
> * when moving a window from one screen to another it could result in an
> infinite jumping between the different DPI modes
> * the totally legit situation of one window on two screens is not handled
> * the window manager does not adjust the window decoration
> * I could go on and on
> 
> Exposing a config option for that would be wrong: we cannot have different
> scale factors on X11. That would just introduce another set of things which
> can go wrong with Qt's utterly broken (and broken beyond repair)
> multi-screen implementation on X11.

Such complain doesn't solve anything. You're just pointing to some "Potential"
Problem that doesn't really happen. 

I have been using QT_DEVICE_PIXEL_RATIO=auto (when it's still old style env
var) since Qt 5.4, and it never cause me any trouble. Dynamically change
window's scale factor is tricky, but it's also the same approach on Windows. 

I have been use it for such a long time. And if any issue you claim actually
happens, Qt should fix it. Not to mention IT IS not the case. I have even seen
user complain about startkde script prevent user to set
QT_AUTO_SCREEN_SCALE_FACTOR to 1. It's not something badly broken, really.

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

[KScreen] [Bug 358689] Support Qt 5.6 new highdpi environment variable

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #7 from Weng Xuetian  ---
This setting has nothing to do with X11, it's just for Qt itself.

you can set it like:
QT_SCREEN_SCALE_FACTORS=eDP1=2;eDP2=3

So when you move window among screen, the Qt's window will be rescaled to the
screen dpi automatically.

Right now kscreen can only set it to the same value.

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

[KScreen] [Bug 358689] Support Qt 5.6 new highdpi environment variable

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #5 from Weng Xuetian  ---
Emm, I'd prefer leave it open until it support real "per screen" setting
instead of set same ratio for all screen.

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

[plasma-pa] [Bug 364687] Default device is not remembered

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #5 from Weng Xuetian  ---
I notice another problem is that "changing default device with
module-switch-on-connect and without module-device-manager" doesn't affect
existing running applications.

BTW, I'm not sure using module-switch-on-connect by default is the right
direction. Is any other desktop/distro using it by default?

And obviously it conflicts with module-device-manager.
Quote:
https://wiki.archlinux.org/index.php/PulseAudio#Switch_on_connect
"On KDE/Plasma5 you should furthermore disable module-device-manager. As soon
as Plasma5 is started it loads (via start-pulseaudio-x11) the module
module-device-manager for pulseaudio to manage the devices."

Quote:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1495865/comments/2
Upstream has generally recommended against loading it by default, claiming the
default sink should only be changed on user interaction.
It also kicks out possible role-based routing (i e, phone call on a USB headset
and music on speakers).

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

[plasma-pa] [Bug 364687] Default device is not remembered

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #4 from Weng Xuetian  ---
Then we probably want to inform distro/upstream to disable it first. Otherwise
it won't work as expected.

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

[plasma-pa] [Bug 364687] Default device is not remembered

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #2 from Weng Xuetian  ---
(In reply to David Rosca from comment #1)
> Hm, that's kind of to be expected actually. All it does is to change the
> default device in pulseaudio, so ideally pulseaudio should remember it.

If you know about start-pulseaudio-kde, you'll know that in the past, kde uses
different pulseaudio mechanism to select default device. (by using
/usr/bin/pactl load-module module-device-manager "do_routing=1" > /dev/null )

So that the old kcm phonon will be able to set a list of device to pa. I don't
think it uses the same "default" device mechanism  like other desktop. And
actually select default device from kcm doesn't do anything on my desktop. It
doesn't change application to use another device.

I think you probably want to pick up the same mechanism used by kcm phonon to
decide the real default device.

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

[plasma-pa] [Bug 364687] New: Default device is not remembered

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 364687
   Summary: Default device is not remembered
   Product: plasma-pa
   Version: 5.6.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: wen...@gmail.com
CC: plasma-b...@kde.org

I have a bluetooth headphone and I set it as default device in plasma-pa's kcm
after I first use it.

After I close it and reopen it, the default device is still the builtin-analog,
instead of the bluetooth device.

Reproducible: Always

Steps to Reproduce:
1. Connect bluetooth head set
2. Set it as default in plasma-pa's kcm
3. Close the headset
4. reopen and connect the headset

Actual Results:  
builtin-analog is default device.

Expected Results:  
Bluetooth headset becomes default device when it's available.

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

[plasma-pa] [Bug 364686] New: Change volume with global hotkey doesn't "unmute" the device.

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 364686
   Summary: Change volume with global hotkey doesn't "unmute" the
device.
   Product: plasma-pa
   Version: 5.6.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: wen...@gmail.com
CC: plasma-b...@kde.org

My sound card is muted, and press volume up/down doesn't unmute it. Using
plasma-pa 5.6.95

Reproducible: Always

Steps to Reproduce:
1. Mute the device
2. use volume up and down to change it

Actual Results:  
volume changes, but it's still muted

Expected Results:  
volume changes and device is unmuted.

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

[Touchpad-KCM] [Bug 349545] Disable touchpad when mouse is plugged in, never re-enables when mouse is unplugged

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #6 from Weng Xuetian  ---
(In reply to jose luis m from comment #5)
> This problem isn't fixed for everybody, in my system ,re-enable the touchpad
> once a mouse gets disconnected never worked. Not now , not before. I'm in
> Arch linux using:
> Touchpad  KCM version 5.6.4  
> KDE Frameworks 5.21.0
> Qt 5.6.0 (built against 5.6.0)

I just tried it and it worked for me. You'd probably want to blacklist some of
your usb device in kcm.

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

[neon] [Bug 362767] High DPI is messed up after Qt 5.6 update

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #9 from Weng Xuetian  ---
IIRC, though QT_DEVICE_PIXEL_RATIO is still there, it's not doing the exact
same thing as it is in 5.5 . For now I'm using a combination of
QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS to achieve the same
effect.

And kwin/plasma shouldn't be affected since they are not using it anyway, if
you found kwin/plasma is scaled, probably your distro need to compile
kwin/plasma against Qt 5.6 to make some qt5.6 compile time specific check work.

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #14 from Weng Xuetian  ---
Git commit 38804556588e977aaaea5f50115363d9f4dc379d by Weng Xuetian.
Committed on 08/05/2016 at 16:11.
Pushed by xuetianweng into branch 'Applications/16.04'.

Fix high dpi region selection.

Coordinates need to be scaled to native pixel before clip.

REVIEW: 127814

M  +8-2src/QuickEditor/EditorRoot.qml

http://commits.kde.org/kscreengenie/38804556588e977aaaea5f50115363d9f4dc379d

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

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

--- Comment #12 from Weng Xuetian  ---
I'm afraid this is not completely fixed yet.

If I use region selection, the actual selected image is not the correct one.
It's clipped to 1/4 of the top-left of selected region on my screen setup. Can
you check it again? I think the clip region also need to be scaled.

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #13 from Weng Xuetian  ---
Comment 12 is based on Applications/16.04 branch.

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

[Breeze] [Bug 361885] Kalarm crashes when closing main woindow

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #3 from Weng Xuetian  ---
(In reply to Aleix Pol from comment #2)
> That's the bug, it's fixed in Qt, just need to wait for Qt 5.6.1.
> 
> https://bugreports.qt.io/browse/QTBUG-51648

I don't think this is the right bug. The new dbus implementation is only
introduced in qt 5.6, while the reporter is using Qt 5.4.

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

[Breeze] [Bug 362041] New: Using Breeze icon theme with Gtk will have some warning

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 362041
   Summary: Using Breeze icon theme with Gtk will have some
warning
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: wen...@gmail.com
CC: kain...@gmail.com

When using breeze icon with gtk, gtk will output following warnings. Don't know
if this actually affects any functionality.

(thunderbird:10201): Gtk-WARNING **: Theme directory actions/48 of theme breeze
has no size field
(thunderbird:10201): Gtk-WARNING **: Theme directory categories/16 of theme
breeze has no size field
(thunderbird:10201): Gtk-WARNING **: Theme directory categories/22 of theme
breeze has no size field
(thunderbird:10201): Gtk-WARNING **: Theme directory categories/48 of theme
breeze has no size field
(thunderbird:10201): Gtk-WARNING **: Theme directory devices/48 of theme breeze
has no size field

Reproducible: Always

Steps to Reproduce:
1. Set icon theme to breeze
2. launch a gtk app

Actual Results:  
gtk outputs some warnings.

Expected Results:  
no warning.

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

[dolphin] [Bug 361946] New: Dolphin may crash when file in opened folder get modified

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 361946
   Summary: Dolphin may crash when file in opened folder get
modified
   Product: dolphin
   Version: unspecified
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: wen...@gmail.com

Application: dolphin (16.04.0)

Qt Version: 5.6.0
Frameworks Version: 5.21.0
Operating System: Linux 4.3.3-1-surfacepro3 x86_64
Distribution (Platform): Chakra

-- Information about the crash:
- What I was doing when the application crashed:
I was editing a po file in lokalize (Though I don't think which application
matters), just at the time I hit save button, dolphin crashed while dolphin was
displaying the folder containing the saved file.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8498b09800 (LWP 5827))]

Thread 5 (Thread 0x7f8482afe700 (LWP 5830)):
#0  0x7f849852e18d in poll () from /usr/lib/libc.so.6
#1  0x7f848ca9cae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f848ca9e757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f8484625329 in QXcbEventReader::run (this=0x176de90) at
qxcbconnection.cpp:1313
#4  0x7f8493004238 in QThreadPrivate::start (arg=0x176de90) at
thread/qthread_unix.cpp:340
#5  0x7f848f50f464 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f849853712d in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f8481861700 (LWP 5831)):
#0  0x7f848d3e9a23 in g_main_context_query () from
/usr/lib/libglib-2.0.so.0
#1  0x7f848d3ea157 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f848d3ea322 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f849322d1fb in QEventDispatcherGlib::processEvents
(this=0x7f84740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f84931d5c2a in QEventLoop::exec (this=this@entry=0x7f8481860d90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f8492fff434 in QThread::exec (this=this@entry=0x7f8498c5ed80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#6  0x7f8498be7859 in QDBusConnectionManager::run (this=0x7f8498c5ed80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#7  0x7f8493004238 in QThreadPrivate::start (arg=0x7f8498c5ed80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#8  0x7f848f50f464 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f849853712d in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f84788db700 (LWP 5832)):
#0  0x7f848f51503f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f8478a631b4 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f8478a631f9 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f848f50f464 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f849853712d in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f83f3bef700 (LWP 5833)):
#0  0x7f849852e18d in poll () from /usr/lib/libc.so.6
#1  0x7f848d3ea1e5 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f848d3ea322 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f849322d1fb in QEventDispatcherGlib::processEvents
(this=0x7f83ec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f84931d5c2a in QEventLoop::exec (this=this@entry=0x7f83f3beedc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f8492fff434 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f8493004238 in QThreadPrivate::start (arg=0x1dcf680) at
thread/qthread_unix.cpp:340
#7  0x7f848f50f464 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f849853712d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f8498b09800 (LWP 5827)):
[KCrash Handler]
#6  QList::operator+= (this=this@entry=0x7ffec9a5bf50, l=...) at
/usr/include/qt5/QtCore/qlist.h:931
#7  0x7f8498196d79 in QList::append (t=..., this=0x7ffec9a5bf50)
at /usr/include/qt5/QtCore/qlist.h:954
#8  KFileItemModelRolesUpdater::rolesData (this=this@entry=0x1dc4110, item=...)
at
/chakra/desktop/dolphin/src/dolphin-16.04.0/src/kitemviews/kfileitemmodelrolesupdater.cpp:1091
#9  0x7f849819ab32 in KFileItemModelRolesUpdater::applyResolvedRoles
(this=this@entry=0x1dc4110, index=index@entry=2,
hint=hint@entry=KFileItemModelRolesUpdater::ResolveAll) at
/chakra/desktop/dolphin/src/dolphin-16.04.0/src/kitemviews/kfileitemmodelrolesupdater.cpp:1047
#10 0x7f849819c791 in KFileItemModelRolesUpdater::resolveNextPendingRoles
(this=0x1dc4110) at

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

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

--- Comment #5 from Weng Xuetian  ---
Now I'm on 16.03.90 (with Qt 5.6.0 KF 5.21), I notice that "Rectangle region"
had the this problem again. It only shows the left top 1/4 part of the screen.

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #6 from Weng Xuetian  ---
I have no problem with 15.12.3 if I downgrade only spectacle.

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

[kate] [Bug 350535] Ctrl-Shift-U fails for inputting unicode

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Resolution|FIXED   |INVALID

--- Comment #2 from Weng Xuetian  ---
No, I don't think it's related. 2022 is not a over U+1 character.

The underline u is a feature provided by ibus. You should check whether you
have ibus's qt5 input context installed and configured correctly.

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

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #74 from Weng Xuetian  ---
Unfortunately now I get this crash again with qt 5.6.0, kf 5.20.0, plasma
5.6.0.

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

[kmail2] [Bug 355938] some messages become unread again and persist in folder

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #4 from Weng Xuetian  ---
Ok, now I notice a thing.

The unread status currently (15.12.3) is never sync'ed if there's no new
email/newly deleted mail in the folder. If there's a new email comes in , the
unread status will be updated.

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

[dolphin] [Bug 308309] Open file containing folder from search result.

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from Weng Xuetian  ---
This feature is included in at least since 15.12.3.

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

[krunner] [Bug 360268] New: KRunner autocomplete should not override the typed character case

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 360268
   Summary: KRunner autocomplete should not override the typed
character case
   Product: krunner
   Version: 5.5.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: wen...@gmail.com

For example, if I have typed "KSYSGUARD" before. next time krunner will already
replace what I have type with upper case even I type lowercase.

Reproducible: Always

Steps to Reproduce:
1. Make sure history is empty
2. Type KSYSGUARD to start ksysguard
3. type "ksys"

Actual Results:  
ksys is replaced by "KSYS".

Expected Results:  
it should still keep what user have typed exactly.

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

[plasmashell] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #79 from Weng Xuetian  ---
Git commit 6a26adb50c0bfce031df55bf200ebc7f44420301 by Weng Xuetian.
Committed on 01/03/2016 at 16:05.
Pushed by xuetianweng into branch 'master'.

Workaround by always reset model when insert and remove from model.

M  +6-5applets/systemtray/plugin/tasklistmodel.cpp

http://commits.kde.org/plasma-workspace/6a26adb50c0bfce031df55bf200ebc7f44420301

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

[plasmashell] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #78 from Weng Xuetian  ---
Welcome to test this patch to see if it can workaround this issue finally.

https://git.reviewboard.kde.org/r/127229/

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

[plasmashell] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #74 from Weng Xuetian  ---
(In reply to David Edmundson from comment #73)
> When you say "it's not fixed yet" are you including this patch or not?
> 
> https://codereview.qt-project.org/#/c/141620/
> 
> This is the one that we've said is the actual relevant fix not just
> attempted workarounds.

This is not the only bug in list view unfortunately. I didn't report it to qt
because I have no stable way to reproduce it. See my comment #30.

I wonder replace all {begin,end}InsertRow with {begin,end}ResetModel in
TaskListModel would workaround it.

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

[plasmashell] [Bug 358719] fcitx creates blank unusable xembed icon in systray

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.6.0
  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/829158f830555c
   ||031755c6d4348e684779264342

--- Comment #6 from Weng Xuetian  ---
Git commit 829158f830555c031755c6d4348e684779264342 by Weng Xuetian.
Committed on 09/02/2016 at 03:29.
Pushed by xuetianweng into branch 'master'.

Check whether there is any BadWindow error before monitor the event

The tray window itself may be destroyed before we start monitor the
event of it. Check the returned error and skip this window if BadWindow
happens.

FIXED-IN: 5.6.0
REVIEW: 127014

M  +23   -5xembed-sni-proxy/fdoselectionmanager.cpp
M  +1-1xembed-sni-proxy/fdoselectionmanager.h

http://commits.kde.org/plasma-workspace/829158f830555c031755c6d4348e684779264342

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

[digikam] [Bug 358910] New: OpenCV 3.1 support for libkface

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 358910
   Summary: OpenCV 3.1 support for libkface
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Engine
  Assignee: digikam-de...@kde.org
  Reporter: wen...@gmail.com

libkface doesn't compile with opencv 3.1, because of upstream change of
opencv-face interface.

I made a patch for it at:
https://git.reviewboard.kde.org/r/126833/


Reproducible: Always

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

[digikam] [Bug 358911] New: MySQL database cannot be configured if INTERNAL_MYSQL=Off

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 358911
   Summary: MySQL database cannot be configured if
INTERNAL_MYSQL=Off
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Database
  Assignee: digikam-de...@kde.org
  Reporter: wen...@gmail.com

The database ui combo box index doesn't match the enum value if internal_mysql
is off, thus it will always show the configuration for internal db, but no
external mysql.

I made a patch for it at:
https://git.reviewboard.kde.org/r/126872/

Reproducible: Always

Steps to Reproduce:
1. build digikam with mysql=on and internalmysql=off
2. open database settings
3. select mysql

Actual Results:  
the db option still shows a db path instead of host name etc.

Expected Results:  
shows the correct ui with host, username etc,

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

[digikam] [Bug 358911] MySQL database cannot be configured if INTERNAL_MYSQL=Off

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #2 from Weng Xuetian  ---
Created attachment 96977
  --> https://bugs.kde.org/attachment.cgi?id=96977=edit
patch

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

[Touchpad-KCM] [Bug 357907] Crash eventual crash, often on load

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #12 from Weng Xuetian  ---
Emm, one thing I mistook is that I thought it is in 5.5.3 because of the report
says so. But it's acutally in git.

So this should be fixed by
http://commits.kde.org/plasma-desktop/cda58f0e256d53e66ca44b77fa7307ee670b8313
.

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

[kate] [Bug 357097] kate v.15.08.3 segfaults when saving a new file

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #5 from Weng Xuetian  ---
Git commit cda58f0e256d53e66ca44b77fa7307ee670b8313 by Weng Xuetian.
Committed on 20/01/2016 at 18:44.
Pushed by xuetianweng into branch 'master'.

remove the duplicate m_touchpadOffAtom member.

m_touchpadOffAtom is already in XlibTouchpad, which makes ctor of
SynapticsTouchpad initialize wrong atom.

M  +1-1kcms/touchpad/src/backends/x11/synapticstouchpad.h

http://commits.kde.org/plasma-desktop/cda58f0e256d53e66ca44b77fa7307ee670b8313

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

[kdevelop] [Bug 358174] Icon of file entries in file tree is in the wrong space when using hidpi

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #1 from Weng Xuetian  ---
Created attachment 96713
  --> https://bugs.kde.org/attachment.cgi?id=96713=edit
Screenshot that shows the problem

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

[Touchpad-KCM] [Bug 357907] Crash eventual crash, often on load

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #9 from Weng Xuetian  ---
(In reply to Hrvoje Senjan from comment #8)
> The crash happens with plasma desktop master

Can you print out m_connection value with gdb? Can you make sure when it
crashes it run with newly installed instead of old one?

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

[Touchpad-KCM] [Bug 356923] Touchpad settings not applied upon touchpad plugin

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-desktop/a39677c1fd1e6303
   ||ddaf31da5ccd0a6454104066
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.6.0
 Resolution|--- |FIXED

--- Comment #1 from Weng Xuetian  ---
Git commit a39677c1fd1e6303ddaf31da5ccd0a6454104066 by Weng Xuetian.
Committed on 11/01/2016 at 20:38.
Pushed by xuetianweng into branch 'master'.

Refactor kcm touchpad to fix some issue related to hotplug touchpad

1. Remove SynapticsBackend and LibinputBackend and add three new classes
called XlibTouchpad/SynapticsTouchpad/LibinputTouchpad. So findTouchpad
may pick up both synaptics or libinput device, and no need to depend on
a fixed backend. This change also make it easier to support multiple
touchpad device easier if needed.

2. hotplug touchpad config not being applied (bug 356923) is mainly
because one can't apply settings to a disabled device. Change the
statement order in handleReset, apply settings first then set enable
status.

3. findTouchpad() is changed to use XListInputDevices, because it
provides necessary information of device type in order to filter
out non-touchpad device. xf86-input-libinput doesn't have a
unique atom for touchpad, so current identityAtom cannot
guarantee that findTouchpad always returns a touchpad device for
libinput.

4. On my surface pro 4 system, if touchpad is unpluged, the device will
be set to disabled automatically first, then touchpadDetached is called,
which makes m_enabled in TouchpadDisabled always to be false after
unplug the touchapd. This patch makes TouchpadDisabler have two
different enabled property. m_userRequestedState only stores the user
requested status, so when handleReset is called, it can properly set
enabled state to the last user requested state.

REVIEW: 126513
Related: bug 349545
FIXED-IN: 5.6.0

M  +2-2kcms/touchpad/src/applet/qml/contents/ui/touchpad.qml
M  +7-6kcms/touchpad/src/applet/touchpadengine.cpp
M  +1-0kcms/touchpad/src/applet/touchpadengine.h
M  +5-3kcms/touchpad/src/backends/x11.cmake
R  +28   -2kcms/touchpad/src/backends/x11/libinputtouchpad.cpp [from:
kcms/touchpad/src/backends/x11/libinputproperties.c - 059% similarity]
C  +7-22   kcms/touchpad/src/backends/x11/libinputtouchpad.h [from:
kcms/touchpad/src/applet/touchpadengine.h - 055% similarity]
A  +90   -0kcms/touchpad/src/backends/x11/propertyinfo.cpp [License:
GPL (v2+)]
C  +23   -18   kcms/touchpad/src/backends/x11/propertyinfo.h [from:
kcms/touchpad/src/applet/touchpadengine.h - 060% similarity]
R  +178  -69   kcms/touchpad/src/backends/x11/synapticstouchpad.cpp [from:
kcms/touchpad/src/backends/x11/synclientproperties.c - 053% similarity]
C  +12   -20   kcms/touchpad/src/backends/x11/synapticstouchpad.h [from:
kcms/touchpad/src/applet/touchpadengine.h - 056% similarity]
D  +0-71   kcms/touchpad/src/backends/x11/synclientproperties.h
M  +79   -557  kcms/touchpad/src/backends/x11/xlibbackend.cpp
M  +20   -30   kcms/touchpad/src/backends/x11/xlibbackend.h
A  +292  -0kcms/touchpad/src/backends/x11/xlibtouchpad.cpp [License:
UNKNOWN]  *
A  +88   -0kcms/touchpad/src/backends/x11/xlibtouchpad.h [License: GPL
(v2+)]
M  +39   -13   kcms/touchpad/src/kded/kded.cpp
M  +5-1kcms/touchpad/src/kded/kded.h
M  +2-1kcms/touchpad/src/touchpadbackend.h

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


http://commits.kde.org/plasma-desktop/a39677c1fd1e6303ddaf31da5ccd0a6454104066

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

[kwin] [Bug 357232] New: KWin crashes when spectacle tries to capture screenshot of a large window with "include title bar and borders" checked

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 357232
   Summary: KWin crashes when spectacle tries to capture
screenshot of a large window with "include title bar
and borders" checked
   Product: kwin
   Version: 5.5.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: wen...@gmail.com

When capture screen shot of a large window on my system, kwin ends with:
The X11 connection broke (error 4). Did the X11 server die?

Reproducible: Always

Steps to Reproduce:
1. open spectacle
2. select capture window under cursor
3. check "include title bar and borders"
4. tries to capture a large window, a maximized window will do and my screen
resolution is 3200x1800

Actual Results:  
screenshot captured and kwin still running

Expected Results:  
kwin exits

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

[Touchpad-KCM] [Bug 349545] Disable touchpad when mouse is plugged in, never re-enables when mouse is unplugged

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #2 from Weng Xuetian  ---
(In reply to Rex Dieter from comment #1)
> I tested and verified this behavior using both libinput and synaptics
> backends.

I have a review that may fix this bug:
https://git.reviewboard.kde.org/r/126513/

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

[Spectacle] [Bug 356765] Spectacle doesn't work properly with QT_DEVICE_PIXEL_RATIO=2

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Resolution|REMIND  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Weng Xuetian  ---


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

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #4 from Weng Xuetian  ---
*** Bug 356765 has been marked as a duplicate of this bug. ***

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

[kscreenlocker] [Bug 344145] ksmserver randomly hangs after suspend

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #6 from Weng Xuetian  ---
Me neither, probably close it as worksforme?

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

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

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #15 from Weng Xuetian  ---
I can confirm that this fixes the issue for me, thanks!

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

[Spectacle] [Bug 356765] New: Spectacle doesn't work properly with QT_DEVICE_PIXEL_RATIO=2

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 356765
   Summary: Spectacle doesn't work properly with
QT_DEVICE_PIXEL_RATIO=2
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: wen...@gmail.com

when select "rectangle" region, the screenshot prevent is scaled 2x and it only
shows 1/4 of the screen.

Reproducible: Always

Steps to Reproduce:
1. QT_DEVICE_PIXEL_RATIO=2 spectacle
2. Select "rectangle region"
3. Take a screen shot

Actual Results:  
The screenshot preview is scaled and only left top part of screen is shown.

Expected Results:  
Whole screen is shown properly.

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

[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #36 from Weng Xuetian  ---
(In reply to Albert Astals Cid from comment #32)
> I could always reproduce this bug doing
>echo 3 > /proc/sys/vm/drop_caches
> as root and then as my user killing and restarting plasmashell.
> 
> But now I can not reproduce it anymore. Neither in my two Ubuntu Xenial
> systems running  Plasma 5.4.3 + Qt 5.5.1 nor on my Arch Linux system running
> Plasma 5.5.1 + Qt 5.5.1 so can't help with fixing this anymore.
> 
> If you guys are convinced the above patch does not fix it reopen the bug.

Personally I don't have problem on my system with 5.4.3. I tried to bisect the
problem, and actually found it's a007f294b4991c6f5730e0ec8d9d20f36e31acab,
which is quite unrelated to the original problem. More specifically, it's this
change below. But anyway it seems to be a Qt bug since if I increase the time
(0 -> 300), then I will be able to reproduce the bug will be it no matter which
syntax it is used  on my system.

diff --git a/applets/systemtray/plugin/host.cpp
b/applets/systemtray/plugin/host.cpp
index 27ca227..61e8705 100644
--- a/applets/systemtray/plugin/host.cpp
+++ b/applets/systemtray/plugin/host.cpp
@@ -99,7 +99,7 @@ Host::Host(QObject* parent) :
 QObject(parent),
 d(new HostPrivate(this))
 {
-QTimer::singleShot(0, this, SLOT(init()));
+QTimer::singleShot(0, this, ::init);
 }

Now I workaround the bug by using "Always show all icon" option in system tray.

BTW To reproduce this bug, I need to have at least 10 icons in the system tray.

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

[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #30 from Weng Xuetian  ---
When I clicked on the "hole" on my system, I can see some warning from
plasmashell input, which says "modelData" undefined (qml file is
PlasmoidItem.qml). And I tried to print out the modelIndex, and found it's -1.

So this is not a visual problem but the attached model infomation is wrong.
While the linked QT bug itself looks like a pure visual problem. I'm afraid
that QT-BUG 48870 is not the only problem.

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

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

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #13 from Weng Xuetian  ---
(In reply to Thomas Lübking from comment #12)
> Outmost weird.
> 
> Xuetian, how do you start konsole maximized (by restored size, kwin rule,
> kstart, some konsole key I don't know ... ;-) and does it matter whether you
> flag --notransparency to it?
> 
> Can you also "qDebug() << object;" in the ::adjustPendingPalettes() loop to
> see what widgets there would actually be to fit this breeze code?
> 
> PS: In case Xuetian is actually your surname - sorry ^_^

I start konsole maximized just by closing konsole when it's maximized. It's
easier to reproduce the issue when it's maximized (so nothing covers it or
triggers repainting).

With --notransparency, it seems that there's no problem anymore, even though my
konsole profile doesn't use transparency.

After add qDebug(), only shows some some qmenu
http://paste.ubuntu.com/13836079/ .

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

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

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #6 from Weng Xuetian  ---
Ok, now I discover something new. I tried to downgrade kwin only but problem
was still there. But I tried to downgrade whole plasma group, it went back to
normal.

But once I get breeze updated to 5.5, with either version of kwin the problem
appears. So this seems to be related to breeze theme. I tried to use breeze
decoration with oxygen widget style, there's no problem, so probably related to
breeze widget style.

(In reply to Thomas Lübking from comment #5)
> Also try
>KWIN_USE_BUFFER_AGE=0 KWIN_EXPLICIT_SYNC=0 kwin_x11 --replace &
This doesn't help.

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

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

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

  Component|general |QStyle
   Assignee|kwin-bugs-n...@kde.org  |hugo.pere...@free.fr
Product|kwin|Breeze

--- Comment #7 from Weng Xuetian  ---
First bad commit in breeze found by git bisect.

http://commits.kde.org/breeze/6d852f30a1f2c1988359d4e0cdb21e2f1714a6bd

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

[kwin] [Bug 356343] New: Rendering issue after upgrade to kwin 5.5

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 356343
   Summary: Rendering issue after upgrade to kwin 5.5
   Product: kwin
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: wen...@gmail.com

E.g start konsole maximized will render something behind it, and it can be
captured by ksnapshot.

Output of  qdbus org.kde.KWin /KWin org.kde.KWin.supportInformation
http://paste.ubuntu.com/13764936/

Reproducible: Sometimes

Steps to Reproduce:
start konsole


Actual Results:  
render issue will be uploaded in next attachment.

Expected Results:  
renders correctly.

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

[plasma-nm] [Bug 356342] New: Size of popup of plasma-nm inside panel or desktop is very small

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 356342
   Summary: Size of popup of plasma-nm inside panel or desktop is
very small
   Product: plasma-nm
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: wen...@gmail.com
CC: lu...@kde.org

After adding plasma-nm applet to desktop or panel, it is shown as its compact
representation. Clicking on it will make it show a popup, but extremely small
and non-operational.

Reproducible: Always

Steps to Reproduce:
1. Add plasma-nm to desktop / panel
2. Click on it

Actual Results:  
Popup size is very small.

Expected Results:  
Popup size should be similar to the size when it is in system-tray popup.

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

[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

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