debuginfo install: file /usr/lib/debug from PKG conflicts with file from package gtk2-debuginfo-2.24.22-2.fc19.i686
by Franta Hanzlík
I did build some rpm package. Now when I install it's debuginfo rpm
(by 'rpm -i PKG-debuginfo-VER-REL.fc19.i686.rpm'), I got lot of errors
such as:
file /usr/lib/debug from install of PKG-debuginfo-VER-REL.fc19.i686.rpm
conflicts with file from package hunspell-debuginfo-1.3.2-13.fc19.i686
where files (it are directories) are
/usr/lib/debug
/usr/lib/debug/.build-id
/usr/lib/debug/.build-id/eb
/usr/lib/debug/.dwz
/usr/lib/debug/usr
and it conflict perhaps with all -debuginfo packages which are
installed from Fedora/Rpmfusion/ATrpms repos.
It seems as the problem is in directories permissions - in filesystem
these are 0755, but in my debuginfo package these rights appear to be
2755.
Thus my questions:
- debuginfo packages are automatically generated and I not see any
option how set permissions at these directories. How is possible set
correct values there?
- Is some way how install debuginfo pkg with bad permissions? E.g.
with rpm/yum/debuginfo-install (this tool has too short man page)?
It is perhaps possible manually uncpio debuginfo package, but... ;)
Thanks, Franta
10 years
Re: lightdm fails to start a gnome session
by Joachim Backes
On 04/15/2014 04:05 PM, Paul Cartwright wrote:
> On 04/15/2014 09:51 AM, Joachim Backes wrote:
>> Hi all,
>>
>> having the problem that lightdm is'nt able to start a gnome-session:
>> only seeing a screen with the (well known):
>>
>> Oh no! Something has gone wrong. Please log out and try again.
>>
>> Login in again shows the same phenomena, and so on...
>>
>> No problem to start a kde session with lightdm.
> 2 things to try..
> 1. add a guest user & see if that can log in to gnome.
No, fails. (Oh, no. Something ...)
Only the root account can start a gnome session iniated by lightdm.
> 2. rename your .gnome folders and try logging in again. probably a
> configuration issue
Did not try, because even a fresh user fails (see 1.)
Kind regards
Joachim Backes
--
Fedora release 20 (Heisenbug)
Kernel-3.13.10-200.fc20.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes/de-index.html
https://www-user.rhrk.uni-kl.de/~backes/en-index.html
10 years
An scp question
by William W. Austin
I run current Fedora releases on my home office boxes, but at my "real"
office (i.e., where I *don't* own the machines) it is still mandated
that 2 particular machines will stay with FC17. (This is a BIG
improvement because I was only able to upgrade the first one (machine
"A") a week or so ago. The other (machine B) is still running FC14 and
will stay that way until the next "maintenance weekend" some time in
October.
I need to set things up so that cron jobs can run the scp commands
without anyone having to key in a password. But since the upgrade,
I've been having a problem getting scp to work in both directions on
the FC17 machine.
First I generated the two necessary id_dsa and id_dsa.pub files (ssh-
keygen -t dsa on both machines), and then I installed the id_dsa.pub
key from machine A into the authorized_keys file on machine B and vice-
versa (in the appropriate ~/.ssh directories).
From a terminal, scp works fine in both directions. However...
From machine A (FC17) I can successfully do both of these:
scp <FILENAME> <machine B>:/PATH (copy to machine A from B)
scp <machine B>:/PATH/<FILENAME> (copy to machine B from A)
BUT from machine B (FC14), both of these fail:
scp <FILENAME> <machine A>:/PATH
scp <machine A>:/PATH/<FILENAME>
As I had this working when both machines were running FC14, I suspect
that there's something I'm overlooking, and I haven't found it yet.
I've been working at this for about a week with no results, and
if anyone has any pointers, suggestions, or a URL or two, I'd really
appreciate any help you can give me (yes I've read the manuals and
looked it up on line - but so far without figuring out a solution).
- Thanks,
wwa
--
airedad(a)att.net
"life is just another phase i'm going through. this time, anyway ..."
10 years
RE: SSH Login timeout
by Patrick Kobly
In /etc/ssh/sshd_config:
UseDNS no
May help. Alternatively, setting up proper reverse DNS for your private network on the Fedora machine would probably help.
PK
-----Original message-----
From: Aero Maxx <aero.maxx.d(a)gmail.com>
Sent: Tue 15-04-2014 03:42
Subject: Re: SSH Login timeout
To: Community support for Fedora users <users(a)lists.fedoraproject.org>;
> On 14/04/2014 18:35, Mike Wright wrote:
> > 04/14/2014 09:24 AM, Aero Maxx wrote:
> >> Hi All,
> >>
> >> I have been having some internet issues at home today, and as a result I
> >> have been unable to login to a fedora machine on my local network from a
> >> windows 7 machine also on the local network.
> >>
> >> I believe it must have something to do with trying to resolve the ip of
> >> the local machine trying to connect to a hostname which it is having
> >> problems in doing so due to lack of internet.
> >>
> >> Is there anything I am able to do to solve this issue when there is no
> >> internet connection available ?
> >
> > Hi Daniel,
> >
> > Have you tried to ssh into the fedora machine by using its IP?
> >
> Hi Mike,
>
> Yes I only use the IP to login, when internet access is available i get
> the prompt for my username, and then fairly quickly it asks for the
> password.
>
> When no internet access is available it asks for my username, and then
> hangs until it times out, and never asks for my password.
>
> Thanks,
> Daniel.
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
10 years
Grub2 ignoring timeout
by Shane Johnson
Ran into an odd problem this morning, I have two seperate systems installed
over the last two days where Grub is ignoring the time out in the grub.cfg
file. Anyone seen this, had this problem, or know how to resolve it?
Thanks
--
Shane D. Johnson
IT Administrator
Rasmussen Equipment
10 years
R: Re: Some failures at boot-time
by antonio montagnani
No reply from your command, shall I assume that is not connected to selinux??
ausearch -m avc -c systemd-sysctl
<no matches>
----Messaggio originale----
Da: pomidorabelisima(a)gmail.com
Data: 14-apr-2014 14.57
A: <users(a)lists.fedoraproject.org>
Ogg: Re: Some failures at boot-time
On 14.04.2014 13:48, antonio.montagnani(a)alice.it wrote:
> I noted some failures at boot time: digging I found:
>
> [root@Fujiantonio antonio] systemctl | grep failed
> rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon
> systemd-sysctl.service loaded failed failed Apply Kernel Variables
>
> [root@Fujiantonio antonio]# journalctl -a -b _SYSTEMD_UNIT=systemd-sysctl.service --no-pager
> -- Logs begin at mer 2014-03-12 22:00:56 CET, end at lun 2014-04-14 13:24:40 CEST. --
>
> [root@Fujiantonio antonio]# systemctl -l status systemd-sysctl.service
> systemd-sysctl.service - Apply Kernel Variables
> Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
> Active: failed (Result: exit-code) since lun 2014-04-14 08:54:03 CEST; 4h 32min ago
> Docs: man:systemd-sysctl.service(8)
> man:sysctl.d(5)
> Process: 512 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
> Main PID: 512 (code=exited, status=1/FAILURE)
>
> apr 14 08:54:03 Fujiantonio systemd[1]: Starting Apply Kernel Variables...
> apr 14 08:54:03 Fujiantonio systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=1/FAILURE
> apr 14 08:54:03 Fujiantonio systemd[1]: Failed to start Apply Kernel Variables.
> apr 14 08:54:03 Fujiantonio systemd[1]: Unit systemd-sysctl.service entered failed state.
>
> Is this connected to any known bug??
# ausearch -m avc -c systemd-sysctl
poma
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
10 years
SSH Login timeout
by Aero Maxx D
Hi All,
I have been having some internet issues at home today, and as a result I
have been unable to login to a fedora machine on my local network from a
windows 7 machine also on the local network.
I believe it must have something to do with trying to resolve the ip of
the local machine trying to connect to a hostname which it is having
problems in doing so due to lack of internet.
Is there anything I am able to do to solve this issue when there is no
internet connection available ?
Thanks
Daniel.
10 years
Fedora update killed router? Or just coincidence?
by Tom Horsley
I just ran yum update on fedora 20, then as long as I
needed to reboot to get some libs active, booted into
my fedora 19 partition and also ran yum update.
Obviously I had a working network for all that, but when
I booted back into fedora 20, I had no network.
Nothing I tried worked, I even booted a live CD from
a different distro and it had no network either.
But when I power cycled my router, the network started
working again.
Was the router just sitting around waiting for me to
reboot so it could confuse me by crashing at that
exact time? Did the fedora updates manage to do something
totally strange to the network that made the router
crash? Very weird.
If the network disappears again, I'll try power cycling
the router first thing :-).
10 years
