Been there. On adobe reader 10.1 for windows
"No man is an island, entire of itself; every man is a piece of the continent, a part of the main; if a clod be washed away by the sea, the World is less, as well as if a promontory were, as well as if a manor of thy friends or of thine own were; any man's death diminishes me, because I am involved in mankind; and therefore never send to know for whom the bell tolls; it tolls for thee."
From: Heinz Diehl <htd(a)fritha.org>
Date: Thu, 27 Sep 2012 06:38:08
Subject: Re: Printing problem with acroread
On 27.09.2012, Steven Stern wrote:
> F17, AdobeReader_enu-9.5.1-1.i486
[htd@wildsau ~]$ rpm -qa | grep -i adobe
> When I attempt to print from Acrobat Reader, I can print all pages or
> the current page. But, an entering "4-5" in the "print only pages...."
> box on the print dialog generates a 0K job in the print queue that is
> stuck in the "processing" state.
Works for me, no problems here.
users mailing list
To unsubscribe or change subscription options:
Have a question? Ask away: http://ask.fedoraproject.org
Running FC16 LXDE spin and having an Android 4.1 SGS2.
The telephone is configured to MTP when plugged to the PC.
The PC cannot browse the media in the telephone.
What package should I install in order to get it recognize the MTP?
I have alternate solutions such as FTP over WiFi, but it's slow and I
would like to to it USB.
Howdy All -
I have an old 80GB iPod that has a bunch of music on it that I'd like to
I've tried to use gtkpod, but the stock export dumps everything into one
directory. That's not very useful.
Does anyone know of a way to dump an iPod to my filesystem with the format:
I recently had a weird problem after "upgrade" to Fedora 18 Alpha. I
decided to share the solution, maybe it will help someone.
1. The rant
Clearly something bad is going on in Fedora world. I've been
upgrading to Alphas/Betas for years now and it never caused more
trouble than occasional need to rebuild some packages manually.
I read this:
but I didn't suspect that not only Rawhide, but also Alpha releases
First of all PreUpgrade crashes before it starts. I thought, well, I'll
try DVD. It kind of worked. I was looking for words like "upgrade" or
"update" in the new and shiny anaconda but no luck. Eventually it
started the installation (without any "Warning: write changes to
disk?" or alike). At that point partitions of Fedora 17 where already
magically renamed to Fedora 18, so I hoped for the best. Unfortunately
anaconda crashed when it tried to format my Win7 partition to the
widely used filesystem "None"?! Imagine my amusement when after reboot
I realised that MBR and GPT where wiped out and all of my partitions
were nowhere to be found.
2. The problem
It turned out anaconda not only wipes out MBR but also removes magic
numbers from partitions superblocks (anyone can explain why?). So the
good news was my data was still there, the bad news was: none of
automatic "lost partition detection" tool could find them (at least none
that I know of).
3. The solution
If it happens to you as well, here is what you can try to get your
a. Accept that you do all this on your own risk ;)
b. Backup your HDD, preferably all of it. Backup can be done with dd.
c. Connect damaged HDD to some other Linux box or use a Live
d. Now you need to locate your first partition. There is a good chance
that this will be your /boot and Fedora usually locates it at
0x100000 (i.e. it starts in 2048 sector). Other possibility is
sector 63/64 from pre-GPT world.
e. Set magic value in superblock (see below).
f. Try mounting partition using offset option in mount.
g. Calculate where next partition is most likely to start using block
count and block size from superblock.
h. Fix your MBR. You can probably do that in parted or some similar
tool, but who would trust tools after one just nearly destroyed all
i. If you have more partitions to find, go back to (d).
Important: All values on disk are LITTLE ENDIAN.
Important: Try mounting your partitions read-only first.
Notes on EXT4.
Ext4 is quite easy to find. You will recognize it by two zeroed out
sectors (1024 bytes of zeroes) at the beginning of every partition.
NOTE: those zeroes are *in* the partition, do not skip them when trying
to mount. After zeroes there is a superblock. What you are looking
for is offset +0x38 in the superblock, where you once had a magic value
of 0xEF53, you will probably have to put it back there. More information
Notes on NTFS.
NTFS partition starts with EB 52 90, there are no zeroes in front. Magic
value which is removed by anaconda is "4E 54 46 53 20 20 20 20"
at offset 0x03 into a partition. Its literally "NTFS " (with spaces).
dd - will help you to copy blocks of data around. If you don't know it
already, I advise you to read some tutorial and practise first. It's
easy to destroy thing with one wrong dd.
emacs, okteta etc. - hex editor...
losetup - is a tool which enables you to mount files and drives at
particular offset as loop devices. Very useful, read more here:
dumpe2fs, nftsinfo - will decode superblock for you.
bash calculator - $((1+2+3+4*4)) can save you a lot of time.
bash printf - printf "%d\n" 0x1AB2F or printf "%x\n" $((7863*4096)) is
handy as well.
Good luck from (a sightly less happy) Fedora user
I've searched, but cannot find how to add an application (with an
icon) to the gnome shell in Fedora 17. No right-clicking,
left-clicking, or anything seems to provide any reasonable indication
of how to add a file to an application category. Anybody know where
to find this information or how to do it?
Just a pointer to a solution if it helps anyone, if you have a system which
isn't shutting down properly and cites a missing library, bug 890120 has useful
information. I post only because the obvious bug searches return more matches
than you might want to read, and fewer answers to the issue I had.
Bill Davidsen <davidsen(a)tmr.com>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
I'm more than a little confused. I got a new 3tb seagate hdd and typo'd by placing a filesystem on /dev/sdc instead of /dev/sdc1. Now the drive thinks it's a 801.6 GB. At least this is what fdisk -l reports.
1) how do I "fix" this?
2) do I really need to fix this?
3) what did I wipe out by the typo?
Any/all help or suggestions would be GREATLY appreciated.
I am using Fedora 17 KDE (specifically the computing science spin), I
have been running it for a while and never have major problems ;)
until this morning, since when KDE refuses to start. The system boots
normally to the login screen, I provides my username and password and
it seem that KDE will start, but the scren blink and return to the
However, I get logged without any problem via console
(<CTRL><ALT><F2>) and have full access to the system. Does any one
know about this bug and how to solve it? Anything to cleanup from some
Any help would be apreciated.
Hello, insightful users!
I finally got a new desktop system for my home office, so I get to
tinker with a completely fresh install.
My query is how to best divide the storage. I will be installing the
system on SSD, and I tentatively decided to put swap, /home, /var, and
/tmp directories on a separate, conventional hard drive on the
assumption that this is where most of the rapidly changing data (and
most of the disk writes) would be.
I put swap in it's own partition, sized by the old two-times-RAM
(24GB, in my case -- woohoo!) rule of thumb. Not even sure if that
rule still applies.
The rest of the 2TB spindle is configured LVM, and in that reside the
/home, /tmp, and /var directories. In my ignorance, I guessed 50GB for
/var and 100GB for /tmp, and the rest for /home. (I do a lot of audio
and video work, so I figured /tmp might be used heavily.)
Does that arrangement sound sensible? Does anybody have a contrary
opinion about how it should be divided? Or better: is there a way to
make the division between /home, /tmp, and /var more fluid?
I installed dovecot and postfix rpms on my system at work,
and they didn't create the local users in my local passwd
and group files.
Apparently, they didn't create the local users because
the yp server happened to have those same users defined
When I rebooted my system both postfix and dovecot failed
to start because yp wasn't up yet, so the users were not
Shouldn't packages like this always want to really create
real local users on they system doing the install?