Upgraded to Skype 7 But crashes after login

Hi,
I updated my skype the other night and it crashes every time it logs me in.
I'm using my hotmail/msn login. on windows 7 home premium.
Had no problem until I upgraded.
I tried uninstalling skype, then clearing anythig in %appdata% roaming and local
Installed skype again and same thing.
Solved!
Go to Solution.

Hi,
Here's that info
Faulting application name: Skype.exe, version: 7.0.0.102, time stamp: 0x54897add
Faulting module name: FFsource.ax, version: 0.0.0.0, time stamp: 0x5310fb94
Exception code: 0xc0000005
Fault offset: 0x000031b1
Faulting process id: 0x1750
Faulting application start time: 0x01d019d3954a2efb
Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe
Faulting module path: C:\Program Files (x86)\FFsplit\Filters\FFsource.ax
Report Id: e0092e67-85c6-11e4-8d17-b870f4f304eb
I didn't install that click to call option maybe that ahd soemthign to do with it?
Thank

Similar Messages

  • Skype 7.5 Crashing After Login/Startup

    DxDiag is attached. There are NO LOGS in my event viewer for Skype. Nothing is being logged on crash. No error message either. The window simply pops up for ~1-3 seconds and then disappears.
    ALL VERSIONS OF SKYPE ARE DOING THIS. NOT JUST 7.5
    I've tried reinstalling, completely wiping everything and all that jazz. No dice.
    I've tried skype 6.3. No dice.
    Updated ALL drivers. No dice.
    Windows 7 x64 SP1 ALL UPDATES.
    sfc /scannow log attached as well.
    Attachments:
    SkypeCrashStuff.zip ‏89 KB

    What is the version of Internet Explorer installed on your computer?
    In Internet Explorer go to Help -> About Internet Explorer.
    P.S. Please, don’t say that you are not using Internet Explorer. This is irrelevant. Skype depends on Internet Explorer.

  • Having upgraded from iPhoto 11 to iPhoto 2.0 (531) it now loads but crashes after a minute or so and none of the buttons work. Can anyone help please.

    Having upgraded from iPhoto 11 to iPhoto 2.0 (531) it now loads but crashes after a minute or so and none of the buttons work. Can anyone help please.

    Hey Ian
    That would be correct. because of the nature of your issue, you may find more information by using another one of Apple's support resources.
    Contact Apple Support
    https://getsupport.apple.com/GetproductgroupList.action
    Thank you for using the Apple Support Community.
    -Norm G.

  • Ios7 bookamrking web application to home screen via Safari crashes after login and when we try to open any link inside. Can anyone please tell me if there is any scheduled fix for this bug in safari?

    ios7 bookmarking web application to home screen via Safari, crashes after login and when we try to open any link inside from the icon that gets created on the home screen. Can anyone please tell me if there is any scheduled fix for this bug in safari?
    From what i understand i see that - Cookies are not transferred between your website and your webapp when installing the icon on the home screen (for authentication purposes for example). It was working until 6.1 and now it’s not working anymore.
    Can someone please tell me if this bug will be fixed in any future release, if so the ticket number of some kind that i can track, or if there is a workaround for this issue?

    ios7 bookmarking web application to home screen via Safari, crashes after login and when we try to open any link inside from the icon that gets created on the home screen. Can anyone please tell me if there is any scheduled fix for this bug in safari?
    From what i understand i see that - Cookies are not transferred between your website and your webapp when installing the icon on the home screen (for authentication purposes for example). It was working until 6.1 and now it’s not working anymore.
    Can someone please tell me if this bug will be fixed in any future release, if so the ticket number of some kind that i can track, or if there is a workaround for this issue?

  • Skype v7.0.0.102 crashes after login

    Hello comunity,
    after i update my skype from 6.21.0.104 to 7.0.0.102 it always crashes after i login in skype.
    I get the following message in my event log:
    Name der fehlerhaften Anwendung: Skype.exe, Version: 7.0.0.102, Zeitstempel: 0x54897add
    Name des fehlerhaften Moduls: Skype.exe, Version: 7.0.0.102, Zeitstempel: 0x54897add
    Ausnahmecode: 0xc0000005
    Fehleroffset: 0x00d527d7
    ID des fehlerhaften Prozesses: 0x11ac
    Startzeit der fehlerhaften Anwendung: 0x01d02a93dc7b1329
    Pfad der fehlerhaften Anwendung: C:\SkypePortable\App\Skype\Phone\Skype.exe
    Pfad des fehlerhaften Moduls: C:\SkypePortable\App\Skype\Phone\Skype.exe
    I hope you can help me
    Kind regards
    Attachments:
    DxDiag.zip ‏6 KB

    Most likely this is one of the several cases when the latest Skype 7.0 version is not able correctly to interpret BIOS data. At least, this was the issue with the previously reported cases with this error message:
    Exception code: 0xc0000005
    Fault offset: 0x00d527d7
    It seems that Skype has identified the issue and a fix is promised in one of the upcoming Skype versions.
    http://community.skype.com/t5/Windows-desktop-clie​​nt/Skype-has-stopped-working/m-p/3815022#M323073
    Meanwhile, the working solution is to uninstall the 7.0 version and install the previous 6.21.0.104 Skype version:
    http://download.skype.com/msi/SkypeSetup_6.21.0.10​4.msi

  • GNOME 3.16: Crash after login with GDM

    Hi all,
    I've just upgraded to GNOME 3.16, but unfortunately it wasn't completely successful. After I login with GDM, I get the "Oh no! something has gone wrong" screen, with logout the only option. Funny thing is: when I press the super-key, I have a working GNOME shell. I can even start programs like nautilus and firefox. But the error screen is in my view.
    The full log can be viewed here:
    https://dl.dropboxusercontent.com/u/52318319/log.txt
    Notable things:
    - GNOME settings daemon crashes
    - After that nautilus
    But I can't find any obvious solution in the log. Anyone who could help me here?
    Thanks in advance!
    Last edited by sh4wn (2015-04-10 20:51:06)

    Welcome to the club, https://bbs.archlinux.org/viewtopic.php?id=195880  and  https://bbs.archlinux.org/viewtopic.php?id=195866   i guess just have patience...

  • Skype on Mac crashes after a few seconds

    Hi, so a couple weeks ago I was trying to use skype and it just kept crashing after a few seconds of me opening it. I've tried reinstalling it, updating it, updating my computer, nothing has worked. If I'm actually able to call someone it's fine, but otherwise it just crashes on me.

    Hi Ruby,
    are you using the latest Skype version 7.7? It was just released yesterday.
    If it's still crashing for you on 7.7, then could you attach your crashlog to this thread?
    Thanks,
    Rene

  • After upgrade to 2014.2 - unusable, crashes after 30 seconds

    Hi, I am new to this forum. I've bought a year plan with premiere cc2014.
    And I am shocked how often this most recent update (2014.2) is crashing after 30 seconds of editing. When I close program monitor, it does not crash, so I assume it has something to do with mercury playback. It is indeed unusable. I've downgraded to cc2014.1 and it seems to work perfectly.
    But what is the point of paying the cash for most recent software?
    I also use cineform material, editing in realtime in 4k resolution, including realtime grading with direct link to speedgrade. It is all possible in 2014.1 with no crashes.
    But, actually - is there any new feature in 2014.2 that is worth the frustration for?
    Right now I am staying with 2014.1
    My system specs:
    intel i7 3930k on ASUS P97 motherboard
    48GB ram
    4k LG TV as a timeline panel & full hd NEC monitor as program monitor.
    2x gtx780 gigabyte cuda cards (1.5 GB ram each)
    4 x ssd from intel, samsung and adata.
    3 x 4TB hdd from seagate and western digital.
    ssd used for scratch and preview disk.
    I dont know how to extract exact data about error - there is no option for this after crash. It says only "program stopped working" and thats all.

    qwertyuiopxeoo wrote:
    Since Skype new version emerged, Skype app always stops working in my tablet ("unforunately Skype app stopped working"). I also tried uninstalling and reinstalling many times, but it had no effect. Is there a fix for this problem ? Thank you!
    Yup, 5.2.0.61097 broke my Memo also. "Skype has stopped working"
    So I went to my Dell Venue Android device which has been sitting unused for a month.
    Before I could stop it, i also auto updated and it too broke.
    So i went and downloaded a previous version from http://skype.en.uptodown.com/android.
    I uninstall the newest version from both tablets and installed 5.1.0.58677.
    Everything is working just fine again. Maybe Skype should roll out an auto downdate
    Don't forget to turn off auto updates in the PlayStore app and in Security check
    " allow unknown sources" so that you can install the .apk you just downloaded.

  • Macbook crashes after login, but fine in safe mode... please help!!

    So, out of nowhere my trusty macbook a few seconds after my desktop appears the computer needs to restart screen scrolls down, and that's pretty much it, as far as i'm aware I haven't changed any permissions and as far as i can see there isn't a programme to blame, as mentioned safe mode is fine, this is how i'm able to write this, is there anything I can do from here to try and fix the problem with the regular login?
    Thanks.
    Will.

    If it works in safe mode then that usually means there is something related to system files causing the problem or the installation of incompatible software or malfunctioning software. The simplest solution is to reinstall OS X as follows:
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • After upgrade GDM accepts password but doesn't login

    I've upgraded system tonight. Then I restarted the system. Now GDM (Gnome Display Manager) shows me the login window, I type password, then I see black screen and then GDM shows the login window again.
    This is last messages in /var/log/pacman.log:
    [2013-07-02 19:47] [PACMAN] Running 'pacman -Syu'
    [2013-07-02 19:47] [PACMAN] synchronizing package lists
    [2013-07-02 19:49] [PACMAN] starting full system upgrade
    [2013-07-02 20:09] [PACMAN] upgraded automake (1.13.4-1 -> 1.14-1)
    [2013-07-02 20:09] [PACMAN] upgraded clutter-gtk (1.4.4-1 -> 1.4.4-2)
    [2013-07-02 20:09] [PACMAN] upgraded lcms2 (2.4-1 -> 2.5-1)
    [2013-07-02 20:09] [PACMAN] upgraded colord (1.0.0-1 -> 1.0.1-1)
    [2013-07-02 20:09] [PACMAN] upgraded cronie (1.4.9-4 -> 1.4.9-5)
    [2013-07-02 20:09] [PACMAN] upgraded cups-filters (1.0.34-4 -> 1.0.35-1)
    [2013-07-02 20:09] [PACMAN] upgraded curl (7.30.0-1 -> 7.31.0-1)
    [2013-07-02 20:09] [PACMAN] upgraded giflib (4.2.1-2 -> 4.2.1-3)
    [2013-07-02 20:09] [PACMAN] upgraded git (1.8.3.1-1 -> 1.8.3.2-1)
    [2013-07-02 20:09] [PACMAN] upgraded libsecret (0.15-1 -> 0.15-2)
    [2013-07-02 20:09] [PACMAN] upgraded gnome-shell (3.8.3-1 -> 3.8.3-3)
    [2013-07-02 20:09] [PACMAN] upgraded grub (2.00-1 -> 2.00.5043-2)
    [2013-07-02 20:09] [PACMAN] upgraded gtkmm (2.24.3-1 -> 2.24.4-1)
    [2013-07-02 20:09] [PACMAN] upgraded gvfs (1.16.3-1 -> 1.16.3-2)
    [2013-07-02 20:09] [PACMAN] upgraded imagemagick (6.8.5.10-1 -> 6.8.6.2-1)
    [2013-07-02 20:09] [PACMAN] upgraded isl (0.11.2-1 -> 0.12-1)
    [2013-07-02 20:09] [PACMAN] upgraded libgsf (1.14.26-1 -> 1.14.27-1)
    [2013-07-02 20:09] [PACMAN] upgraded libtheora (1.1.1-2 -> 1.1.1-3)
    [2013-07-02 20:09] [PACMAN] upgraded libvdpau (0.6-1 -> 0.6-2)
    [2013-07-02 20:09] [PACMAN] upgraded mesa (9.1.3-2 -> 9.1.4-1)
    [2013-07-02 20:09] [PACMAN] upgraded xorg-server-common (1.14.1-1 -> 1.14.2-2)
    [2013-07-02 20:09] [PACMAN] upgraded xorg-server (1.14.1-1 -> 1.14.2-2)
    [2013-07-02 20:09] [PACMAN] upgraded nvidia-utils (319.23-1 -> 319.32-1)
    [2013-07-02 20:09] [PACMAN] upgraded nvidia-libgl (319.23-1 -> 319.32-1)
    [2013-07-02 20:09] [PACMAN] upgraded libva (1.1.1-1 -> 1.2.1-1)
    [2013-07-02 20:09] [PACMAN] upgraded libwebp (0.3.0-3 -> 0.3.1-1)
    [2013-07-02 20:09] [PACMAN] upgraded libxi (1.7.1-2 -> 1.7.1-3)
    [2013-07-02 20:09] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
    2013-07-02 20:09] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Starting build: 3.9.8-1-ARCH
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Image generation successful
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Starting build: 3.9.8-1-ARCH
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2013-07-02 20:09] [ALPM-SCRIPTLET] ==> Image generation successful
    [2013-07-02 20:09] [PACMAN] upgraded linux (3.9.7-1 -> 3.9.8-1)
    [2013-07-02 20:09] [PACMAN] upgraded man-db (2.6.3-3 -> 2.6.5-1)
    [2013-07-02 20:09] [PACMAN] upgraded nvidia (319.23-3 -> 319.32-2)
    [2013-07-02 20:09] [PACMAN] upgraded openmpi (1.6.4-2 -> 1.6.5-1)
    [2013-07-02 20:09] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
    [2013-07-02 20:09] [PACMAN] upgraded pacman-mirrorlist (20130601-1 -> 20130626-1)
    [2013-07-02 20:09] [PACMAN] upgraded perl-tk (804.030-5 -> 804.031-1)
    [2013-07-02 20:09] [PACMAN] upgraded procps-ng (3.3.8-1 -> 3.3.8-2)
    [2013-07-02 20:09] [PACMAN] upgraded qt4 (4.8.4-18 -> 4.8.5-1)
    [2013-07-02 20:09] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
    [2013-07-02 20:09] [PACMAN] upgraded virtualbox-host-modules (4.2.12-9 -> 4.2.14-2)
    [2013-07-02 20:10] [PACMAN] upgraded virtualbox (4.2.12-3 -> 4.2.14-1)
    [2013-07-02 20:10] [PACMAN] upgraded xorg-server-xephyr (1.14.1-1 -> 1.14.2-2)
    [2013-07-02 20:13] [PACMAN] Running 'pacman -S lua'
    [2013-07-02 20:13] [PACMAN] Running 'pacman -S lua lua-posix lua-filesystem'
    [2013-07-02 20:14] [PACMAN] Running 'pacman -S lua lua-posix lua-filesystem'
    [2013-07-02 20:14] [PACMAN] installed lua (5.2.2-1)
    [2013-07-02 20:14] [PACMAN] installed lua-posix (29-1)
    [2013-07-02 20:14] [PACMAN] installed lua-filesystem (1.6.2-2)
    [2013-07-02 20:30] [PACMAN] Running 'pacman -S rsync'
    [2013-07-02 20:30] [PACMAN] installed rsync (3.0.9-6)
    Last events from journalctl:
    Jul 02 19:43:38 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x244ad4e (Confir
    m Ex)
    Jul 02 19:43:38 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
    Jul 02 19:43:39 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x24002de (C/C++
    - st)
    Jul 02 19:43:39 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
    Jul 02 20:09:36 dima-dell-ws /etc/gdm/Xsession[746]: /proc/self/exe: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or
    directory
    Jul 02 20:09:36 dima-dell-ws /etc/gdm/Xsession[746]: /proc/self/exe: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or
    directory
    Jul 02 20:09:36 dima-dell-ws /etc/gdm/Xsession[746]: /proc/self/exe: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or
    directory
    ... A lot of the same complains about libGL.so.1...
    Jul 02 20:09:37 dima-dell-ws /etc/gdm/Xsession[746]: /proc/self/exe: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory
    Jul 02 21:40:29 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
    Jul 02 21:40:29 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: Got a request to focus 0x160005a (Texas Adva) with a timestamp of 0. This shouldn't happen!
    Jul 02 21:40:29 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
    Jul 02 21:40:29 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
    Jul 02 21:40:39 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
    Jul 02 21:40:39 dima-dell-ws /etc/gdm/Xsession[746]: Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
    Jul 02 21:40:40 dima-dell-ws /etc/gdm/Xsession[746]: Check failed: g_pipe_pid == getpid()
    -- Reboot --
    Jul 02 21:44:12 dima-dell-ws /etc/gdm/Xsession[681]: /etc/gdm/Xsession: Beginning session setup...
    Jul 02 21:44:27 dima-dell-ws /etc/gdm/Xsession[812]: /etc/gdm/Xsession: Beginning session setup...
    Jul 02 21:44:40 dima-dell-ws /etc/gdm/Xsession[898]: /etc/gdm/Xsession: Beginning session setup...
    Could you tell me please what the problem is? Thank you in advance!

    I changed the dima line in the /etc/passwd.
    Rebooted. Tried to login. After password entering GDM appeared again.
    $ systemctl status gdm
    gdm.service - GNOME Display Manager
    Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled)
    Active: active (running) since Tue 2013-07-02 23:21:39 AST; 1min 27s ago
    Main PID: 367 (gdm)
    CGroup: name=systemd:/system/gdm.service
    ├─367 /usr/bin/gdm
    ├─699 /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/_1
    ├─703 /usr/bin/Xorg :1 -background none -verbose -auth /var/run/gdm/auth-for-gdm-H9ArG5/database -seat seat0 -nolisten tcp vt1
    └─711 gdm-session-worker [pam/gdm-launch-environment]
    $ journalctl -b
    Hint: You are currently not seeing messages from other users and the system.
    Users in the 'systemd-journal' group can see all messages. Pass -q to
    turn off this notice.
    Error was encountered while opening journal files: No data available
    -- Logs begin at Thu 2013-06-13 21:32:03 AST, end at Tue 2013-07-02 23:23:34 AST. --
    Jul 02 23:21:55 dima-dell-ws /etc/gdm/Xsession[628]: /etc/gdm/Xsession: Beginning session setup...
    Jul 02 23:23:34 dima-dell-ws /etc/gdm/Xsession[862]: /etc/gdm/Xsession: Beginning session setup...

  • Crashes after login

    My computer crashed, and after restarting, at first the desktop would build and startup scripts would appear. But now, the desktop is not building, and I can't get past the login page.
    It Command+V boot, safe boot, or boot from the start disk.
    1.83 GHz.
    Any help is appreciated!

    Hello dd:
    Welcome to Apple discussions.
    Do I understand your post that you cannot boot from your software install DVD?
    If that is the case, I suggest you take the computer to an Apple store or to an Apple-certified technician for diagnosis/repair. There is really little one can do without being able to boot from that DVD.
    Barry
    P.S. Please post more descriptive information in your profile (see mine below).

  • Installing upgrade to G5 and computer crashes after 20-30 mins. Any advice?

    BACKSTORY: I have a slow running G5 (2nd generation 2005). It came with the standard two 512 MB chips. When I upgraded my Abode programs to CS3 I notes problems. After being pin ponged from Adobe & Apple support I was told to upgrade my memory. After weeks of calls & talking with the Genius Bar guys I was directed to a site to get memory for my G5 [because Apple no longer carried the upgradable memory].
    WHAT I DID: I order and got four 1GB Memory sticks and added them to my system. [All installed with no problems and correctly.] Which when turned back on caused applications to fail and the screen to turn gray and ask for manual shutdown. This happened five times.
    MORE PROBLEMS: I called the support hot-line {for crucial.com] after I tried safe re-starts, Disk Utility and going through the painful shutdown/ start up with different combinations of the new memory sticks. The tech asked me to do a few more checks. Sometimes I'd get 20 mins before the system locked up and I had to manually restart. One guy said it may be a timing issue- memory good but the computer can't process at the right level. He said that nothing could be done, but that possibility was no unlikely unless my board was fried. Finally, I've returned the memory and and am waiting for replacements. I'm back to the 512 MB sticks and everything is okay, just really slow.
    QUESTION: Does this sound familiar to anyone?? I am having no luck with any tech support people. If so what did you do. PLEASE HELP!!! Other than working really slow the G5 is actually a great machine.
    Too bad Apple is too busy with iPods and not making better towers upgrades. Sorry, that comment was just mean.

    If the replacement chips don't work I'll check out the site. Thanks!. Its cheaper too.

  • ITunes opening but crashing after "checking itunes library"

    My computer has issues with multiple applications, which mostly are connected to itunes/ilife. iPhoto, iWeb, Front Row and iTunes all crash at certain points, but iMovie opens fine, although I haven't tested anything within it other than playback. YouControlTunes (an iTunes controller) also has issues. Reinstalling the OS has made no difference, nor has reinstalling iTunes. I will try reinstalling iLife (again).
    iTunes did work after reinstalling the OS the first time after trashing iTunes and iLife and other applications that used up hard drive space (was running low so wanted to make sure Mac OS X installed fine), but after reinstalling iLife and Firefox and other applications then iTunes stopped working again. Garageband and iDVD weren't reinstalled.
    I shall try trashing the iTunes library.
    Also, the application Mactracker and the installers for 1.0.4 & 1.0.5 of Age of Empires III did not work, so the problem is presumably not iLife.

    Try this;-
    try removing the Genius database. In the "Finder" go to the /username/Music/iTunes/ folder and delete the "iTunes Library Genius.itdb" file. This may allow the program to launch again. This file will be recreated upon first use of the "Genius" feature.
    and
    I found that the TSLicense plugin was causing the problem.
    From the log:
    PlugIn Path: /Library/Frameworks/TSLicense.framework/Versions/A/TSLicense
    PlugIn Identifier: net.telestream.license
    This pIugin is installed with the Flip4Mac Windows Media Components. I solved the problem by uninstalling the WM Components via the uninstaller at /Applications/Flip4Mac/Flip4Mac WMV Uninstaller.pkg, after which iTunes opens successfully.
    worked for me!

  • MBP not displaying to external monitor at startup, but does after login

    After I installed Yosemite my MBP will not automatically display to my external monitor (HDMI) when I start it up. I have to first login to my MBP and then my external monitor is immediately recognized and my mirroring desktops works as intended...as it did before I upgraded to Yosemite. I have no idea why the signal to my external monitor doesn't/will not work upon system start up. Anyone out there know??

    Did you find  a solution? I have the exact same problem. I just install Yosemite and did not have the problem before.

  • App installs but crashes after launching

    I installed an application - a driver for a 3G mobile usb modem - onto my MPB and my wife's identical MBP. On my computer it works fine, but on hers it crashes shortly after launching. The Problem Report gives the info pasted below (there's a lot more but this appeared to be the most important data since it came first. The modem support people haven't heard of this happening before. I think it's the Mac problem since the installation works fine on the other MBP.
    The app is actually a driver which launches a simple interface to work with the modem. When it launches, it opens and presents a small screen into which I type a PIN for the modem. It then opens a bigger screen with settings for the modem. That is when the problem occurs on one machine - the bigger second screen opens for about 5 seconds then the whole app quits with no signs or warnings.
    Any help much appreciated. Thanks.
    === the text from the crash/problem report:===
    Process: MobileConnect [2181]
    Path: /Applications/MobileConnect.app/Contents/MacOS/MobileConnect
    Identifier: com.yourcompany.MobileConnect
    Version: ??? (1.0)
    Code Type: X86 (Native)
    Parent Process: launchd [161]
    Date/Time: 2008-06-19 11:25:08.775 +0800
    OS Version: Mac OS X 10.5.3 (9D34)
    Report Version: 6
    Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000005
    Crashed Thread: 0
    Thread 0 Crashed:
    0 com.apple.CoreFoundation 0x96f66058 CFEqual + 72
    1 com.yourcompany.MobileConnect 0x00002d22 GetServiceID + 128
    2 com.yourcompany.MobileConnect 0x00002d4c IsConnectedEx + 19
    3 com.yourcompany.MobileConnect 0x00002dc8 IsConnected + 11
    4 com.yourcompany.MobileConnect 0x00003907 DialEventLoopTimerCallback + 28
    5 com.apple.CoreFoundation 0x96f63b3e CFRunLoopRunSpecific + 4494
    6 com.apple.CoreFoundation 0x96f63cf8 CFRunLoopRunInMode + 88
    7 com.apple.HIToolbox 0x92e13da4 RunCurrentEventLoopInMode + 283
    8 com.apple.HIToolbox 0x92e13bbd ReceiveNextEventCommon + 374
    9 com.apple.HIToolbox 0x92e725f2 _AcquireNextEvent + 58
    10 com.apple.HIToolbox 0x92e70d4f RunApplicationEventLoop + 207
    11 com.yourcompany.MobileConnect 0x0000a04c main + 987
    12 com.yourcompany.MobileConnect 0x00001f72 _start + 216
    13 com.yourcompany.MobileConnect 0x00001e99 start + 41
    Thread 1:
    0 libSystem.B.dylib 0x91d455c6 machwaituntil + 10
    1 libSystem.B.dylib 0x91dbd1e5 nanosleep + 314
    2 libSystem.B.dylib 0x91dbd0a5 usleep + 61
    3 com.yourcompany.MobileConnect 0x00018389 ReadThreadFun + 30
    4 ...ple.CoreServices.CarbonCore 0x91f2655b PrivateMPEntryPoint + 56
    5 libSystem.B.dylib 0x91d766f5 pthreadstart + 321
    6 libSystem.B.dylib 0x91d765b2 thread_start + 34
    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x00000000 ebx: 0x96f66029 ecx: 0x00000007 edx: 0xa09614a0
    edi: 0x00025a94 esi: 0x00000400 ebp: 0xbffff238 esp: 0xbffff210
    ss: 0x0000001f efl: 0x00010246 eip: 0x96f66058 cs: 0x00000017
    ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
    cr2: 0x00000005
    === end===
    Additional and subsequent info:
    I just checked permissions on both machines for this app and on my MBP the permissions are "system: Read & Write / wheel: Read only / everyone: Read only" whereas on the problem installation the permissions are totally different!: "aewr (my wife's username): Read & Write / admin: Read & Write / everyone: Read & Write".
    How come these are so different! And how can I make then the same??? I've reinstalled the app several times and once even copied it lock stock and barrel from my MBP to the other one, but same result. Did permissions repair on the problem machine too but the permissions I've quoted are the result (don't know what the permissions were beofre the repair but it wasn't working then either).
    Many thanks.
    Message was edited by: PaulWR - Added permissions info.

    I don't have an exact answer for you, but can provide some thoughts. First, a bus error is typically indicative of a bug in application code; the program is trying to access memory that can't be addressed (that's a typical cause, anyway). So I'd immediately suspect this 3G driver, which presumably is named Mobile Connect as identified by the kernel.
    There's a thread here:
    http://forum.huawei.com/jive4/thread.jspa?threadID=322226
    that implies that only 10.5.2 is supported by this device at this time. Are you certain that 10.5.3 is supported with your device? Perhaps it's a fluke that it is working on your machine...

Maybe you are looking for