Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 34

Thread: When something locks and crashes; how do I investigate it?

  1. #11
    Join Date
    Oct 2008
    Location
    ExodusHair<Čubura
    Beans
    3,930
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it??

    Quote Originally Posted by cariboo907 View Post
    Opps, I guess I missed that ,

    Quote Originally Posted by cariboo907 View Post
    What's the difference between the Chromium browser in the ppa's and the repositories? Are there any new features? Or do the ppa versions just have higher version numbers?
    As far as I remember they stopped upgrading at some time so ppa's are for newer (and higher) versions...
    Last edited by zika; January 13th, 2013 at 09:15 AM.

  2. #12
    Join Date
    Mar 2006
    Location
    Williams Lake
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    There was a new maintainer appointed not to long ago, so the repository version, should be fairly close to the daily version.

    Edit: I just installed the daily version from the ppa, and I can't see any differences, I guess I'm going to have to look at the changelog.

  3. #13
    Join Date
    Oct 2008
    Location
    ExodusHair<Čubura
    Beans
    3,930
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    Quote Originally Posted by cariboo907 View Post
    There was a new maintainer appointed not to long ago, so the repository version, should be fairly close to the daily version.

    Edit: I just installed the daily version from the ppa, and I can't see any differences, I guess I'm going to have to look at the changelog.
    I've not used Chromium for a while, since last reinstall (after couple of years) month or two ago, so... Cutting the number of possible toys to play in order to get some real work done...

  4. #14
    Join Date
    Dec 2012
    Location
    europa
    Beans
    104
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    chromium 26

    http://download-chromium.appspot.com/dl/Linux_x64

    is a no go as you have to launch a terminal and run it from there, it's just a zipped folder


    John Swing figured the way to install chromium 24 and that is perfect:

    I do wish they updated chromium in software center like they do firefox.


    anyway I think what's crashing lightworks is a badly functioning sound driver, I've noticed that programs like kazam aren't able to record line-in audio (monitor of stereo blabla)

    0.190 : R3D SDK license #R86, licensed to 'Lightworks UK LTD'
    g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting


    I leave the logs here in case someone smarter figures it out

    Code:
    ATTENTION: default value of option vblank_mode overridden by environment.
    ATTENTION: default value of option vblank_mode overridden by environment.
    ATTENTION: default value of option vblank_mode overridden by environment.
    ATTENTION: default value of option vblank_mode overridden by environment.
    Compiling shader : /usr/share/lightworks/Shaders/flip.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/posterize.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/flop.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/alphakey.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/ColTemp.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/dve1.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/VideoAnalyserHelpers.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/shapes2.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/null.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/squeeze.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/blend.fx .. ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
    ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
    ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
    bt_audio_service_open: connect() failed: Connection refused (111)
    bt_audio_service_open: connect() failed: Connection refused (111)
    bt_audio_service_open: connect() failed: Connection refused (111)
    bt_audio_service_open: connect() failed: Connection refused (111)
    ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
    Cannot connect to server socket err = No such file or directory
    Cannot connect to server request channel
    jack server is not running or cannot be started
    done
    Compiling shader : /usr/share/lightworks/Shaders/greyscale.fx .. done
    Compiling shader : /usr/share/lightworks/Shaders/wipes.fx .. ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
    ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
    ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
    bt_audio_service_open: connect() failed: Connection refused (111)
    bt_audio_service_open: connect() failed: Connection refused (111)
    bt_audio_service_open: connect() failed: Connection refused (111)
    bt_audio_service_open: connect() failed: Connection refused (111)
    ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
    Cannot connect to server socket err = No such file or directory
    Cannot connect to server request channel
    jack server is not running or cannot be started
    Lightworks No. 110 : Beta release Lightworks 11.1.D Build 48522 dated Dec 12 2012
    Starting at Fri Jan 11 22:49:37 2013
    
    Available memory      : 1.4 Gb
    Total memory          : 2.9 Gb
    Virtual Address Range : 2.9 Gb
    Number of CPUs        : 2
    User has admin rights : No
    
    Setting project base directory /home//Lightworks/Projects/
    -0.000   : ---
    Plugins loaded: 19 (full: 19, demo: 0, free: 0)
    PortAudio version number = 1899
    PortAudio version text = 'PortAudio V19-devel (built Oct  8 2012 16:37:35)'
    Number of devices = 9
    --------------------------------------- device #0
    Name                        = HDA Intel: ALC268 Analog (hw:0,0)
    Host API                    = ALSA
    Is full duplex              = 1
    Is input only               = 0
    Is output only              = 0
    Max inputs = 2, Max outputs = 2
    Default low input latency   = 0.01161
    Default low output latency  = 0.01161
    Default high input latency  = 0.0464399
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #1
    Name                        = sysdefault
    Host API                    = ALSA
    Is full duplex              = 1
    Is input only               = 0
    Is output only              = 0
    Max inputs = 128, Max outputs = 128
    Default low input latency   = 0.0426531
    Default low output latency  = 0.0426531
    Default high input latency  = 0.0464399
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #2
    Name                        = front
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.01161
    Default high input latency  = -1
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #3
    Name                        = surround40
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.01161
    Default high input latency  = -1
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #4
    Name                        = surround51
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.01161
    Default high input latency  = -1
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #5
    Name                        = surround71
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.01161
    Default high input latency  = -1
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #6
    Name                        = pulse
    Host API                    = ALSA
    Is full duplex              = 1
    Is input only               = 0
    Is output only              = 0
    Max inputs = 32, Max outputs = 32
    Default low input latency   = 0.01161
    Default low output latency  = 0.01161
    Default high input latency  = 0.0464399
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #7
    Name                        = dmix
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.0426667
    Default high input latency  = -1
    Default high output latency = 0.0426667
    Default sample rate         = 48000
    --------------------------------------- device #8
    [ Default Input, Default Output ]
    Name                        = default
    Host API                    = ALSA
    Is full duplex              = 1
    Is input only               = 0
    Is output only              = 0
    Max inputs = 32, Max outputs = 32
    Default low input latency   = 0.01161
    Default low output latency  = 0.01161
    Default high input latency  = 0.0464399
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    ----------------------------------------------
    0.184    : PortAudio is using [default](8) for OUTPUT
    0.184    : PortAudio is using [default](8) for INPUT
    0.190    : R3D SDK library version = 4.2
    0.190    : R3D SDK header version  = 4.2
    0.190    : Library & header versions match
    0.190    : R3D SDK license #R86, licensed to 'Lightworks UK LTD'
    g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    
    
    Lightworks No. 110 : Beta release Lightworks 11.1.D Build 48522 dated Dec 12 2012
    Starting at Sat Jan 12 10:11:09 2013
    
    Available memory      : 990.4 Mb
    Total memory          : 2.9 Gb
    Virtual Address Range : 2.9 Gb
    Number of CPUs        : 2
    User has admin rights : No
    
    Setting project base directory /home//Lightworks/Projects/
    -0.000   : ---
    Plugins loaded: 19 (full: 19, demo: 0, free: 0)
    PortAudio version number = 1899
    PortAudio version text = 'PortAudio V19-devel (built Oct  8 2012 16:37:35)'
    Number of devices = 9
    --------------------------------------- device #0
    Name                        = HDA Intel: ALC268 Analog (hw:0,0)
    Host API                    = ALSA
    Is full duplex              = 1
    Is input only               = 0
    Is output only              = 0
    Max inputs = 2, Max outputs = 2
    Default low input latency   = 0.01161
    Default low output latency  = 0.01161
    Default high input latency  = 0.0464399
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #1
    Name                        = sysdefault
    Host API                    = ALSA
    Is full duplex              = 1
    Is input only               = 0
    Is output only              = 0
    Max inputs = 128, Max outputs = 128
    Default low input latency   = 0.0426531
    Default low output latency  = 0.0426531
    Default high input latency  = 0.0464399
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #2
    Name                        = front
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.01161
    Default high input latency  = -1
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #3
    Name                        = surround40
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.01161
    Default high input latency  = -1
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #4
    Name                        = surround51
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.01161
    Default high input latency  = -1
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #5
    Name                        = surround71
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.01161
    Default high input latency  = -1
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #6
    Name                        = pulse
    Host API                    = ALSA
    Is full duplex              = 1
    Is input only               = 0
    Is output only              = 0
    Max inputs = 32, Max outputs = 32
    Default low input latency   = 0.01161
    Default low output latency  = 0.01161
    Default high input latency  = 0.0464399
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    --------------------------------------- device #7
    Name                        = dmix
    Host API                    = ALSA
    Is full duplex              = 0
    Is input only               = 0
    Is output only              = 1
    Max inputs = 0, Max outputs = 2
    Default low input latency   = -1
    Default low output latency  = 0.0426667
    Default high input latency  = -1
    Default high output latency = 0.0426667
    Default sample rate         = 48000
    --------------------------------------- device #8
    [ Default Input, Default Output ]
    Name                        = default
    Host API                    = ALSA
    Is full duplex              = 1
    Is input only               = 0
    Is output only              = 0
    Max inputs = 32, Max outputs = 32
    Default low input latency   = 0.01161
    Default low output latency  = 0.01161
    Default high input latency  = 0.0464399
    Default high output latency = 0.0464399
    Default sample rate         = 44100
    ----------------------------------------------
    Last edited by nomenkultur; January 13th, 2013 at 11:15 AM.

  5. #15
    Join Date
    Oct 2008
    Location
    ExodusHair<Čubura
    Beans
    3,930
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    Quote Originally Posted by nomenkultur View Post
    chromium 26

    http://download-chromium.appspot.com/dl/Linux_x64

    is a no go as you have to launch a terminal and run it from there, it's just a zipped folder
    No, You do not have to start it from terminal... You can start it from any prompt (even in GUI) avilable...
    @cariboo907 showed You how...
    I thought that You had another (plausible) reason for starting it from CLI...
    I'm using FF that way for years (nightly channel) and lot of SW is distributed that way...
    You've made me DL that archive... There is something fishy about it, I'll investigate further...
    I would sincerely avoid that implementation of Chromium... I'd wish I'm wrong...
    Any reason why not You use https://launchpad.net/~a-v-shkop/+archive/chromium-dev ...?

    Update₁: No, it is OK... I'm writing this from „Your“ version of Chromium, started in awesome through Run dialog in GUI, not using Terminal...
    Update₂: Now I have to force myself to stop using Chromium again...
    Last edited by zika; January 13th, 2013 at 04:37 PM.

  6. #16
    Join Date
    Aug 2010
    Location
    Arizona USA
    Beans
    2,845
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    Quote Originally Posted by zika View Post
    Nope. No reason(s) not to use it.

    I've been using Alex's dev PPA for a while now...

    Quote Originally Posted by zika View Post
    Update: Now I have to force myself to stop using Chromium again...
    Heh! I must admit, I love Chromium!

    The only thing I use Fx for, these days, is DL'ing important things, e.g. via the Fx DTA (DownThemAll) extension.

    IMO, Chromium has been outshining Fx for a couple of years, and it just keeps getting better n' better.

    Fx, one the other hand, seems to be sliding off the backside of the table...
    Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
    Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
    XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU

  7. #17
    Join Date
    Oct 2008
    Location
    ExodusHair<Čubura
    Beans
    3,930
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    Quote Originally Posted by VinDSL View Post
    Nope. No reason(s) not to use it.

    I've been using Alex's dev PPA for a while now...


    Heh! I must admit, I love Chromium!

    The only thing I use Fx for, these days, is DL'ing important things, e.g. via the Fx DTA (DownThemAll) extension.

    IMO, Chromium has been outshining Fx for a couple of years, and it just keeps getting better n' better.

    Fx, one the other hand, seems to be sliding off the backside of the table...
    Yes, but Alex's dev PPA is a bit outdated... That did drive me away from chromium for some time...
    I'm thankfull to @nomenkultur that pointed me to this new resource of newest version of Chromium... It took a while before I've got enough trust to try it on working machine but... It is OK... I must be honest: I love these apps that are only un-zipped... Easy to get rid of them... But those do stay to the last minute of the life of an install...

  8. #18
    Join Date
    Aug 2010
    Location
    Arizona USA
    Beans
    2,845
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    Quote Originally Posted by zika View Post
    Yes, but Alex's dev PPA is a bit outdated... That did drive me away from chromium for some time...

    I'm thankfull to @nomenkultur that pointed me to this new resource of newest version of Chromium...
    WoW! They did it again!

    Chromium is getting slicker, all the time!


    Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
    Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
    XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU

  9. #19
    Join Date
    Aug 2010
    Location
    Arizona USA
    Beans
    2,845
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    Quote Originally Posted by zika View Post
    No, You do not have to start it from terminal...

    You can start it from any prompt (even in GUI) avilable...

    @cariboo907 showed You how...
    Been playing with Chromium 26 for a few hours. Works great! Flash apps run much better than on Chromium 25.

    The only extension I cannot live without is Ghostery. Installed it. Don't mind ads (kinda like them), but I hate trackers.

    Switched to one of my favorite themes -- Ubuntu Black Magic.

    Imported my bookmarks, and tweaked a few settings, blah, blah, blah.

    As far as starting Chromium 26 goes...

    To recap:

    • I downloaded chromium.zip from the link above.
    • Extracted chromium zip to: /home/vindsl/chrome-linux
    • Renamed resultant folder from: chrome-linux -> .chrome-linux (e.g. hid it).
    • Created an empty config folder: /home/vindsl/.config/chromium-canary
    • Created a .desktop file: /home/vindsl/.local/share/applications/chromium-canary.desktop
    • Here's the command I used: ./.chrome-linux/chrome --user-data-dir=~/.config/chromium-canary %u
    • Made chromium-canary.desktop executable: "Allow executing file as program" (in Nautilus).
    • Added: chromium-canary.desktop to my Gnome-Shell Favorites.

    Loads, runs, shuts down, just like any other proggie...
    Last edited by VinDSL; January 14th, 2013 at 01:47 AM. Reason: Typo Demon Strikes Again
    Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
    Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
    XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU

  10. #20
    Join Date
    Aug 2010
    Location
    Arizona USA
    Beans
    2,845
    Distro
    Ubuntu Development Release

    Re: When something locks and crashes; how do I investigate it?

    w00t! Native RTC channels work...




    Plus, YouTube streaming speeds are up +17%.

    Back on topic...
    Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
    Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
    XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU

Page 2 of 4 FirstFirst 1234 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •