[plasmashell] [Bug 371472] New: Icon drawing of active programs

2016-10-21 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371472

Bug ID: 371472
   Summary: Icon drawing of active programs
   Product: plasmashell
   Version: 5.8.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: jonfr1...@jonfr.com
CC: plasma-b...@kde.org

This is a odd "bug" (I don't consider it a feature). It is possible to move
icons of active programs from the task manager to a other areas of the screen.
This has the annoying side effect that sometimes the active program is brought
into moving mode and it's impossible to properly get rid of it. If it is
dropped into Firefox all that comes up is a random Chinese letters.  I have not
found an option to disable this behaviour in the Task manager.

Reproducible: Always

Steps to Reproduce:
1. Log into KDE Plasma 5.8.2. Click on active program and move the icon of the
active program.
2. Go to task manger and move the icon.
3.

Actual Results:  
Active programs can be moved to areas outside of the Task manager. This should
not happen (according to the settings menu).

Expected Results:  
It should not be able to move the icons around outside the task manager.

The chinease text that shows up when Firefox icon (I've also tested this using
the Shell window, shows the same information).

"楦敬⼺⼯獵⽲桳牡⽥灡汰捩瑡潩獮漯杲欮敤欮湯潳敬搮獥瑫灯਍"

Google translate says, "Last King ⼺ ⼯ Zongyang Qiang Tang Shan Yak ⸯ inertia
destination time Ben Mu Lan ⽥ eliminating Transition Shiyi Hunting is the thing
Han Yan Li Jiaotao lamp ਍"

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

[frameworks-kactivities] [Bug 370579] New: Crash messages from kactivitymanage (connected with qt 5.6.1)

2016-10-12 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370579

Bug ID: 370579
   Summary: Crash messages from kactivitymanage (connected with qt
5.6.1)
   Product: frameworks-kactivities
   Version: 5.8.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: jonfr1...@jonfr.com
CC: plasma-b...@kde.org

For some reason kactivitymanager crashes silently and leaves a message in
dmesg. I don't have more details since this crash doesn't seem to affect
performance that much at the moment. This might even be connected to a
nvidia-driver (I'm using version 367.44).

Reproducible: Always

Steps to Reproduce:
1. Keep KDE Plasma 5.8.0 running for some time.
2. 
3. Crash message appears in dmesg.

Actual Results:  
kactivitymanager crashes at random and is restarted.

Expected Results:  
kactivitymanager should not crash at all.

The error message from dmesg.
-
[121954.512853] traps: ck-remove-direc[26024] trap int3 ip:7f06427135d7
sp:7ffdb38c5220 error:0
[121954.555703] kactivitymanage[9354]: segfault at 7f4cf41d1c50 ip
7f4cf41e9071 sp 7ffc3a9ade18 error 4 in
libQt5Sql.so.5.6.1[7f4cf41d4000+42000]
[121954.957162] nvidia-modeset: Freed GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[121955.391324] nvidia-modeset: Allocated GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[121967.496527] traps: ck-remove-direc[26067] trap int3 ip:7f38ee1a35d7
sp:7ffe67e64af0 error:0
[122621.356608] traps: ck-remove-direc[26738] trap int3 ip:7eff8ebab5d7
sp:7ffc0a670e20 error:0
[122621.364902] kactivitymanage[26227]: segfault at 7ffab1e49c50 ip
7ffab1e61071 sp 7fff3b686cb8 error 4 in
libQt5Sql.so.5.6.1[7ffab1e4c000+42000]
[122621.776431] nvidia-modeset: Freed GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[122622.210805] nvidia-modeset: Allocated GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[123089.709593] traps: ck-remove-direc[26786] trap int3 ip:7fed81abb5d7
sp:7ffe673f9b20 error:0
[123104.581870] traps: ck-remove-direc[26826] trap int3 ip:7f8e0e6a35d7
sp:7fff65e38a20 error:0
[123112.371407] traps: ck-remove-direc[26840] trap int3 ip:7f412ebc35d7
sp:7ffc5a32b540 error:0
[123141.342976] traps: ck-remove-direc[27191] trap int3 ip:7f7d54f835d7
sp:7fff88a33900 error:0
[123141.347964] kactivitymanage[27005]: segfault at 7f1d9e4d9c50 ip
7f1d9e4f1071 sp 7fffd10bcf08 error 4 in
libQt5Sql.so.5.6.1[7f1d9e4dc000+42000]
[123141.765806] nvidia-modeset: Freed GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[123142.200405] nvidia-modeset: Allocated GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[123166.057593] traps: ck-remove-direc[27224] trap int3 ip:7f0ad3a6b5d7
sp:7ffc251a8e50 error:0
[123308.659877] traps: ck-remove-direc[27262] trap int3 ip:7f15b47bb5d7
sp:7ffd8bae01f0 error:0
[123315.099812] traps: ck-remove-direc[27276] trap int3 ip:7f3329ee35d7
sp:7ffc2ad8ae70 error:0
[125330.588056] traps: ck-remove-direc[28224] trap int3 ip:7fcc7efe35d7
sp:7ffe3261acd0 error:0
[125330.593040] kactivitymanage[27450]: segfault at 7ff5b62f1c50 ip
7ff5b6309071 sp 7ffc3dc49d68 error 4 in
libQt5Sql.so.5.6.1[7ff5b62f4000+42000]
[125331.023700] nvidia-modeset: Freed GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[125331.458176] nvidia-modeset: Allocated GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[125343.901146] traps: ck-remove-direc[28256] trap int3 ip:7f8aea96b5d7
sp:7ffd79f39990 error:0
[125369.388120] traps: ck-remove-direc[28283] trap int3 ip:7f781a9735d7
sp:7ffd15e8f940 error:0
[125376.730157] traps: ck-remove-direc[28297] trap int3 ip:7f0589deb5d7
sp:7ffebf8455d0 error:0

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

[Spectacle] [Bug 367907] spectacle segfault

2016-10-12 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=367907

--- Comment #3 from Jón Frímann  ---
(In reply to Peter Wu from comment #1)
> Could you provide more details? What settings were you using? Have you done
> other things like opening a file dialog prior to exiting?
> 
> (I managed to crash Kate and Spectacle after opening a file dialog once, but
> that does not seem to be a bug in Spectacle.)
> 
> Can you also include what versions of Spectacle, Qt, Plasma and theme (like
> Breeze) you have been using?

The crash happened after I saved a screenshot using the "rectangular"  option
and when I pressed save and exit. I'm no longer running kde plasma 5.7.4 and I
have upgraded to 5.8.0 where so far this has not yet happened. I'm currently
running Qt framework 5.6.1. I'm using the default theme (Breeze).

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

[dolphin] [Bug 370430] Dolphin samba read-write issue on top folder share

2016-10-11 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370430

--- Comment #1 from Jón Frímann  ---
I can confirm this bug also in KDE 5.8.0. I can no longer copy or create new
files on samba shares if I'm not in a sub-folder.

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

[dolphin] [Bug 370430] New: Dolphin samba read-write issue on top folder share

2016-10-10 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370430

Bug ID: 370430
   Summary: Dolphin samba read-write issue on top folder share
   Product: dolphin
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: folders
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: jonfr1...@jonfr.com

There is a odd bug regarding with the samba protocol. When I have this
directory structure I can't create or copy files into it.

smb://{IP address}/{share}/ (folder is read only)
Any sub-folder is read-write as normally. The bug also has other odd thing to
it. If I create a new folder on Windows XP (remote computer) and share it that
top folder is read-write. This bug is not present in KDE plasma version 5.7.4,
but it is present in version 5.7.5. I'm currently running Dolphin version
16.04.3. This also happens when I'm communicating with a computer that has
Samba version 4.4.3 installed (FreeBSD). I know this is not a remote computer
problem or a samba problem as I tested that possibility.

I'm going to upgrade to kde version 5.8.0 soon and I hope this bug is resolved
in that version.

Reproducible: Always

Steps to Reproduce:
1. Log on to a Windows share (I only have Windows XP/FreeBSD Samba 4.4.3 share)
2. Log-in to the remote computer. Options for creating folder or copy files to
samba shares is disabled at top level folder, but works in sub-folder.
3.

Actual Results:  
Samba share appears to be read only while it is in fact read-write and all
settings are correct. Sub-folders work properly.

Expected Results:  
All samba shares should be read-write and accessible. 

This did not happen with KDE plasma version 5.7.4 or older versions. Only
appears in KDE Plasma after version 5.7.5.

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

[frameworks-plasma] [Bug 370361] New: Crash when closing windows (Firefox)

2016-10-09 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370361

Bug ID: 370361
   Summary: Crash when closing windows (Firefox)
   Product: frameworks-plasma
   Version: 5.7.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: jonfr1...@jonfr.com

I got a crash on the activity banner (where the clock is and all that) when
closing down Firefox windows. Automatic crash report was generated but the
system didn't want to send it. So I'm doing it manually. Debug from the crash
assistant attached with this bug report. 

Reproducible: Didn't try

Steps to Reproduce:
1. Close down Firefox windows. 
2. ???
3. ???

Actual Results:  
The banner with the clock and open windows suddenly crashes.

Expected Results:  
It should not have crashed. 

Application: plasmashell (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4 x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:


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

Thread 13 (Thread 0x7f63a4f52700 (LWP 11769)):
#0  0x7f63b2ee0c8d in poll () from /lib64/libc.so.6
#1  0x7f63b6f278b2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f63b6f295d7 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f63a70daef9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f63b35a317b in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f63b26f242c in start_thread () from /lib64/libpthread.so.0
#6  0x7f63b2ee9b9d in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f639e9aa700 (LWP 11771)):
#0  0x7f63aef7e591 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f63aef3ba51 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f63aef3c227 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f63aef3c3bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f63b378afdc in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f63b373f192 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f63b359eaa4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f63b86881dd in ?? () from /usr/lib64/libQt5DBus.so.5
#8  0x7f63b35a317b in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f63b26f242c in start_thread () from /lib64/libpthread.so.0
#10 0x7f63b2ee9b9d in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f639cf52700 (LWP 11780)):
#0  0x7f63aef39470 in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7f63aef3bbff in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f63aef3c250 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f63aef3c3bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f63b378afdc in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f63b373f192 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f63b359eaa4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f63b5dd3dd5 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7f63b35a317b in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f63b26f242c in start_thread () from /lib64/libpthread.so.0
#10 0x7f63b2ee9b9d in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f63975c2700 (LWP 11813)):
#0  0x7f63aef393ed in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7f63aef3b7bb in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f63aef3c1d8 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f63aef3c3bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f63b378afdc in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f63b373f192 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f63b359eaa4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f63b5dd3dd5 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7f63b35a317b in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f63b26f242c in start_thread () from /lib64/libpthread.so.0
#10 0x7f63b2ee9b9d in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f6395952700 (LWP 11849)):
#0  0x7f63b26f7f4f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f63b7fcbf64 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f63b7fcbfa9 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f63b26f242c in start_thread () from /lib64/libpthread.so.0
#4  0x7f63b2ee9b9d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f6303ada700 (LWP 11865)):
#0  0x7f63b2ee0c8d in poll () from /lib64/libc.so.6
#1  0x7f63aef3c2ac in ?? () from /usr/lib64/libglib-2.0.so.0
#2

[frameworks-plasma] [Bug 370018] New: Scrolling window group results in crash of task manager

2016-10-04 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370018

Bug ID: 370018
   Summary: Scrolling window group results in crash of task
manager
   Product: frameworks-plasma
   Version: 5.7.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: jonfr1...@jonfr.com

The grouping of active windows in KDE task-manager has a serious bug in it. The
bug works in the following way.

When you have a group of Firefox windows open and they are arranged by activity
(or alphabetically) in the group. The trigger for the crash is when Facebook is
open and a new message appears. This makes the window order being moved as the
Facebook browser window blinks (notification of a new message) . This also
results in the window being moved up and down as the header text changes. When
attempting to click the active windows (in this case, Facebook) is difficult as
it moves, after few attempts the task-manager crashes. Log-out is needed in
order to restore the function of the task-manager.

I have not found any settings to change this behaviour in the task manager and
I have been looking for it.

Reproducible: Sometimes

Steps to Reproduce:
1. Create open windows (Firefox or other browser) so that a group of open
windows is created. 
2. Open Facebook and get a new message. This creates the active Facebook window
to blink and move up and down in the window group. 
3. After several attempts to click the windows (difficult as it moves around
when attempting to click) the task-manager crashes.

Actual Results:  
The task manager crashes and logout is needed to get it working again. 

Expected Results:  
The task manager should not move the window up and down and should not crash.

This bugs happen in KDE version 5.7.4 running on Gentoo Linux. The error
message I get from dmesg is this one. No other error message appears.

"949747.031966] kactivitymanage[3601]: segfault at 7f400c01cc50 ip
7f40001a4071 sp 7fff66c2e8d8 error 4 in
libQt5Sql.so.5.6.1[7f400018f000+42000]
[949747.122753] traps: ck-remove-direc[21748] trap int3 ip:7feff0ede537
sp:7ffcbaa39ce0 error:0
[949758.146407] traps: ck-remove-direc[21835] trap int3 ip:7f9770946537
sp:7ffd0de237c0 error:0

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

[plasmashell] [Bug 369218] Icon location on Desktop is not kept during reboot / shutdown

2016-10-04 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=369218

--- Comment #4 from Jón Frímann  ---
This bugs seems to have been resolved in KDE version 5.7.4 since it did not
happen after a crash that got triggered by a different bug that I found.
Earlier versions a crash did resolve in the icon being moved around from the
locations I had dropped them. The fix seems to be the deletion of the files I
did do few weeks ago.

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

[plasmashell] [Bug 369218] Icon location on Desktop is not kept during reboot / shutdown

2016-09-24 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=369218

--- Comment #2 from Jón Frímann  ---
There is no change in screen resolution. I was checking a other problem that
was making kactivitymanager crash (Bug 348194). One of the solution (comment
27) suggested there was that I deleted the following directories.

~/.local/share/kactivitymanagerd/resources/database and
~/.local/share/kscreen/*

After deleting those databases and folders the icons did go into mess, but
after moving them around as I wanted they have stayed on the correct location
since.

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

[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout

2016-09-23 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=348194

--- Comment #32 from Jón Frímann  ---
(In reply to H.d.V. from comment #31)
> (In reply to Jón Frímann from comment #30)
> > I'm getting this bug. Running the following in Gentoo Linux.
> > 
> > "x11-drivers/nvidia-drivers-367.44"
> > "uname -a
> > Linux jupiter 4.7.4 #1 SMP PREEMPT Fri Sep 23 04:31:06 CEST 2016 x86_64 AMD
> > A6-7400K Radeon R5, 6 Compute Cores 2C+4G AuthenticAMD GNU/Linux"
> > "x11-base/xorg-server-1.18.4"
> > 
> > This issue only appears after using version nvidia-driver-367.44 (or it
> > happens when switched to the nvidia-driver-367 version), using version
> > 364.18 and this crash does not happen. I'm going to downgrade to latest
> > long-term kernel so I can continue to use nvidia-driver 364 driver so this
> > issue doesn't happen. Using xorg-server-1.18.4 prevents hangs. I don't know
> > why that is.
> > [...]
> 
> Sorry no, I can not confirm.
> I use the same versions on Gentoo-Linux
> # emerge -pvq xorg-server nvidia-drivers
> [ebuild   R   ] x11-base/xorg-server-1.18.4  USE="ipv6 suid systemd udev
> xorg xvfb -dmx -doc -glamor -kdrive -libressl -minimal (-selinux)
> -static-libs -tslib -unwind -wayland -xephyr -xnest" 
> [ebuild   R   ] x11-drivers/nvidia-drivers-367.44  USE="X acpi driver gtk3
> kms multilib tools wayland -compat -pax_kernel -static-libs -uvm"
> # uname -r
> 4.7.4-gentoo
> and it works works very well.
> 
> Try the tip/workaround from  Comment 27
> or test it with a fresh clean testuser.

I'm currently testing the suggested fix in comment 27. It takes around 24 to 48
hours to see if it works without a problem. This might be a local database
corruption problem related to this issue. I just don't know yet. While we might
be running the same version of software, there might be difference at deeper
level in the system that is difficult to know about. Anything from version of
video card (I'm using 01:00.0 VGA compatible controller: NVIDIA Corporation
GK208 [GeForce GT 720] (rev a1)) down to some software library that I'm using
and has not been updated yet.

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

[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout

2016-09-23 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=348194

--- Comment #30 from Jón Frímann  ---
I'm getting this bug. Running the following in Gentoo Linux.

"x11-drivers/nvidia-drivers-367.44"
"uname -a
Linux jupiter 4.7.4 #1 SMP PREEMPT Fri Sep 23 04:31:06 CEST 2016 x86_64 AMD
A6-7400K Radeon R5, 6 Compute Cores 2C+4G AuthenticAMD GNU/Linux"
"x11-base/xorg-server-1.18.4"

This issue only appears after using version nvidia-driver-367.44 (or it happens
when switched to the nvidia-driver-367 version), using version 364.18 and this
crash does not happen. I'm going to downgrade to latest long-term kernel so I
can continue to use nvidia-driver 364 driver so this issue doesn't happen.
Using xorg-server-1.18.4 prevents hangs. I don't know why that is.

The last error code I get was this.

"[ 2528.367412] traps: ck-remove-direc[5366] trap int3 ip:7fe4a3173537
sp:7ffe21337230 error:0
[ 2528.372413] kactivitymanage[3669]: segfault at 7f63d8569c50 ip
7f63d5031071 sp 7ffda4d749d8 error 4 in
libQt5Sql.so.5.6.1[7f63d501c000+42000]
[ 2528.789604] nvidia-modeset: Freed GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[ 2529.224775] nvidia-modeset: Allocated GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[ 2563.764099] traps: ck-remove-direc[5411] trap int3 ip:7f74433cb537
sp:7ffc01f0ac60 error:0
[ 2597.270142] traps: ck-remove-direc[5684] trap int3 ip:7f53907fb537
sp:7ffd2604e2e0 error:0
[ 2597.685181] nvidia-modeset: Freed GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[ 2598.119525] nvidia-modeset: Allocated GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[ 2609.796294] traps: ck-remove-direc[5728] trap int3 ip:7f0402273537
sp:7ffc4bedc5f0 error:0"

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

[frameworks-plasma] [Bug 369218] New: Icon location on Desktop is not kept during reboot / shutdown

2016-09-22 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=369218

Bug ID: 369218
   Summary: Icon location on Desktop is not kept during reboot /
shutdown
   Product: frameworks-plasma
   Version: 5.7.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: libplasma
  Assignee: notm...@gmail.com
  Reporter: jonfr1...@jonfr.com

For some reason kde 5.7.4 does not save or honour the icon location on desktop
after a reboot or a shutdown. Icons are moving around in random order along the
desktop space. Locking them down does not work, this bug is also present in
earlier versions of KDE Plasma 5. This bug is annoying and was not present in
KDE Plasma 4 (at least the latest version that I was using). I don't like to
use the folder view in KDE Plasma 5, since I find it difficult to use.

Reproducible: Sometimes

Steps to Reproduce:
1. Arrange icons on Desktop in special order. 
2. Shut down computer for a while. 
3. Power it up, there is a good chance icons are not where you placed them.
This should not happen.

Actual Results:  
Icons move around the desktop in random order after a shutdown or reboot. More
common if the reboot or shutdown doesn't go as planned or the computer has been
off-line for a few hours.

Expected Results:  
Icons to be in the place where I put them on the desktop.

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

[frameworks-plasma] [Bug 368754] KDE Plasma version 5.7.4 kactivitymanager

2016-09-14 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368754

--- Comment #1 from Jón Frímann  ---
I wanted to add to this information. I was using an old xorg-server (version
1.7.4). This seems to have triggered the issue I found. I hope that upgrading
to xorg-server version 1.8.3 solves this problem. The problem has to due with
how graphic (of KDE) is not properly handled by the old xorg-server, along with
changes in the nvidia driver that are not properly supported by older versions
of xorg-server.

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

[frameworks-plasma] [Bug 368754] New: KDE Plasma version 5.7.4 kactivitymanager

2016-09-13 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368754

Bug ID: 368754
   Summary: KDE Plasma version 5.7.4 kactivitymanager
   Product: frameworks-plasma
   Version: 5.7.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: jonfr1...@jonfr.com

When on Facebook and new message is received this can trigger a crash in
kactivitymanager due to the banner of Firefox going up and down as it blinks.
This completely freezes  the kde framework and only way to restart it is to go
shell and restart xdm. This happens every time a new message is received on
Facebook. This might be related to nvidia, that also crashes at the same time
but I do not think the drivers are at fault here. 

Reproducible: Always

Steps to Reproduce:
1. Log-in to Facebook in Firefox 45.3.0 (ESR).
2. Get new message while logged into Facebook, several windows needs to be open
so the list appears along with other normal desktop application. I just have
Thunderbird and shell open. Along with clementine as an icon in the task bar
next to the clock.
3. The banner is going to blink with the new message making it hard to click on
as it moves up and down and then crash happens.

Actual Results:  
KDE plasma 5 crashes hard and cannot be worked on.

Expected Results:  
I should be able to click on the open window list with out crash happening.

>From dmesg, I don't have other debug information due to the nature of the
crash.
--
[  765.864078] kactivitymanage[3551]: segfault at 7fa2a4ff1c50 ip
7fa2a4111071 sp 7fffe4763958 error 4 in
libQt5Sql.so.5.6.1[7fa2a40fc000+42000]
[  765.948650] traps: ck-remove-direc[4119] trap int3 ip:7f2d5be2b537
sp:7ffd150e2290 error:0
[  766.162120] nvidia-modeset: Freed GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[  766.613672] nvidia-modeset: Allocated GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[  778.642296] traps: ck-remove-direc[4209] trap int3 ip:7fc4e28eb537
sp:7ffca3201a00 error:0
[  779.661008] QXcbEventReader[4304]: segfault at 7fd9a90d3ef9 ip
7fd9a90d3ef9 sp 7fd9a650aea0 error 14 in
locale-archive[7fd9a918c000+26c000]
[16865.944833] traps: ck-remove-direc[9220] trap int3 ip:7f1991deb537
sp:7fff6c34d820 error:0
[16865.952519] kactivitymanage[4317]: segfault at 7f1f0c021c50 ip
7f1f00351071 sp 7ffee1a4f8a8 error 4 in
libQt5Sql.so.5.6.1[7f1f0033c000+42000]
[16866.371451] nvidia-modeset: Freed GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[16866.806249] nvidia-modeset: Allocated GPU:0
(GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI::01:00.0
[16881.976298] traps: ck-remove-direc[9260] trap int3 ip:7f5c14f1b537
sp:7ffd89f6f230 error:0
[21853.867588] kactivitymanage[9384]: segfault at 7f66e8f39c50 ip
7f66e8059071 sp 7ffdbf01c398 error 4 in
libQt5Sql.so.5.6.1[7f66e8044000+42000]
[21853.892186] traps: ck-remove-direc[11549] trap int3 ip:7f5b22f43537
sp:7fff94837700 error:0
[21861.462516] traps: ck-remove-direc[11636] trap int3 ip:7fb3ed613537
sp:7ffed9d0c1d0 error:0
[31277.972176] kactivitymanage[11755]: segfault at 7f9863361c50 ip
7f9860059071 sp 7ffeb7ea1b38 error 4 in
libQt5Sql.so.5.6.1[7f9860044000+42000]
[31278.034639] traps: ck-remove-direc[13579] trap int3 ip:7fd172ebb537
sp:7fffe0fc2110 error:0
[31283.524440] traps: ck-remove-direc[13666] trap int3 ip:7f2e37703537
sp:7ffc84741a50 error:0

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

[ksmserver] [Bug 368574] Nvidia driver update triggers ksmserver crash

2016-09-10 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368574

Jón Frímann  changed:

   What|Removed |Added

Summary|Nvidia driver triggers  |Nvidia driver update
   |ksmserver crash |triggers ksmserver crash

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

[ksmserver] [Bug 368574] New: Nvidia driver triggers ksmserver crash

2016-09-10 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368574

Bug ID: 368574
   Summary: Nvidia driver triggers ksmserver crash
   Product: ksmserver
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: ui
  Assignee: l.lu...@kde.org
  Reporter: jonfr1...@jonfr.com

During a update on Nvidia driver ksmserver crashed on logout. 

Reproducible: Didn't try

Steps to Reproduce:
1. Update nvidia-driver to new version.
2. Logout or reboot.
3.

Actual Results:  
ksmserver crashes due to a missing driver component or mismatching version. 

Expected Results:  
Logged out without crashing.

GNU gdb (Gentoo 7.10.1 vanilla) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/ksmserver...(no debugging symbols found)...done.
Attaching to program: /usr/bin/ksmserver, process 3683

warning: .dynamic section for "/usr/lib64/opengl/nvidia/lib/libEGL.so.1" is not
at the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/usr/lib64/opengl/nvidia/lib/libGLX.so.0" is not
at the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/usr/lib64/opengl/nvidia/lib/libEGL_nvidia.so.0"
is not at the expected address (wrong library or version mismatch?)

warning: Could not load shared library symbols for
/usr/lib64/libnvidia-glsi.so.364.19.
Do you need "set solib-search-path" or "set sysroot"?
Reading symbols from /usr/lib64/libkdeinit5_ksmserver.so...(no debugging
symbols found)...done.
Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
Reading symbols from /usr/lib64/libKScreenLocker.so.5...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libkworkspace5.so.5...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libSM.so.6...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libICE.so.6...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libX11.so.6...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libXrender.so.1...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libKF5KDELibs4Support.so.5...(no debugging
symbols found)...done.
Reading symbols from /usr/lib64/libKF5Declarative.so.5...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libQt5Quick.so.5...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libQt5Qml.so.5...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libKF5Package.so.5...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libKF5Notifications.so.5...(no debugging
symbols found)...done.
Reading symbols from /usr/lib64/libphonon4qt5.so.4...(no debugging symbols
found)...done.
Reading symbols from /usr/lib64/libKF5XmlGui.so.5...(no debugging symbols
found)...done.  
Reading symbols from /usr/lib64/libKF5GlobalAccel.so.5...(no debugging symbols
found)...done.  
Reading symbols from /usr/lib64/libKF5DBusAddons.so.5...(no debugging symbols
found)...done.  
Reading symbols from /usr/lib64/libKF5ConfigCore.so.5...(no debugging symbols
found)...done.  
Reading symbols from /usr/lib64/libQt5DBus.so.5...(no debugging symbols
found)...done.  
Reading symbols from /usr/lib64/libKF5CoreAddons.so.5...(no debugging symbols
found)...done.  
Reading symbols from /usr/lib64/libKF5WidgetsAddons.so.5...(no debugging
symbols found)...done.  
Reading symbols from /usr/lib64/libKF5I18n.so.5...(no debugging symbols
found)...done.  
Reading symbols from /usr/lib64/libKF5WindowSystem.so.5...(no debugging symbols
found)...done.  
Reading symbols from /usr/lib64/libQt5X11Extras.so.5...(no debugg

[gwenview] [Bug 368123] New: gwenview-16.04.3 crashes when closing, happens at random

2016-09-01 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368123

Bug ID: 368123
   Summary: gwenview-16.04.3 crashes when closing, happens at
random
   Product: gwenview
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: jonfr1...@jonfr.com
CC: myr...@kde.org

When closing gwenview-16.04.3 it crashed without reason. This does seem to be
random crash and is hard to make it happen again.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. Open up a image.
2. Change to an other image.
3. Close gwenview.

Actual Results:  
On closing the gwenview crashes, this crash is difficult to make happen and
might only happen once in a while without clear reason.

Expected Results:  
The program should close normally.

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

Thread 2 (Thread 0x7f5c3282e700 (LWP 19797)):
#0  0x7f5c48600dcd in read () from /lib64/libc.so.6
#1  0x7f5c42171090 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f5c4212fcd4 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f5c421301b0 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f5c4213031c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f5c48eaefdc in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f5c48e63192 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f5c48cc2aa4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f5c4d5541dd in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x7f5c48cc717b in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x7f5c437e642c in start_thread () from /lib64/libpthread.so.0
#11 0x7f5c4860db9d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5c4d1c3800 (LWP 19795)):
[KCrash Handler]
#6  0x7f5c491f3842 in ?? () from /usr/lib64/libQt5Gui.so.5
#7  0x7f5c491f3911 in QImageReader::~QImageReader() () from
/usr/lib64/libQt5Gui.so.5
#8  0x7f5c49209a4c in QMovie::~QMovie() () from /usr/lib64/libQt5Gui.so.5
#9  0x7f5c4cca85d1 in ?? () from /usr/lib64/libgwenviewlib.so.5
#10 0x7f5c4cca8629 in ?? () from /usr/lib64/libgwenviewlib.so.5
#11 0x7f5c4ccab589 in Gwenview::Document::~Document() () from
/usr/lib64/libgwenviewlib.so.5
#12 0x7f5c4ccabba1 in Gwenview::Document::~Document() () from
/usr/lib64/libgwenviewlib.so.5
#13 0x7f5c4ccb1850 in ?? () from /usr/lib64/libgwenviewlib.so.5
#14 0x7f5c4ccb117d in Gwenview::DocumentFactory::~DocumentFactory() () from
/usr/lib64/libgwenviewlib.so.5
#15 0x7f5c4855c4b8 in ?? () from /lib64/libc.so.6
#16 0x7f5c4855c505 in exit () from /lib64/libc.so.6
#17 0x7f5c48547617 in __libc_start_main () from /lib64/libc.so.6
#18 0x0042b6b9 in _start ()

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

[Spectacle] [Bug 367907] New: spectacle segfault

2016-08-27 Thread Jón Frímann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=367907

Bug ID: 367907
   Summary: spectacle segfault
   Product: Spectacle
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: jonfr1...@jonfr.com

Spectacle segfault in use when I pressed save on image that I took. It only
happened once. This might be a fault of libQt5, but I'm not sure since I'm not
good with reading this type of error messages so I don't know what is at fault
here.

Reproducible: Sometimes

Steps to Reproduce:
1. Use Spectacle, press save option.
2. Image is saved right away.
3. The exit of the program seems to crash it .

Actual Results:  
Spectacle crashes when pressing save button.

Expected Results:  
Spectacle should exit clean when the image was saved.

[89307.582039] spectacle[24906]: segfault at 7f551e906280 ip 7f552d80c6f4
sp 7fff92854fd8 error 4 in libQt5Core.so.5.6.1[7f552d6f2000+46f000]

The crash message.

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