Gnome Keyboard Shortucts broke after update

Hey!
Subj.
Broken keyboards shortcuts are media keys, and few custom other like Mod4-L(Lock Screen)
They were all defined using System/Preferences/Keyboard shortcuts
How do I fix that?
Thanks!

I don't use Gnome, but I'm pretty sure there is a .gnome file that handles that stuff. I'd look to see if you have backups of .gnome and .gconf.

Similar Messages

TS3048 Number pad on extended keyboard stopped working after updating to OSX 10.9.1. Testing keyboard on old system still works perfectly.

Expanded keyboard stopped working correctly after updating my system from OSX 10.8.6 to OSX 10.9.1 and now 10.9.2. The keypad numbers do not work although the numbers along the top of the keyboard work fine. Moving the keyboard back to computer still using 10.8.6 and it works fine.

See if zapping the PRAM works. Check out KB Article: http://support.apple.com/kb/HT1379 Resetting your Mac's PRAM and NVRAM

Keyboard falls asleep after update to OS X 10.8.2 Help!

After update to OSX10.8.2 my MacBook Pro Keyboard and trackpad falls asleep after 10-20 seconds.
Then it takes 4-5 sec to awake. Usually the first keystrokes are lost.
The mouse works perfectly.
Anyone else having this problem or has a solution?

I don't know if it is any help but I forced quit (shutdown) and restarted and it seems to have solved the problem.

Keyboard shortcuts cleared after updating to ios 8.0.2

After updating my iPhone 6 from IOS8 to IOS 8.0.2, the keyboard shortcuts have been cleared out. I've tried to reset the Keyboard Dictionary but no change.

Many others have the same problem. They say misery loves company. Does this help?
Re: Keyboard shortcut problems in iPhone 5S with iOS 8 update
Re: Keyboard Shortcuts still not working...

[solved] gnome-shell bad looking after update

Hi,
After update (about two weeks ago) my gnome looks bad. You can see this in screenshots. Very large icons and strange rectangles in gnome shell menu on started applications.
Can you help?
Last edited by skoczo (2015-05-01 17:27:23)

eyemonen wrote:
Hi
Desktop icons: open Files (nautilus) and change default zoom level for icons from standard to small (preferences - views).
Rectangles: this is how running applications are displayed in the default theme. If those rectangles bother you too much, the easiest way is to change theme. For example, ceti-2 and vertex are already ported to 3.16.
It works. Thanks for help.

Connect to remote server broke after update to 10.5.5

After updating my system to Leopard 10.5.5, I can no longer access a critical server at work while at home. I get the Errror -36 message after a bit of a wait. I don't even get the login dialog.
I have tried both using the URL and the IP number to the remote server, with and without the "afp://"-prefix. (AppleTalk is enabled in the SysPrefs.)
I have also tried a 10.5.4-related tip that you could via Terminal alter the way the Mac sends its access codes. No luck with that either.
The server runs OSX Server (10.4.?) as far as I know. It used to work in 10.5.4. Any ideas?

If you are at home what are you doing to access the server?
I have tried both using the URL and the IP number to the remote server, with and without the "afp://"-prefix. (AppleTalk is enabled in the SysPrefs.)
If this is a critical server then it is unwise to have the afp protocol opened up to the internet. Also Appletalk is not used in Leopard for file sharing it is a legacy protocol that still exists for printers.
The server runs OSX Server (10.4.?) as far as I know. It used to work in 10.5.4. Any ideas?
If your server is running Tiger server you should enable the vpn server and use that to access it from outside.
If a server admin setup your Tiger server I would be very surprised if they had opened up AFP to the world.

Keyboard broke after update

Okay so I decided to try out the program Shaman the other day since I just got it, and I updated my system with it. I know how to do this with CLI but I thought I'd see how it worked, my problem is that it seems that it cleaned my cache out when it was done. Normally, thats been fine but this time my keyboard broke.
After a restart of X, the keyboard detected by HAL (I believe it uses evdev) causes the input to freak out. Pressing any letter will cause it to enter the letter three times. Pressing a number causes something like this: "1!1" or "2@2" which is the number followed by the shift number.
I have tried telling X to not auto add devices and it works for the most part, usually. But I have had even more problems for some reason recently. Would anybody be able to help me? I haven't tried everything I can yet, but I'm going to go back to work on it now that I have posted this.

okay this seemed to solve some problems, but now i also have a problem where i need to hold down the key a long time before it gets any response. This sentence alone took a long time to type. any way to downgrade to evdev 2.0.7? Thank you for the help so far!
Update: well apparently the accessability option "slow keys" was enabled and was causing a huge headache. I'm gonna reboot and try this again.
Last edited by St. Ares (2008-12-30 06:30:56)

New keyboard layout appeared after update - how to remove it?

Hello community,
I'm using two keyboard layouts RU and DE and switching them with Ctrl+Shift. After a recent update a third keyboard layout appeared - US. I checked /etc/X11/xorg.conf, /etc/hal/fdi/policy/10-keymap.fdi and /etc/rc.conf but in all of them there is no US layout. Setting everything there up for the DE and RU layout didn't help, still the US layout is in the layouts list in Gnome. If I remove it from that list, it appears after the next reboot. So how can I go rid of it?
Here are the config files:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de,ru"
Option "XkbVariant" ",winkeys"
Option "XkbOptions" "grp:alt_shift_toggle"
EndSection
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>

<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">de,ru</merge>
<merge key="input.xkb.variant" type="string">nodeadkeys,winkeys</merge>
<merge key="input.xkb.options" type="string">grp: ctrl_shift_toggle</merge>
</match>
</device>
</deviceinfo>
# /etc/rc.conf - Main Configuration for Arch Linux
LOCALE="de_DE.utf8"
HARDWARECLOCK="local"
USEDIRECTISA="no"
TIMEZONE="Europe/Berlin"
KEYMAP="de-latin1-nodeadkeys"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
Thanks, PhotonX

Thanks for your input, guys, I think, this issue has been already reported (quite a long time ago) which is even the top entry of the most wanted tasks: http://bugs.archlinux.org/toplevel/proj1 So the only thing we can do is to follow the comments and to hope for a fix.

[SOLVED] GDM/Gnome won't start after update

Today after I run pacman -Suy, GDM/Gnome won't start anymore after reboot. The error message I get after GDM starts is:
Oh no! Something has gone wrong.
A problem has occurred and the system can't recover. Please contact a system administrator
Does anyone have any idea what happened and how can I recover the system?
Here is the complete log for the update:
http://bpaste.net/show/209520/
Here is the journalctl -u gdm log:
http://sprunge.us/LEOU
Here is tail -2000 /var/log/messages.log:
http://sprunge.us/ObWY
And here is the /var/log/Xorg.0.log:
http://bpaste.net/show/209549/
I can't imagine any other log file that might help figure out what happened, let me know if there's anything else.
Any help is appreciated. Thanks.
Edit: I stopped gdm, created a ~/.xinitrc and could successfully start Gnome with startx. The problem remains with GDM.
Edit: The last update solved my problem: http://sprunge.us/RKWA
Last edited by falmp (2014-04-22 20:38:20)

I'm not sure my issue is really the same one, but am hoping for some guidance here if possible. Trying to start GDM gives me the same error message/screen. After tdm fails I can switch to a console,
sudo systemctl stop gdm.service
then
sudo systemctl start lightdm.service
and lightdm starts fine. However, trying to log in to gnome-session gives me the very same error as I had with GDM. I can log into XFCE just fine. Attempting to start gnome-ession via startx also gives me the error screen. Does anyone know how I can diagnose the problem? Thanks,
Matt

[SOLVED] Keyboard stopped working after update

Greetings,
after my most recent update (I now update infrequently, so I had quite a bunch of packets to update) I experienced my keyboard refraining from working in any way under my desktop environment (KDEmod legacy) - switching to console, the keyboard works again.
I did a few downgrades (info from /var/log/pacman.log) and it now works again.
[2009-02-18 13:47] upgraded xkeyboard-config (1.5-1 -> 1.4-2)
[2009-02-18 13:47] upgraded xf86-input-keyboard (1.3.2-1 -> 1.3.1-1)
[2009-02-18 13:48] upgraded xcb-util (0.3.3-1 -> 0.3.2-1)
Are there any known problems occuring concerning these packets? They seem to change the way, XOrg is accessing the keyboard, which is obviously not working.
Thanks for any advice on this matter!
Regards,
cg
// EDIT
Solution: xorg-server was amongst the IgnorePkg list as in pacman.conf - updating xorg-server together with xf86-input-keyboard, input devices work like charms again.
Last edited by chaosgeisterchen (2009-02-20 01:34:00)

ise wrote:
The new xorg server introduces some new handling of the input devices. Have a look here:
http://wiki.archlinux.org/index.php/Xor … otplugging
And here is the news announcement:
http://www.archlinux.org/news/424/
Daniel
Thank you for your contribution. I tried my best to configure my input devices conform to the new XOrg hotplugging, but I have to say that the problem persisted.
Step 0:
Updating all packages (again). Conclusion: Not working.
Step 1:
Copying the keyboard configurations from /usr/share to /etc for persistent use by HAL. Conclusion: Not working.
Step 2:
Commenting out the lines referring to the static declaration of input devices within /etc/X11/xorg.conf. Conclusion: Not working.
Step 3:
Adding the command to disable the hotplugging (Option "AutoAddDevices" "False") on bottom of my xorg.conf. Conclusion: Not working.
Step 4:
Downgrading: xf86-input-keyboard (1.3.2-1 -> 1.3.1-1) Conclusion: Working again.
Guessing by the fact that more than one person posted in this thread, this problem seems not to be limited to my specific configuration (which is rather basic, a basic keyboard and a basic mouse, both using USB). For now, the 'solution' is adding xf86-input-keyboard to the IgnorePkg list of pacman.conf - or is there any known workaround?
I would be glad to be informed about wrongs in the steps I have taken.
Thanks for your information in advance,
regards,
cg
// EDIT
Problem resolved. The solution was stunningly obvious - after having run into problems with the upgrade lately, xorg-server was on the IgnorePkg list as well and defaulted to 1.4.2.2, which would not work well together with the input hotplugging. After having solved the problem with XOrg and updating all the packages again, I can happily use my keyboard again. Sorry for all the hassle!
Last edited by chaosgeisterchen (2009-02-20 01:32:52)

Gnome won't start after update

Hey, so after I've updated gnome to 3.14 it refuses to start. The moment I get past the login screen (that works - I use lightdm), gnome will just tell me that "something has gone wrong" and it won't launch the session. For the past two hours or so I've been trying to identify the issue with no good results. What I think might be relevant is that I use the catalyst driver and also this part of journalctl -e /usr/bin/gnome-shell:
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: gnome-session[602]: WARNING: Could not parse desktop file screensaver-settings.desktop or it references a not found TryExec binary
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: WARNING: Could not parse desktop file screensaver-settings.desktop or it references a not found TryExec binary
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: ** (gnome-settings-daemon:626): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: ** (gnome-settings-daemon:626): WARNING **: Ignoring unknown module 'org.gnome.settings-daemon.plugins.updates'
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: X Error of failed request: BadValue (integer parameter out of range for operation)
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Major opcode of failed request: 141 (RANDR)
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Minor opcode of failed request: 13 (RRChangeOutputProperty)
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Value in failed request: 0x99
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Serial number of failed request: 280
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Current serial number in output stream: 282
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: gnome-session[602]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: X Error of failed request: BadValue (integer parameter out of range for operation)
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Major opcode of failed request: 141 (RANDR)
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Minor opcode of failed request: 13 (RRChangeOutputProperty)
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Value in failed request: 0x99
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Serial number of failed request: 280
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Current serial number in output stream: 282
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: gnome-session[602]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: gnome-session[602]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Unrecoverable failure in required component gnome-shell.desktop
Any ideas? ^^
Last edited by SnowyMan95 (2014-10-17 19:44:43)

Same problem here, and I think that it's all Catalyst fault.
Many people are reporting GNOME 3.14 / Catalyst compatibility issue in AMD Bar & Grill thread (https://bbs.archlinux.org/viewtopic.php?id=57084&p=272) and I totally agree with Vi0l0 (unofficial Catalyst packages maintainer):
Vi0l0 wrote:As for the GNOME 3.14 - wish I have more time to look at this closer, I catched problems with GNOME latelly (but before 3.14) - it started to crash before start - I spent not much time on it, but didn't find solution. Fixing it is not that important for me right now, since im planning to install arch on btrfs 2xSSD smile. Its just the time... Wish I had some kind of clone of myself with shared awareness tongue.
But anyhow I think that GNOME 3.14 support could be real problem atm (at least with unmodified gnome packages), afaik 3.14 is really close to wayland and catalyst doesn't even have egl.
EDIT: if confirmed seems to be a display manager issue:
Vi0L0 wrote:BTW I installed new arch on new drives, and all seems to work fine, GDM didn't start so I used KDM. All problems are gone and GNOME 3.14 works pretty nice.
Last edited by IVIonty (2014-10-19 20:13:20)

Gnome 3 language changed after update

After a recent update, it seems that the language of gnome 3 defaults to Arabic.
Every time I login there is a pop-up that asks me to "Update standard folders to current language?" (The folder listed is ~/Music)
Also, Google chrome defaults to Arabic version of Google in incognito mode, which makes me believe that Google sees something in my computer which I can't see. I have run out of options as to where this changed has occurred. Any ideas?

Thanks. But none of these solve the issue. Issuing "locale -a" returns:
C
en_US
en_US.iso88591
en_US.utf8
POSIX
So, there does not seem to be an issue there.
There is a very simple Region & Language section in System Settings in Gnome 3. I had selected English there (there is no OK button ...) There is something else going on.

SOLVED Spanish keyboard stopped loading after update, upgrade

I am trying archlinux. The newest stable version with updates, and kde 4.3.2. Brilliant it is. However, after a few weeks of perfect use today I booted up and found, I think, US keyboard instead of Spanish one. Apart from a standard update and upgrade, I do not think I have changed anything.
I tried system settings and chose regional and language/keyboard layout. It gives me an error message only. Cannot cut and paste but it sayd something like> Cannot load /usr/lib/kde4/kcm_keyboard_layout.so (libxklavier.so.12. Cannot open shared object file. No such file or directory) Cannot load library.
I check for first file and it shows it is there>
[root@antec etc]# find / -name kcm_keyboard*
/usr/lib/kde4/kcm_keyboard.so
/usr/lib/kde4/kcm_keyboard_layout.so
/usr/share/kde4/services/kcm_keyboard.desktop
So is second file but see it is number 15 not number 12 as said in error message above>
[root@antec etc]# find / -name libxklav*
/usr/lib/pkgconfig/libxklavier.pc
/usr/lib/libxklavier.so.15
/usr/lib/libxklavier.so
/usr/lib/libxklavier.so.15.0.0
/usr/share/gtk-doc/html/libxklavier
/usr/share/gtk-doc/html/libxklavier/libxklavier.devhelp
/usr/share/gtk-doc/html/libxklavier/libxklavier.devhelp2
/usr/share/gtk-doc/html/libxklavier/libxklavier-xklavier.html
/usr/include/libxklavier
/var/lib/pacman/local/libxklavier-4.0-1
/var/lib/pacman/sync/extra/libxklavier-4.0-1
/var/cache/pacman/pkg/libxklavier-3.9-2-i686.pkg.tar.gz
/var/cache/pacman/pkg/libxklavier-4.0-1-i686.pkg.tar.gz
[root@antec etc]#
I check in rc.conf and the es keyboard is selected. I search in the archlinux wiki and in google and also here but do not find help.
EDIT> now also found that Printer Config in Settings also shows similar error messages about orphan modules, old third party models etc.
Can you help please....
Last edited by arjay (2009-10-31 11:49:10)

Very kind of you to reply.
The results of your first request is>
linux-gate.so.1 => (0xb77cd000)
libxklavier.so.12 => not found
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7745000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7629000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xb7620000)
libkdeui.so.5 => /usr/lib/libkdeui.so.5 (0xb7244000)
libkdecore.so.5 => /usr/lib/libkdecore.so.5 (0xb6fcb000)
libQtCore.so.4 => /usr/lib/libQtCore.so.4 (0xb6d9c000)
libQtGui.so.4 => /usr/lib/libQtGui.so.4 (0xb640b000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb6319000)
libc.so.6 => /lib/libc.so.6 (0xb61d3000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb61b4000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb6102000)
libpcre.so.0 => /lib/libpcre.so.0 (0xb60d1000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb60b8000)
libdl.so.2 => /lib/libdl.so.2 (0xb60b4000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb60a4000)
libQtSvg.so.4 => /usr/lib/libQtSvg.so.4 (0xb6051000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb6038000)
libSM.so.6 => /usr/lib/libSM.so.6 (0xb6030000)
libICE.so.6 => /usr/lib/libICE.so.6 (0xb6019000)
libQtXml.so.4 => /usr/lib/libQtXml.so.4 (0xb5fd6000)
libXtst.so.6 => /usr/lib/libXtst.so.6 (0xb5fd0000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb5fc7000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb5fc2000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb5fb9000)
libQtDBus.so.4 => /usr/lib/libQtDBus.so.4 (0xb5f49000)
libm.so.6 => /lib/libm.so.6 (0xb5f23000)
libQtNetwork.so.4 => /usr/lib/libQtNetwork.so.4 (0xb5e14000)
libz.so.1 => /usr/lib/libz.so.1 (0xb5e00000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb5df0000)
liblzma.so.0 => /usr/lib/liblzma.so.0 (0xb5dcf000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb5dcb000)
librt.so.1 => /lib/librt.so.1 (0xb5dc1000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb5d9b000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb5d16000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb5ceb000)
/lib/ld-linux.so.2 (0xb77ce000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb5ce8000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb5ce2000)
libuuid.so.1 => /lib/libuuid.so.1 (0xb5cde000)
libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb5c98000)
libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb5b46000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb5b1f000)
[richard@antec ~]$
And the second>
[root@antec richard]# ls -l /usr/lib/libxklavier.so*
lrwxrwxrwx 1 root root 21 2009-08-23 22:28 /usr/lib/libxklavier.so -> libxklavier.so.15.0.0
lrwxrwxrwx 1 root root 21 2009-08-23 22:28 /usr/lib/libxklavier.so.15 -> libxklavier.so.15.0.0
-rwxr-xr-x 1 root root 115321 2009-08-23 22:28 /usr/lib/libxklavier.so.15.0.0
[root@antec richard]#
As you suspected, libxklavier.so.15 is there, but not so.12 which is presumably what kde is looking for_
The question is, how do I correct this
Richard
BTW thanks for the tip about locate. I used to use this ages ago but got out of the habit. Not sure why. Maybe the distro I had back then did not have it by default and I needed it quickly one day. It could not be that I was too lazy to install it I am sure

Backlight keyboard stopped working after updating to snow leopard

Hi I have a late 2008 macbook pro. When I got the laptop it had 10.5.8 on it and the keyboard backlight was working fine. I dimmed it all the way down to save battery life. Later on I installed 10.6.2 then did an update to 10.6.5. I don't know where it stopped working allong the way but the keyboard backlight no longer works.
I can turn it up using the f keys. It will increase and decrease. There is not a circle with a line through it like I have read that other users have had when their backlight is not working properly.
I can increase it and decrease it. The light never comes on. I have installed that program that lets you control the backlight by putting it in the taskbar, that doesnt fix it. I called apple and reset the SMC by taking the battery out and holding the power button down for 5 seconds then putting the battery back in and turning it back on. That did not fix it. I also asked if there was some preference files that we could throw away to maybe reset it. We tossed about 5 files and that didnt fix it - sorry I cant remember the files. I did a fresh install of snow leopard but i didnt go past the "would you like to bring back your files" part of the install.
Can someone help me? The caps lock button lights up. I dont know if that matters. Please help me fix the backlight on my keyboard. I really dont want to install 10.5.8 again just to see if the light comes back on or not. Is there a bug in snow leopard that messes up my macbook? help!

maybe its fried ? could be just bad luck when you were doing the update ?
Ridiculous!
To the OP:
I'd recommend doing a SMC reset, if that doesn't take care of it do a PRAM reset. The instructions are:
_SMC RESET_
• Shut down the computer.
• Unplug the computer's power cord and all peripherals.
• Press and hold the power button for 5 seconds.
• Release the power button.
• Attach the computers power cable.
• Press the power button to turn on the computer.
_PRAM RESET_
• Shut down the computer.
• Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
• Turn on the computer.
• Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
• Hold the keys down until the computer restarts and you hear the startup sound for the second time.
• Release the keys.

[Gnome 3] gnome-tweak-tool crashes after update

Todays update apparently adds config to edit the window borders as well as checking for 2 folders for themes / icons: ~/.themes and ~/.icons.
These folders were not available by default on my gnome 3 installation, shouldn't these directories be provided by metacity?
[stefan@pcsteef ~]$ gnome-tweak-tool
Traceback (most recent call last):
File "/usr/bin/gnome-tweak-tool", line 81, in <module>
MainWindow()
File "/usr/bin/gnome-tweak-tool", line 46, in __init__
model)
File "/usr/lib/python2.7/site-packages/gtweak/tweakview.py", line 38, in __init__
self._model.load_tweaks()
File "/usr/lib/python2.7/site-packages/gtweak/tweakmodel.py", line 97, in load_tweaks
mods = __import__("gtweak.tweaks", globals(), locals(), tweak_files, 0)
File "/usr/lib/python2.7/site-packages/gtweak/tweaks/tweak_windows.py", line 72, in <module>
WindowThemeSwitcher(size_group=sg),
File "/usr/lib/python2.7/site-packages/gtweak/tweaks/tweak_windows.py", line 43, in __init__
[(t, t) for t in self._get_valid_themes()],
File "/usr/lib/python2.7/site-packages/gtweak/tweaks/tweak_windows.py", line 53, in _get_valid_themes
for t in os.listdir(thdir):
OSError: [Errno 2] No such file or directory: '/home/stefan/.themes'
the related commit:
http://git.gnome.org/browse/gnome-tweak … e8b78b367e
*edit*
related bugreport is already open:
https://bugzilla.gnome.org/show_bug.cgi?id=648735
Last edited by stefanwilkens (2011-04-27 08:04:55)

Probably should, but those two directories weren't there on my clean install. I just created .themes and .icons and restarted the application, and it worked. (Saw the bug report)
...and the fix has already been released per bugzilla.
Last edited by caseyjp1 (2011-04-27 11:08:39)

Gnome Keyboard Shortucts broke after update

Similar Messages

Maybe you are looking for