[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

2016-10-12 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361236

Thomas Meiner  changed:

   What|Removed |Added

 CC|tho@gmx.net |

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


[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

2016-10-12 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361236

Thomas Meiner  changed:

   What|Removed |Added

 CC||tho@gmx.net

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


[kwin] [Bug 365170] New: KWin Crash while opening a dialog of LibreOffice 5

2016-07-06 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365170

Bug ID: 365170
   Summary: KWin Crash while opening a dialog of LibreOffice 5
   Product: kwin
   Version: 5.6.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tho@gmx.net

Application: kwin_x11 (5.6.5)

Qt Version: 5.6.0
Frameworks Version: 5.23.0
Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- Unusual behavior I noticed:
KWin Crash while opening a dialog of LibreOffice 5. (on Fedora 24)

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6843d5d940 (LWP 3961))]

Thread 6 (Thread 0x7f68165e5700 (LWP 3976)):
#0  0x7f6856c4bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f685c881424 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f685c881469 in  () at /lib64/libQt5Script.so.5
#3  0x7f6856c465ca in start_thread () at /lib64/libpthread.so.0
#4  0x7f6853fceead in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f681c8d5700 (LWP 3971)):
#0  0x7f6853fc5103 in select () at /lib64/libc.so.6
#1  0x7f68554dfaef in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7f68554e11e4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7f68554e171a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f6855492a6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f68552f2a03 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f685b8c9145 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f68552f703a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f6856c465ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f6853fceead in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f68348c6700 (LWP 3969)):
#0  0x7f6855392fc0 in unixCheckClockType() () at /lib64/libQt5Core.so.5
#1  0x7f6855393009 in QElapsedTimer::clockType() () at
/lib64/libQt5Core.so.5
#2  0x7f6855393029 in QElapsedTimer::isMonotonic() () at
/lib64/libQt5Core.so.5
#3  0x7f68554e200e in QTimerInfoList::repairTimersIfNeeded() () at
/lib64/libQt5Core.so.5
#4  0x7f68554e2083 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f68554e16ba in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f6855492a6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f68552f2a03 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f685b8c9145 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#9  0x7f68552f703a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7f6856c465ca in start_thread () at /lib64/libpthread.so.0
#11 0x7f6853fceead in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f6837138700 (LWP 3966)):
#0  0x7f6853fc5103 in select () at /lib64/libc.so.6
#1  0x7f68554dfaef in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7f68554e11e4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7f68554e171a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f6855492a6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f68552f2a03 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f68567453b9 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f68552f703a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f6856c465ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f6853fceead in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f683c854700 (LWP 3965)):
#0  0x7f6853fc332d in poll () at /lib64/libc.so.6
#1  0x7f6855039f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f685503bb79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f683d0bb0f9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f68552f703a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f6856c465ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f6853fceead in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6843d5d940 (LWP 3961)):
[KCrash Handler]
#6  0x7f685b8b4ab0 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/lib64/libQt5Qml.so.5
#7  0x7f685b8b5807 in
QQmlBinding::update(QFlags) () at
/lib64/libQt5Qml.so.5
#8  0x7f685b8bee85 in
QQmlObjectC

[gwenview] [Bug 365278] New: gwenview crashes wihle opening a image form trash://

2016-07-09 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365278

Bug ID: 365278
   Summary: gwenview crashes wihle opening a image form trash://
   Product: gwenview
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: tho@gmx.net
CC: myr...@kde.org

Application: gwenview (16.04.2)

Qt Version: 5.6.0
Frameworks Version: 5.23.0
Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
gwenview crashes wihle opening a image form trash://

- 100% reproducible!

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3bcc6e99c0 (LWP 8679))]

Thread 2 (Thread 0x7f3bc1bdf700 (LWP 8681)):
#0  0x7f3bdaa7532d in poll () at /lib64/libc.so.6
#1  0x7f3bd6bf1a46 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f3bd6bf1b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f3bdb87965b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f3bdb828a6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f3bdb688a03 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f3bdbf743b9 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f3bdb68d03a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f3bd94a15ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f3bdaa80ead in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f3bcc6e99c0 (LWP 8679)):
[KCrash Handler]
#6  0x7f3bdcf8c2c5 in
QGraphicsItemPrivate::invalidateParentGraphicsEffectsRecursively() () at
/lib64/libQt5Widgets.so.5
#7  0x7f3bdcf971b5 in QGraphicsItem::update(QRectF const&) () at
/lib64/libQt5Widgets.so.5
#8  0x7f3be2b7a49d in Gwenview::RasterImageView::updateImageRect(QRect
const&) () at /lib64/libgwenviewlib.so.5
#9  0x7f3be2be54d9 in
Gwenview::RasterImageView::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) () at /lib64/libgwenviewlib.so.5
#10 0x7f3bdb852012 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#11 0x7f3be2be26f5 in Gwenview::Document::imageRectUpdated(QRect const&) ()
at /lib64/libgwenviewlib.so.5
#12 0x7f3bdb852012 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#13 0x7f3be2be23d2 in
Gwenview::AbstractDocumentImpl::imageRectUpdated(QRect const&) () at
/lib64/libgwenviewlib.so.5
#14 0x7f3be2b65d9b in Gwenview::DocumentLoadedImpl::init() () at
/lib64/libgwenviewlib.so.5
#15 0x7f3be2b5aae5 in
Gwenview::Document::switchToImpl(Gwenview::AbstractDocumentImpl*) () at
/lib64/libgwenviewlib.so.5
#16 0x7f3be2b66ea8 in Gwenview::LoadingDocumentImpl::slotImageLoaded() ()
at /lib64/libgwenviewlib.so.5
#17 0x7f3bdb852012 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#18 0x7f3bdb685666 in QFutureWatcherBase::event(QEvent*) () at
/lib64/libQt5Core.so.5
#19 0x7f3bdcca234c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#20 0x7f3bdcca752f in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#21 0x7f3bdb829bfa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#22 0x7f3bdb82bc9f in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#23 0x7f3bdb8795c3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#24 0x7f3bd6bf1703 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#25 0x7f3bd6bf1ab0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#26 0x7f3bd6bf1b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#27 0x7f3bdb87963f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#28 0x7f3bdb828a6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#29 0x7f3bdb8305fc in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#30 0x55878b7b1cd8 in main ()

Reported using DrKonqi

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


[kwin] [Bug 365988] New: Kwin crashes on firefox start

2016-07-22 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365988

Bug ID: 365988
   Summary: Kwin crashes on firefox start
   Product: kwin
   Version: 5.6.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tho@gmx.net

Application: kwin_x11 (5.6.5)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.6.4-301.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Kwin crashes on firefox start
Not reprodusable.
When will you fix this issues with KWin finally? We deal with it sind a long
time now.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb753438940 (LWP 1155))]

Thread 6 (Thread 0x7fb739696700 (LWP 1503)):
#0  0x7fb7636a4103 in select () at /lib64/libc.so.6
#1  0x7fb764bc06df in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7fb764bc1dd4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7fb764bc230a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fb764b735ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fb7649d2343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fb76afb18f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7fb7649d699a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fb7636adead in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fb738e95700 (LWP 1310)):
#0  0x7fb766333bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb76bf6abc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7fb76bf6ac09 in  () at /lib64/libQt5Script.so.5
#3  0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0
#4  0x7fb7636adead in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fb73bfff700 (LWP 1254)):
#0  0x7fb7636a4103 in select () at /lib64/libc.so.6
#1  0x7fb764bc06df in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7fb764bc1dd4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7fb764bc230a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fb764b735ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fb7649d2343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fb76afb18f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7fb7649d699a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fb7636adead in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fb74a866700 (LWP 1207)):
#0  0x7fb7636a4103 in select () at /lib64/libc.so.6
#1  0x7fb764bc06df in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7fb764bc1dd4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7fb764bc230a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fb764b735ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fb7649d2343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fb765e2a559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fb7649d699a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fb7636adead in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fb74bf2b700 (LWP 1200)):
#0  0x7fb7636a232d in poll () at /lib64/libc.so.6
#1  0x7fb764718f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fb76471ab79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fb74c9d6da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fb7649d699a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0
#6  0x7fb7636adead in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fb753438940 (LWP 1155)):
[KCrash Handler]
#6  0x7fb76af9cd50 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/lib64/libQt5Qml.so.5
#7  0x7fb76af9daa7 in
QQmlBinding::update(QFlags) () at
/lib64/libQt5Qml.so.5
#8  0x7fb76afa7615 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at
/lib64/libQt5Qml.so.5
#9  0x7fb76af3142e in QQmlComponentPr

[kscreenlocker] [Bug 368884] New: Kscreenlocker locks screen for ever! (a critical bug)

2016-09-16 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368884

Bug ID: 368884
   Summary: Kscreenlocker locks screen for ever! (a critical bug)
   Product: kscreenlocker
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: breeze-theme
  Assignee: plasma-b...@kde.org
  Reporter: tho@gmx.net
CC: bhus...@gmail.com, mgraess...@kde.org

Description of problem:
Since the last update for Kscreenlocker, it displays only a black screen and
does not react on any key or mouse movement.The only way to get out is to kill
Xorg.

Version-Release number of selected component (if applicable):
Fedora 24
Kscreenlocker 5.7.4

How reproducible: 100%

Reproducible: Always

Steps to Reproduce:
Each time Kscreenlocker takes control of the screen!

Actual Results:  
Only a totality black screen. Does not react on any key or mouse movement.

Expected Results:  
At least: Show the password line for unlock at mouse movement or key hit. 
Nice to have: Play a screensavers like it used to be in KED 4. ;-) 

The only way to unlock the screen is to kill Xorg! This may causes loose of
data, because the howl X-Sesseion is killed. Under this aspect it is a very
critical but!

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


[kscreenlocker] [Bug 368884] Kscreenlocker locks screen for ever! (a critical bug)

2016-09-16 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368884

Thomas Meiner  changed:

   What|Removed |Added

 CC||tho@gmx.net

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


[kscreenlocker] [Bug 368884] Kscreenlocker locks screen for ever! (a critical bug)

2016-09-16 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368884

--- Comment #1 from Thomas Meiner  ---
See: https://bugs.kde.org/show_bug.cgi?id=368884

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


[kscreenlocker] [Bug 368884] Kscreenlocker locks screen for ever! (a critical bug)

2016-09-16 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368884

--- Comment #2 from Thomas Meiner  ---
Sorry that above was the wrong address:
see: https://bugzilla.redhat.com/show_bug.cgi?id=1376364

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


[gwenview] [Bug 360590] New: The background in fullscreen mode is not black, even is it is set to black in the settings.

2016-03-15 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360590

Bug ID: 360590
   Summary: The background in fullscreen mode is not black, even
is it is set to black in the settings.
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: tho@gmx.net
CC: myr...@kde.org

I often use Gwenview fullscreen mode to present images on a projector. But
since the last update in Fedora 22 (to Gwenview 4.14.17) the background isn't
really black any more, Is exactly #191919. This causes an ugly shine beside the
image. In the configurations dialogue I've backgrund colour set to back and
there it's really black (#000)

Reproducible: Always

Steps to Reproduce:
1. Set backgrund colour to #000 in the configurations dialogue.
2. Open an image in fullscreen mode, witch has an other aspect ratio then your
screen.
3. Have a look at the not form the image covered backgrund. It's #191919.

Actual Results:  
color: #191919

Expected Results:  
color: #000

I'm on Fedora 22 with the latest stable package: gwenview.x86_64_4.14.3-4.fc22

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2016-06-27 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #59 from Thomas Meiner  ---
Created attachment 99725
  --> https://bugs.kde.org/attachment.cgi?id=99725&action=edit
networkmanager uses not even the half of the screeen size

Networkmanager uses not even the half of the screeen size.
On Fedora 24.

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2016-06-27 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #60 from Thomas Meiner  ---
Created attachment 99726
  --> https://bugs.kde.org/attachment.cgi?id=99726&action=edit
The "add Widgets" dialogue is able to use the howl screen.

The "add Widgets" dialogue is able to use the howl screen. On Fedora 24.
Like this should all Plasashell elements work. Like in KED4!

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2016-06-27 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #61 from Thomas Meiner  ---
The two screenshots I posted above illustrate the still existing problem. It
seams nothing happens here. Really sad!

Why is it so hard to bring back the behavior of KDE4?
Are there any plans to fix this?

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2016-02-20 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #44 from Thomas Meiner  ---
I did in Bug 354879 not ask for the "pin button". That's not the solution to
this bug. None at all.

I was asking for the behaver of KED 4. There all items, like Kickoff,
Clipboard, Networkmanager or Notifications did automatic change their high.
According to there content size. Only if they have been larger then the screen,
a scrollbar appeared. This worked in KDE 4 very well. The exciting solution in
KED 5 is a big step backwards. Sad.

Pleas bring back the more user-friendly behaver of KED4. The "pin button" is
just a workaround and not a solution or a fix. None at all

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2016-02-20 Thread Thomas Meiner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #46 from Thomas Meiner  ---
Again:
The user should not need to resize the items by it self. Plasma should do it by
itself. As it was in KED 4.
All the ' "alt" key and drag with rightclick mous'-staff is just a workaround,
but does not solve the problem.

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