Looks like Gnome is doing the same thing that Microsoft did after XP. I
can no longer set nautilus so that when I double click on a directory,
it opens up with the filesystem tree in the left pane, and the contents
of my directory in the right pane in *list* view. I used to be able to
set a checkbox for 'always open in browse mode" or something similar,
but I can't find that in F18 beta.
Is that option still around? Where is it hiding?
apologies for this being slightly off-topic (I work in Fedora, so this
list occurred to me as one place to ask the question...)
In a nutshell: I'm wondering if anyone could point me to useful
resources that describe where user-specific Postscript
information/customizations/etc. are stored on a standard, vanilla Fedora
installation ? I really do mean /user-specific/ (not global)
preferences here, so I imagine the info/settings probably live somewhere
in $HOME/, but my Linux/Fedora print config knowledge has become
outdated and quite rusty... I tried some obvious things -- like blasting
away the $HOME/.gtklp that exists if one has GtkLP installed (this is a
GTK frontend to CUPS) -- but all this was to no avail, my page-scaling
problem persists. I've also searched extensively online for the info
(queries like "linux postscript user customization file"), but still
can't find anything.
A bit of backstory: Suddenly, any email I print from Thunderbird, by
sending to the default print queue, ends up being scaled-down by a
factor of ~0.8x, positioned flush-left and flush-bottom on the
standard-sized (8.5"x11" letter) paper. I learned the following from
various troubleshooting efforts and tests:
1. problem is not the printer itself -- e.g., a simplex queue on the
same printer works fine (problem is I use duplex)
2. problem is not Thunderbird-specific -- I initially thought I must
have mung'd a t-bird setting in prefs.js or something like that,
but turns out that's not the problem -- interestingly, this
scaling problem does /not/ occur if I print a PDF file to the
troublesome print queue, but it /does/ occur if I print a
postscript file from any postscript-aware app (e.g. okular), which
led me to conclude it's some generic postscript config problem...
3. problem is not global, but rather is user-specific -- the scaling
problem does not occur with another user account on the same machine
From the above I deduced it's some user-specific Postscript weirdness,
and was hoping this could be traced to something in $HOME, but for the
life of me I can't get any further.... maybe I'm missing something
...any tips or pointers to online resources would be greatly appreciated!
Hi Bruno, Alan,
The rpmbuild interface does not provide the user a way
to go through the entire config options before proceeding
to build the kernel. If it does, I would really like to know
how it's done.
The current rpmbuild of the kernel builds bazillions of
drivers, most of which are very likely not needed by
the user's platform. This leads to an extremely time
consuming default build, and in my case, I have only
one machine which is a unicore.
Other problems are features that a user might neither
want nor need.
Is there a way to propagate this issue to development leads?
I did the minimal install on my ee701. At least the first attempt.
I set my swap at 768Mb, and left /boot at 500Mb (probably could shrink
this next time). This left 2.7Gb for /
That swap will be too small for hibernate....
So a minimal install with also selecting Gnome (and deselecting a few
things like snapwell or whatever it is called) resulting in only 737Mb
used in /! Now I have a local repo, so I was able to select my local
update repo to eliminate the update step.
So when the computer boots, I come up in multiuser, not graphical and it
did not prompt me to create a non-root user and all those other first
time boot options of a regular install. Sooo...
How do I start gnome so I can use its tools for things like creating my
Whatelse do I need to set from the 1st time boot?
How do I change the runtime to grahical with no /etc/inittab? I looked
at what inittab has in it now and tried the ln command:
ln -s /lib/systemd/system/graphical.target
But of course this fails as there already is the symbolic link to
It was quite a pain getting to this point as the ee701 has a narrow
screen and you cannont move the screens in install to see what is off
the bottom of the screen. You just have to guess....
Kernel-3.7.0-rc6.git local build, belched out
[90658.498609] irq 19: nobody cared (try booting with the "irqpoll" option)
irq19 belongs to my Atheros AR-5008 mini-pci card.
This problem does not occur on kernels prior to 3.7.
Every time it happens, the card gets stuck in a mode
that renders it unusable, so that even restarting wpa_supplicant
does not restore association with AP. Only a reboot
fixes the problem until it happens again.
Is there a user util to force a soft reset of a mini-pci wifi card?
VDPAU works, finally. libvdpau.i686 was recently updated to 0.5-1 in
Fedora 17. There have also been recent updates to the proprietary
nvidia drivers. The result of this is that vdpau works well, at least
with XBMC running on Fedora 17 on Asus 1012P EeeBox PCs.
Asus (and others) made compact form factor PCs based on the Atom series
of processors. Asus called their line the EeeBox PC.
One of these devices, the EB1012P was particularly suited for use as a
stand alone media center box (like Apple TV, only with Linux and on
steroids) because it had the right combination of size, cost, quiet
operation, just enough processing power and HDMI output.
The later was provided by an nVidia ION2 graphics controller
(http://en.wikipedia.org/wiki/Nvidia_ION), which was supposedly capable
of 4th generation pure video.
(http://en.wikipedia.org/wiki/Nvidia_PureVideo) The advantage of which
is supposedly the near total processing of various video streams by the
video card directly into HDMI video, aka VDPAU.
About 16 months ago I began working on a whole house video solution
using EB1012P devices as the media player component specifically because
of their VDPAU capability.
What I quickly learned was that VDPAU functionality was all but broken
on this device for the at least the 2 applications I was interested in,
namely XBMC and MythTV. The symptoms ranged from high CPU utilization
playing 1080P streamed mkv files, to screen stuttering to outright
freezing that only a reboot could cure.
Without VDPAU functionality, the EB1012Ps were just about useless as
media center devices. I put my devices to work in other capacities, but
kept one set up as a test device for XBMC and MythTV.
Fast forward to last week when I noticed that libvdpau had received an
update, the first I had seen in a while. Earlier this evening I ran an
update on Fedora 17 that included the libvdpau update. Thereafter I
started XBMC and ran the same 1080p mkv file that I have been fighting
to get displayed properly for the last 16 months.
I am happy to report that a stock F17 XBMC 11 (Eden) install on Fedora
17 running on my EB1012P now renders my test mkv stream perfectly.
I always thought that the EB1012P should be able to do this, but this is
the first time I have ever actually seen it done.
The sad part of all this is that the world has moved on from the
EB1012Ps. They are no longer in production, though one can probably
pick up used devices. At one point I was able to buy them for $120
new, without OS, RAM or a hard drive. Those items were inexpensive
additions, allowing me to equip the 1012Ps exactly how I needed them.
Times have changed and we now have Raspberry Pis capable of rendering
1080P HDMI output, for a lot less money. But the RPis don't have as
much RAM (512 MB versus 2GB), nor USB 3.0, nor an eSATA port, nor a hard
drive interface, nor built in WIFI nor a sleek case and power supply.
The EB1012P is fully capable of running KDE sessions on F17, browsing
with Firefox and displaying Youtube videos, making it a decently high
end media center, mostly thanks to the power of Linux and the 1012Ps
high end graphics capability. The 1012P running XBMC, KDE and Firefox
makes the applications and network integration built into 2012 high end
TVs look like a toy.
I think its a shame that the world essentially missed out on such a
wonderful device for lack of a working driver. Its amazing what one can
do with an EB1012P. Part of that spirit has been captured with RPi,
but the EB1012P did it first and does it with quite a bit more power and
finesse than the RPi does.
If anyone from Asus reads this, I highly recommend you bring these
devices back, with an improved processor, an infared receiver and a
slightly lower price point. RPi is just catching on as a media
center. An upgraded 1012P, unlocked, loaded with the right Linux
software and priced right could literally revolutionize how we use our TVs.
I have installed Fedora 18 on seven machines using yum distro-sync,
and am happy with the result.
On my son's machine, however, gdm presents a fuzzy rectangular patch
instead of the Fedora logo. This is also the case with the icons at
the top right of the gdm screen, until you move the mouse over them.
Can anyone suggest what I might be able to do here?
Nick Urbanik http://nicku.org 808-71011 nick.urbanik(a)optusnet.com.au
GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
I disclaim, therefore I am.
How do I find out what wireless card is in a system, and thus which
driver to install?
This is for my asus ee701 with the whole minimal business. I am not
seeing any wireless in NM, and I know it is there, as it was their once
ago in an earlier install (f14). When I did the install, I unclicked a
lot of drivers, thinking I knew what I had, but no wireless is showing.
Thus I really need to figure this out.