[Touch-packages] [Bug 1798868] Re: Compiz Crashed with SIGSEGV [Radeon]

2018-12-29 Thread Liam McDonagh-Greaves
** Description changed: + SEE WORKAROUND AT END OF POST + Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the is

[Touch-packages] [Bug 1798867] [NEW] Compiz Crashed with SIGSEGV [Radeon]

2018-10-19 Thread Liam McDonagh-Greaves
Public bug reported: Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ub

[Touch-packages] [Bug 1798868] [NEW] Compiz Crashed with SIGSEGV [Radeon]

2018-10-19 Thread Liam McDonagh-Greaves
Public bug reported: Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ub

[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

2018-08-03 Thread Liam McDonagh-Greaves
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 Apologies for double-posting. Some additional info that may be helpful. Paste from /var/crash/_usr_bin_compiz.1000.crash: //BEGIN CODE PASTE// ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentD

[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

2018-08-03 Thread Liam McDonagh-Greaves
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 I can confirm I have what I believe to be this bug in 16.04. All packages updated to current. Have also downloaded latest 16.04 LTS release .iso and run it off a USB drive. Same symptoms. Originally, the is