Thanks for the suggestions. I guess I will remove the kde config files and start from scratch. The last time I got a borked configuration was also resolved by me wiping everything and starting from new. Hopefully that resolves things. On Saturday 19 Sep 2015 18:45:46 Carl Symons wrote:

On Saturday, September 19, 2015 08:23:18 PM Chan Ju Ping wrote:

...

Hi.

I decided to upgrade from 13.2 to Tumbleweed, but couldn't get the login screen to load when I did the steps with `zypper dup` in the Tumbleweed installation guide. Some failure with Plymouth or X to load properly.

Since that failed, I went ahead and downloaded the Tumbleweed ISO for KDE and installed it within my LUKS partition setup and by also importing the mount points from my previous installation. Amazingly enough, everything worked out of the box with the wipe and reinstallation of /, and I didn't have to reconfigure my core applications.

However, I have now been running into frequent crashes and freezes, where the computer stops responding. This seems to happen every time online video is being played, for both Flash and HTML5.

I have toggled the compositor via KDE's settings to use OpenGL 3.1 as the screen stutters on OpenGL 2.0. I suspect it is a compositor issue.

Any thoughts on how to track down and resolve this issue?

Does it only happen when you play online video? Or are there other actions that cause crashes?

With the information you've provided, the first thing I'd suggest is to switch from OpenGL to XRender. System Settings/Configure Desktop > Display and Monitor

...

Compositor > rendering backend

Tumbleweed repositories should replace 13.2 ones.

I have no experience with installing to LUKS partition setup.

If I were in your situation... I'd back up /home/YOURNAME Install Tumbleweed from scratch without reformatting /home

In that case, some of your configurations are probably going to be incorrect. But without some knowledge of your current set up, it's hard to tell what might need to be different. Might be good to rename KDE configuration files to filenameOLD and let the KDE set up create new ones. I just looked at my set up and I'm hesitant to say which things to hide like this. (~/.config has a bunch; ~/.kde4, ~/.local/share

If this doesn't make your machine feel right, then (if it was me) I would back up the entire home directory and then reinstall everything including a newly formatted home directory. Then you can copy necessary personal files from the backup into your home.

Carl

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

I have actually got it down to a science now. I have a second hard-drive just to hold my data files, and symlink everything to the Home folder after installation. It's just getting Kontact, my gpg keys, and ssh keys and all that jazz back up that takes up time. That's a neat trick with rpm. I exported the packages with Software Management though. It's a fresh enough installation that I should be able to get everything back up and running. Thanks for the additional feedback! On Saturday, September 19, 2015 08:40:41 PM Carl Symons wrote:

On Saturday, September 19, 2015 10:26:00 PM Chan Ju Ping wrote:

...

Thanks for the suggestions. I guess I will remove the kde config files and start from scratch.

The last time I got a borked configuration was also resolved by me wiping everything and starting from new.

Hopefully that resolves things.

After doing hundreds of these install or upgrades, I've found that starting fresh gives the best result. Otherwise it seems to be one little thing after another. This is particularly the case when there are little irritations that evade solution.

If you have an external drive that will hold your home directory, then rsync will catch everything. From that you can put back in /home/... what you really need.

The other thing that I do is work from a listing of apps installed. rpm -qa > pkglist150917.txt then open the txt file with LibreOffice and sort it.

I just did a fresh install a couple of days ago. There were some minor glitches (such as installing Scribus 1.5.0 from source with all dependencies). It's all good now, and seems snappier than ever.

Carl

...

On Saturday 19 Sep 2015 18:45:46 Carl Symons wrote:

...

On Saturday, September 19, 2015 08:23:18 PM Chan Ju Ping wrote:

...

Hi.

I decided to upgrade from 13.2 to Tumbleweed, but couldn't get the login screen to load when I did the steps with `zypper dup` in the Tumbleweed installation guide. Some failure with Plymouth or X to load properly.

Since that failed, I went ahead and downloaded the Tumbleweed ISO for KDE and installed it within my LUKS partition setup and by also importing the mount points from my previous installation. Amazingly enough, everything worked out of the box with the wipe and reinstallation of /, and I didn't have to reconfigure my core applications.

However, I have now been running into frequent crashes and freezes, where the computer stops responding. This seems to happen every time online video is being played, for both Flash and HTML5.

I have toggled the compositor via KDE's settings to use OpenGL 3.1 as the screen stutters on OpenGL 2.0. I suspect it is a compositor issue.

Any thoughts on how to track down and resolve this issue?

Does it only happen when you play online video? Or are there other actions that cause crashes?

With the information you've provided, the first thing I'd suggest is to switch from OpenGL to XRender. System Settings/Configure Desktop > Display and Monitor

...

Compositor > rendering backend

Tumbleweed repositories should replace 13.2 ones.

I have no experience with installing to LUKS partition setup.

If I were in your situation... I'd back up /home/YOURNAME Install Tumbleweed from scratch without reformatting /home

In that case, some of your configurations are probably going to be incorrect. But without some knowledge of your current set up, it's hard to tell what might need to be different. Might be good to rename KDE configuration files to filenameOLD and let the KDE set up create new ones. I just looked at my set up and I'm hesitant to say which things to hide like this. (~/.config has a bunch; ~/.kde4, ~/.local/share

If this doesn't make your machine feel right, then (if it was me) I would back up the entire home directory and then reinstall everything including a newly formatted home directory. Then you can copy necessary personal files from the backup into your home.

Carl

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Spoke too soon. The crashes due to random config settings from 13.2 were resolved, The ones related to video have not. The strange thing is, the freezes occur regardless of online video or standalone video. How would you suggest I trace the issue? On Sunday, September 20, 2015 08:30:41 AM Chan Ju Ping wrote:

It works now. I guess I really had to bite the bullet and think of Tumbleweed as an entirely new distro rather than something with a straightforward upgrade path.

On Saturday, September 19, 2015 10:47:30 PM Chan Ju Ping wrote:

...

I have actually got it down to a science now. I have a second hard-drive just to hold my data files, and symlink everything to the Home folder after installation.

It's just getting Kontact, my gpg keys, and ssh keys and all that jazz back up that takes up time.

That's a neat trick with rpm. I exported the packages with Software Management though. It's a fresh enough installation that I should be able to get everything back up and running.

Thanks for the additional feedback!

On Saturday, September 19, 2015 08:40:41 PM Carl Symons wrote:

...

On Saturday, September 19, 2015 10:26:00 PM Chan Ju Ping wrote:

...

Thanks for the suggestions. I guess I will remove the kde config files and start from scratch.

The last time I got a borked configuration was also resolved by me wiping everything and starting from new.

Hopefully that resolves things.

After doing hundreds of these install or upgrades, I've found that starting fresh gives the best result. Otherwise it seems to be one little thing after another. This is particularly the case when there are little irritations that evade solution.

If you have an external drive that will hold your home directory, then rsync will catch everything. From that you can put back in /home/... what you really need.

The other thing that I do is work from a listing of apps installed. rpm -qa > pkglist150917.txt then open the txt file with LibreOffice and sort it.

I just did a fresh install a couple of days ago. There were some minor glitches (such as installing Scribus 1.5.0 from source with all dependencies). It's all good now, and seems snappier than ever.

Carl

...

On Saturday 19 Sep 2015 18:45:46 Carl Symons wrote:

...

On Saturday, September 19, 2015 08:23:18 PM Chan Ju Ping wrote:

...

Hi.

I decided to upgrade from 13.2 to Tumbleweed, but couldn't get the login screen to load when I did the steps with `zypper dup` in the Tumbleweed installation guide. Some failure with Plymouth or X to load properly.

Since that failed, I went ahead and downloaded the Tumbleweed ISO for KDE and installed it within my LUKS partition setup and by also importing the mount points from my previous installation. Amazingly enough, everything worked out of the box with the wipe and reinstallation of /, and I didn't have to reconfigure my core applications.

However, I have now been running into frequent crashes and freezes, where the computer stops responding. This seems to happen every time online video is being played, for both Flash and HTML5.

I have toggled the compositor via KDE's settings to use OpenGL 3.1 as the screen stutters on OpenGL 2.0. I suspect it is a compositor issue.

Any thoughts on how to track down and resolve this issue?

Does it only happen when you play online video? Or are there other actions that cause crashes?

With the information you've provided, the first thing I'd suggest is to switch from OpenGL to XRender. System Settings/Configure Desktop > Display and Monitor

...

Compositor > rendering backend

Tumbleweed repositories should replace 13.2 ones.

I have no experience with installing to LUKS partition setup.

If I were in your situation... I'd back up /home/YOURNAME Install Tumbleweed from scratch without reformatting /home

In that case, some of your configurations are probably going to be incorrect. But without some knowledge of your current set up, it's hard to tell what might need to be different. Might be good to rename KDE configuration files to filenameOLD and let the KDE set up create new ones. I just looked at my set up and I'm hesitant to say which things to hide like this. (~/.config has a bunch; ~/.kde4, ~/.local/share

If this doesn't make your machine feel right, then (if it was me) I would back up the entire home directory and then reinstall everything including a newly formatted home directory. Then you can copy necessary personal files from the backup into your home.

Carl

Online, it would be Flash sites like Crunchyroll. Offline, it is with mpv using either smplayer or bomi as the GUI frontend, playing mp4, wmv, and the usual formats. I have toggled various settings in the KDE compositor since writing the last email, and the latest one with the Scale method set to Crisp, rendering with OpenGL 3.1 with EGL as the interface, and suspending compositor for full screen windows has been the most reliable set-up so far. Managed to make it through a whole episode in Crunchyroll without crashing. On Sunday, September 20, 2015 09:31:42 AM Carl Symons wrote:

On Sunday, September 20, 2015 11:16:34 AM Chan Ju Ping wrote:

...

Spoke too soon. The crashes due to random config settings from 13.2 were resolved, The ones related to video have not.

The strange thing is, the freezes occur regardless of online video or standalone video.

How would you suggest I trace the issue?

More information would be helpful. What application are you using for local video? What online videos/websites are causing problems?

Carl

...

On Sunday, September 20, 2015 08:30:41 AM Chan Ju Ping wrote:

...

It works now. I guess I really had to bite the bullet and think of Tumbleweed as an entirely new distro rather than something with a straightforward upgrade path.

On Saturday, September 19, 2015 10:47:30 PM Chan Ju Ping wrote:

...

I have actually got it down to a science now. I have a second hard-drive just to hold my data files, and symlink everything to the Home folder after installation.

It's just getting Kontact, my gpg keys, and ssh keys and all that jazz back up that takes up time.

That's a neat trick with rpm. I exported the packages with Software Management though. It's a fresh enough installation that I should be able to get everything back up and running.

Thanks for the additional feedback!

On Saturday, September 19, 2015 08:40:41 PM Carl Symons wrote:

...

On Saturday, September 19, 2015 10:26:00 PM Chan Ju Ping wrote:

...

Thanks for the suggestions. I guess I will remove the kde config files and start from scratch.

The last time I got a borked configuration was also resolved by me wiping everything and starting from new.

Hopefully that resolves things.

After doing hundreds of these install or upgrades, I've found that starting fresh gives the best result. Otherwise it seems to be one little thing after another. This is particularly the case when there are little irritations that evade solution.

If you have an external drive that will hold your home directory, then rsync will catch everything. From that you can put back in /home/... what you really need.

The other thing that I do is work from a listing of apps installed. rpm -qa > pkglist150917.txt then open the txt file with LibreOffice and sort it.

I just did a fresh install a couple of days ago. There were some minor glitches (such as installing Scribus 1.5.0 from source with all dependencies). It's all good now, and seems snappier than ever.

Carl

...

On Saturday 19 Sep 2015 18:45:46 Carl Symons wrote: > On Saturday, September 19, 2015 08:23:18 PM Chan Ju Ping wrote: > > Hi. > > > > I decided to upgrade from 13.2 to Tumbleweed, but couldn't get > > the > > login > > screen to load when I did the steps with `zypper dup` in the > > Tumbleweed > > installation guide. Some failure with Plymouth or X to load > > properly. > > > > Since that failed, I went ahead and downloaded the Tumbleweed > > ISO > > for > > KDE > > and installed it within my LUKS partition setup and by also > > importing > > the > > mount points from my previous installation. Amazingly enough, > > everything > > worked out of the box with the wipe and reinstallation of /, > > and > > I > > didn't > > have to reconfigure my core applications. > > > > However, I have now been running into frequent crashes and > > freezes, > > where > > the computer stops responding. This seems to happen every time > > online > > video > > is being played, for both Flash and HTML5. > > > > I have toggled the compositor via KDE's settings to use OpenGL > > 3.1 > > as > > the > > screen stutters on OpenGL 2.0. I suspect it is a compositor > > issue. > > > > Any thoughts on how to track down and resolve this issue? > > Does it only happen when you play online video? Or are there > other > actions > that cause crashes? > > With the information you've provided, the first thing I'd > suggest > is > to > switch from OpenGL to XRender. System Settings/Configure Desktop > > > Display > and Monitor > > > Compositor > rendering backend > > Tumbleweed repositories should replace 13.2 ones. > > I have no experience with installing to LUKS partition setup. > > If I were in your situation... > I'd back up /home/YOURNAME > Install Tumbleweed from scratch without reformatting /home > > In that case, some of your configurations are probably going to > be > incorrect. But without some knowledge of your current set up, > it's > hard > to > tell what might need to be different. Might be good to rename > KDE > configuration files to filenameOLD and let the KDE set up create > new > ones. > I just looked at my set up and I'm hesitant to say which things > to > hide > like this. (~/.config has a bunch; ~/.kde4, ~/.local/share > > If this doesn't make your machine feel right, then (if it was > me) > I > would > back up the entire home directory and then reinstall everything > including > a > newly formatted home directory. Then you can copy necessary > personal > files > from the backup into your home. > > Carl

Spoke too soon again. Restarting the computer left me with a black screen on the next boot up. I could run krunner and yast but could not see the desktop or the panel. My GPU is the SAPPHIRE Vapor-X 100364VXL Radeon R9 270X 2GB 256-Bit GDDR5 PCI Express 3.0 CrossFireX Support OC WITH BOOST Video Card It's a pretty high end card, and I just built this machine early this summer, so heat should not be an issue. It is now running at a steady 35℃ for the GPU. I have read a lot of announcements that indicate TW is best supported by the free drivers, so I don't think using fglrx would improve the situation, in fact I suspect it will make it worse. Oh well, this is what living on the edge feels like! It's what I signed up for when I thought stable releases were getting boring. :-) For now I have disabled the compositor on startup, and will now install some debug symbols for the next batch of tests. On Sunday, September 20, 2015 07:11:37 PM Simon Heimbach wrote:

What graphic card do you have? For me this issue sounds like a step back for your video-driver due to the newer kernel version. This does happen sometimes. Your GPU might overheat. Above 90°C most computers shut down for safety reasons.

Start KSysGuard (you are using KDE, right - if not something similar on your DE) and have a look at the HW-temperatures. If it's not working, install "sensors" from the package "sensors". Just call "sensors" in the terminal to see what temperatures your CPU and GPU is working or even better run a shell-script and log it.

In case, consider switching to the proprietary video-driver (does it work with TW???) or do some research whether a kernel upgrade or downgrade might improve your situation.

Maybe this is a hint that can help you. Simon

Am 20.09.2015 18:47, schrieb Chan Ju Ping:

...

Online, it would be Flash sites like Crunchyroll. Offline, it is with mpv using either smplayer or bomi as the GUI frontend, playing mp4, wmv, and the usual formats.

I have toggled various settings in the KDE compositor since writing the last email, and the latest one with the Scale method set to Crisp, rendering with OpenGL 3.1 with EGL as the interface, and suspending compositor for full screen windows has been the most reliable set-up so far. Managed to make it through a whole episode in Crunchyroll without crashing.

Yes. When it froze up, that's the first thing I tried. Sometimes if I am lucky, I get to switch to the other tty, otherwise it just freezes in place. Or in the case when video is playing, the scene gets stuck in a loop and I am unable to get the desktop back, even after killing the process in tty. Getting to the other terminals is only useful for a reboot, without having to reach for the reboot button. Luckily with an SSD, I am not as concerned with physical damage to the hard drive as I would with a normal spinning disk. Is there a way to log these events so I can give useful debugging information? On Sunday, September 20, 2015 04:07:15 PM Roman Bysh wrote:

On 09/20/2015 03:10 PM, Chan Ju Ping wrote:

...

Spoke too soon again. Restarting the computer left me with a black screen on the next boot up. I could run krunner and yast but could not see the desktop or the panel.

My GPU is the SAPPHIRE Vapor-X 100364VXL Radeon R9 270X 2GB 256-Bit GDDR5 PCI Express 3.0 CrossFireX Support OC WITH BOOST Video Card

It's a pretty high end card, and I just built this machine early this summer, so heat should not be an issue.

It is now running at a steady 35℃ for the GPU.

I have read a lot of announcements that indicate TW is best supported by the free drivers, so I don't think using fglrx would improve the situation, in fact I suspect it will make it worse.

Oh well, this is what living on the edge feels like! It's what I signed up for when I thought stable releases were getting boring. :-)

For now I have disabled the compositor on startup, and will now install some debug symbols for the next batch of tests.

On Sunday, September 20, 2015 07:11:37 PM Simon Heimbach wrote:

...

What graphic card do you have? For me this issue sounds like a step back for your video-driver due to the newer kernel version. This does happen sometimes. Your GPU might overheat. Above 90°C most computers shut down for safety reasons.

Start KSysGuard (you are using KDE, right - if not something similar on your DE) and have a look at the HW-temperatures. If it's not working, install "sensors" from the package "sensors". Just call "sensors" in the terminal to see what temperatures your CPU and GPU is working or even better run a shell-script and log it.

In case, consider switching to the proprietary video-driver (does it work with TW???) or do some research whether a kernel upgrade or downgrade might improve your situation.

Maybe this is a hint that can help you. Simon

Am 20.09.2015 18:47, schrieb Chan Ju Ping:

...

Online, it would be Flash sites like Crunchyroll. Offline, it is with mpv using either smplayer or bomi as the GUI frontend, playing mp4, wmv, and the usual formats.

I have toggled various settings in the KDE compositor since writing the last email, and the latest one with the Scale method set to Crisp, rendering with OpenGL 3.1 with EGL as the interface, and suspending compositor for full screen windows has been the most reliable set-up so far. Managed to make it through a whole episode in Crunchyroll without crashing.

Did you try:

CTRL+ALT+F1 then CTRL+ALT+F7

I have the X.org.0.old log from a crash about an hour ago, which is probably due to me using Adobe connect for a course I am taking. The panel froze, then the programs began to fail one at a time. What's the standard way of attaching the log to the mailing list? On Monday, September 21, 2015 10:12:52 AM Jiri Slaby wrote:

On 09/21/2015, 03:23 AM, Chan Ju Ping wrote:

...

Yes. When it froze up, that's the first thing I tried. Sometimes if I am lucky, I get to switch to the other tty, otherwise it just freezes in place.

Or in the case when video is playing, the scene gets stuck in a loop and I am unable to get the desktop back, even after killing the process in tty. Getting to the other terminals is only useful for a reboot, without having to reach for the reboot button.

Luckily with an SSD, I am not as concerned with physical damage to the hard drive as I would with a normal spinning disk.

Is there a way to log these events so I can give useful debugging information? Most likely Xorg crashes, not the kernel, guessing from your description. So /var/log/Xorg.log should be helpful (.0.old if you reboot first).

regards,

Thanks. I didn't know about suse paste. http://paste.opensuse.org/28157517 On Monday, September 21, 2015 11:40:40 AM Patrick Shanahan wrote:

* Chan Ju Ping [09-21-15 11:36]:

...

I have the X.org.0.old log from a crash about an hour ago, which is probably due to me using Adobe connect for a course I am taking.

The panel froze, then the programs began to fail one at a time.

What's the standard way of attaching the log to the mailing list?

On Monday, September 21, 2015 10:12:52 AM Jiri Slaby wrote:

...

On 09/21/2015, 03:23 AM, Chan Ju Ping wrote:

...

Yes. When it froze up, that's the first thing I tried. Sometimes if I am lucky, I get to switch to the other tty, otherwise it just freezes in place.

Or in the case when video is playing, the scene gets stuck in a loop and I am unable to get the desktop back, even after killing the process in tty. Getting to the other terminals is only useful for a reboot, without having to reach for the reboot button.

Luckily with an SSD, I am not as concerned with physical damage to the hard drive as I would with a normal spinning disk.

Is there a way to log these events so I can give useful debugging information?

Most likely Xorg crashes, not the kernel, guessing from your description. So /var/log/Xorg.log should be helpful (.0.old if you reboot first).

regards,

Post the log to an accessable location where it can be seen. Can be google or pastebook or susepaste or .... Or display it on your own web site/page/...