Re: Documentation and Docstring Format
On 04/17/2014 12:09 PM, Tim Flink wrote: On Thu, 17 Apr 2014 10:03:24 -0400 (EDT) Kamil Paral wrote: https://pythonhosted.org/an_example_pypi_project/sphinx.html#auto-directives I'm not suggesting that we drop everything and fix all the docstrings right now but I am suggesting that we start following the sphinx docstring format for new code and fix other-formatted docstrings as we come across them. Any objections? Well, my only objection is, that the Sphinx format has IMHO the worst impact on how docstrings look. That is my impression as well [1]. The improved versions of Markdown are more legible and easier to remember than ReST (+Sphinx) [2]. OTOH, there are certain Sphinx features that look really great (for example documentation of attributes or global variables). So let's try it. This gets down to personal preference but in general, I prefer ReST to markdown. I thought that we had already decided to use sphinx when mike did his documentation tool survey a couple of months ago. Maybe it is just me, but I use help() more often than html docs. The Spyder editor shows HTML output of docstrings, even though it seems it uses plain ReST conversion instead of Sphinx conversion. But other than that, I have no issues. I played with it a little and the syntax is quite complex. If we are to use it, we will need at least: 1. basic sphinx config committed into the repository 2. some instructions in the readme how to generate the docs Yeah, my plan is to have sphinx docs live in the same repo as libtaskotron so changes can be built locally before submitting any patches. "build docs" sounds like a reasonable section to have in the dev documentation. so that we can at least generate the docs locally and look at it before posting the patch. As Tim already said, sphinx is pretty strict in its syntax. There is one more alternative, I think - use Sphinx for docs generation, but keep the docstrings free-form (I assume there must be an option in Sphinx to do that). That way we lose some pretty formatting, but won't be forced to adhere to a particular syntax. I put an example of the output from both sphinx-style docstrings and freeform docstrings up on fedorapeople: http://tflink.fedorapeople.org/taskotron/test-libtaskotron-docs/library.html It sounds like the general consensus is that sphinx-style docstrings are ugly but generate nice html output and it's not clear whether the ugly-ness of the docstrings is worth the nice html api docs. My 2 cents: The sphinx docstrings are not that bad, and the HTML output in places like readthedocs.org is quite good. Besides, a good deal of python projects fully embrace sphinx, precisely the reason why we migrated all autotest, virt-test and related projects docstrings. Example straight from virt-test: http://virt-test.readthedocs.org/en/latest/api/modules.html From avocado: http://avocado-framework.readthedocs.org/en/latest/api/modules.html Besides, rst is a quite capable language to write great non API documentation and keep it in tree, using sphinx as well. So with one solution, you get it all. Another reason why having not-so-pretty docstrings in this case is worth the effort. ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Taskbot: TAP vs Subunit
On 10/31/2013 02:27 PM, Josef Skladanka wrote: Lucas, do you use any library for producing TAP format? No, at least not in the sense of an external project. Producing TAP in the client is an autotest specific implementation. It is the TAPReport() object defined in: https://github.com/autotest/autotest/blob/master/client/shared/base_job.py#L682 Also, do you have any TAP parser, or do you just emit it? Currently, autotest only outputs TAP, there's no parser available. Cleber from my time was evaluating writing one, but we didn't go forward with it. Matěj Cepl, also a Red Hat employee, implemented one parser at some point, but I think he felt discouraged because people did not give feedback to him (he did ask, though). I for one am also guilty of not following up with his work. He used to have it on his github account, but I can't seem to find it. https://github.com/mcepl?tab=repositories I was looking for something in Python, but all I got is either outdated, or non-complete. I wish we had a better answer to give you, but unfortunately we don't. ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Taskbot: TAP vs Subunit
On 10/31/2013 01:23 PM, Kamil Paral wrote: = TAP = TAP is not unittest-specific, and is human-readable plaintext format. It also has just PASS/FAIL logic, but there is a possibility to add YAML 'metadata' to any result (since TAP v. 13). The real issue with TAP is Python support. There is a TAP-consumer library created as an example for PyParsing <http://pyparsing.wikispaces.com/file/detail/TAP.py>, but it does not support the v13 protocol, and is quite useless as such. TAP-producer library for Python <https://github.com/rjbs/pytap> is also using the old version (i.e. no YAML extensions), and seems to be dead (2 years since last update). It is also quite badly written. Doesn't autotest support TAP results storage? How do they do it? Lucas, can you comment? Thanks. Here you can see an example: $ client/autotest-local --tap client/tests/sleeptest/control 14:11:58 INFO | Writing results to /home/lmr/Code/autotest.git/autotest/client/results/default 14:11:58 INFO | Could not symlink init scripts (lack of permissions) 14:11:58 INFO | Not logging /proc/slabinfo (lack of permissions) 14:11:58 INFO | START timestamp=1383235918 localtime=Oct 31 14:11:58 14:11:58 INFO | START sleeptest sleeptest timestamp=1383235918 localtime=Oct 31 14:11:58 14:11:58 INFO | Not logging /proc/slabinfo (lack of permissions) 14:11:59 INFO | Not logging /proc/slabinfo (lack of permissions) 14:11:59 INFO | Not logging /var/log/messages (lack of permissions) 14:11:59 INFO | GOOD sleeptest sleeptest timestamp=1383235919 localtime=Oct 31 14:11:59 completed successfully 14:11:59 INFO | END GOOD sleeptest sleeptest timestamp=1383235919 localtime=Oct 31 14:11:59 14:11:59 INFO | END GOOD timestamp=1383235919 localtime=Oct 31 14:11:59 14:11:59 INFO | Report successfully generated at /home/lmr/Code/autotest.git/autotest/client/results/default/job_report.html $ cd /home/lmr/Code/autotest.git/autotest/client/results/default/ $ ls control control.state debug job_report.html meta.yml sleeptest status status.json status.tap sysinfo tap.tar.gz $ cat meta.yml file_order: - status.tap - sleeptest/status.tap - sleeptest/keyval.tap $ cat status.tap 1..2 ok 1 - sleeptest ok 2 - job $ cat sleeptest/status.tap 1..1 ok 1 - sleeptest $ cat sleeptest/keyval.tap 1..2 ok 1 - results --- param-seconds: 1 version: 1 ... ok 2 - results --- sysinfo-cmdline: BOOT_IMAGE=/vmlinuz-3.11.6-301.fc20.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 rd.luks.uuid=luks-8c032338-feaa-456a-873c-a08c768b8861 vconsole.keymap=us rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.utf8 sysinfo-memtotal-in-kb: 8061220 sysinfo-phys-mbytes: 8192 sysinfo-uname: 3.11.6-301.fc20.x86_64 #1 SMP Mon Oct 21 21:54:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ... ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Taskbot: TAP vs Subunit
On 10/31/2013 01:23 PM, Kamil Paral wrote: = TAP = TAP is not unittest-specific, and is human-readable plaintext format. It also has just PASS/FAIL logic, but there is a possibility to add YAML 'metadata' to any result (since TAP v. 13). The real issue with TAP is Python support. There is a TAP-consumer library created as an example for PyParsing <http://pyparsing.wikispaces.com/file/detail/TAP.py>, but it does not support the v13 protocol, and is quite useless as such. TAP-producer library for Python <https://github.com/rjbs/pytap> is also using the old version (i.e. no YAML extensions), and seems to be dead (2 years since last update). It is also quite badly written. Doesn't autotest support TAP results storage? How do they do it? Autotest does support recording results in TAP format, due to the work made by a guy from AMD. Breaking the expectations that a TAP enabled test tool would just output tap on standard output, the autotest client can optionally produce files with the results in tap format, and those files can be further processed by other systems. Let me make some runs here and show you examples. Lucas, can you comment? Thanks. ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: cisco vpn because of ipsec over tcp
On 11/16/2011 04:49 PM, David Woodhouse wrote: > On Mon, 2011-11-14 at 21:08 +0400, Lucas wrote: >> >> I am talking about ipsec over TCP. >> >> Everything can do ipsec over UDP, but none over TCP. But on my job for >> the security reason UDP is blocked, cisco vpn can do ipsec over tcp. > > That's entirely stupid. The Cisco "IPsec over TCP" is basically the > *same* as UDP, except it fakes a TCP header on each packet in order to > make it pass through crappy firewalls and NAT which only supports TCP. > > If your IT department think that UDP needs to be blocked "for the > security reason", then it sounds like they are incompetent and should be > fired. Or just taken out back and shot. > > We *have* had Cisco's IPSec over TCP working; it's not particularly > difficult. However, we never really worked out how to make it work > nicely on Linux; the kernel really *really* wants to eat all TCP packets > and will give a TCP RST to any connection it doesn't think is open. Any > mechanism to effectively operate TCP in userspace, which is what we need > to do, would be very much frowned upon. > > > > Dear All. The question was not how good or bad is Cisco IPSec over TCP, personally I do not like politics of that company. I also can't complain to our IT, because they just do not want to forward any udp port to internal network. They are just happy that cisco manages to wrap udp to tcp, and cisco vpn works on windows. That is all. The problem is that it looks like I can't compile it under F16, and can't find any normal manual in internet. So my question was - if anyone has done it under Fedora16 32bit, and if yes, please share with me your experience. Of course, I can install winxp on virtualbox, and I can use windows version, BUT I do not like it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: cisco vpn because of ipsec over tcp
I am talking about ipsec over TCP. Everything can do ipsec over UDP, but none over TCP. But on my job for the security reason UDP is blocked, cisco vpn can do ipsec over tcp. That is why I asked. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
cisco vpn because of ipsec over tcp
Dear All Have anyone here tried to compile cisco vpn for Fedora 16 - 32 or 64 bit? I need it sometimes and it should support ipsec over tcp, unfortunately nothing in unix can provide it. Thanks for suggestions. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F16: systemd nfs-server.service is absent in "systemctl --all"
Thanks. I totally forgot about that difference. There is loaded, dead, ... and disabled. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F16: systemd nfs-server.service is absent in "systemctl --all"
Dear All I was trying to setup nfs server on fedora 16 and first off all started from nfs-server. I checked "chkconfig" - nothing, then "systemctl --all | grep nfs" - nothing again. Then I searched in "rpm -q nfs-utils -l" and found out that I have it: /lib/systemd/system/nfs-blkmap.service /lib/systemd/system/nfs-idmap.service /lib/systemd/system/nfs-lock.service /lib/systemd/system/nfs-secure-server.service /lib/systemd/system/nfs-secure.service /lib/systemd/system/nfs-server.service /lib/systemd/system/proc-fs-nfsd.mount /lib/systemd/system/var-lib-nfs-rpc_pipefs.mount Why "systemctl --all | grep nfs" doesn't show me nfs-server.service ? Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
irqbalance doesn't balance well x86_64 Fedora 16
Dear All I would like to tell that irqbalance doesn't balance irqs properly: 0:126 0 0 0 IO-APIC-edge timer 1: 2 0 0 0 IO-APIC-edge i8042 8: 1 0 0 0 IO-APIC-edge rtc0 9: 0 0 0 0 IO-APIC-fasteoi acpi 12: 4 0 0 0 IO-APIC-edge i8042 16:644106 0 0 IO-APIC-fasteoi ehci_hcd:usb1 23: 45 0 0 0 IO-APIC-fasteoi ehci_hcd:usb2 40: 0 0 0 0 PCI-MSI-edge PCIe PME 41: 0 0 0 0 PCI-MSI-edge PCIe PME 42: 7882 0 0 53 PCI-MSI-edge ahci 43: 1 0 0 0 PCI-MSI-edge xhci_hcd 44: 0 0 0 0 PCI-MSI-edge xhci_hcd 45: 0 0 0 0 PCI-MSI-edge xhci_hcd 46: 0 0 0 0 PCI-MSI-edge xhci_hcd 47: 0 0 0 0 PCI-MSI-edge xhci_hcd 48: 3158 0 0 0 PCI-MSI-edge i915 49: 35 0 0 0 PCI-MSI-edge eth0 50:253 0 0 0 PCI-MSI-edge snd_hda_intel Package 0: numa_node is 0 cpu mask is 000f (load 0) Cache domain 0: numa_node is 0 cpu mask is 0001 (load 0) CPU number 0 numa_node is 0 (load 0) Interrupt 49 node_num is -1 (ethernet/1) Interrupt 23 node_num is -1 (legacy/1) Cache domain 1: numa_node is 0 cpu mask is 0002 (load 0) CPU number 1 numa_node is 0 (load 0) Interrupt 18 node_num is -1 (legacy/1) Interrupt 16 node_num is -1 (legacy/1) Cache domain 2: numa_node is 0 cpu mask is 0004 (load 0) CPU number 2 numa_node is 0 (load 0) Interrupt 19 node_num is -1 (legacy/1) Interrupt 40 node_num is -1 (legacy/1) Cache domain 3: numa_node is 0 cpu mask is 0008 (load 0) CPU number 3 numa_node is 0 (load 0) Interrupt 42 node_num is -1 (storage/1) Interrupt 41 node_num is -1 (legacy/1) Interrupt 50 node_num is -1 (other/1) Interrupt 11 node_num is -1 (other/1) Interrupt 48 node_num is -1 (other/1) I do not understand why it places i915, eth0 and snd_hda_intel on the same CPU uname -a = 3.1.0-1.fc16.x86_64 #1 SMP Mon Oct 24 12:18:13 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Any thoughts? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Device Audio codec hwC0D0: Realtek and Device Audio codec hwC0D3: Intel on HDA Intel sound
Ok, as long as my sound "onboard" I disabled it, rebooted and enabled it again. So now I got in /sys/devices/pci:00/:00:1b.0/label only: Realtek High Definition Audio Device Where is my Intel HDA ? lspci: 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Device Audio codec hwC0D0: Realtek and Device Audio codec hwC0D3: Intel on HDA Intel sound
Dear All. Recently I checked powertop and the first lines are: 100.0% Device Audio codec hwC0D0: Realtek 100.0% Device Audio codec hwC0D3: Intel I remember that it was only Intel codec. Do I really need - Audio codec hwC0D0: Realtek ? lspci: 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) ... Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel uname: Linux 3.1.0-0.rc10.git0.1.fc16.x86_64 #1 SMP Wed Oct 19 05:02:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Thanks in advance. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: General systemd questions in respect to Fedora project.
On 07/20/2011 09:54 PM, Lennart Poettering wrote: > >> 2. How can one disable it? > > If you build systemd you can leave it out of your build. On Fedora it is > enabled however. > > Lennart > You have just renamed Linux to Window, Fedora Linux is dead. Welcome Fedora Windows. If I will use Linux any more in the future, I promise, I will do everything to remove systemd from any available system. Hopefully, I will manage to fix FreeBSD for my desktop. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: General systemd questions in respect to Fedora project.
On 07/20/2011 12:03 PM, Jeff Spaleta wrote: > hey Lucas, > > Can you point me to the on system manpage and docs for > console-kit-daemon which is running be default on my F15 install? I > can't seem to find the documentation. > > >> From my reading about available systemd roadmapping for systemd-logind > in the context of upstream systemd development systemd-logind is > meant to replace the functionality of provided by the consolekit > deamon. So with that in mind perhaps its best if you take a step back > and dig up the information for console-kit-daemon as its being used in > active Fedora releases to get a baseline understanding of what > systemd-logind is meant to achieve. > > Or you could read: > > https://docs.google.com/document/d/1_ev4f0gwBuvs6SH_N8fN5LO4LV3sbwtJsLq52F_wwpU/edit?hl=en&authkey=CObM_7UI&pli=1 > and the thread started here: > http://lists.freedesktop.org/archives/consolekit/2011-May/000136.html > and the thread started here: > http://lists.freedesktop.org/archives/systemd-devel/2011-May/002166.html > > I think its great your finally taking a good look at what is running > by default in Rawhide. But it would also be a good idea if you took > into account some historical perspective and set your expectations > accordingly with regard to documentation, > > -jef All those links are general words, nothing about "systemd-logind" which is daemon. But I would like to know what does "systemd-logind" do and how. ..."There's a tool "systemd-loginctl" which you can use to introspect the state of it, and manipulate users, sessions and seats."... Where is an explanation of this also ? Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: General systemd questions in respect to Fedora project.
On 07/20/2011 11:45 AM, Johannes Lips wrote: > You were told to move this discussion to the systemd mailing list not to > a freedesktop mailing list. > > http://lists.fedoraproject.org/pipermail/devel/2011-July/154557.html > > > On 07/20/2011 09:40 AM, Lucas wrote: >> Dear All. >> >> In my previous post here I asked about "systemd-logind", which is already >> enabled by default and >> does something no one knows what: >> >> 1. Where is its documentation or man page? >> 2. How can one disable it? >> >> And I was suggested to ask that question in freedesktop mailing list. >> >> Why should I ask my question there if I am asking about Fedora (Rawhide) >> distribution and we do not >> have documentation about this service in Fedora (Rawhide). And we do not >> know how to disable this >> service in Fedora (Rawhide). >> >> Please, I would like to read any answers here in fedoraproject mailing list, >> because I talk about >> Fedora. >> >> >> Thanks. > Ok. Where is located "systemd mailing list" ? Tell me please it URL? Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
General systemd questions in respect to Fedora project.
Dear All. In my previous post here I asked about "systemd-logind", which is already enabled by default and does something no one knows what: 1. Where is its documentation or man page? 2. How can one disable it? And I was suggested to ask that question in freedesktop mailing list. Why should I ask my question there if I am asking about Fedora (Rawhide) distribution and we do not have documentation about this service in Fedora (Rawhide). And we do not know how to disable this service in Fedora (Rawhide). Please, I would like to read any answers here in fedoraproject mailing list, because I talk about Fedora. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd-logind - I need to know more about it
On 07/19/2011 08:22 PM, Bill Nottingham wrote: > Lucas (macach...@gmail.com) said: >> I found the following in internet: >> >> The good news for embeded folks: all of this will be implemented in a >> tiny new dbus service "systemd-logind", which can easily be removed for >> minimal setups, when tracking unprivileged user logins is unnecessary. >> >> Can someone please, tell me: >> 1. how can I easily remove it? Because it by default always enabled. >> 2. where is documentation about systemd-logind? How does it work and what >> does it do? > > I strongly suggest you take this to the systemd mailing list. For #1, > they're taking patches for making it compile-time. For #2, that's the > right place anyway to start... > > Bill The problem is that systemd-logind enabled by default, without any documentation and it is not easy to disable it. But it is already in and already conflicts with kernel. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
systemd-logind - I need to know more about it
Dear All I found the following in internet: The good news for embeded folks: all of this will be implemented in a tiny new dbus service "systemd-logind", which can easily be removed for minimal setups, when tracking unprivileged user logins is unnecessary. Can someone please, tell me: 1. how can I easily remove it? Because it by default always enabled. 2. where is documentation about systemd-logind? How does it work and what does it do? Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: on /etc/sysconfig
You know, I am not really developer, I just a user and my laptop starts only Xorg, Apache, DNS proxy (to filter web adv sites), Privoxy, Perl and something else. Right now systemd can't boot my system up, it hangs everything. So I fixed up upstart (mainly to be able use selinux and update the system) and I want to say it works and works as usually good. I do not see any reason why should I use systemd if I can use upstart without any problems and do not have any configuration confusion now and in the future. If I like some things in Fedora, I do not think I have to get all of it. This is my thoughts. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: One big old problem and one new with Rawhide
On 07/17/2011 12:49 AM, Lucas wrote: > One big problem is that my laptop can't go through systemd startup with > selinux enabled. > Boot hangs at random points - setup keyboard, stdio syslog bridge, kernel > variables. Laptop just > hangs, nothing happens and all I can do it turn it off. The only way is to > add "selinux=0". > > > > The second one that raises today - I can't log in at all - nor with root nor > with user. > I reported yesterday about: > > [ 37.654015] [ INFO: possible recursive locking detected ] > [ 37.654015] 3.0-0.rc7.git0.1.fc16.i686 #1 > [ 37.654015] - > [ 37.654015] systemd-logind/651 is trying to acquire lock: > > And yesterday I was able to log into user and root account, today I can't - > it looks like it checks > the password, because it reports if it is wrong, when I type the right one it > hangs again. May be > system can't start console (I was trying to do it in level 3). > > What I can do with it? > Need advice. > Thanks. Ok. I have managed to boot properly. I use upstart. No errors, quickly and reliably. So I going to transfer everything for upstart from fedora 14. It works and I going to use it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: One big old problem and one new with Rawhide
On 07/17/2011 01:03 AM, Tom London wrote: > On Sat, Jul 16, 2011 at 1:49 PM, Lucas wrote: >> One big problem is that my laptop can't go through systemd startup with >> selinux enabled. >> Boot hangs at random points - setup keyboard, stdio syslog bridge, kernel >> variables. Laptop just >> hangs, nothing happens and all I can do it turn it off. The only way is to >> add "selinux=0". > > Its usually better to add "enforcing=0" rather than "selinux=0". > "enforcing=0" keeps files appropriately labeled. "enforcing=0" doesn't help me, system hangs. I installed XFCE spin and then upgrade it to Rawhide, I do not have gnome because I hate it. I turned off enforcing when I start to test it, but selinux doesn't report anything, may be selinux can't do its job with new kernels, because system hangs in different points. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
One big old problem and one new with Rawhide
One big problem is that my laptop can't go through systemd startup with selinux enabled. Boot hangs at random points - setup keyboard, stdio syslog bridge, kernel variables. Laptop just hangs, nothing happens and all I can do it turn it off. The only way is to add "selinux=0". The second one that raises today - I can't log in at all - nor with root nor with user. I reported yesterday about: [ 37.654015] [ INFO: possible recursive locking detected ] [ 37.654015] 3.0-0.rc7.git0.1.fc16.i686 #1 [ 37.654015] - [ 37.654015] systemd-logind/651 is trying to acquire lock: And yesterday I was able to log into user and root account, today I can't - it looks like it checks the password, because it reports if it is wrong, when I type the right one it hangs again. May be system can't start console (I was trying to do it in level 3). What I can do with it? Need advice. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[ INFO: possible recursive locking detected ] systemd-logind/651 is trying to acquire lock:
Dear All.
Just updated and got the following in dmesg:
[ 37.653381] =
[ 37.654015] [ INFO: possible recursive locking detected ]
[ 37.654015] 3.0-0.rc7.git0.1.fc16.i686 #1
[ 37.654015] -
[ 37.654015] systemd-logind/651 is trying to acquire lock:
[ 37.654015] (&ep->mtx){+.+.+.}, at: []
ep_scan_ready_list+0x32/0x154
[ 37.654015]
[ 37.654015] but task is already holding lock:
[ 37.654015] (&ep->mtx){+.+.+.}, at: [] sys_epoll_ctl+0x103/0x481
[ 37.654015]
[ 37.654015] other info that might help us debug this:
[ 37.654015] Possible unsafe locking scenario:
[ 37.654015]
[ 37.654015]CPU0
[ 37.654015]
[ 37.654015] lock(&ep->mtx);
[ 37.654015] lock(&ep->mtx);
[ 37.654015]
[ 37.654015] *** DEADLOCK ***
[ 37.654015]
[ 37.654015] May be due to missing lock nesting notation
[ 37.654015]
[ 37.654015] 2 locks held by systemd-logind/651:
[ 37.654015] #0: (epmutex){+.+.+.}, at: []
sys_epoll_ctl+0xbe/0x481
[ 37.654015] #1: (&ep->mtx){+.+.+.}, at: []
sys_epoll_ctl+0x103/0x481
[ 37.654015]
[ 37.654015] stack backtrace:
[ 37.654015] Pid: 651, comm: systemd-logind Not tainted
3.0-0.rc7.git0.1.fc16.i686 #1
[ 37.654015] Call Trace:
[ 37.654015] [] ? printk+0x2d/0x2f
[ 37.654015] [] __lock_acquire+0x811/0xb63
[ 37.654015] [] ? sched_clock+0x8/0xb
[ 37.654015] [] ? sched_clock_local+0x10/0x18b
[ 37.654015] [] ? ep_scan_ready_list+0x32/0x154
[ 37.654015] [] lock_acquire+0xad/0xe4
[ 37.654015] [] ? ep_scan_ready_list+0x32/0x154
[ 37.654015] [] __mutex_lock_common+0x49/0x2ee
[ 37.654015] [] ? ep_scan_ready_list+0x32/0x154
[ 37.654015] [] ? __might_sleep+0x29/0xfb
[ 37.654015] [] ? mark_lock+0x26/0x1f2
[ 37.654015] [] mutex_lock_nested+0x43/0x49
[ 37.654015] [] ? ep_scan_ready_list+0x32/0x154
[ 37.654015] [] ep_scan_ready_list+0x32/0x154
[ 37.654015] [] ? ep_remove+0x9b/0x9b
[ 37.654015] [] ep_poll_readyevents_proc+0x14/0x16
[ 37.654015] [] ep_call_nested.constprop.2+0x6d/0x9a
[ 37.654015] [] ? ep_scan_ready_list+0x154/0x154
[ 37.654015] [] ep_eventpoll_poll+0x45/0x55
[ 37.654015] [] sys_epoll_ctl+0x1ff/0x481
[ 37.654015] [] ? ep_send_events_proc+0xd5/0xd5
[ 37.654015] [] syscall_call+0x7/0xb
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Security updates for Firefox 4 in F-15
> You are of course free to do this if you choose, but Fedora is a > package managed system. Doing this you lose a number of benefits of a > package management system. For me the most important benefit is OS independent software, especially web browser. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Security updates for Firefox 4 in F-15
To All I do not understand what are talking about. Firefox and Thunderbird now does not require any kind of linux distribution attention. Download bz2 archive from their site, unpack it to any directory (for example - /usr/local/share) and start it. It will use USER settings in home directory and if you decide to delete it later - just delete it. Previous version will perfectly work with the new one. Now it is not necessary to wait for update - do it you self. I did - it works just fine. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
SLIM + patch = CK works
So I applied this patch
cut--
Index: slim-1.3.2/app.cpp
--- slim-1.3.2-orig/app.cpp
+++ slim-1.3.2/app.cpp
@@ -236,7 +236,6 @@
pam.start("slim");
pam.set_item(PAM::Authenticator::TTY, DisplayName);
pam.set_item(PAM::Authenticator::Requestor, "root");
-pam.set_item(PAM::Authenticator::Host, "localhost");
}
catch(PAM::Exception& e){
cut--
, compiled slim and now CK activates the user.
There is some problems still - xfce doesn't allow me to "reboot" (actually it
understands it like
shutdown), but I think it is different song.
I will be appreciate if one with more experience can check it also.
Thanks.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Orphaning Slim, To Jan Kaluža for Fedora 16 Rawhide
I know that you was going to orphan Slim, but I would like to ask you for some
additional help with it.
I found that slim currently works with pam but it looks like not properly.
In the March post in XFCE lists there is the message:
*
Hi,
Some days ago i tried to replace gdm with slim, but this gave me the
problem that one could not access the system devices (soundcard, gfx hardware
opengl missing etc.) properly, because of broken pam/consolekit support in slim.
then I did the following:
1. applied a slim-1.3.2-ck.patch
cut--
Index: slim-1.3.2/app.cpp
--- slim-1.3.2-orig/app.cpp
+++ slim-1.3.2/app.cpp
@@ -236,7 +236,6 @@
pam.start("slim");
pam.set_item(PAM::Authenticator::TTY, DisplayName);
pam.set_item(PAM::Authenticator::Requestor, "root");
-pam.set_item(PAM::Authenticator::Host, "localhost");
}
catch(PAM::Exception& e){
cut--
2. appended
"sessionrequiredpam_ck_connector.so"
to the slim.pam file
with these two fixes f14's slim plays just nice here.
maybe one should also update the symlink to slims default-background image to
reflect the current release artwork.
***
Can you please compile SLIM last time with this patch, so may be it starts to
use PAM and CK will
activate user.
Thanks in advance
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
appletalk+psnap+ipx modules in the kernel-3.0-0.rc3.git5.1.fc16
Dear All I have installed the latest kernel from koji and found out that now I have 3 new modules: appletalk psnap ipx I know what is IPX. But do we really need to have AppleTalk always loaded in the kernel? What is "psnap"? Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: laptop LCD color temperature request
On 06/16/2011 08:10 PM, Jeff Spaleta wrote: > On Thu, Jun 16, 2011 at 7:17 AM, Lucas wrote: >> Dear All. >> >> Since Fedora 13 I am trying to replace my old OpenSuse 11.1 with Fedora and >> always failed. >> The problem is I can't use my laptop LCD picture. After about 20-30 minutes >> I feel eye strain. > > Have you looked at installing and configuring redshift on user login? > yum info redshift > > > -jef Thanks a lot for your advice, I will play with it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
laptop LCD color temperature request
Dear All. Since Fedora 13 I am trying to replace my old OpenSuse 11.1 with Fedora and always failed. The problem is I can't use my laptop LCD picture. After about 20-30 minutes I feel eye strain. So, today I've come across this discussion about LED backlight and similar eyes effect on Mac. https://discussions.apple.com/thread/1677617?start=0&tstart=0 On the last page one gave a solution which may helps (may not, may be): 1. Changed the colour temperature to exactly 5000K via the calibration in Displays. I know that Fedora has color management and I suppose we can change temperature with it. Please, who can, generate profile for different color temperature - for 3000K 4000K 5000K 6000K I can't do this, I do not know how. But I want to check if it helps. Thanks in advance. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16
I checked it again - it is not me. Boot stops at random points - for example last time it stops at: "Configure read-only root support" So it can't even relabel FS, because it happens mush farther. But option "selinux=0" solves this problem. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16
On 06/14/2011 09:57 PM, Lennart Poettering wrote:
> On Tue, 14.06.11 21:32, Lucas (macach...@gmail.com) wrote:
>
>>
>> On 06/14/2011 06:53 PM, Lennart Poettering wrote:
>>> On Tue, 14.06.11 18:48, Lucas (macach...@gmail.com) wrote:
>>>
>>>>> Do you see any errors?
>>>>
>>>> Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling,
>>>> then reboot and process
>>>> stops on: Starting Remount Root FS. And nothing more, no errors, systemd
>>>> hung.
>>>
>>> Boot with "systemd.log_level=debug systemd.log_target=kmsg
>>> rd_NO_PLYMOUTH plymouth.enable=0" on the kernel cmdline, and paste the
>>> last output generated output on the console somewhere, possibly take a
>>> photo of it, and upload it somewhere.
>>>
>>> Lennart
>>>
>>
>> Did it, there is no any kind of debug messages on the screen.
>
> Did you also remove "quiet" and "rhgb" from the kernel cmdline? If you
> leave that in all output will not be visible.
>
> Lennart
>
Actually I never use them ("quiet" and "rhgb"), I prefer to see what is going
on, and that is why I
know where the boot stops. There is no any debug or error messages.
May be I know what is going on. May be I did something.
I will let you know latter.
Thanks
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16
On 06/14/2011 06:53 PM, Lennart Poettering wrote: > On Tue, 14.06.11 18:48, Lucas (macach...@gmail.com) wrote: > >>> Do you see any errors? >> >> Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling, >> then reboot and process >> stops on: Starting Remount Root FS. And nothing more, no errors, systemd >> hung. > > Boot with "systemd.log_level=debug systemd.log_target=kmsg > rd_NO_PLYMOUTH plymouth.enable=0" on the kernel cmdline, and paste the > last output generated output on the console somewhere, possibly take a > photo of it, and upload it somewhere. > > Lennart > Did it, there is no any kind of debug messages on the screen. Boot process just stops. I updated to libselinux-2.0.102-6.fc16 and boot starts to go faster, but any way after few successful times, it starts to stop again. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16
On 06/14/2011 04:38 PM, Daniel J Walsh wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/14/2011 06:37 AM, Lucas wrote: >> On 06/14/2011 02:10 PM, Frank Murphy wrote: >>> On 14/06/11 11:02, Lucas wrote: >>> >>>> The only possible way to boot is to add "selinux=0". >>>> Especially for Daniel J Walsh, the addition of "enforcing=0" doesn't make >>>> any difference - boot stops. >>>> >>>> Thanks. >>> >>> Last time I had similar problem, ended up: >>> >>> rpm -e --nodeps selinux-policy selinux-policy-targeted >>> yum install selinux-policy selinux-policy-targeted >>> touch /.autorelabel; reboot >>> >>> and then all was ok. >>> ymmv. >>> >>> >> >> In my case relabeling did not help at all. > > > > Lucas if you run > > yum reinstall selinux-policy-targeted > > Do you see any errors? Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling, then reboot and process stops on: Starting Remount Root FS. And nothing more, no errors, systemd hung. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: please stop trying to take over the world :)
Is not it easy to remove everything from: default.target basic.target graphical.target ... and then add whatever we want to start or to execute or mount? I do not really care what systemd CAN do, but really care what it is doing on my system. So, may be some cleaning will be the wise solution. One would like to eat fish Eat one's cake and have it И волки сыты и овцы целы. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16
On 06/14/2011 02:10 PM, Frank Murphy wrote: > On 14/06/11 11:02, Lucas wrote: > >> The only possible way to boot is to add "selinux=0". >> Especially for Daniel J Walsh, the addition of "enforcing=0" doesn't make >> any difference - boot stops. >> >> Thanks. > > Last time I had similar problem, ended up: > > rpm -e --nodeps selinux-policy selinux-policy-targeted > yum install selinux-policy selinux-policy-targeted > touch /.autorelabel; reboot > > and then all was ok. > ymmv. > > In my case relabeling did not help at all. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16
My laptop can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16 - the boot process just stops at random points and CPU usage goes high. systemd-28-3.fc16 and kernel-3.0-0.rc2.git0.2.fc16 - did not have this behavior. The only possible way to boot is to add "selinux=0". Especially for Daniel J Walsh, the addition of "enforcing=0" doesn't make any difference - boot stops. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Are 3.0 kernels working for anyone?
On 06/13/2011 04:33 PM, Daniel J Walsh wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/11/2011 03:11 PM, Lucas wrote: >> On 06/11/2011 11:00 PM, Andre Robatino wrote: >>> Lucas gmail.com> writes: >>> >>>> I use systemd-28-3.fc16.i686 and updated it when it became available, >>>> but still have real problems >>>> with boot. >>>> If it stops it happens definitely in systemd job - when it is starting >>>> services. And I can't find any errors. >>>> More important that I have changed selinux to permissive - there is >>>> no difference. I can boot only with selinux=0. >>>> I have tried upstart - it works without any problems. >>> >>> If you've been using selinux=0, try doing a relabeling. I did "touch >>> /.autorelabel" and rebooted without selinux=0, but got dropped to >>> single-user mode. I then did "restorecon -R -v /" and rebooted successfully >>> without selinux=0. After that, I did "touch /.autorelabel" again and was >>> able >>> to successfully reboot without selinux=0, without getting dropped to >>> single-user mode, and booting has been normal since. (This is all after >>> updating to the latest systemd.) >>> >> >> Actually it does relabel by it self after boot with option "selinux=0", and >> of course I did relabel. >> It manages to stop anyway. But not always, sometime I can boot, sometime not. >> > Does booting with enforcing=0 work? > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk32A5UACgkQrlYvE4MpobOh1QCgmZ3uYWh4KY58Z4460HQrzmrX > PTMAnj6bM8Xla6SDEun9p41IogiksPsz > =MCU1 > -END PGP SIGNATURE- I have not tried to boot with enforcing=0, because I solved this problem removing b43 driver (blacklist) and I also removed some systemd services (md and something else - I do not remember exactly, as rawhide on different HDD) So now rawhide boots properly. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On 06/13/2011 03:27 PM, Alexander Kurtakov wrote: > On 02:12:43 PM Monday, June 13, 2011 Lucas wrote: >> >PLEASE give us a option for systems upgraded with yum >> >NOT USING "systemd" and force "upstart" as before >> > >> >* the system is running since years >> >* every dist-upgrade via yum was no problem >> >* now see screenshot >> >* WTF is there to relabel if started with "selinux=0"-kernel-param >> > >> >WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE >> >THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER >> >ON UPDATES >> > >> >I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING >> >FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START >> >IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS >> >> My opinion: >> >> You know what was wrong, sir - you put on your 20 servers Fedora - free >> software. And that means that you can't get personal support, because most >> of real developers are employees of Redhat. >> Have you notice that they use Fedora like a toy, to play with, to test a >> new ideas, to try new things on it. Developers do not count it like >> anything serious - it is a toy for them. Today they decided that upstart >> is wrong and they need systemd, tomorrow they can change their mind, they >> going to implement btrfs soon. Fedora is a test toy. Do not expect any >> respect for the long time use. And that is why linux is not so popular - >> it has always been a TOY and nothing more. Consider to use something >> different for your server or solve your problems by your self. > > The generalization that we(Red Hat associates) see Fedora as a toy is > INSULTING. > Do you know how many of us are spending their free time to get Fedora better? > Do you know how many of us have worked on Fedora(or related things) before > working for Red Hat? > Do you know how big part of the Red Hat work is available in Fedora without > being available in RHEL? > > Yes, we have opinions and we stick to them - most of the time without our > managers even know - because it's smth we do on our own. Speaking personally > everyone can accuse me of not fullfilling some user's wishes (which I'm not > oblided to do) but someone saying that I(we) look at Fedora as a toy is really > hurting a lot of feelings. > > Alexander Kurtakov > >> >> Thanks. What do you think I thought when found that udev was compiled: * Fri May 20 2011 Harald Hoyer 170-1 - version 170 - removed /sbin/start_udev REMOVED /sbin/start_udev - this means that upstart wont be able to start udev without manual tweak. Upstart reads rc.sysinit and there is still "/sbin/start_udev". And also this means that any one who will try to use upstart in Fedora 16 (now rawhide) wont get udev works. What do you think I thought about all of this? I wont be really upset if I'll lose upstart, I can clean systemd as I need, but the idea is wrong. Systemd is just a project, project which may tomorrow be changed, so why all others have to follow. It should be like selinux, which can be easily disabled "selinux=0". That is what I think. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On 06/13/2011 11:40 AM, Reindl Harald wrote: > > > Am 13.06.2011 09:37, schrieb Michal Schmidt: >> On Mon, 13 Jun 2011 11:26:46 +0400 Lucas wrote: >>> Have you notice that they use Fedora like a toy, to play with, to >>> test a new ideas, to try new things on it. Developers do not count it >>> like anything serious - it is a toy for them. Today they decided that >>> upstart is wrong and they need systemd, tomorrow they can change >>> their mind, they going to implement btrfs soon. Fedora is a test toy. >>> Do not expect any respect for the long time use. And that is why >>> linux is not so popular - it has always been a TOY and nothing more. >>> Consider to use something different for your server or solve your >>> problems by your self. >> >> I disagree. Fedora is much more than a toy to me. I use it every day >> for work. I hope it is the same for the most of the developers. > > and if not they should be quickly sorted out before shortly after > systemd will get stable sooner or later the next one comes out > with a new replacement and all peopole forget how long sysvinit > worked very well and that this should be the measure for quality > > Also, be prepared - Fedora 13 end of life on 2011-06-24, next is yours Fedora 14 and it will be very soon. After that time no one will talk to you. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
>PLEASE give us a option for systems upgraded with yum >NOT USING "systemd" and force "upstart" as before > >* the system is running since years >* every dist-upgrade via yum was no problem >* now see screenshot >* WTF is there to relabel if started with "selinux=0"-kernel-param > >WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE >THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER >ON UPDATES > >I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING >FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START >IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS My opinion: You know what was wrong, sir - you put on your 20 servers Fedora - free software. And that means that you can't get personal support, because most of real developers are employees of Redhat. Have you notice that they use Fedora like a toy, to play with, to test a new ideas, to try new things on it. Developers do not count it like anything serious - it is a toy for them. Today they decided that upstart is wrong and they need systemd, tomorrow they can change their mind, they going to implement btrfs soon. Fedora is a test toy. Do not expect any respect for the long time use. And that is why linux is not so popular - it has always been a TOY and nothing more. Consider to use something different for your server or solve your problems by your self. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and "Sandy Bridge" graphics
On 06/12/2011 10:02 PM, Reindl Harald wrote: > > > Am 12.06.2011 19:28, schrieb Lucas: > >> Strange, I did exactly the same thing with Fedora 14, I add new kernel, >> changed xorg and intel driver. >> But I have i686. > > mhh - strange - an trying to update glibc results in chaos > "Datei oder Verzeichnis nicht gefunden" means "file not found" in english > yes as advanced user i was able to repair this with some luck > > updating only the kernel/kernel-headers/kernel-devel results in > no longer able to build kernel-modules (vmware-workstation) > > and this all for a graphics-driver? > i remember times where feodra updated the kernel in the lifetime > of a supported release and now you can do nothing if you do not > want replace of "upstart" by "systemd", if systemd would not > be hardly activated in F15 a dist-upgrade would be no problem > > BULLSHIT BULLSHIT BULLSHIT > >> scripts/basic/fixdep: /lib64/libc.so.6: version `GLIBC_2.14' not found >> (required by scripts/basic/fixdep) >> make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driverLog.o] Fehler 1 >> make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Fehler 2 >> make[1]: Leaving directory `/usr/src/kernels/2.6.38.8-31.fc15.x86_64' >> make: *** [vmmon.ko] Fehler 2 >> make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' > > [master 1f5151f] saving uncommitted changes in /etc prior to yum run > 1 files changed, 29 insertions(+), 0 deletions(-) > create mode 100644 yum.repos.d/fedora-15.repo >Aktualisieren : glibc-common-2.14-1.x86_64 >1/24 >Aktualisieren : glibc-2.14-1.x86_64 >2/24 > Error: Cannot open file kernel-headers-2.6.38.8-31.fc15.x86_64.rpm: [Errno 2] > Datei oder Verzeichnis nicht > gefunden: 'kernel-headers-2.6.38.8-31.fc15.x86_64.rpm' > TypeError: an integer is required > Fehler: Python-Callback of 0x43bcab8>> fehlgeschlagen, abbrechen! > > > [root@rh:/downloads]$ rpm -Uvh --force *.rpm > Warnung: libdrm-2.4.25-1.fc15.x86_64.rpm: Header V3 RSA/SHA256 Signature, > Schlüssel-ID 069c8460: NOKEY > Vorbereiten... ### [100%] > 1:glibc-common ### [ > 8%] > 2:glibc ### [ > 15%] > Fehler: Öffnen von xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm > fehlgeschlagen: Datei oder Verzeichnis nicht > gefunden > Fehler: Öffnen von linux-firmware-20110601-1.fc15.noarch.rpm fehlgeschlagen: > Datei oder Verzeichnis nicht gefunden > Fehler: Öffnen von kernel-headers-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: > Datei oder Verzeichnis nicht gefunden > Fehler: Öffnen von glibc-headers-2.14-1.x86_64.rpm fehlgeschlagen: Datei oder > Verzeichnis nicht gefunden > Fehler: Öffnen von glibc-devel-2.14-1.x86_64.rpm fehlgeschlagen: Datei oder > Verzeichnis nicht gefunden > Fehler: Öffnen von kernel-devel-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: > Datei oder Verzeichnis nicht gefunden > Fehler: Öffnen von kernel-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei > oder Verzeichnis nicht gefunden > Fehler: Öffnen von libdrm-2.4.25-1.fc15.x86_64.rpm fehlgeschlagen: Datei oder > Verzeichnis nicht gefunden > Fehler: Öffnen von xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm > fehlgeschlagen: Datei oder Verzeichnis nicht gefunden > Fehler: Öffnen von xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm > fehlgeschlagen: Datei oder Verzeichnis nicht gefunden > Fehler: Öffnen von > xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64.rpm > fehlgeschlagen: Datei oder > Verzeichnis nicht gefunden > > Wait a second, have you enable Fedora 15 repository? If you did, yum should find all dependences in there without your help. You need just type "yum update xorg-x11-drv-intel". Everything should be there. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and "Sandy Bridge" graphics
On 06/12/2011 09:18 PM, Reindl Harald wrote: > > > Am 12.06.2011 19:14, schrieb Lucas: >> On 06/12/2011 09:12 PM, Reindl Harald wrote: > >> Look, to be able to use Sandy Bridge you need - i915 driver, kernel, and >> Xorg. >> >> You can add Fedora 15 repository and update only kernel, Xorg and intel >> driver. >> All of this you can download from koji and install manually. > > i tried this before my first post > this is simply not true because this forces glibc as requirement > > --> Führe Transaktionsprüfung aus > ---> Paket kernel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu > werden > ---> Paket kernel-devel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert > zu werden > ---> Paket kernel-headers.x86_64 0:2.6.38.8-31.fc15 markiert, um > aktualisiert zu werden > ---> Paket libdrm.x86_64 0:2.4.25-1.fc15 markiert, um aktualisiert zu werden > ---> Paket linux-firmware.noarch 0:20110601-1.fc15 markiert, um aktualisiert > zu werden > ---> Paket xorg-x11-drv-intel.x86_64 0:2.14.0-6.fc15 markiert, um > aktualisiert zu werden > --> Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: > xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 > ---> Paket xorg-x11-server-Xorg.x86_64 0:1.10.1-14.fc15 markiert, um > aktualisiert zu werden > --> Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: > xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 > ---> Paket xorg-x11-server-common.x86_64 0:1.10.1-14.fc15 markiert, um > aktualisiert zu werden > --> Abhängigkeitsauflösung beendet > Fehler: Package: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 > (/xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64) > Requires: libc.so.6(GLIBC_2.14)(64bit) > Fehler: Package: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 > (/xorg-x11-drv-intel-2.14.0-6.fc15.x86_64) > Requires: libc.so.6(GLIBC_2.14)(64bit) > Sie können versuchen --skip-broken zu benutzen, um das Problem zu umgehen. > You could try running: rpm -Va --nofiles --nodigest > [root@rh:/downloads]$ ls > insgesamt 40M > drwxr-xr-x 16 harry verwaltung 4,0K 2011-06-09 10:58 teletest > -rw-r--r-- 1 harry verwaltung 23M 2011-06-12 19:17 > kernel-2.6.38.8-31.fc15.x86_64.rpm > -rw-r--r-- 1 harry verwaltung 6,8M 2011-06-12 19:17 > kernel-devel-2.6.38.8-31.fc15.x86_64.rpm > -rw-r--r-- 1 harry verwaltung 739K 2011-06-12 19:16 > kernel-headers-2.6.38.8-31.fc15.x86_64.rpm > -rw-r--r-- 1 root root69K 2011-04-15 05:54 > libdrm-2.4.25-1.fc15.x86_64.rpm > -rw-r--r-- 1 harry verwaltung 8,3M 2011-06-12 19:17 > linux-firmware-20110601-1.fc15.noarch.rpm > -rw-r--r-- 1 root root 202K 2011-04-28 19:13 > xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm > -rw-r--r-- 1 root root77K 2011-05-05 22:55 > xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm > -rw-r--r-- 1 root root 1,4M 2011-05-05 22:52 > xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm > > I probably already had libc.so.6 in Fedora 14. Because I did not have any problem with update process. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and "Sandy Bridge" graphics
On 06/12/2011 09:18 PM, Reindl Harald wrote: > > > Am 12.06.2011 19:14, schrieb Lucas: >> On 06/12/2011 09:12 PM, Reindl Harald wrote: > >> Look, to be able to use Sandy Bridge you need - i915 driver, kernel, and >> Xorg. >> >> You can add Fedora 15 repository and update only kernel, Xorg and intel >> driver. >> All of this you can download from koji and install manually. > > i tried this before my first post > this is simply not true because this forces glibc as requirement > > --> Führe Transaktionsprüfung aus > ---> Paket kernel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu > werden > ---> Paket kernel-devel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert > zu werden > ---> Paket kernel-headers.x86_64 0:2.6.38.8-31.fc15 markiert, um > aktualisiert zu werden > ---> Paket libdrm.x86_64 0:2.4.25-1.fc15 markiert, um aktualisiert zu werden > ---> Paket linux-firmware.noarch 0:20110601-1.fc15 markiert, um aktualisiert > zu werden > ---> Paket xorg-x11-drv-intel.x86_64 0:2.14.0-6.fc15 markiert, um > aktualisiert zu werden > --> Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: > xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 > ---> Paket xorg-x11-server-Xorg.x86_64 0:1.10.1-14.fc15 markiert, um > aktualisiert zu werden > --> Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: > xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 > ---> Paket xorg-x11-server-common.x86_64 0:1.10.1-14.fc15 markiert, um > aktualisiert zu werden > --> Abhängigkeitsauflösung beendet > Fehler: Package: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 > (/xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64) > Requires: libc.so.6(GLIBC_2.14)(64bit) > Fehler: Package: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 > (/xorg-x11-drv-intel-2.14.0-6.fc15.x86_64) > Requires: libc.so.6(GLIBC_2.14)(64bit) > Sie können versuchen --skip-broken zu benutzen, um das Problem zu umgehen. > You could try running: rpm -Va --nofiles --nodigest > [root@rh:/downloads]$ ls > insgesamt 40M > drwxr-xr-x 16 harry verwaltung 4,0K 2011-06-09 10:58 teletest > -rw-r--r-- 1 harry verwaltung 23M 2011-06-12 19:17 > kernel-2.6.38.8-31.fc15.x86_64.rpm > -rw-r--r-- 1 harry verwaltung 6,8M 2011-06-12 19:17 > kernel-devel-2.6.38.8-31.fc15.x86_64.rpm > -rw-r--r-- 1 harry verwaltung 739K 2011-06-12 19:16 > kernel-headers-2.6.38.8-31.fc15.x86_64.rpm > -rw-r--r-- 1 root root69K 2011-04-15 05:54 > libdrm-2.4.25-1.fc15.x86_64.rpm > -rw-r--r-- 1 harry verwaltung 8,3M 2011-06-12 19:17 > linux-firmware-20110601-1.fc15.noarch.rpm > -rw-r--r-- 1 root root 202K 2011-04-28 19:13 > xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm > -rw-r--r-- 1 root root77K 2011-05-05 22:55 > xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm > -rw-r--r-- 1 root root 1,4M 2011-05-05 22:52 > xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm > > Strange, I did exactly the same thing with Fedora 14, I add new kernel, changed xorg and intel driver. But I have i686. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and "Sandy Bridge" graphics
On 06/12/2011 09:12 PM, Reindl Harald wrote: > > > Am 12.06.2011 19:03, schrieb drago01: >> On Sun, Jun 12, 2011 at 6:59 PM, Reindl Harald >> wrote: > >>> you said "upstart is still maintained and shipped, you should be able to >>> install and use it" - so how and why damned must be a init-replace >>> in a early state forced on a existing system? >> >> That was the case in F14, now we are making the switch. For people >> that for whatever reasons want upstart it is still here. But for the >> rest we move on ... >> >> But please don't start yet another systemd flamewar we had enough of them > > if will not start a flamewar i still have not the time yet to verify > a couple of services/service-orders and it is useless for me making > a 30 second reboot 2 seconds faster, so i like to use the old init-system > and have NO IDEA how to do this and that is why a UPGRADE should not > forcing switch essential core-systems if not really needed > > Look, to be able to use Sandy Bridge you need - i915 driver, kernel, and Xorg. You can add Fedora 15 repository and update only kernel, Xorg and intel driver. All of this you can download from koji and install manually. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Are 3.0 kernels working for anyone?
Ok, it looks like I have managed to fix it. I have blacklisted "b43" and removed rpc and some other things. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Are 3.0 kernels working for anyone?
On 06/11/2011 11:00 PM, Andre Robatino wrote: > Lucas gmail.com> writes: > >> I use systemd-28-3.fc16.i686 and updated it when it became available, >> but still have real problems >> with boot. >> If it stops it happens definitely in systemd job - when it is starting >> services. And I can't find any errors. >> More important that I have changed selinux to permissive - there is >> no difference. I can boot only with selinux=0. >> I have tried upstart - it works without any problems. > > If you've been using selinux=0, try doing a relabeling. I did "touch > /.autorelabel" and rebooted without selinux=0, but got dropped to > single-user mode. I then did "restorecon -R -v /" and rebooted successfully > without selinux=0. After that, I did "touch /.autorelabel" again and was able > to successfully reboot without selinux=0, without getting dropped to > single-user mode, and booting has been normal since. (This is all after > updating to the latest systemd.) > Actually it does relabel by it self after boot with option "selinux=0", and of course I did relabel. It manages to stop anyway. But not always, sometime I can boot, sometime not. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Are 3.0 kernels working for anyone?
On 06/11/2011 08:42 PM, Bruno Wolff III wrote: > On Sat, Jun 11, 2011 at 20:47:41 +0400, > Lucas wrote: >> >> I use systemd-28-3.fc16.i686 and updated it when it became available, but >> still have real problems >> with boot. >> If it stops it happens definitely in systemd job - when it is starting >> services. >> And I can't find any errors. >> More important that I have changed selinux to permissive - there is no >> difference. I can boot only >> with selinux=0. >> I have tried upstart - it works without any problems. > > You probably need to rebuild the initramfs file for your kernel. One way > to do it is to uninstall the latest kernel and then reinstall it. (I am not > sure if that break things if that is the kernel you are running. So you > might want to boot with an older one to do this.) Doesn't work that way, just checked. Stops in different points. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Are 3.0 kernels working for anyone?
On 06/11/2011 08:35 PM, Tom London wrote: > On Sat, Jun 11, 2011 at 9:29 AM, Lucas wrote: >> >> I can only boot if selinux is disabled - "selinux=0" in grub. Otherwise boot >> always stops in >> different moments. >> I can't figured out which problem is this - selinux or systemd? >> -- > > Does this sound like it? https://bugzilla.redhat.com/show_bug.cgi?id=711015 > > If so, you need a newer systemd. systemd-28-3.fc16.x86_64 "works for me". > > tom I use systemd-28-3.fc16.i686 and updated it when it became available, but still have real problems with boot. If it stops it happens definitely in systemd job - when it is starting services. And I can't find any errors. More important that I have changed selinux to permissive - there is no difference. I can boot only with selinux=0. I have tried upstart - it works without any problems. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Are 3.0 kernels working for anyone?
I can only boot if selinux is disabled - "selinux=0" in grub. Otherwise boot always stops in different moments. I can't figured out which problem is this - selinux or systemd? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: please stop trying to take over the world :)
On 06/10/2011 08:42 PM, Denys Vlasenko wrote: > On Fri, 2011-06-10 at 15:36 +0200, Michal Schmidt wrote: >>> Why does systemd link against libpam? >>> systemd does logins now, not /bin/login or gdm or ...? >> >> to implement PAMName= (man systemd.exec) > > I don't see any users of this feature on my F15. > I searched with Google and come up empty too. > > But anyway, assuming it's a useful feature, why it has to be done by > systemd? > > I looked at implementation. > systemd-26/src/execute.c::setup_pam(): > > /* We set up PAM in the parent process, then fork. The child > * will then stay around until killed via PR_GET_PDEATHSIG or > * systemd via the cgroup logic. It will then remove the PAM > * session again. The parent process will exec() the actual > * daemon. We do things this way to ensure that the main PID > * of the daemon is the one we initially fork()ed. */ > > I don't see any attempt to free at least something in the child. > So, systemd forks a process with eleven megabyte of malloced stuff > to act just as a babysitter - wait for parent to die, call pam_end, > exit? > For how long will it hang around in the system - possibly days? > > Yes, COW, so not all of these eleven megabytes will be around... > ...at first, until parent execs, or modifies sufficiently many pages > so that most of them are copied. > > But memory consumption is not really the gist of my argument, it's: > why systemd tries to be all things for all people? > > Why it has to care about PAM? I think most tools which need it do it > themselves, and we can write a small, really small helper for those > which don't. > > >>> libwrap? systemd is a network application now too? >> >> to implement TCPWrapName= (man systemd.exec) > > Again, why it has to be done *by systemd*? > > > > > On Fri, 2011-06-10 at 10:09 -0400, Steve Clark wrote: >>> Yes, whatever happened to the *NIX philosophy of simple non-complex >> programs that did their job well. It has seemed to serve well since >> the 70's. > > Exactly my point. > It looks like it is the right time to think about upstart again. I will definitely check it out on rawhide. Thanks to OP for pointing on some difficulties. More important that it will be not so easy to clean that all up latter and we will get eventually unmanageable windows. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning Slim
On 06/10/2011 07:04 PM, Christoph Wickert wrote: > Am Donnerstag, den 09.06.2011, 13:40 +0400 schrieb Lucas: >> What kind of relation between Xfce maintainers and SLIM. > > The Fedora Xfce SIG considered SLIM but we didn't use it because (at > least at that time) it had some problems with ConsoleKit. > I use xfce since fedora 13 and slim also. I always had to do something to make it works. What are those problems with consolekit you mentioned? > We are still trying to get rid of GDM but we are more after LightDM now. > I have packaged it and it basically works on F>= 15, but the package > and LightDM requires some more work. > > I don't think that Xfce upstream has a relationship to SLIM in > particular because the project seems pretty much dead. > >> I always thought SLIM is just display manager, which can start >> whatever I want. > > That is correct, but you either need to configure the default desktop or > use the sylm-dynwm script. For more info have a look at > https://fedoraproject.org/wiki/LXDE#SLiM > > Regards, > Christoph > > I, personally, agree that GDM should be replaced, especially after someone decided to move "reboot" and "shutdown" to it. (I found it in Fedora XFCE spin), so now I am thinking how to allow "systemctl reboot" for normal user from xfce. I will check LightDM, but as long as slim works for me, I am going to use it. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning Slim
On 06/09/2011 01:34 PM, Lucas wrote: > On 06/09/2011 01:19 PM, Lucas wrote: >> >Hi, >> > >> >I'm not using this package and I have not checked its state before >> >taking the ownership (which was mistake). It doesn't work for users who >> >upgraded from F14 to F15 and I wasn't able to find out why exactly it >> >fails. There are also some bugs untouched for long time. >> > >> >To sum it up, it is probably better to hand it over to someone else who >> >has more time and actually still uses it. >> > >> >Regards, >> >Jan Kaluza >> >> You will be surprised, but I use it with Fedora 14, 15, and now with >> Rawhide. It works and quite >> good actually. >> >> So, thanks for making rpm. > > > > Check with the Xfce maintainers, > > they believe it's dead upstream. What kind of relation between Xfce maintainers and SLIM. I always thought SLIM is just display manager, which can start whatever I want. Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning Slim
On 06/09/2011 01:19 PM, Lucas wrote: > >Hi, > > > >I'm not using this package and I have not checked its state before > >taking the ownership (which was mistake). It doesn't work for users who > >upgraded from F14 to F15 and I wasn't able to find out why exactly it > >fails. There are also some bugs untouched for long time. > > > >To sum it up, it is probably better to hand it over to someone else who > >has more time and actually still uses it. > > > >Regards, > >Jan Kaluza > > You will be surprised, but I use it with Fedora 14, 15, and now with Rawhide. > It works and quite > good actually. > > So, thanks for making rpm. > > Check with the Xfce maintainers, > they believe it's dead upstream. What kind of relation between Xfce maintainers and SLIM. I always thought SLIM is just display manager, which can start whatever I want. Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning Slim
>Hi, > >I'm not using this package and I have not checked its state before >taking the ownership (which was mistake). It doesn't work for users who >upgraded from F14 to F15 and I wasn't able to find out why exactly it >fails. There are also some bugs untouched for long time. > >To sum it up, it is probably better to hand it over to someone else who >has more time and actually still uses it. > >Regards, >Jan Kaluza You will be surprised, but I use it with Fedora 14, 15, and now with Rawhide. It works and quite good actually. So, thanks for making rpm. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
GDM in rawhide
Dear All. After yesterday update GDM became quite selfish. It sees only it self as a WM, I have also FXCE4 and was not be able to start it - there was no any place where it suppose to be chosen. Did anybody else notice it and was it fixed in today update. Or, shell I install SLIM and solve this and many others future problems? Thank you. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
