Gdm not working on Vaio SVS13A

Hi to all,
I just managed to install and run archlinux on a brand new VAIO SVS13A with Insyde H2O EFI, core i7 and intel HD4000 graphics card. The notebook also has a discrete nvidia graphics card.
I was able to install Xorg and startx shows the minimal xorg environment so it should work fine but when I try to run gdm only a black screen appears with the clock that tells you to wait....
What can be wrong? I tried to look for error logs but it doesn't seem to show errors, the last lines are:
intel(0): Modeline "1600x900"x0.0 100.22 1600 ......
AIGLX: Suspending AIGLX clients for vt switch
I run the notebook with the hw switch on "stamina" mode so the discrete graphics card should be off. Maybe I can use the discrete card for getting things to work?
Thanks

Trying to startx from normal user only a black screen appears, even if Xorg.log doesn't have any errors, and only these warnings:
(WW) The directory /usr/share/fonts/OTF/ does not exist
(WW) 'fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/"
(WW) 'fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/"
But I can startx from root and the warnings are the same
Last edited by Mocco (2012-07-21 09:14:10)

Similar Messages

Restore Factory Setings - F10 Not Working on Vaio VPCF232FX/B

Like i said in the Title post. I'm up to date with all drivers. I do a back-up on my flash driver, also the Recovery partition are intact i never touch it. Isn't first time when i make a restore on factory settings, but its first time when not work. I shut down/restart the vaio , when the vaio logo appear i press F10 ( and much more combinations that i found on the web ) and i get an error. I try to fix that error but not effect. ( CLICK TO SEE IMAGE ). I read lot's of post/discussion and still have the problem. i think the problem is came from Vaio care last update because in the past i won't get any problem. I try to install a new windows and an older Vaio Care but the problem won't fix. Now i have 2 Windows 7 Installed on my Vaio grate to Sony. HELP !

If you already followed the steps on How to recover the computer to the originalfactory condition using the F10 key then there might be a possibility that the recovery partition is corrupted already. You may need to purchase the recovery disc for your VAIO computer. You can purchase recovery discs from Sony Parts and Accessories:
If my post answers your question, please mark it as "Accept as Solution"
http://bit.ly/Win-4K

Bluetooth AR3011 not working SONY VAIO VPCA2S1E

Hello,
my problem is that the built-in bluetooth does not work, however it works on ubuntu. (It did not work there when I installed it either. But I am not using it anyway, just checked if it is available now.)
So I checked which hardware I have and it is Atheros AR3011.
The necessary firmware is ath3k-1.fw, as stated here: http://wireless.kernel.org/en/users/Drivers/ath3k
I have found an aur package for it, but it wouldn't install, since it is installed already. OK, checked it out via package file list, the linuwfirmware has it, which is installed.
Do you know what I could do to make it work?
I am new to kernel or drivers so any -seemingly stupid thing- basic thing would be of help.
(I don't even know if it loaded, tried using modprobe too, but I think without any success, didn't get any output from it - and I am not sure how to use it.)
Thanks,
B

Hi szebenyib
I have a ASUS Bluetooth USB dongle (USB-BT211) that uses the same Atheros AR3011 chip inside.
I've made this adapter work after this steps:
Be sure that your modules section on rc.conf don't load "automatically" the ath3k module.
Make sure that you have the ath3k module in the kernel ( ls -la /lib/firmware/ath* )(Probably you have if you are using a not too old kernel)
Then, load the module:
sudo moprobe ath3k
And, finally, insert the Bluetooth dongle.
Hummm, just after writing this I realized that you don't have a way to remove/insert. Hahahah
So you can try to remove the ath3k module after booting:
sudo modprobe -r ath3k
and after that, load the module again and see if it works.
If this don't work, paste here the "dmesg | tail" output and your kernel version. I'm not an expert in this thing but we can try some others way. Haha
By the way, I have installed the ath3k package from AUR, but I don't think that is necessary either. I will remove it and see if it works next boot.
Cheers,
Gabriel

Sony Vaio Webcam Not Working in windows 7

I have a Sony Vaio Model (VGN-CR507E) and I have recently put on the Windows 7 Evaluation Copy, Build 7100.
Everything seems to be in good order except for the Webcam. When I try to run msn, skype or any other webcam related programs it says that the webcam is in use by another program.
When I go to my Device Manager It says that the USB Video Device is installed and fully updated.
If someone could give me a step by step guide on how to fix this problem it would be much appreciated.
Thanks.

Hello,
First you might go to Device Manager, right click your hardware device in the list and select Update Driver Software; then click Search automatically for updated driver software.
Note: Drivers on the Windows Update site are directly provided by hardware manufacturers. Microsoft tests drivers in various environments before they are published; however, we cannot guarantee all drivers will work on all hardware platforms as there are too many different models, although their hardware ID are the same as the standard version. In some cases, due to hardware modifications by different manufacturers, the driver updates may cause some error.
If it does not work on your issue, I'd suggest you installing the Vista driver in Compatibility mode. Remove and rescan that hardware device in Device Manager, right-click on the driver executable/installer file -> Properties and select the Compatibility tab; click the checkbox before Run this program in Compatibility mode for option and select Windows Vista in the list-down box; then try installing the device driver via Run as administrator. In addition, you can use the Windows XP driver for testing.
Meanwhile, please understand that Windows 7 is a new operating system and whole driverstore has been reprogrammed; you might wait or push the device manufacturer to upgrade its driver. Thanks for your time and understanding!
For more details, please look at the first Sticky thread at the top of this forum.
What can I do if my hardware does not work?
This will give you some guidelines.
Good Luck!
Andy

Sony Vaio Pro 13.3 Touch: Touch screen not working

Hi, The touch screen for my Sony Vaio Pro 13 Touch suddenly stopped working two days ago and I have no idea how to fix it. I didn't install anything new before it stopped working, and I tried to install all the new drivers on the VAIO update but it still didn't work. I thought it might be because of Windows so I updated to Windows 8.1 today and it still does not work. On the PC info it even says" Pen abd touch: No pen or touch input is available for this display". but this laptop is supposed to have touch capability and it has been working up until now. Please help! My model number is SVP13215CDB. Do I need to install or update my driver?

Hi FlyingTortoise,
Was there any changes prior to touch screen not working? Like installing software or hardware? If not, then try using windows system restore to restore back to a date that you know when it was working. If that still does not resolve issue. Then we may have to put the unit back to factory condition to eliminate software related before servicing the unit for hardware.
Nick--

Upgrading to Firefox 17 on ubuntu linux 10.04 caused my xmodmap remapped keys to not work in Firefox

After upgrading from Firefox 16 (16.0.2+build1-0ubuntu0.10.04.1) to Firefox 17 (17.0+build2-0ubuntu0.10.04.1) on 22-November-2012 I no longer can use an xmodmap remapped F key in Firefox. It still works in other gnome programs but pressing the new F key anywhere in Firefox 17 produces no action. I even had to use the gedit program in order to type all this before copying it into the Ask a Question form.
Here is my situation: I use Ubuntu Linux 10.04 LTS on a circa 2004 Sony Vaio notebook pc. I've been using linux on it dating back to Ubuntu 8.04. When I got the used pc the "F" key on the keyboard was broken off. I programmed the .xmodmaprc file in my home folder to initiate the "Keycode 133 = F" command on startup in order to remap the missing key to the unused Windows Logo key on the lower left of the keyboard. This has worked flawlessly for over four years. In all prior versions of Firefox going back to whatever version was included in Ubuntu 8.04 I have had no trouble using this key through all Firefox upgrades until now.
On the morning of 22-Nov-2012 the Update Manager notified me of an upgrade to the following packages as shown in the history log of Synaptic Package Manager:
Commit Log for Thu Nov 22 09:20:16 2012
Upgraded the following packages:
firefox (16.0.2+build1-0ubuntu0.10.04.1) to 17.0+build2-0ubuntu0.10.04.1
firefox-branding (16.0.2+build1-0ubuntu0.10.04.1) to 17.0+build2-0ubuntu0.10.04.1
firefox-gnome-support (16.0.2+build1-0ubuntu0.10.04.1) to 17.0+build2-0ubuntu0.10.04.1
firefox-locale-en (16.0.2+build1-0ubuntu0.10.04.1) to 17.0+build2-0ubuntu0.10.04.1
ubufox (2.1.1-0ubuntu0.10.04.1) to 2.6-0ubuntu0.10.04.1
xul-ext-ubufox (2.1.1-0ubuntu0.10.04.1) to 2.6-0ubuntu0.10.04.1
After performing the upgrade and restarting Firefox I noticed I was no longer able to use my remapped F key at all. I checked other programs and it worked OK so I know it's a Firefox 17 problem only. I tried reinstalling all the packages again with no results. I even went so far as to perform a Reset Firefox in Help-->Troubleshooting Information to try and get it working. All this ended up doing was removing all add-on extensions and changing some of my settings in Preferences but I'm not positive of any changes beyond the Location Bar setting in Privacy changing from Nothing to History and proxy setting going from No to Auto-Detect.
The only solution that has worked to fix this problem is uninstalling Firefox 17 and reinstalling Firefox 16 using a downloaded firefox_16.0.2+build1-0ubuntu0.10.04.1_i386.deb file from Ubuntu as Firefox 16 no longer shows up in the main repository since 22-November-2012. The only versions available for a Force Version in Synaptic are 3.6 and 17 now. After downgrading only the firefox package shows version 16.0.2, all other components I listed above stayed at version 17. I don't know if this will cause any other problems but so far nothing bad has happened.
After I submit this question I will be downgrading again to Firefox 16 until this problem can be solved.
Edit: noted the following Language Packs were disabled on restart after downgrading to Firefox 16 again:
English (GB) Language Pack 17.0
English (South Africa) Language Pack 17.0
If my memory is correct I only remember having an English (GB) Language Pack in all prior versions of Firefox. Firefox 17 was the first time I noticed a English (South Africa) Language Pack installed. It's possible the problem with xmodmap keys not functioning in Firefox 17 could be related to something in these two packs.

Ok I tested a bunch of different Firefoxes on my pos linux box.
'''''Worked with xmodmap:'''''
Vanilla 16.0.2,
Vanilla 16.0B6,
Ubuntu Firefox 16.0.2 (16.0.2+build1-0ubuntu0.10.04.1)
'''''Did Not Work with xmodmap:'''''
Vanilla 17.0.1,
Ubuntu Firefox 17.0.1 (17.0+build2-0ubuntu0.10.04.1)
I have an old Dell Dimension 2400 I plan to use as a replacement for the Sony Vaio when it pops. I've held out as long as possible because it lacks a pci or usb wifi and I really didn't want to run 50 feet of cat5 up a flight of stairs to it. [as i type this i think i remember where a linksys stick for it might be]. Yes I guess it's about time I just do that.
Don't laugh but the reason I held off adding a simple usb keyboard was just lack of space in my tiny bedroom. My setup is on two tray tables side-by-side. Sony Vaio is on left one, my lcd monitor and mouse are on the other. I barely have room to put a cup of coffee on the one with monitor and mouse let alone a full size usb keyboard lol.
Anyway thank you again for all your help.

HT1349 iTunes and Windows 8 will not work!!! Please help!!!

I just purchased a new sony vaio laptop computer with Window's 8 and I have uninstalled and installed itunes over 5 times and it will not work. When attempting to open it, a box pops up that says "ITunes has stopped working: A problems caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.". I have motified the compatibility under each selection, I have changed my securing options and nothing works. I am overwhelmed and frustrated with this issue!! Please help how to make this work, so disappointed with itunes!!!

I have the same problem!

After Security updation of Windows 7 in Boot Camp (Mac Book Pro with Retina Display) on 13-Nov-2013, Windows 7 Desktop Gadgets are not working properly.

After Security updation of Windows 7 in Boot Camp (Mac Book Pro with Retina Display) on 13-Nov-2013, Windows 7 Desktop Gadgets are not working properly.
This is boot camp problem, because in other normal notebooks (e.g. SONY VAIO, Lenovo with Windows 7) the gadgets are working normally.
I am attaching the screen shot of Desktop Gadgets and Security updates of Windows 7.
Kindly solve this issue ASAP.
Shailendra Gupta
<edited by host>

You are not addressing Apple, but a community of unpaid volunteers. So ASAP won't cut it. Also, you should refrain from posting personal information (like your email address) in the body of your comments, as this is part of the community usage guidelines.
Have you reinstalled the latest Boot Camp Windows 7 drivers, just in case Microsoft overwrote some of them during the Windows 7 security update?
If you want to communicate issues with Apple about Boot Camp and OS X, click on the link. Just don't hold your breath on receiving a response.

[solved] keyboard not working correctly on vc/1

the behaviour is quite odd.
when i hit ctrl-alt-f1, and switch to the first virtual console, trying to login, or even type doesnt work quite as it should.
example, i try to login: this is what i get:
lappy login: elragn
password:
when the user name should be eldragon, if i type each letter at a time, until i get it to work, i can type correctly, and its not always the same letters that dont work. of course, the password comes in blank, and sometimes, when i get it all right, i can login, and the effect contiues
this is not a hardware issue, other virtual consoles work ok, and the keyboard works fine under Xorg.
so, what could be wrong with this vc? anyone got a clue? ive searched the wiki, bug reports, google, and the forums (not in this order) for an answer but i came up empty.
PD. if im posting in the wrong forum, please move it where it should go
Last edited by eldragon (2009-03-22 18:08:54)

Hi,
Since the problem is in the vc's, and the keymap is loaded "pre Xorg", I'd start by doing some tests there.
I'm still a learner myself, so this might not work, or it might, either way, you've got nothing to loose
First of all check logs for errors, maybe something pops out.
If no errors on logs, than here's what I would do if I were you:
(backup /etc/rc.conf , /etc/inittab , /etc/locale.gen to some directory)
1. Let's start by isolating the problem by not going to gdm->gnome automatically, so you can test vc's themselfs more efficiently and quicker.
take out gdm from the DAEMONS line in /etc/rc.conf (something like this)
DAEMONS=(syslog-ng network netfs crond alsa hal fam)
2. let your /etc/inittab be like you have in this section (id:3)
## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:
and comment everything here:
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null
3. do you use a non-us keyboard?
check your rc.conf for the 1st lines, mainly your KEYMAP
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="your.timezone.here"
KEYMAP="your.keymap.here"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
confirm that your keymap exists in /usr/share/kbd/keymaps and double confirm the name is right, example:
for US keyboard the file is 'us.map.gz' so KEYMAP="us" (take out .map.gz); in case your keyboard is not US, check the name, as some have more letters than others
(usually /usr/share/kbd/keymaps/i386/qwerty unless your pc is not i386 or qwerty ofc )
4. reboot pc.
You'll be in vc/1.
Now, instead of jumping in consoles with ctr-alt-Fx, try jumping just with Alt+Fx. (if it doesn't work, go ctrl+alt+fx ofc)
Do Alt+F2 and start typing as normal, anything and manything at any speed and confirm is good. Don't press enter. Just testing keystrokes.
Do Alt+F3, Alt+F4, Alt+F5 and test the same for each vc.
Now for the final and problematic one, go Alt+F1 and test.
If it's good, then probably your problem is on X/gdm/gnome or anything that is loading after vc, or if you changed your keymap, then that was the faulty thing.
If it's not good, keep on reading
5. don't enter in vc/1, rather jump to vc/2 or 3 or something and enter as root, let's edit your /etc/rc.conf again.
copy to a piece of paper your 1st options in case they are different from below:
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="your.timezone.here"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
basicly is trying to put it to a default state. Put your options just like they are above, except TIMEZONE, you can put yours, I don't remember default one.
Reboot and test again just like in step 4.
If it doesn't work, you might give a look at /etc/locale.gen and just uncomment these 2 lines:
#en_SG.UTF-8 UTF-8
#en_SG ISO-8859-1
en_US.UTF-8 UTF-8
en_US ISO-8859-1
#en_ZA.UTF-8 UTF-8
#en_ZA ISO-8859-1
leave every other line commented. in case you had some of your own uncommented, copy to a paper wich ones were, and comment them.
write in console
locale-gen
let it end generating the locales, reboot, and step 4 again.
6. Still not working, let's try to put things bad proposedly! Change your KEYMAP to another one, if qwerty, just choose another qwerty language, all letters should be on same place, except for punctuation ofc.
Reboot and try again as step 4.
Still not working? Change the LOCALE and keep your wrong qwerty keyboard. (LOCALE will probably change some words, like password to it's LOCALE language, etc).
Reboot and try again as step 4.
Still not working? ok, final attempt, change back your LOCALE and your KEYMAP to the values you had before, the correct ones.
Reboot and try again as step 4.
7. If still not working, well, for now I don't know much more. Take in consideration that the boot process goes through several steps, the error might be in one of those steps. One last thing you can try, altho I think it works just in DE/WM modes, I've read in some posts (here or not, can't remember) that by pressing Ctrl-Alt-K you can change your keyboard layout, assuming you have a second one, and use them for different things, I think the example I read on the post was something like, you wanna code in english but talk in irc in russian for example.
I kinda doubt it works, but if it also activates in vc's mode, then you could have pressed it accidently (like when doing ctrl-alt-fx, your finger slipped ).
press ctrl-alt-k, type a few letters, press ctrl-alt-k again, type more letters, and you'll see if it does something or not.
Again, just try, you got nothing to loose
One thing I noticed, is that when trying to put some characters on vc as username, it acts as delete, some even erase the all line in one go and some don't do nothing, some of the characters were # @ £ §.
8. Since it didn't work, let's put everything as it was.
8.1. go to /etc/inittab and put like this:
(comment id:3, uncomment id:5 // uncomment x:5:...gdm...)
## Only one of the following two lines can be uncommented!
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null
8.2. edit /etc/rc.conf and DON'T put back the gdm on daemons line.
Alter the 1st lines ranging from LOCALE to USECOLOR to the ones you copied to a paper.
8.3. comment/uncomment the locales on /etc/locale.gen as you have on paper and run in console
locale-gen
8.4. you're set, reboot and you're on gdm->gnome again. (still no vc/1 working tho )
note: in your initial /etc/iniitab you had id:3 uncommented and gdm on daemons, so you would go automatically to gdm as you started your pc, but, what if something happens and you need to go to another mode before gdm runs? you couldn't do it easily with gdm on daemons.
If you put it like I wrote above, when you turn on the pc, it's the same, you go automatically to the gdm, but, in case something happens, you can always go to another mode before gdm runs, by doing the following (read here on wiki or foruns, will put link when I find it)
Pc reboots and you're on GRUB, press 'e', choose the kernel and press 'e' again, go to the end of the line where it says 'ro', and add a 3 to the end, to look like this 'ro 3', press 'b' (boot) and you're on mode 3 without going to gdm
But ofc, this is just a choice, if you prefer to have as you had it, by all means, just put gdm on daemons line, and your /etc/inittab as initially, that's the beauty of Linux, it's to your fit
Good Luck!

DPMS/Screen blanking not working in gnome-shell

The title pretty much sums it up. I've tried setting screen blanking in gnome-control-center->power, but it doesn't seem to work. However DPMS has worked in pretty much every other WM I've tried by default.
I've installed gnome-shell and gnome-control-center. Not using gdm.
I've tried 'xset -dpms' which apparently should've helped at least in earlier gnome releases, but it makes no difference on my system.
Any ideas what could be causing this?

\hbar wrote:
Could you be more specific so as to what does not work? Is it the automatic screen blanking, or just plain screen blanking? If you run
xset dpms force off
does the screen turn off?
I want my screen to turn off automatically when system is not in use, so I've enabled the automatic screen blanking from gnome settings.
That command turns my monitor off fine, but doesn't happen automatically when system is idle like it does in other WMs
\hbar wrote:Also 'xset -dpms' disables dpms, so I don't understand how that would help.
Apparently there's been an issue where xserver's dpms settings get in gnome's way, and disabling dpms with xset has helped some people in arch forums and others. Although if I'm not mistaken that issue should be fixed already.

Keyboard, touchpad and assist button not working

Hello, I have a touchscreen VAIO laptop on which the keyboard, touchpad and assist button are not working. The touckscreen keyboard works, and if a plug in a bluetooth USB mouse it works too. Te problem as I said before is with the touchpad and physical keyboard, which don't work even in the BIOS inicialization. I tried the assist button but it doesn't work neither. Instead of accessing VAIO Care, it turns the computer on. I also tried to restore the system and update drives, but with no success. The problem started with some bubbles on the screen that freezed the computer. I restarted it and only the keyboard was working (the light under it was on) but the display was off. Then I restarted it again, and again and now only the dispaly is on (I can access Windows 8 via touchscreen), and the rest of it is off (not working, leds off, etc).

Hi Damares,
Thank you for considering Sony Community!
I am sorry to hear your issues but it seems that you are experience a combination of hardware and software issues. First, the Assist button should work when you press it. Try to press Assist button again while the unit is off (just in case you were trying to use it while the unit is off).
Power cycle the unit - Remove the battery and all peripherals -> press and hold the power button for 5 seconds OR, if the battery is not removable, remove all peripherals-> look for a battery off button on the bottom of the laptop -> push the button for 5 seconds.
Test again the unit. If this won't push through then we highly suggest to visit Sony's Authorized Service Center in your area.
For further assistance, we kindly recommend visiting our Sony Global Web site for information on contacting the Sony Support Center in your region at http://www.sony.net/SonyInfo/Support/.
Best regards,
Vincent
If my post answers your question, please mark it as "Accept as Solution"

Running syndaemon at startup in .xinitrc not working

I'm trying to run syndaemon so I can set my touchpad to turn off when typing. I'm using the command:
syndaemon -i 1 -d
If I issue this after logging into Gnome in a terminal, it works fine and I can see the syndaemon process running in System Monitor.
But if I add the command to my .xinitrc it doesn't work. I followed the instructions in the wiki, to no avail. I also found that another command I wanted to issue in .xinitrc ("xset -dpms") to solve a different problem with gnome-power-manager wasn't working either. I got that to work by issuing the command as a startup program in Gnome's Starup Applications gui.
Anyway, I guess I could do the same thing with syndaemon, but I'm wondering why it's not working in .xinitrc, as it's supposed to. Thanks for any help.

Okay, I tried slim and it did execute the xset and syndaemon commands from .xinitrc.
Then in a Google search this old post from the Arch forums turned up, from way back in 2003: http://bbs.archlinux.org/viewtopic.php?id=726. At the end Xentac explains that GDM does in fact only look to .xinitrc for what window manger to start and ignores everything else (which of course is also what Wilco says above).
Xentac wrote:
If you choose the option to load fluxbox, that's all it will do. It won't load anything in .xinitrc or .xsession.
There should be a Session option in gdm. Add fluxbox to the end of your .xsession (so it should now look exactly like your .xinitrc) and choose the Session option in gdm.
Gdm assumes that your window manager will do all the auto-loading stuff (like gnome and kde do) so if it doesn't there isn't an easy way to add it, apart from hacking up the gdm menu item scripts (if you wanted to they're in like /etc/gdm/Session.d or something).
So I guess using the startup applications gui in Gnome is the right way to do it. Unless anyone objects, I'm going to add a note to the wiki. Reading around, it seems like it might be possible to somehow execute startup processes with GDM reading a .xession file, but I didn't really get it.
Curiously, when I was using Slim it solved a different bug I was having, with my brightness getting dimmed after every shutdown. So at least now I know it's gdm that's doing that. And once again I've learned that I'm more likely to turn up relevant Arch forum posts with google searches than with the Arch forum search function.
And thanks again to everyone for their suggestions and ideas about how to address this issue.

Help! My PSE8 Editor will not work!

When I try to open it, the editor will not load and I get an error message when I attempt to open a previously saved document I did in photoshop. the message says that the editor will not work. I already tried the ctrl+alt+shift keys at startup.

I am having the same issue. In my case the software was inside the new computer that i've purchased.It is a vaio with windows 7, 64bit.The organizer runs normally from the first time.When I tried to open the editor, appeared the license agreement on which you have to accept in order to continue. I clicked accept but absolutely nothing happened.Then I had to start task manager and close the program because it didn't respond.
I also tried to restart my pc and re-do the whole process, but again nothing changes.Any ideas?

( SOLVED )gnome-terminal, su, sudo, gksu, gksudo does not work

Hello,
In my fresh installed gnome3 graphical environment, in gnome-terminal, I can not gain root access.
I've tried diverse su commands.
1. su command, ends with:
su -
Password:
su: Authentication failure
2. sudo command, ends with:
sudo -l
[sudo] password for root:
Sorry, try again.
[sudo] password for root:
Sorry, try again.
[sudo] password for root:
sudo: 2 incorrect password attempts
Of course - each time, I typed correct password.
In my sudoers file, group wheel ( into which belongs user I logged in ) has permissions to execute any command.
3. gksudo with debug:
gksudo -ld gnome-terminal
No ask_pass set, using default!
xauth: /tmp/libgksu-stbGos/.Xauthority
STARTUP_ID: gksudo/gnome-terminal/879-0-Bex_TIME0
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: root
cmd[7]: --
cmd[8]: gnome-terminal
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
sudo: 1 incorrect password attempt
xauth: /tmp/libgksu-stbGos/.Xauthority
xauth_env: /var/run/gdm/auth-for-tangram-9JYTNt/database
dir: /tmp/libgksu-stbGos
I've been asked for my password, not root, after typing I get "incorrect password attempt", if I type root pwd I get the same.
4. Same with this command:
gksu -ld gnome-terminal
No ask_pass set, using default!
xauth: /tmp/libgksu-SBPcOB/.Xauthority
STARTUP_ID: gksu/gnome-terminal/1028-0-Bex_TIME0
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: root
cmd[7]: --
cmd[8]: gnome-terminal
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
sudo: 1 incorrect password attempt
xauth: /tmp/libgksu-SBPcOB/.Xauthority
xauth_env: /var/run/gdm/auth-for-tangram-6RCSoJ/database
dir: /tmp/libgksu-SBPcOB
In multi-user-mode I can login to root account.
Last edited by tangram (2013-12-23 08:42:09)

tangram wrote:
Hurrican, ok, there is no need to install antother terminal, as I wrote it did not work also in xterm.
Yesterday evening, tired and sad that gk(su|sudo) still does not work,
as the "last chance idea", I logged in into multi-user mode ( init level 3 ) and changed root's password,
then loged in into graphical mode ( init level 5 ), start gnome-terminal and suddenly ... command "su -" started to work.
By the way, similar solution ( but with chroot ) has suggested Gulver in his post ( this thread, answer #2 ).
The question is, why root's password, set during install, after finished installation is recognized in text mode, but not im graphical ?
First root's password was really simple, like "dog4356", without any national chars.
You're right. I don't even have xterm installed so I guess I just singled out gnome-terminal and forgot that xterm also wasn't working.
Forgive me for my shaky advice. Like you I've been super busy, and sweating out a fever of 102 degrees (that's Fahrenheit no my
blood wasn't boiling ). Anyways, glad you got it working. After reading over the whole thread and thinking about it for a little bit, I
can't really make a good guess as to what was happening.
I'm sure you probably had tried this, but you could have typed the password out in the command line so you could see it. If there was
something wrong with it, it would have shown up there as well. If it was perfectly fine, then it would have been very, very weird.
The important thing is you got it working.
Merry Christmas.

Mouse Not Working / Not Turned On

Hello,
This week I decided to up my Linux experience. I was using Ubuntu Linux before, and I decided to step-up to something a little less... handed-to-you. Enter Arch Linux, and enter problems! I've been in the IRC all day trying to get X running (apprently, I decided to install Arch Linux on the wrong day, as the new X7 package just entered the Arch Repo). Well, I got it running, and I can log into GNOME...
...but from there, I'm stuck.
My mouse (A Logitech MX510) not only does not work in Gnome... it doesn't work anywhere in Arch! The laser does not turn on when I select Arch VIA GRUB... once selected, the thing turns off and stays off.
I was suggested to use gpm; however, that did not work, and would throw up lines of error whenever I rebooted. Then, I read to install xf86-input-mouse... but I already have that!
What am I to do! It was suggested that is was not a problem in X... to veer away from the X 7.0 malarkey that's ensueing in the forums and IRC room.
Thanks for any help. Other than not being able to do anything, Arch Linux is great! Damn fast.

# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/unimaps
# USECOLOR: use ANSI color sequences in startup messages
LOCALE=
HARDWARECLOCK="localtime"
TIMEZONE="America/Los_Angeles"
KEYMAP=us
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by hwdetect
MOD_BLACKLIST=()
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to disable it
MODULES=(evdev usb_storage usbhid ohci_hcd ehci_hcd uhci_hcd)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
HOSTNAME="backroom"
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles
#NET_PROFILES=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs crond dbus hal httpd openntpd gdm alsa)
# End of file

Gdm not working on Vaio SVS13A

Similar Messages

Maybe you are looking for