Booklet printing - with enscript?
by Robert Moskowitz
I have been using enscript to nicely print Internet draft .txt two up
duplex,
enscript -2r --margins=:::45 -DDuplex:true -P HP-Officejet-Pro-8500
draft-moskowitz-hip-rg-dex-06.txt
but it would be nice to do this in booklet form like I can get with a
pdf with acrobat reader.
I looked at the enscript man, and did not see a way to do this. Anyone
have experience with booklet printing?
Oh, I am still on F16.
11 years, 7 months
yum --downloadonly question
by Trutwin, Joshua
Hi,
I upgraded a number of lab computers from Fedora 14 to Fedora 17 this summer and a process I used to push patches out to them en mass no longer works.
What I used to do was:
yum --downloadonly --security update
Then I would copy /var/cache/yum to a shared NFS drive and from each client run an update script that would include:
rm -rf /var/cache/yum
cp -pR /nfs/yum-cache /var/cache/yum
yum -C -y --security update
In fedora 14 this would run the update from the local cache (-C option) without prompting via -y so I could script/push security patches to all my clients. I use this method as occasionally some of the clients are offline and need to be manually started up - this way I can be sure each client has the exact same patches.
In fedora 17 when I do this I get the following error message when running the yum -C command on the client:
[Error -1] Check uncompressed DB failed
I ran with -v -e 10 -d 10 and it's failing after printing: "Setting up Package Sacks".
The following yum plugins are enabled: downloadonly, presto, security, tsflags, verify, versionlock
Is this process simply not allowed anymore? If not is there an alternate way to do what I'm attempting?
Thank you!
Josh
11 years, 7 months
Printing problem with acroread
by SternData
F17, AdobeReader_enu-9.5.1-1.i486
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.
Just me or anyone else seeing this?
--
-- Steve
11 years, 7 months
Failed to update Fedora 17 due to dependency problem
by Mateusz Marzantowicz
I have a problem updating Fedora 17. When I try yum distro-sync - it
fails with dependency error. When I add --skip-broken option, it also
fails to resolve dependencies. What should I do to upgrade my system?
Why there are packages marked x86-32? Isn't it too early for this ABI to
be introduced in F17?
Here is what yum says in first case:
--> Running transaction check
---> Package libstdc++-devel.i686 0:4.7.0-5.fc17 will be installed
--> Processing Dependency: libstdc++(x86-32) = 4.7.0-5.fc17 for package:
libstdc++-devel-4.7.0-5.fc17.i686
---> Package libstdc++-devel.x86_64 0:4.7.0-5.fc17 will be updated
--> Finished Dependency Resolution
Error: Package: libstdc++-devel-4.7.0-5.fc17.i686 (fedora)
Requires: libstdc++(x86-32) = 4.7.0-5.fc17
Removing: libstdc++-4.7.0-5.fc17.i686 (@fedora)
libstdc++(x86-32) = 4.7.0-5.fc17
Updated By: libstdc++-4.7.2-2.fc17.i686 (updates)
libstdc++(x86-32) = 4.7.2-2.fc17
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
When I add --skip-broken as suggested yum fails with following error:
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing it that there is a problem. Eg.:
1. You have an upgrade for libgfortran which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libgfortran of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what).
2. You have multiple architectures of libgfortran installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of libgfortran installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: libgfortran-4.7.0-5.fc17.i686 !=
libgfortran-4.7.2-2.fc17.x86_64
Error: Protected multilib versions: libquadmath-4.7.0-5.fc17.i686 !=
libquadmath-4.7.2-2.fc17.x86_64
Error: Protected multilib versions: libgomp-4.7.2-2.fc17.x86_64 !=
libgomp-4.7.0-5.fc17.x86_64
Here is my yum repolist output:
adobe-linux-x86_64 Adobe Systems
Incorporated 2
fedora Fedora 17 -
x86_64 27,033
fedora-chromium-stable Builds of the
"stable" tag of the Chromium Web Browser 20
rpmfusion-free RPM Fusion for
Fedora 17 - Free 449
rpmfusion-free-updates RPM Fusion for
Fedora 17 - Free - Updates 313
rpmfusion-nonfree RPM Fusion for
Fedora 17 - Nonfree 193
rpmfusion-nonfree-updates RPM Fusion for
Fedora 17 - Nonfree - Updates 193
updates Fedora 17 - x86_64 -
Updates 8,915
Mateusz Marzantowicz
11 years, 7 months
Re: Printing problem with acroread
by Errol Mangwiro
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."
-----Original Message-----
From: Heinz Diehl <htd(a)fritha.org>
Date: Thu, 27 Sep 2012 06:38:08
To: <users(a)lists.fedoraproject.org>
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
adobe-release-i386-1.0-1.noarch
AdobeReader_enu-9.5.1-1.i486
> 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
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
11 years, 7 months
What package to have MTP?
by Mihamina Rakotomandimby
Hi all
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.
Thank you.
--
RMA.
11 years, 7 months
Looking for a way to get mp3s off an ipod
by thomas cameron
Howdy All -
I have an old 80GB iPod that has a bunch of music on it that I'd like to
get off.
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:
/home/Music/ipod/[artist]/[album]/[track]
Thanks!
Thomas
11 years, 7 months
How to rescue your partitions after upgrade to Fedora 18 Alpha eats them
by Jakub Kicinski
Hi all,
I recently had a weird problem after "upgrade" to Fedora 18 Alpha. I
decided to share the solution, maybe it will help someone.
But first:
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:
http://lwn.net/Articles/506831/
but I didn't suspect that not only Rawhide, but also Alpha releases
became unusable.
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
data back:
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
distribution.
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
your data.
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
on EXT4:
https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout
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).
More info:
http://technet.microsoft.com/en-us/library/cc781134%28v=ws.10%29.aspx
Useful tools:
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:
http://rackerhacker.com/2010/12/14/mounting-a-raw-partition-file-made-wit...
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
-- Kuba
11 years, 7 months
Adding applications
by Shane
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?
Shane
11 years, 7 months
Shutdown crashes in FC16
by Bill Davidsen
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
11 years, 7 months