Howto change window colours in GNOME3
by Jouk Jansen
L.S.
How can I change the colour scheme of the windows in GNOME3? (I hate the
greyish colours and my eyes are more suited to some other colours) In GNOME2
I could do this with the gnome-appearance-properties, which seems to be
absent in GNOME3. I tried the gnome-tweak-tool, but that one only allows for
different themes, but not the colour schems of the themes.
Jouk
Pax, vel iniusta, utilior est quam iustissimum bellum.
(free after Marcus Tullius Cicero (106 b.Chr.-46 b.Chr.)
Epistularum ad Atticum 7.1.4.3)
>------------------------------------------------------------------------------<
Jouk Jansen
joukj(a)hrem.nano.tudelft.nl
Technische Universiteit Delft tttttttttt uu uu ddddddd
Kavli Institute of Nanoscience tttttttttt uu uu dd dd
Nationaal centrum voor HREM tt uu uu dd dd
Lorentzweg 1 tt uu uu dd dd
2628 CJ Delft tt uu uu dd dd
Nederland tt uu uu dd dd
tel. 31-15-2782272 tt uuuuuuu ddddddd
>------------------------------------------------------------------------------<
12 years, 11 months
Skype on Fedora 14
by mike
Has anyone had any luck running Skype on Fedora 14 86_x64. It installs
just fine but, when I try to launch it nothing happens!
I get nothing in messages or demesg to show it even attempted to
launch! Is it like Flash and needs to be wrapped in order to work? If
so how?
Mike
12 years, 11 months
Serious problem: boot + systemd + luks + selinux + autorelabel = poop
by Genes MailLists
Sure could use some experts to help me fix this. touching /.autorelabel
on F15 leads to a horrible situation.
Doing this seems to fail because /run is read-only - and so autorelabel
never completes - leaving the .autorelabel flag and leaving perpetual
poop on each reboot.
Booting the machine in this state is possible but very very difficult.
systemd and luks seems to have a problem when things dont go as expected
- in particular removing rhgb confuses systemd into a terrible state -
it prints text prompts for luks password but never waits for an answer -
it also attempts to ask plymouth to do graphical prompt for luks which
you dont see without some carefully timed series of ESC key presses to
flip it on and off ... and only in single user mode - perhaps systemd
does more in multi user mode and gets more confused.
Details:
F15 installed on sandy bridge laptop with i915 intel graphics. The
laptop has luks encyrpted swap and /home but not /.
I did a "touch /.autorelabel" and rebooted - poo rained upon me in large
amounts ... very large :-(
At some point the relabel ended and it booted but screen was hung at the
white balloon. I wasn't watching the relabelling process so ... Hard
reset - and reboot again.
The machine now hangs during every boot - it hangs with the blue screen
+ balloon - and it no longer gives me the plymouth graphical luks
password prompt.
Hard reset - reboot removing rhgb and quiet -
I see error:
Unable to fix label of /run: read-only file system.
in red text and it is clearly is trying to finish the relabeling and
failing on /run.
I see multiple text password prompts for luks password - but it
doesn't stop - it keeps going - says something about 'forwarding to
plymouth'.
typing in the luks password into the text console has no effect.
I repeated above but in single user with selinux=0 - now same as
above - but if I type password and also toggle ESC enough times the
balloon will eventually show password prompt. Toggling ESC again leads
me back to text single user prompt.
I can now exit single user and it comes up in multi user mode with
graphical login.
There is some magic timing to get the series of ESC toggles to get a
luks password prompt otherwise the just machine hangs.
(a) I dont think graphical prompts should be used in text boot.
(b) systemd needs to wait for the password to be typed in.
(c) what can I do to get the relabel to finish - every boot it keeps
trying - the /.autorelable file is never removed.
I can no longer boot except doing the above contortions in single user
+ ESC key flipping to get luks password in.
Am very open to ideas how to fix this ... if i remove the
.autorelabel I assume things will go back to the way they were - but
clearly there are some issues here.
thanks for any guidance
gene
12 years, 11 months
intel wifi link 5100 hangs on
by Hüvely Balázs
Hi All!
I have a big and old problem with my toshiba satellite notebook's wifi.
The original wifi card was a realtek, which is always freezed, so after
a few months I decided to replace that card to an intel one. I searched
the net for full supported wifi card, and I found that intel wifi link
5100 will be the good choice for linux.
I get the interface, installed to my computer, and everything was fine
for a little time.
Now my problem is the card after few minutues or an hour hangs on. I
tried to associate the card again to my AP, but no success. I look after
for my dmesg, and here below my results:
[ 120.302525] iwlagn 0000:06:00.0: Aggregation not enabled for tid 0 because load = 0
[ 123.115878] process `skype' is using obsolete setsockopt SO_BSDCOMPAT
[ 123.542529] iwlagn 0000:06:00.0: iwlagn_tx_agg_start on ra = 74:ea:3a:a5:d3:28 tid = 0
[ 183.974273] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[ 400.474353] TCP lp registered
[ 1723.179600] iwlagn 0000:06:00.0: Error sending REPLY_ADD_STA: time out after 500ms.
[ 1723.179611] HW problem - can not stop rx aggregation for tid 0
[ 1723.679449] iwlagn 0000:06:00.0: Error sending REPLY_ADD_STA: time out after 500ms.
[ 1723.679458] HW problem - can not stop rx aggregation for tid 6
[ 1724.179220] iwlagn 0000:06:00.0: Error sending REPLY_QOS_PARAM: time out after 500ms.
[ 1724.179230] iwlagn 0000:06:00.0: Failed to update QoS
[ 1724.678972] iwlagn 0000:06:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 1724.678984] iwlagn 0000:06:00.0: Error clearing ASSOC_MSK on BSS (-110)
[ 1725.178850] iwlagn 0000:06:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 1725.178860] iwlagn 0000:06:00.0: Error clearing ASSOC_MSK on BSS (-110)
[ 1725.678547] iwlagn 0000:06:00.0: Error sending REPLY_QOS_PARAM: time out after 500ms.
[ 1725.678561] iwlagn 0000:06:00.0: Failed to update QoS
[ 1726.178336] iwlagn 0000:06:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 1726.178348] iwlagn 0000:06:00.0: Error clearing ASSOC_MSK on BSS (-110)
[ 1726.178369] iwlagn 0000:06:00.0: Stopping AGG while state not ON or starting
[ 1726.680114] iwlagn 0000:06:00.0: Error sending REPLY_ADD_STA: time out after 500ms.
[ 1726.680137] ieee80211 phy0: failed to remove key (0, 74:ea:3a:a5:d3:28) from hardware (-110)
[ 1727.179980] iwlagn 0000:06:00.0: Error sending REPLY_REMOVE_STA: time out after 500ms.
[ 1727.179988] iwlagn 0000:06:00.0: Error removing station 74:ea:3a:a5:d3:28
[ 1727.679730] iwlagn 0000:06:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 1727.679740] iwlagn 0000:06:00.0: Error clearing ASSOC_MSK on BSS (-110)
[ 1729.680851] iwlagn 0000:06:00.0: fail to flush all tx fifo queues
[ 1730.180672] iwlagn 0000:06:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 1730.180687] iwlagn 0000:06:00.0: Error clearing ASSOC_MSK on BSS (-110)
[ 1730.686517] iwlagn 0000:06:00.0: Error sending REPLY_ADD_STA: time out after 500ms.
[ 1730.686533] ieee80211 phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-110)
[ 1730.686660] cfg80211: Calling CRDA to update world regulatory domain
[ 1731.187203] iwlagn 0000:06:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 1731.187211] iwlagn 0000:06:00.0: Error clearing ASSOC_MSK on BSS (-110)
[ 1731.627020] iwlagn 0000:06:00.0: Queue 4 stuck for 10000 ms.
[ 1731.627032] iwlagn 0000:06:00.0: On demand firmware reload
[ 1731.687024] iwlagn 0000:06:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 1731.687037] iwlagn 0000:06:00.0: Error clearing ASSOC_MSK on BSS (-110)
[ 1731.687059] iwlagn 0000:06:00.0: Request scan called when driver not ready.
[ 1731.687325] cfg80211: World regulatory domain updated:
[ 1731.687331] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1731.687337] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1731.687343] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1731.687348] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1731.687354] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1731.687359] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1731.687707] cfg80211: Calling CRDA for country: HU
[ 1731.706420] iwlagn 0000:06:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF
[ 1731.720236] cfg80211: Regulatory domain changed to country: HU
[ 1731.720240] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1731.720243] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1731.720246] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1731.720248] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1731.720251] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
[ 1731.725271] iwlagn 0000:06:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF
[ 1731.744111] iwlagn 0000:06:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF
[ 1731.762903] iwlagn 0000:06:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF
[ 1731.781597] iwlagn 0000:06:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF
[ 1731.800298] iwlagn 0000:06:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF
[ 1731.818996] iwlagn 0000:06:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF
[ 1731.837699] iwlagn 0000:06:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF
.
.
.
.
And many MAC is in deep sleep message.
Is there any workaround or fix for my card?
Additional info, my card is placed my notebook sorrounded by pastic
parts, and there is no possibility to cool down the interface. Maybe
it's overheated.
Any suggestion? How I will able to use this card normally?
Thanks: Balazs
12 years, 11 months
Re: cannot boot to F14
by Jackson Byers
>
>>I tried adding
>> chainloader +1
>>to grub.conf .
>>
>> makeactiveWhen I tried to use it, I got
>>Error 18 : Selected cylinder exceeds maximum supported by BIOS.
>You need to get a new(er) BIOS as the physical location where F14 is
located cannot be >used for booting by your current BIOS. Nothing can be
done about this by Fedora, it is a >physical limitation of your system.
Maybe putting a /boot partition below where your BIOS >can boot from could
help (but I don't know if this is possible with your current system
>configuration.)
>>Could the problem with using my boot partition with my
>>Could I fix that by editing my F14's /etc/mtab ?
>Neither of these options will help. Again, this is NOT a Fedora issue.
Some BIOS's are old >appened in the history of PC configurations (I
remember the old 32MB boot issue...)
>James McKenzie
James,
You came in late to this thread.
In fact his problem was solved by
1)redoing his bootloader
root (hd1,8)
setup (hd1,8)
2) copying his f14 stanza to his f13 grub.conf
Your analysis may be correct re error 18,
but that was when the OP was still badly floundering.
His last response to me was
thank you thank you thank you
which I interpreted meaning he had successfully booted f14.
Jack
12 years, 11 months
frozen gnome 3 desktop
by L
Hi
After upgraded to fedora 15, most are working well. The gnome 3
desktop are weired. It frequently freeze, not responding to mouse or
keyboard. I have to login a virtual term (alt+ctrl+F2) to restart gdm
(init 3; init 5). I checked Xorg.0.log file and output of dmesg, I
can't spot any hint.
Linux 2.6.38.8-32.fc15.x86_64 #1 SMP Mon Jun 13 19:49:05 UTC 2011
x86_64 x86_64 x86_64 GNU/Linux
Any one experienced this or where is find a fix? thanks
Y
--
°v°
/( $ )\ Linux Toys
^ ^ http://linuxishbell.wordpress.com/
12 years, 11 months
gnome 3: how to manage energy with laptop
by Adel ESSAFI
Hi list
I want to know which tool enables me to manage en power in gnome 3. I want
that my laptop keep working (do not suspend)
when I put the screen down.
Regards
--
PhD candidate in Computer Science
Address
3 avenue lamine, cité ezzahra, Sousse 4000
Tunisia
tel: +216 97 246 706 (+33640302046 jusqu'au 15/6)
fax: +216 71 391 166
12 years, 11 months
libproxy PAC breakage
by Sam Varshavchik
libproxy is not picking up my WPAD-based config:
[mrsam@monster ~]$ _PX_DEBUG=1 proxy http://www.cnn.com
Using config: 22gnome_config_extension
Using ignore: localhost,127.0.0.0/8
Config is: wpad://
Trying to find the PAC using WPAD…
WPAD search via: 24dns_alias_wpad_extension
PAC found!
Unable to find a required pacrunner!
direct://
It's getting my PAC, but libproxy chokes on it. Looking at the libproxy's
rpm, it appears that all the javascript-related is disabled.
Am I missing something, or is libproxy's PAC support broken?
12 years, 11 months
Re: cannot boot to F14
by Jackson Byers
> I messed up installing F14 and don't know how to fix it.
> What I had planned to do was reuse a /boot partition and put the rest
> in a single new partition I had already created for the purpose.
> I forgot about the /boot partition and I think I told it the
> wrong thing when it asked where to put the bootloader.confusing "reuse
/boot partition"
--meaning trying to reuse f13 /boot partition?
your f14 looks like it doesnt have a /boot partition,
instead a /boot dir under sdb9.
Is that consistent with f14 /etc/fstab (nothing listed for /boot) ?
That /boot directory also isnt consistent with "reusing f13 /boot partition"
If your entire problem is your messing up where to install the bootloader
just redo it:
from your f13, with your f14 sdb9 unmounted,
or booting from a knoppix cd..
I think the following will work:
# grub>
root (hd1,8)
setup (hd1,8)
quit
this should install the bootloader on 1st sector of sdb9
reboot,
see if f14 boots
HTH
Jack
12 years, 11 months
