[amarok] [Bug 362523] New: Amarok was terminated

2016-04-30 Thread Linus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362523

Bug ID: 362523
   Summary: Amarok was terminated
   Product: amarok
   Version: 2.8.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: ioher6yfd98ouyu03...@gmail.com

Application: amarok (2.8.0)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-21-generic i686
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
When starting the application (Amarok), I moved the mouse pointer to the top
menu border (to grab it and move it). The application was terminated upon
entering the border area without delay.

The crash can be reproduced every time.

-- Backtrace:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xae56e800 (LWP 15021))]

Thread 35 (Thread 0xa81fcb40 (LWP 15037)):
#0  0xb7787c31 in __kernel_vsyscall ()
#1  0xb54d9c4f in read () at ../sysdeps/unix/syscall-template.S:84
#2  0xb1070548 in pa_read () from
/usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#3  0xb3ddb997 in pa_mainloop_prepare () from
/usr/lib/i386-linux-gnu/libpulse.so.0
#4  0xb3ddc4ad in pa_mainloop_iterate () from
/usr/lib/i386-linux-gnu/libpulse.so.0
#5  0xb3ddc57c in pa_mainloop_run () from /usr/lib/i386-linux-gnu/libpulse.so.0
#6  0xb3deafc1 in ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0
#7  0xb109ee5e in ?? () from
/usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#8  0xb4c332b5 in start_thread (arg=0xa81fcb40) at pthread_create.c:333
#9  0xb54eb16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 34 (Thread 0x9d8e3b40 (LWP 15038)):
#0  0xb7787c31 in __kernel_vsyscall ()
#1  0xb5430e8c in __GI___sigwaitinfo (set=, info=0x9d8e31cc) at
../sysdeps/unix/sysv/linux/sigwaitinfo.c:56
#2  0x9e4355d7 in timer_notify_thread_func () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#3  0xb4c332b5 in start_thread (arg=0x9d8e3b40) at pthread_create.c:333
#4  0xb54eb16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 33 (Thread 0x68030b40 (LWP 15039)):
#0  0xad9c6570 in ?? () from /lib/i386-linux-gnu/libaio.so.1
#1  0xad9c65e6 in io_getevents () from /lib/i386-linux-gnu/libaio.so.1
#2  0x9ea07893 in LinuxAIOHandler::collect() () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#3  0x9ea10085 in LinuxAIOHandler::poll(fil_node_t**, void**, IORequest*) ()
from /usr/lib/kde4/amarok_collection-mysqlecollection.so
#4  0x9ea12b5f in os_aio_handler(unsigned long, fil_node_t**, void**,
IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so
#5  0x9ebfe4f1 in fil_aio_wait(unsigned long) () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#6  0x9ed40a61 in io_handler_thread () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#7  0xb4c332b5 in start_thread (arg=0x68030b40) at pthread_create.c:333
#8  0xb54eb16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 32 (Thread 0x6782fb40 (LWP 15040)):
#0  0xad9c6570 in ?? () from /lib/i386-linux-gnu/libaio.so.1
#1  0xad9c65e6 in io_getevents () from /lib/i386-linux-gnu/libaio.so.1
#2  0x9ea07893 in LinuxAIOHandler::collect() () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#3  0x9ea10085 in LinuxAIOHandler::poll(fil_node_t**, void**, IORequest*) ()
from /usr/lib/kde4/amarok_collection-mysqlecollection.so
#4  0x9ea12b5f in os_aio_handler(unsigned long, fil_node_t**, void**,
IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so
#5  0x9ebfe4f1 in fil_aio_wait(unsigned long) () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#6  0x9ed40a61 in io_handler_thread () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#7  0xb4c332b5 in start_thread (arg=0x6782fb40) at pthread_create.c:333
#8  0xb54eb16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 31 (Thread 0x6702eb40 (LWP 15041)):
#0  0xad9c6570 in ?? () from /lib/i386-linux-gnu/libaio.so.1
#1  0xad9c65e6 in io_getevents () from /lib/i386-linux-gnu/libaio.so.1
#2  0x9ea07893 in LinuxAIOHandler::collect() () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#3  0x9ea10085 in LinuxAIOHandler::poll(fil_node_t**, void**, IORequest*) ()
from /usr/lib/kde4/amarok_collection-mysqlecollection.so
#4  0x9ea12b5f in os_aio_handler(unsigned long, fil_node_t**, void**,
IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so
#5  0x9ebfe4f1 in fil_aio_wait(unsigned long) () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#6  0x9ed40a61 in io_handler_thread () from
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#7  0xb4c332b5 in start_thread (arg=0x6702eb40) at pthread_create.c:333
#8  0xb54eb16e in clone () at 

[kwin] [Bug 359188] kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts and finishing loading

2016-02-19 Thread Linus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359188

Linus  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #9 from Linus  ---
I think yes, because I had a similar bug a long time ago with Plasma where Kwin
mostly crashing everytime, I adding/removing/activating/deactivating a monitor.

Currently I have two Monitors:
DVI (BenQ): Primary Monitor [1920x1080]
VGA (Samsung TFT): Secondary Monitor [1024x768]
HDMI (Samung SmartTV): Gaming Monitor (uses when play Steam-Games with
Controller) [1920x1080; Mirror of BenQ]

Screenshot of KDE's Monitor-Settings: http://i.epvpimg.com/pkvcd.png

Everytime I starting my SmartTV (if not at current boot), kwin crashes.

My Laptop which I using in School and which is running ArchLinux with latest
Updates, crashes often when I unplug a Monitor. But then kwin restarts and
shows me a Crash-Dialog.

It seems that kwin has mayor problems with multiple Monitors or screen
resolutions.

I think that it isn't a fault of my Nvidia GTX 750 Ti because my Laptop only
has a Intel i3 with HD Graphics 2000 which should work fine on Linux.

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


[kwin] [Bug 359188] kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts and finishing loading

2016-02-13 Thread Linus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359188

--- Comment #5 from Linus  ---
Created attachment 97174
  --> https://bugs.kde.org/attachment.cgi?id=97174=edit
Kwin-Crashlog

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


[kwin] [Bug 359188] kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts and finishing loading

2016-02-13 Thread Linus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359188

--- Comment #6 from Linus  ---
Created attachment 97175
  --> https://bugs.kde.org/attachment.cgi?id=97175=edit
Kwin-Crashlog (with 'grep -i buffer')

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


[kwin] [Bug 359188] kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts and finishing loading

2016-02-10 Thread Linus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359188

Linus  changed:

   What|Removed |Added

 Resolution|FIXED   |WAITINGFORINFO

--- Comment #3 from Linus  ---
I found out that if kwin_x11 crashes (shattered screen) I can use the Hotkey to
disable/enable the compositor twice instead of restarting kwin_x11.
Then this image is restored.

This means that it definitly is a bug of the compositor.
Maybe a fullscreen or OpenGL problem?

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


[kwin] [Bug 359188] kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts and finishing loading

2016-02-10 Thread Linus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359188

Linus  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Linus  ---
I tried it.
"$ xev -root -event randr" did not gave me any output while crashing.

Blocking the Compositor with SHIFT + ALT + F12 seems to work best.
As I tried it with the Window-Rule and start Minecraft the Compositor got
blocked but then my middle panel (Windowlist) freezed and kwin shuts down
(windowdecoration was gone).
After I restarted both (kwin_x11 and plasmashell) I noticed that the Hotkey ALT
+ F2 to enter commands did not work (sure only till the next reboot) but my
Hotkey to pop up my Application-Launcher (SUPER + Y).

To sum it up:
- Not a cause of the "Root-Window" ("$ xev -root -event randr" with no output)
- Disabling Compositor works but caused a big crash as I set it as windowrule.

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


[kwin] [Bug 359188] New: kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts and finishing loading

2016-02-09 Thread Linus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359188

Bug ID: 359188
   Summary: kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts
and finishing loading
   Product: kwin
   Version: 5.4.2
  Platform: Ubuntu Packages
   URL: https://youtu.be/jHEEnC79HZc
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: wendefelix1...@gmail.com

Happens if Minecraft 1.6.4 ('Attack of the B-Team') starts.

Reproducible: Sometimes

Steps to Reproduce:
1. Download and start the "Technic Launcher" from http://www.technicpack.net/
(Note: a premium minecraftaccount from minecraft.net is needed to play this)
2. Install the Modpack "Attack of the B-Team"
3. Play it

Actual Results:  
with a 80% chance, kwin_x11 crashes with result as a shattered screen, till it
gets restarted with "$ kwin_x11 --replace"

Expected Results:  
No crash of kwin_x11

I regonized that Minecraft with the current modpack starts in fullscreen and if
loaded wants to exit the fullscreen, I tried it with a Window-Rule that deny
fullscreen. It works but kwin_x11 is still crashing.

I using Kubuntu 15.10 (no alternate PPA/Repo for KDE)
I using a Nvidia GTX 750 Ti with the Nvidia binary driver 352.22

(The freeze in the video is a another bug related to my Nvidia-Card after
boot.)

I don't know weather that is related to this crash, but in case of a V-Sync
failure I added following entrys to the file ~/.profile:
export __GL_YIELD="USLEEP"
export __GL_THREADED_OPTIMIZATIONS=1
This forces all applications to use V-Sync.

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