Re: Starting user UIDs at 1000 - please check your packages
Miloslav Trmač wrote: No, applications expect system accounts and user accounts to have non-overlapping ID intervals. So this would be just a more broken version of keeping the limit at 500. +1. And keeping consistency with other distros. Definitely the right move, since UID=1000 is the documented standard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: biosdevname in fedora 15 - why is this inconsistency?
Adam Williamson wrote: ifconfig shows I have em1, p2p1; Why does it not defined as pcislot#port? The man page is out of date. pciXp_Y got changed to pXpY, I believe because it turned out to be important that the names be kept below a certain length. I also have biosdevname-0.3.8-1.fc15.x86_64, but ifconfig says I have eth0 and eth1 for the wireless. How come? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: biosdevname in fedora 15 - why is this inconsistency?
Adam Williamson wrote: That would indicate your BIOS doesn't have the necessary support; quite a few don't. There's some notes on what's needed for biosdevname to work at https://fedoraproject.org/wiki/Test_Day:2011-01-27_Network_Device_Nami ng_With_Biosdevname#Hardware_Requirements I ran the script, output: Checking hardware requirements [ OK ] Checking for SMBIOS type 41 support[FAILED] Checking for SMBIOS type 9 support [ OK ] Checking for PCI Interrupt Routing support [ OK ] The instructions say: If the output of the script is [ OK ] and any of the following checks is [ OK ], your hardware is supported by biosdevname. So, what's wrong? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: biosdevname in fedora 15 - why is this inconsistency?
Tom Hughes wrote: Did you upgrade this machine from an earlier version of Fedora? If so then I suspect the old names will stick because you will have udev persistent naming rules for them. No, I did a clean install. I installed a week before the first Test Candidate for the first Release Candidate of the Alpha for Fedora 15 came out. Check /etc/udev/rules.d/70-persistent-net.rules and I bet you have rules that are forcing the ethX names. Yes, this file is present. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
RE: biosdevname in fedora 15 - why is this inconsistency?
shyam_i...@dell.com wrote: Can you create a BZ with the following output.. ? sudo /sbin/biosdevname -d sudo /usr/sbin/dmidecode sudo /usr/sbin/biosdecode lspci -tv https://bugzilla.redhat.com/show_bug.cgi?id=720068 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: orphaning xine-lib, EOL'ing phonon-backend-xine
Kevin Kofler wrote: there's one third-party KDE-Platform-based application still using xine-lib for the foreseeable future: Kaffeine. kaffeine has begun to look kind of shabby. I always installed it, as xine appeared to have the most complete set of codecs. Can other programs now deal with everything that xine/kaffeine was a fallback for? (Sorry, I have no actual examples, off the top of my head) xine-lib is a requisite for xine-lib-extras-freeworld. Will amarok be using a different library to play mp3 in f16? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: orphaning xine-lib, EOL'ing phonon-backend-xine
John5342 wrote: Hence xine-lib-extras-freeworld should make no difference to amarok when using the default backend anyway. You probably want gstreamer-plugins-* in f15+ (or whenever phonon-backend-gstreamer became the default) unless you changed the back end manually. Oh, so you mean I never needed to install xine-lib-extras-freeworld, since I am using phonon-backend-gstreamer? I can get amarok to play mp3, assuming I have all of the gstreamer-plugins-* installed? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: orphaning xine-lib, EOL'ing phonon-backend-xine
Petrus de Calguarium wrote: John5342 wrote: Hence xine-lib-extras-freeworld should make no difference to amarok when using the default backend anyway. You probably want gstreamer-plugins-* in f15+ (or whenever phonon-backend-gstreamer became the default) unless you changed the back end manually. I guess it works. I just uninstalled xine-lib-extras-freeworld and amarok is fine. I haven't tried any video players, yet, but all looks good so far. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: orphaning xine-lib, EOL'ing phonon-backend-xine
John5342 wrote: I forget which one exactly contains the mp3 plugin gstreamer-plugins-ugly, I believe i just install all of them and then i don't have to worry about any other format i may one day come across. ditto The same plugins are also used by just about every other form of KDE based audio/video. That includes everything from video players like Dragon to audio players like Amarok to System Notifications etc. Curious. I thought Dragon must use xine-lib, since both kdemultimedia and kdebase-runtime require it in F15. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 15 / Gnome 3 gotchas
Denys Vlasenko wrote: Gnome 3 is a usability disaster. I rather like Gnome3. I am a KDE user and through Gnome3, I have managed to discover all kinds of things in KDE that I never knew were there or never knew how to use. Gnome3 is kind of like a simplified KDE4 (imagine a different activity on each virtual desktop and no plasmoids and no desktop layouts, just straight, with wallpaper and nothing else). -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Lennart Poettering wrote: Hmm, the problems you pointed out, which ones of those remain? Can you please file a bug about those! (unless you already did so?) They are all solved. dnsmasq was not caching because I forgot to tell it not to use the default resolv.conf, but rather to use 127.0.0.1. As for kde not shutting down, it does now, having applied systemd-8-3. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Kevin Kofler wrote: What KDM does is that it runs (as root, like all of KDM) the command given by its HaltCmd option, which defaults to its HALT_CMD macro, which is defined on GNU/Linux as /sbin/halt. However, I see that we override this in our default kdmrc in kde-settings-kdm as HaltCmd=/sbin/poweroff. I don't know which update did it, perhaps systemd-8-3, but it now works. So does poweroff from the command line. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Matthew Miller wrote: What do the logs say? Where are the logs? I looked in /var/log/ last night and there is no system.log or systemd.log file on my system. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Thanks Rahul and Martin (other posts in this thread) :) Bill Nottingham wrote: Petrus de Calguarium said: 1. I noticed that one can no longer (with v8-2) turn off the computer by clicking the 'turn off computer' button in KDE. I figured out, with help of recent threads, that one has to run: systemctl isolate poweroff.target. It worked. Is this the correct way? That is a way. The KDE button should still work - what is it actually doing? (Generally, invoking shutdown/reboot/etc is probably the easiest way.) OK, I just updated to v8-3 and have the latest initscripts, too. I tried to shut down twice (I invoked sudo systemctl daemon-reexec before the second time), and I still cannot power down by clicking on the power off button. The screen goes black, but the mouse pointer remains on the black screen and is movable, but nothing further occurs. I have to go to a different virtual terminal, log in as root, and run systemctl isolate poweroff.target. Then, it powers off. 2. I use privoxy as a proxy and dnsmasq for dns cacheing. Previously, I issued: service dnsmasq start ; service privoxy start. I presume I must now run: systemctl start dnsmasq.service ; systemctl start privoxy.service. Is this correct? If you've got the latest packages, either should work. I don't think this is working, either. I ran systemctl start dnsmasq.service ; systemctl start privoxy.service and got no error messages. I opened firefox and was able to navigate to a web page, so it seems that privoxy is working, otherwise it would block loading pages. However, dnsmasq does not appear to be working correctly. When I run dig si.com it says 30 seconds the first time and 29 seconds every time thereafter and the lights on my router flash, meaning it is getting the information from the web. Normally, the second time running dig si.com should be 0 seconds and no flashing lights on the router. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Petrus de Calguarium wrote: Forget the BS about dnsmasq not cacheing! I forgot to change /etc/resolv.conf and was still using the old one that uses the default nameservers. So, the problem reduces to the Shut Off Computer button in KDE not working. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Matthew Miller wrote: And what do the shutdown and poweroff commands do? OK, I'm back. I ran shutdown (forgot to add -h now), so it took a bit, from within konsole. It shut off the system, without running plymouth. To speed things up, I appended 3 (Lennard wrote that you can still to this) to the kernel boot line in grub and ran poweroff. The system ran plymouth and powered off. Now, I'm back and started dnsmasq and privoxy again, no errors, but dig shows that dnsmasq is not cacheing. Where are the logs for systemd? In /var/log/messages, maybe? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Petrus de Calguarium wrote: dnsmasq does not appear to be working correctly. This is odd. systemctl and systemctl status dnsmasq.service both show dnsmasq as active (running), but it is not cacheing. Could it be that it's not reading /etc/dnsmasq.conf? No, I don't think so (Privoxy does appear to be reading it's customized user.action file). -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Bill Nottingham wrote: OK. So the question is ... what does this button do? Invoke 'halt'? Invoke 'shutdown -h now'? Invoke ConsoleKit's Stop() method? Do I need to look in the logs for this? :-) I think this is a question for the KDE guys, non? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Matthew Miller wrote: It doesn't log separately -- it uses syslog. So look in the /var/log/messages file. You know, I'm getting the hang of systemd. I like. I hope we're not going back to sysv, despite the grumbling. I just converted my scripts and this is easier, I think. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: applied, non-theoretical use of systemd
Brendan Jones - I.T. wrote: On 08/27/2010 10:11 AM, Petrus de Calguarium wrote: Where are the logs for systemd? In /var/log/messages, maybe? I add systemd.log_target=kmsg systemd.log_level=debug as kernel parameters to flesh out logging in /var/log/messages Thanks. I think it is not required anymore, because the daemon problem was due to my own error. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
applied, non-theoretical use of systemd
1. I noticed that one can no longer (with v8-2) turn off the computer by clicking the 'turn off computer' button in KDE. I figured out, with help of recent threads, that one has to run: systemctl isolate poweroff.target. It worked. Is this the correct way? 2. I use privoxy as a proxy and dnsmasq for dns cacheing. Previously, I issued: service dnsmasq start ; service privoxy start. I presume I must now run: systemctl start dnsmasq.service ; systemctl start privoxy.service. Is this correct? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: How many lost users is an acceptable loss in exchange for systemd?
Gregory Maxwell wrote: To say it bluntly: Any significant infrastructural change _will_ cost Fedora some users in the short term. I'm not lost. I am using F14α as my day-to-day system since the weekend. I am considering putting F14α on my laptop, too, so goodbye F13. I have experienced no problems whatsoever that could in any way be attributed to systemd, AFAICT (some minor video compositing glitches, a few spambayes, gnome-keyring crashes, that's about it). I trust that the developers know more than I know. They haven't left me lying yet. Novel ideas and the brainpower to be able to implement them are what make Fedora stand out from the other distros. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
mcelog errors
The mcelog script in cron.hourly runs hourly and, hourly, I get system mail stating that a device does not exist. This is a regression, as this error was present in rawhide before f13 came out, and now, in f14α, it is back. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: mcelog errors
Michael Schwendt wrote: Bugs are to be reported in bugzilla, e.g. via this convenient link: http://bugz.fedoraproject.org/mcelog Thanks. It appears that there are a number of bug reports already opened on exactly this problem. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F14 TC2 x86_64b
Clyde E. Kunkel wrote: The workaround is to choose Install with basic video driver. Or, pass nomodeset to the kernel... I tried both nomodeset and the basic video driver. In both cases, the boot hangs at: Waiting for hardware to initialize... It hangs here forever and the CD/DVD drive keeps spinning with its LED lit, but nothing happens. I switch to vt3 and observe the following message (in both nomodeset and basic video driver cases): Error inserting floppy: no such device Note: I don't even have a floppy! How do I get past this??? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Harmless KDE feature upgrades - yeah right
Juha Tuomala wrote: For all those who say that latest stuff is the reason why I use Fedora!!!1, there is rawhide for you. I have tried this, but that is not possible. Generally, a few weeks after the release of a new fedora, rawhide becomes unusable for a while, even unbootable. My last try went pretty well, lasting from the time fedora 12 was released until about 3 weeks ago, when rawhide just hung and I could not even yum updates or log in. In my experience of a few years of trying Rawhide, it becomes usable again around the time of the release of the alpha release, which is the time I generally switch. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: To semi-rolling or not to semi-rolling, that is the question...
Doug Ledford wrote: [the whole nine yards] I like this idea. As a user of fedora updates- testing and kde-redhat, in order to get the latest software the soonest onto my computer, without having the burden of reinstalling my system twice a year on 2 computers, x86_64 desktop and i686/PAE laptop, I like the idea of being able to run rawhide perpetually (and not having it get into such a conundrum that one day it will no longer even boot, due to some bad yum update). I had flippantly proposed 'fedora infinity' a year or two back on this list and it was shot down :-( I was told that I should look into sidux or arch linux, I think. Sorry, I'm not into building my system from scratch and appreciate the fantastic work here and, were rawhide to always work while always being on the edge of the latest development, and no longer having to reinstall twice a year, i.e., having rawhide become a de facto rolling release, I would be thrilled with it!!! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: X server configuration changes
Peter Hutterer wrote: ... Thanks for the 'Heads Up'. As I had said so long ago, I couldn't possibly read every developer's blog to find out what I must do to avoid inevitable doom after updating my system and not taking the required configuration measures -- that I would only know about, had I read the blog. Since most of us have no xorg.conf anymore, we likely don't have to do anything. Excellent work !! ;-) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Unable to start X
Paul F. Johnson wrote: Ta Ta For Now I haven't heard that for a while. Yes, we use that here in .ca sometimes, too. It's only me, only me and no-one else. ditto -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
