Booting
by Richard Vickery
Is there a way to reboot the computer while its stuck on "Starting GNOME
Desktop Manager"?
10 years, 10 months
Cleanup after fedup?
by Timothy Murphy
Fedup 18 -> 19 went fine for me,
but I noticed a few warnings came up during the process.
Is there any command one could or should run after fedup
to clean up yum records?
[I grep-ped for error in fedup.log but didn't find anything
except RPMs with error/Error in their names.]
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 10 months
yum error (grub does not update) while installing kernel
by Ranjan Maitra
Hello,
Of late (since later days of F18), I have been getting the following
error whenever a new kernel gets installed: /boot/grub2/grub.cfg does
not get updated and has to be "fixed" manually using
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Is there any way to fix this problem?
The only error I get appears to be unrelated (or is it?) but consistent
(everytime I install a new kernel):
%yum update
....
Installing: kernel-3.9.9-301.fc19.x86_64
23/45
......
Cleanup :
libipa_hbac-1.10.0-12.fc19.beta2.x86_64 45/45
dracut-install: ERROR: installing '/usr/lib/kbd/consolefonts/True.*'
E: /usr/lib/dracut/dracut-install
-D /var/tmp/initramfs.xo7Lmm /usr/lib/kbd/consolefonts/True.*
I searched on the error message DDG as well as Google but got absolutely
nothing. (I searched on E: /usr/lib/dracut/dracut-install
-D)
Suggestions welcome.
Many thanks again for any help!
Best wishes,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be
deleted on receipt. For those needing to send personal or professional
e-mail, please use appropriate addresses.
____________________________________________________________
FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family!
Visit http://www.inbox.com/photosharing to find out more!
10 years, 10 months
systemd
by Ian Chapman
Hi,
Can someone explain systemd's behaviour? Why is when I have the
following services enabled:
nfs-idmap.service nfs-lock.service nfs-mountd.service nfs-secure.service
I have to enable nfs.target otherwise they fail to start?
This is Fedora 19.
--
Ian Chapman.
10 years, 10 months
Re: disable ssdp
by Kevin Wilson
Hi,
You are right! it is from an Edimax wireless router.
I know now for sure because with sniffer I see the address of
192.168.2.1 as a source address, and the 192.168.2.1 address is the
address of the Edimax wireless router.
However:
There is a UPnP setting - I can reach it from the web interfaces.
But it is disabled !
So I am quite bewildered.
Could it be that it is from an Android phone connected over a Wifi
with the wireless router as a gateway ?
Regards,
Kevin
On Sat, Jul 6, 2013 at 2:12 PM, Andrey Ivanov <anvivanov(a)gmail.com> wrote:
> Maybe it's a router-generated traffic.
> e.g. an Asus router has "Enable UPnP" option in "IP" settings.
>
>
> 2013/7/5 Kevin Wilson <wkevils(a)gmail.com>
>>
>> Hello,
>> I see that from time to time I get in fedora 18 this traffic:
>>
>> SSDP - Simple Service Discovery Protocol
>>
>> every 2-3 minutes a couple of frames for address: 239.255.255.255.
>>
>> I tried to disable bluetooth with no help.
>>
>> google shows that this might be some upnp client, but I don't know how
>> to find it and disable it
>>
>> any ideas?
>>
>> regards,
>> Kevin
>> --
>> 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
>
>
>
>
> --
> Andrey V Ivanov
>
> --
> 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
>
10 years, 10 months
disanle ssdp
by Kevin Wilson
Hello,
I see that from time to time I get in fedora 18 this traffic:
SSDP - Simple Service Discovery Protocol
every 2-3 minutes a couple of frames for address: 239.255.255.255.
I tried to disable bluetooth with no help.
google shows that this might be some upnp client, but I don't know how
to find it and disable it
any ideas?
regards,
Kevin
10 years, 10 months
jar command missing in Fedora 19?
by Amadeus W.M.
I just installed Fedora 19 anew from the live cd and I'm having a few
issues.
One is that I'm trying to install a java application that requires the
jar command, but jar can't be found:
jar xf myApp.jar
bash: jar: command not found...
I have this:
rpm -qa | grep -i java
java-1.7.0-openjdk-1.7.0.25-2.3.10.3.fc19.x86_64
javapackages-tools-0.14.1-2.fc19.noarch
tzdata-java-2013c-1.fc19.noarch
Shouldn't jar be in one of these? If not, could someone please tell me
what package provides that?
Thanks!
10 years, 10 months
F19: System hangs when rebooting guests in qemu/kvm
by Mateusz Marzantowicz
Hello,
I'm experiencing system hangs and kernel oops on Fedora 19. Everything
happens when I restart guest system inside qemu/kvm container. My system
becomes unstable on kernel 3.9.5 and totally hangs on 3.9.6 and later.
It happens just after guest OS (latest stable Debian Linux) shows grub
boot menu. I sometimes see text console with kernel oops message on my
bare hardware but never had time or will to write it down on paper.
I can't provide more details right now, because nothing gets written to
system logs (serious oops?). Besides this issues all other pieces of my
box are working perfectly.
I need some instrumentation and guidance finding what is exactly going
wrong.
Mateusz Marzantowicz
10 years, 10 months
yum delta problems
by Tom Horsley
When I was running f19 beta, I mostly ignored this, but I've
done a distro-sync now and the update I just did once again
got a slew of deltas do not match errors:
Finishing delta rebuilds of 118 package(s) (222 M)
delta does not match installed data==- ] 2.9 MB/s | 96 MB 00:43 ETA
delta does not match installed data==- ] 3.0 MB/s | 103 MB 00:39 ETA
delta does not match installed data=== ] 3.2 MB/s | 105 MB 00:36 ETA
delta does not match installed data
delta does not match installed data==== ] 2.4 MB/s | 120 MB 00:42 ETA
delta does not match installed data
corrupt delta: bad sequence3% [=========- ] 3.3 MB/s | 142 MB 00:23 ETA
delta does not match installed data======- ] 3.6 MB/s | 158 MB 00:17 ETA
Some delta RPMs failed to download or rebuild. Retrying..| 222 MB 00:00 ETA
(1/14): dbus-libs-1.6.12-1.fc19.i686.rpm | 149 kB 00:00
(2/14): cups-libs-1.6.2-12.fc19.i686.rpm | 346 kB 00:00
(3/14): graphite2-1.2.2-2.fc19.i686.rpm | 82 kB 00:00
(4/14): glibc-2.17-11.fc19.i686.rpm | 4.2 MB 00:01
(5/14): gtk2-2.24.19-3.fc19.i686.rpm | 3.3 MB 00:01
(6/14): libcurl-7.29.0-7.fc19.i686.rpm | 214 kB 00:00
(7/14): nspr-4.10-2.fc19.i686.rpm | 122 kB 00:00
(8/14): nss-3.15-5.fc19.i686.rpm | 838 kB 00:00
(9/14): nss-softokn-3.15-3.fc19.i686.rpm | 296 kB 00:00
(10/14): nss-softokn-freebl-3.15-3.fc19.i686.rpm | 145 kB 00:00
(11/14): nss-util-3.15-1.fc19.i686.rpm | 66 kB 00:00
(12/14): openldap-2.4.35-5.fc19.i686.rpm | 330 kB 00:00
(13/14): systemd-libs-204-9.fc19.i686.rpm | 152 kB 00:00
(14/14): krb5-libs-1.11.3-2.fc19.i686.rpm | 787 kB 00:06
I can assure you, I am not manually modifying anything installed by
those packages to cause this mismatch. I do notice they are all
32 bit packages, but I'm running 64 bit. Is yum trying to apply
a 64 bit delta to a 32 bit package or something?
In addition, after the install it apparently didn't cleanup those 14
packages:
[root@zooty ~]# yum clean packages
Loaded plugins: afteryum, fastestmirror, langpacks, refresh-packagekit
Cleaning repos: fedora google-chrome rpmfusion-free rpmfusion-free-updates
: rpmfusion-nonfree rpmfusion-nonfree-updates updates
14 package files removed
Should I file a bugzilla against yum (or something else)?
10 years, 10 months
F18 -> F19 using fedup
by Temlakos
Did somebody ask how fedup would work out in a straight upgrade from F18
to F19?
I just ran through it.
For future reference: tell people how long it will take.
About ten minutes to prepare...
and then two and a half hours to run the upgrade.
Patience. Patience. Patience.
Make sure the log shows no errors. (And would somebody tell us how to
resolve them?)
Then do a restart--and touch *nothing*. Just watch, and be ready when it
does its own restart.
If your system is clean, the upgrade will succeed.
Temlakos
10 years, 10 months