Skype cant login after update to 7.2 cant retrieve...

After the upgrade to 7.2 skyped logged me out and never allowed to log back in. My password must have been reset. The dilemma: the email provided to send a temp password to was discontinued before I could change it in my skype settings. So now I am stuck in a loop of not being able to get a new password since there is no valid email to send it to on file. To seek help I filled out the Skype Account Verification form with a promise to get a response withing 24h which I get...an automated email to fill out that form again. So I do...and 24h later I get the same automated email again to fill out that form...this is the definition insanity. Any chance to talk to real people?
Kind regards,
Anselm

Any takers? This is becoming a massive help desk fail! How can a company the size of MS/Skype have vitually NO support for a product this popular?!?
I filled out the Accoutn Verification Form 4 times by now only to receive an email to fill that same form out again. This is becoming sillyness!!!

Similar Messages

  • TS4348 After update to 10.8 cant login

    Hi anyone help after update max os i cant login, neither as guest.

    Please read this whole message before doing anything.
    I've tested these instructions only with the Safari web browser. If you use another browser, they may not work as described.
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.  
    These steps are to be taken while booted in safe mode.
    Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects. 
    Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands. 
    Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply. 
    Launch the Terminal application in any of the following ways: 
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.) 
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. 
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid. 
    When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign. 
    Step 1 
    Triple-click anywhere in the line of text below on this page to select it:
    for k in {,/S*}/L*/E*/{,.?}*.kext; do test -f "$k/Contents/Info.plist" && /usr/libexec/PlistBuddy -c "Print :CFBundleIdentifier" "$_" | egrep -qv "apple|Accusys|ArcMSR|ATTO|CalDigit|HighPoint|hp-fax|JMicron|print|SoftRAID|stex" && echo $k; done | open -ef
    Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
    Step 2 
    Repeat with this line:
    { sudo defaults read com.apple.loginwindow LoginHook; echo; sudo crontab -l; }  2> /dev/null | open -ef
    This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. 
    Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step. 
    Step 3 
    Repeat with this line:
    { ls -A /e*/{cr,la,mach}* {,/}Lib*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la*; echo; crontab -l; } 2> /dev/null | open -ef
    Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting. 
    Step 4
    osascript -e 'tell application "System Events" to get name of login items' | open -ef
    Remember, Steps 1-4 are all copy-and-paste — no typing, except your password. Also remember to post the output. 
    You can then quit Terminal.

  • WHAT HAPPEN TO MY PHONE AFTER UPDATE IOS7.1 I CANT CALL OUT, WHAT HAPPEN TO MY PHONE AFTER UPDATE IOS7.1 I CANT CALL OUT

    WHAT HAPPEN TO MY PHONE AFTER UPDATE IOS7.1 I CANT CALL OUT, WHAT HAPPEN TO MY PHONE AFTER UPDATE IOS7.1 I CANT CALL OUT. only ppl can call me. what happen??can be fix?

    Hello, Mikimeikei. 
    Thank you for visiting Apple Support Communities.
    Here is an article I would recommend going through when experiencing issues making or receiving calls.
    iPhone: Troubleshooting issues making or receiving calls
    https://support.apple.com/kb/TS3406
    Cheers,
    Jason H.

  • Skype UI issues after updating to 6.10

    Hello,
    My skype auto updated. Now it has problems in UI. See the attached sreenshot. It contains all the error messages and text which is avaiable in skype desktop client
    Solved!
    Go to Solution.
    Attachments:
    Capture.JPG ‏69 KB

    Hi all i am facing Login interface problem after updating skype to latest version - 6.18
    I have seen the suggested solution to download the patch (index.html), i have downloaded it but where to place this file   ? Someone said to put index.html in C:\ProgramData\Skype\App\login but when i go to C:\ProgramData\Skype\   i didn't found 'App' folder. What to do?
    Please help!!!
    Attachments:
    ui_err.png ‏52 KB

  • HT4623 why i cant activate after update my ip 3gs

    why i cant activate after update3gs  to 6.0.1 , how can i acivated  ;(

    Generally this is a sign that the iPhone had previously been
    hacked/modified/jailbroken and the update relocked it to the
    original wireless carrier. If this is the case, only that wireless
    carrier can unlock your iPhone. You must contact them to see
    if they offer unlocking and if you qualify.
    Where did you acquire this iPhone?
    What wireless carrier did you use before this problem?
    Does the app Cydia appear on your iPhone?
    What does it say when you look at Settings=>General=>About=>Carrier?

  • Skype wont start after update on Android 4.0

    My skype wont start any more after update. When i click on icon appear the intro and close all times. Someone can help me?

    Try help here friend with skype support chat:
    http://www.skype.com/go/help.support.request
    OR
    https://support.microsoft.com/en-us/skype?language=en&locale=EN-US&oaspworkflow=start_1.0.0.0&needsl...

  • Cant login after wake from sleep

    In the last month I've noticed that sometimes when I wake my mac book pro (from a deep sleep?), I cant login. I enter my password and press enter and the textbox disables as if it is about to login but then nothing happens. It doesn't complete logging in. I cant press escape, I cant type in the password text box anymore, I cant click the button next to textbox. Nothing. I have to do a hard power off. I've cleared NVRAM. Which, consequently, when I do that, the mac book usually hangs at half of the progress bar on the black screen with the apple logo. I can only get the system back up by booting into safe mode and then restarting.
    Anyone have any idea how to trouble shoot or fix the login issue?
    Mikey

    Sorry to resurrect an old-ish thread but I'm having the EXACT same issue with my MacBook Pro.  I have all the latest OS updates applied..10.6.8 or whatever version is the latest as of 6/27/11.  I have taken it into the Apple store three times now...they've fixed permissions and run all the diagnostics and everything checks out 100%.  I have even done a complete wipe and reinstall of OSX, but it still locks up sometimes when clicking a user on the login screen.
    Have you been able to resolve the issue on your system?

  • Incorrect FileVault Password on login after update from OS X 10.7.4 to 10.7.5

    Today I encountered a minor bug in the update to OS X 10.7.5, found the solution and thought it might be helpful to others:
    After updating my MacMini 2007 (running OS X 10.7.4, with Server services active) to OS X 10.7.5,
    the machine did its normal-post-update restart routine.
    When prompted for the FileVault 2 password, the password I entered was incorrect. I tried several times without success.
    Then I entered the password using the keys of the US-keyboard layout instead of my the german keyboard layout that I actually have.
    Success.
    I live in germany, use a german keyboard, BUT have my system language in english. No clue if that's what confused OS X.
    Bad thing is that there is no indication whatsoever to make you aware of it, no country flag in the corner, no regular text field where you can see what you type.
    Anyway, it was only for the first restart, after that it was back to normal.
    Already posted an Apple Feedback.
    Maybe this post helps some people with the same problem.
    One more thing, the same happened here with the 10.7.4 Install ESD starting from external drive, when I tried to unlock my internal disk via Disk Utility. The password dialog sets the input source ALWAYS to US-keyboard layout, and on the top left corner it can't be changed... a bit annoying when you have millions of special characters in your disk password. But at least its shown in the top right corner... thats why I figured out the problem with my password after the update to 10.7.5, otherwise I would have been quite clueless and probably ended up erasing the whole disk.
    Cheers everyone!

    Hi!
    Thank you for posting this!
    I can verify this issue.
    Search for "us keyboard layout" and you can bring up a picture that will help you find special characters.

  • HT4623 my iphone cant  charge after updating it

    after updating my iphone ,it went to low battery after that it can't charge

    Use an certified Apple charging cable - either Apple brand or one approved by Apple.  Knock-off cables won't work with iOS 7.

  • Cant get past the login after update fail? (OSX 10.8.3)

    Hi!
    I have a big problem! This morning i tried to update my mac to the lastest version (10.8.3). Somthing made it to fail and i hade to reboot the system.
    Now the systems starts as before but when i type in my password and press enter, the screen flashes and i go back to the login again?
    I can start the system i Safe mode but not i normal mode.
    I have tried to repare the system with the disc tool but i still does not work.
    Any ideas?
    //VIktor
    Macbook pro mid 2009

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.  
    These steps are to be taken while booted in safe mode.
    Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects. 
    Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands. 
    Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply. 
    Launch the Terminal application in any of the following ways: 
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.) 
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. 
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid. 
    When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign. 
    Step 1 
    Triple-click the line of text below to select it:
    for k in /Sy*/L*/Ex*/{,.?}*.kext; do test -f "$k/Contents/Info.plist" && /usr/libexec/PlistBuddy -c "Print :CFBundleIdentifier" "$_" | egrep -qv "apple|Accusys|ArcMSR|ATTO|CalDigit|HighPoint|hp-fax|JMicron|print|SoftRAID|stex" && echo $k; done
    Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). Post the lines of output (if any) that appear below what you just entered. You can do that by copying and pasting as well. Omit the final line ending in “$”. No typing is involved in this step.
    Step 2 
    Repeat with this line:
    ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null
    Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting. 
    Step 3
    osascript -e 'tell application "System Events" to get name of every login item' 2> /dev/null 
    Remember, steps 1-3 are all copy-and-paste — no typing. Also remember to post the output. 
    You can then quit Terminal.

  • Cant login after latest security update!

    Just installed the latest security update (along with iTunes which I had put off for a while).
    When it was done downloading and installing, I chose "Restart". It did take forever on the white screen with the apple logo and spinning thingy. It then restarted the machine again and booted up until normal.
    EXCEPT - it now has a login box saying MAC OS X along the top with my machine name in little letters below it. I entered my usual username and password (only user on the machine) and it rumbles / shakes when I hit login and just stays like that waiting for another password... I've never had it ask for this before, yet now it wants a username/password and then wont accept it? (it did ask for my usual password before downloading the update).
    PLEASE help. Got a lot of important work that needs to be done tomorrow and here I am posting on my old iBook..

    Helped myself on this one...
    Restarted and held down Ctrl+S and it booted into my machine, bar the wall paper. Was DOG slow though for some reason.
    Restarted and it all appears as normal, except it is as slow as anything!!
    // Rant mode on...
    <edited by host>
    // Rant off.

  • [SOLVEDCannot login after update despite correct username and password

    I updated today after last updating two or three days ago and after a reboot, everything starts up fine and I'm left at the LightDM login screen.
    When I type in my password, it shows a black screen for a second or so and then goes back to the login screen. It doesn't show any errors or anything and I can't switch to a virtual terminal to try and see what's going on (though I am downloading the Arch Linux ISO since I lost my CD).
    My user shell is zsh and both /bin/zsh and /usr/bin/zsh are listed in /etc/shells (since I know another person had a similar-ish problem).
    I use openbox but I also tried logging into awesome and i3 sessions without any luck.
    EDIT: To anyone else having this problem, the solution here: https://bbs.archlinux.org/viewtopic.php … 3#p1326033 fixed it for me.
    Last edited by Arm-the-Homeless (2013-09-19 00:19:25)

    Yep.
    /var/log/lightdm/x-0-greeter.log
    ** (process:508): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
    (lightdm-gtk-greeter:510): GLib-CRITICAL **: g_shell_parse_argv: assertion `command_line != NULL' failed
    ** (lightdm-gtk-greeter:510): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory
    (lightdm-gtk-greeter:510): Gdk-CRITICAL **: gdk_device_get_source: assertion `GDK_IS_DEVICE (device)' failed
    /var/log/lightdm.log
    [+0.06s] DEBUG: Logging to /var/log/lightdm/lightdm.log
    [+0.06s] DEBUG: Starting Light Display Manager 1.6.1, UID=0 PID=224
    [+0.06s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
    [+0.06s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
    [+0.10s] DEBUG: Registered seat module xlocal
    [+0.10s] DEBUG: Registered seat module xremote
    [+0.10s] DEBUG: Adding default seat
    [+0.10s] DEBUG: Starting seat
    [+0.10s] DEBUG: Starting new display for greeter
    [+0.10s] DEBUG: Starting local X display
    [+0.11s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
    [+0.11s] DEBUG: Using VT 7
    [+0.11s] DEBUG: Activating VT 7
    [+0.13s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+0.20s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+0.20s] DEBUG: Launching X Server
    [+0.20s] DEBUG: Launching process 240: /usr/sbin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+0.20s] DEBUG: Waiting for ready signal from X server :0
    [+0.25s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
    [+0.25s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
    [+8.30s] DEBUG: Got signal 10 from process 240
    [+8.30s] DEBUG: Got signal from X server :0
    [+8.30s] DEBUG: Connecting to XServer :0
    [+8.31s] DEBUG: Starting greeter
    [+8.31s] DEBUG: Started session 371 with service 'lightdm-greeter', username 'lightdm'
    [+8.48s] DEBUG: Session 371 authentication complete with return value 0: Success
    [+8.48s] DEBUG: Greeter authorized
    [+8.48s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+8.52s] DEBUG: Session 371 running command /usr/sbin/lightdm-gtk-greeter
    [+8.52s] DEBUG: org.freedesktop.Accounts does not exist, falling back to passwd file
    [+9.68s] DEBUG: Greeter connected version=1.6.1
    [+9.68s] DEBUG: Greeter connected, display is ready
    [+9.68s] DEBUG: New display ready, switching to it
    [+9.68s] DEBUG: Activating VT 7
    [+12.34s] DEBUG: Greeter start authentication for andy
    [+12.34s] DEBUG: Started session 479 with service 'lightdm', username 'andy'
    [+12.81s] DEBUG: Session 479 got 1 message(s) from PAM
    [+12.81s] DEBUG: Prompt greeter with 1 message(s)
    [+18.37s] DEBUG: Continue authentication
    [+18.41s] DEBUG: Session 479 authentication complete with return value 0: Success
    [+18.41s] DEBUG: Authenticate result for user andy: Success
    [+18.41s] DEBUG: User andy authorized
    [+18.46s] DEBUG: Greeter requests session openbox
    [+18.46s] DEBUG: Using session openbox
    [+18.46s] DEBUG: Stopping greeter
    [+18.46s] DEBUG: Session 371: Sending SIGTERM
    [+18.48s] DEBUG: Greeter closed communication channel
    [+18.48s] DEBUG: Session 371 exited with return value 0
    [+18.48s] DEBUG: Greeter quit
    [+18.48s] DEBUG: Dropping privileges to uid 1000
    [+18.48s] DEBUG: Calling setresgid
    [+18.48s] DEBUG: Calling setresuid
    [+18.51s] DEBUG: Restoring privileges
    [+18.51s] DEBUG: Calling setresuid
    [+18.51s] DEBUG: Calling setresgid
    [+18.51s] DEBUG: Dropping privileges to uid 1000
    [+18.51s] DEBUG: Calling setresgid
    [+18.51s] DEBUG: Calling setresuid
    [+18.51s] DEBUG: Writing /home/andy/.dmrc
    [+18.56s] DEBUG: Restoring privileges
    [+18.56s] DEBUG: Calling setresuid
    [+18.56s] DEBUG: Calling setresgid
    [+18.63s] DEBUG: Starting session openbox as user andy
    [+18.63s] DEBUG: Session 479 running command /etc/lightdm/xsession /usr/bin/openbox-session
    [+18.71s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
    [+18.74s] DEBUG: Session 479 exited with return value 0
    [+18.74s] DEBUG: User session quit
    [+18.74s] DEBUG: Stopping display
    [+18.74s] DEBUG: Sending signal 15 to process 240
    [+19.08s] DEBUG: Process 240 exited with return value 0
    [+19.08s] DEBUG: X server stopped
    [+19.08s] DEBUG: Removing X server authority /run/lightdm/root/:0
    [+19.08s] DEBUG: Releasing VT 7
    [+19.08s] DEBUG: Display server stopped
    [+19.08s] DEBUG: Switching to greeter
    [+19.08s] DEBUG: Starting new display for greeter
    [+19.08s] DEBUG: Starting local X display
    [+19.08s] DEBUG: Using VT 7
    [+19.08s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+19.08s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+19.08s] DEBUG: Launching X Server
    [+19.08s] DEBUG: Launching process 502: /usr/sbin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+19.08s] DEBUG: Waiting for ready signal from X server :0
    [+19.30s] DEBUG: Got signal 10 from process 502
    [+19.30s] DEBUG: Got signal from X server :0
    [+19.30s] DEBUG: Connecting to XServer :0
    [+19.31s] DEBUG: Starting greeter
    [+19.31s] DEBUG: Started session 508 with service 'lightdm-greeter', username 'lightdm'
    [+19.31s] DEBUG: Session 508 authentication complete with return value 0: Success
    [+19.31s] DEBUG: Greeter authorized
    [+19.31s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+19.31s] DEBUG: Session 508 running command /usr/sbin/lightdm-gtk-greeter
    [+19.39s] DEBUG: Greeter connected version=1.6.1
    [+19.39s] DEBUG: Greeter connected, display is ready
    [+19.39s] DEBUG: New display ready, switching to it
    [+19.39s] DEBUG: Activating VT 7
    [+19.52s] DEBUG: Greeter start authentication for andy
    [+19.52s] DEBUG: Started session 527 with service 'lightdm', username 'andy'
    [+19.53s] DEBUG: Session 527 got 1 message(s) from PAM
    [+19.53s] DEBUG: Prompt greeter with 1 message(s)
    [+28.65s] DEBUG: Got signal 15 from process 1
    [+28.75s] DEBUG: Caught Terminated signal, shutting down
    [+28.75s] DEBUG: Stopping display manager
    [+28.75s] DEBUG: Stopping seat
    [+28.75s] DEBUG: Stopping display
    [+28.75s] DEBUG: Session 508: Sending SIGTERM
    [+28.75s] DEBUG: Greeter closed communication channel
    [+28.75s] DEBUG: Session 508 exited with return value 0
    [+28.75s] DEBUG: Greeter quit
    [+28.75s] DEBUG: Sending signal 15 to process 502
    [+28.75s] DEBUG: Session 527 terminated with signal 15
    [+28.75s] DEBUG: Session 527 failed during authentication
    [+28.75s] DEBUG: Authenticate result for user andy: Authentication stopped before completion
    EDIT: As far as the ConsoleKit question goes, no. My xinitrc is just `exec openbox-session` and ConsoleKit is not referenced at all in my openbox autostart/environment files. Plus, that wouldn't explain why this is the first boot to get this error.
    Last edited by Arm-the-Homeless (2013-09-18 01:31:29)

  • [SOLVED] Plasma workspace crash (SIGSEGV) at login after update

    Hi all,
    after I updated via pacman -Syu last weekend and rebooted my system I got a plasma workspace crash at the login which happens ever since.
    I get:
    The application Plasma Workspace (plasma) crashed and caused the signal 11 (SIGSEGV).
    Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.
    and the following bug report:
    This backtrace appears to be of no use.
    This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    [Thread debugging using libthread_db enabled]
    [New Thread 0xb496f720 (LWP 3637)]
    [New Thread 0xa928bb70 (LWP 3638)]
    0xb8054424 in __kernel_vsyscall ()
    [Current thread is 0 (LWP 3637)]
    Thread 2 (Thread 0xa928bb70 (LWP 3638)):
    #0 0xb8054424 in __kernel_vsyscall ()
    #1 0xb635ac55 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
    #2 0xb63d83e7 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
    #3 0xa95709f2 in RenderThread::run () from /usr/lib/kde4/plasma_wallpaper_image.so
    #4 0xb63d73be in ?? () from /usr/lib/libQtCore.so.4
    #5 0xb63566bc in start_thread () from /lib/libpthread.so.0
    #6 0xb61a2ffe in clone () from /lib/libc.so.6
    Thread 1 (Thread 0xb496f720 (LWP 3637)):
    #0 0xb8054424 in __kernel_vsyscall ()
    #1 0xb616cb26 in nanosleep () from /lib/libc.so.6
    #2 0xb616c911 in sleep () from /lib/libc.so.6
    #3 0xb76cce12 in KCrash::startDrKonqi () from /usr/lib/libkdeui.so.5
    #4 0xb76cda84 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
    #5 <signal handler called>
    #6 0xb645fb57 in QIODevice::isOpen () from /usr/lib/libQtCore.so.4
    #7 0xb6809ee7 in QImageReader::supportedImageFormats () from /usr/lib/libQtGui.so.4
    #8 0xb6762e06 in ?? () from /usr/lib/libQtGui.so.4
    #9 0xb6763fbc in ?? () from /usr/lib/libQtGui.so.4
    #10 0xb7b5940f in KIO::pasteActionText () from /usr/lib/libkio.so.5
    #11 0xa9525406 in FolderView::createActions () from /usr/lib/kde4/plasma_applet_folderview.so
    #12 0xa952adda in FolderView::init () from /usr/lib/kde4/plasma_applet_folderview.so
    #13 0xb7ffd6d7 in DesktopCorona::saveDefaultSetup () from /usr/lib/libkdeinit4_plasma.so
    #14 0xb7ffdf18 in DesktopCorona::qt_metacall () from /usr/lib/libkdeinit4_plasma.so
    #15 0xb64de831 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
    #16 0xb64df4a2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
    #17 0xb64e3967 in ?? () from /usr/lib/libQtCore.so.4
    #18 0xb64e3a7c in ?? () from /usr/lib/libQtCore.so.4
    #19 0xb64d879f in QObject::event () from /usr/lib/libQtCore.so.4
    #20 0xb674d6ac in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
    #21 0xb6754e44 in QApplication::notify () from /usr/lib/libQtGui.so.4
    #22 0xb7656bfa in KApplication::notify () from /usr/lib/libkdeui.so.5
    #23 0xb64c874b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
    #24 0xb64f6a26 in ?? () from /usr/lib/libQtCore.so.4
    #25 0xb64f3ad0 in ?? () from /usr/lib/libQtCore.so.4
    #26 0xb4db0288 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
    #27 0xb4db3878 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
    #28 0xb4db39ea in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
    #29 0xb64f3a1c in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
    #30 0xb67ec5c5 in ?? () from /usr/lib/libQtGui.so.4
    #31 0xb64c6cd9 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
    #32 0xb64c7122 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
    #33 0xb64c949f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
    #34 0xb674d527 in QApplication::exec () from /usr/lib/libQtGui.so.4
    #35 0xb8003e16 in kdemain () from /usr/lib/libkdeinit4_plasma.so
    #36 0x0804876b in _start ()
    #0 0xb8054424 in __kernel_vsyscall ()
    The packages I've updated befor this bug appeared are:
    [2009-05-24 09:55] upgraded dbus-core (1.2.4.6permissive-1 -> 1.2.14-1)
    [2009-05-24 09:55] upgraded dbus (1.2.4.6permissive-1 -> 1.2.14-1)
    [2009-05-24 09:55] upgraded ppp (2.4.4-7 -> 2.4.4-8)
    [2009-05-24 09:55]
    [2009-05-24 09:55] > Qt 4.5.1
    [2009-05-24 09:55]
    [2009-05-24 09:55] Prefix: /usr
    [2009-05-24 09:55]
    [2009-05-24 09:55] > ATTENTION
    [2009-05-24 09:55] Some components are split into separate packages:
    [2009-05-24 09:55]
    [2009-05-24 09:55] qtmod : Base libraries and tools
    [2009-05-24 09:55] qtmod-doc : Documentation
    [2009-05-24 09:55] qtmod-demos : Demos & Examples
    [2009-05-24 09:55] qtmod-tools : Development Tools (Assistant, Designer, Linguist)
    [2009-05-24 09:55]
    [2009-05-24 09:55] upgraded qtmod (4.5.1-2 -> 4.5.1-3)
    However I've downgraded all of them back but the crash remains. I also removed qtmod and installed qt from the arch repositories but still no effect on the bug. Also tried to rename the .kde4/ folder to make KDE generating a new plain folder but doesn't help with the problem. Even complete removal of KDEmod and new installation didn't make a change.
    I hope someone can help cause I'm runnig out of ideas what to try next.
    thanks, potzi
    Last edited by potzi (2009-06-03 22:43:52)

    You can find old packages here:
    http://arm.kh.nu/
    That repo has saved my life a number of times. Especially with BLUETOOTH GRRRR.
    As for getting all your old settings back, I didn't investigate this enough because i only have opensuse for curiosity as I think they do some really great stuff.
    Basically I hadn't yet isolated what was causing the problems before I gave up because every time I tried to merge my old settings in to the new user account, I recreated the problem. No logical (subjective term obviously) separation of what to merge and what not to merge worked. So I gave up and just did everything manually. Sorry that I couldn't be more helpful.
    Last edited by tim (2009-05-27 23:59:53)

  • Skype credit gone after update?!

    Hello!
    About a week ago I got an update for Skype on my iPhone and iPad. As usual, I updated. The next day I wanted to call my family in Germany over Skype on my phone and was told I have no credit left. How is that possible?? I KNOW I had enough credit before the update!!! Please help?

    assuming that you already double-checked if you are using the correct username (if in case you have more than one account), try to sign out then sign in again.  That procedure is different that just closing the Skype software, then running it again.
    If your credits still don'tshow, then you may need to contact customer service regarding that matter. 
    https://support.skype.com/en/faq/FA1170/how-can-i-contact-skype-customer-service
    IF YOU FOUND OUR POST USEFUL THEN PLEASE GIVE "KUDOS". IF IT HELPED TO FIX YOUR ISSUE PLEASE MARK IT AS A "SOLUTION" TO HELP OTHERS. THANKS!
    ALTERNATIVE SKYPE DOWNLOAD LINKS | HOW TO RECORD SKYPE VIDEO CALLS | HOW TO HANDLE SUSPICIOS CALLS AND MESSAGES

  • After updating to ios5 i cant find any of my tones that i purchased.

    they show in itunes but cant get them to the phone. is anyone else having this problem? did anyone else find out how to get around this. have like $20.00 in ring tones i'd hate to have to buy them again.

    Where were your documents before you updated?
    Your profile under your post says you are using Mountain Lion which is not an update to Lion.

Maybe you are looking for