[plasma4] [Bug 366256] Plasma / Nvidia

2018-06-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=366256

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED

--- Comment #4 from Nate Graham  ---
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status
in August 2015. KDE Plasma 5's desktop shell has been almost completely
rewritten for better performance and usability, so it is likely that this bug
has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the
issue described  here is still present in KDE Plasma 5.12 or later, please feel
free to open a new ticket in the "plasmashell" product after reading
https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future
mass bug closes like this are less likely, please read
https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham

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

[plasma4] [Bug 366256] Plasma / Nvidia

2016-09-16 Thread Ilya Sheershoff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366256

--- Comment #3 from Ilya Sheershoff  ---
BTW, DrKonqi says bugzilla returned 410, but I've logged in with a just-created
account. Had to copy and post through the web :-)

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


[plasma4] [Bug 366256] Plasma / Nvidia

2016-09-16 Thread Ilya Sheershoff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366256

Ilya Sheershoff  changed:

   What|Removed |Added

 CC||sheersh...@gmail.com

--- Comment #2 from Ilya Sheershoff  ---
Looks similar:

Application: plasma-desktop (4.11.11)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.16.0-77-generic x86_64
Distribution: Ubuntu 14.04.5 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I booted, started google-chrome with ~280 tabs in ~17 windows, started my app
in docker-compose with ~10 machines launched. the crash happened when I
launched IntelliJ IDEA IDE (~ 6 projects in separate windows opened). Also
several programs was running: System Monitor (ksys...), telegram, skype...
I have an Acer Aspire V (V3-572G-72PX), connected to two monitors (Acer V246HL)
- by HDMI and D-SUB, configured to be by sides of the notebook screen, which is
chosen to be the main screen (the bottom launch bar is in the center).
- Unusual behavior I noticed:
Driver manager, btw, doesn't display that any of the displayed drivers are
chosen. None of the list has the radio button ticked. The provided list is the
following:
  NVIDIA binary drivers:
   - 340.96 from nvidia-340
   - 340.96 from nvidia-340-updates
   - 352.63 from nvidia-352 (Recommended Driver)
   - 352.63 from nvidia-352-updates
  X.Org X Server -- Nouveau display driver from xserver-xorg-video-nouveau
Half and a year ago I had hard time after updating NVIDIA drivers, or switching
to it (can't remember exactly) - the two attached monitors displayed the same
as the main screen (became just a duplicates) or were just black (not sure what
happened first, but there were these two states for sure, may be more states).
I spent a day to recover, so I'm not sure now what driver is running and with
what settings, but I'm not eager to experiment with changing or updating driver
settings.
Started around a month ago: sometimes one of the monitors or windows (they're
mostly full-screen) starts to flicker at left and right sides: around 5% at
left and at right (as far as i managed to notice, one of those where there's no
mouse pointer at the moment). This fixes by focusing on the flickering window
by clicking it.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f850bbb87c0 (LWP 2910))]

Thread 13 (Thread 0x7f84e197c700 (LWP 2935)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8504863ffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f8504864039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f84ff10f184 in start_thread (arg=0x7f84e197c700) at
pthread_create.c:312
#4  0x7f850b4ac37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 12 (Thread 0x7f845b8c9700 (LWP 2940)):
#0  0x7f84fea3f61d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f84fea3f979 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f84fe9fd557 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f84fe9fdf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f84fe9fe0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f85080797be in QEventDispatcherGlib::processEvents
(this=0x7f84540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f850804b0af in QEventLoop::processEvents
(this=this@entry=0x7f845b8c8de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f850804b3a5 in QEventLoop::exec (this=this@entry=0x7f845b8c8de0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f8507f47c5f in QThread::exec (this=this@entry=0x1492cc0) at
thread/qthread.cpp:537
#9  0x7f850802c823 in QInotifyFileSystemWatcherEngine::run (this=0x1492cc0)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f8507f4a32f in QThreadPrivate::start (arg=0x1492cc0) at
thread/qthread_unix.cpp:349
#11 0x7f84ff10f184 in start_thread (arg=0x7f845b8c9700) at
pthread_create.c:312
#12 0x7f850b4ac37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 11 (Thread 0x7f845906a700 (LWP 2941)):
#0  0x7f8507f49058 in QThreadData::current () at
thread/qthread_unix.cpp:249
#1  0x7f8508079af5 in postEventSourcePrepare (s=0x7f844c001350,
timeout=0x7f8459069c24) at kernel/qeventdispatcher_glib.cpp:263
#2  0x7f84fe9fd68d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f84fe9fdf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f84fe9fe0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f85080797be in QEventDispatcherGlib::processEvents

[plasma4] [Bug 366256] Plasma / Nvidia

2016-07-31 Thread Christoph Feck via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366256

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |4.11.11
Product|kde |plasma4
  Component|general |general
   Assignee|unassigned-b...@kde.org |plasma-b...@kde.org

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