users October 2014

users@lists.fedoraproject.org

135 participants
152 discussions

5tFTW: Last bit on Shellshock, plus, Fedora Governance, Flock, Fedocal, and F21 (2014-10-03)

by Matthew Miller

Reposted from <http://fedoramagazine.org/5tftw-2014-10-03/>. Fedora is a big project, and it’s hard to keep up with it all. This series highlights interesting happenings in five different areas every week. It isn’t comprehensive news coverage — just quick summaries with links to each. Here are the five things for October 3rd, 2014: Shellshock (CVE-2014-6271/CVE-2014-7169) followup ------------------------------------------------- Hopefully this is the last word on this (knock on wood), but there are a few tidbits to note. First, the Fedora Docker images on the Docker hub have all been updated, from the base image to all of the pre-made specific images including Node.js, OwnCloud, MariaDB, and so on. Second, we have awarded an electrifying new badge to the dozens of people who helped us get the update out. Thanks to all of you! If you missed it but are still curious, see all of our coverage on Fedora Magazine under the shellshock tag. * https://registry.hub.docker.com/_/fedora/ * https://registry.hub.docker.com/repos/fedora/ * https://badges.fedoraproject.org/badge/shellshocked * http://fedoramagazine.org/tag/shellshock/ Important Fedora governance discussion -------------------------------------- In the months leading up to Flock, at Flock, and after, the Fedora Project board and interested community members have been talking about a new top-level governance model for the project. This is intended to provide more clear project-level communication, increase meritocratic representation of people directly involved in the project, and set up a framework for more efficient use of our limited resources for the most impact. The new body, which we are calling the *Fedora Council*, will replace the Fedora board as stewards of the Fedora mission and our shared core values. This is important to everyone involved in the project — end users and all contributors to all aspects of Fedora, at any level. Take a look at the (in-progress and evolving) draft charter, and join the conversation on the public board-discuss mailing list. * https://fedoraproject.org/wiki/Overview#Our_Mission * https://fedoraproject.org/wiki/Foundations * https://fedoraproject.org/wiki/MatthewMiller/council-draft * https://lists.fedoraproject.org/mailman/listinfo/board-discuss Finalizing Flock locations -------------------------- As mentioned last week, we have four bids for 2015’s Flock conference in North America. Flock organizer Ruth Suehle recently announced a call for input on the proposals Your response would be very helpful, if you’re thinking of attending — and if you’re a Fedora contributor or want to become one, I hope to see you there next summer! * http://fedoramagazine.org/5tftw-2014-09-26/ * https://lists.fedoraproject.org/pipermail/flock-planning/2014-September/0... Fedora Calendar upgrade ----------------------- A few months ago, I wrote about Fedora’s calendaring system, Fedocal. Among other things like scheduling team meetings, contributors use it to note their vacations, so the rest of us can coordinate around that. There have been some complaints that this ends up being harder to read than the old wiki-page solution, but this week, Fedocal developer Pierre-Yves Chibon announced a new version which includes a list view which addresses that. It’s in “staging” now (that is, on a test server), but will go into production use soon. Testing is welcome on the staging instance. * http://fedoramagazine.org/five-things-in-fedora-this-week-2014-04-15/ * https://apps.fedoraproject.org/calendar/ * https://fedorahosted.org/fedocal/ticket/130 * https://lists.fedoraproject.org/pipermail/infrastructure/2014-October/014... * https://apps.stg.fedoraproject.org/calendar/list/test/ Fedora 21 progress ------------------ The Fedora Alpha was released last week, and we’re in the process of evaluating the test criteria for the Beta release scheduled for October 28th, and fixing corresponding bugs. If you’re interested in helping, join the QA team, or simply participate in a Test Day. (If you haven’t before, it’s easy. Read Amita Sharma’s article on what it’s like to get a feel, or just jump in.) Also, please keep in mind that Fedora release days are targets, not deadlines — we aim for them, but our releases come out only when we meet our criteria for quality. We hope that there won’t be any more schedule slips, but when that happens, it’s just part of the process, not some sort of failure. * http://fedoraproject.org/wiki/Releases/21/Schedule * https://fedoraproject.org/wiki/QA/Join * http://fedoraproject.org/wiki/QA/Test_Days * http://fedoramagazine.org/how-it-feels-when-you-participate-in-a-test-day... -- Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/> Fedora Project Leader mattdm(a)fedoraproject.org <http://fedoraproject.org/>

9 years, 6 months

1
0
0 / 0

Display resolution -

by Bob Goodwin

I need to swap monitors as the backlight in my old Dell monitor grows dim. I have a Viewsonic vx2035WM that Fedora can never get the resolution right for. I've gone through the following process using information I found on Google. [root@box7 bobg]# cvt 1680 1050 # 1680x1050 59.95 Hz (CVT 1.76MA) hsync: 65.29 kHz; pclk: 146.25 MHz Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync [root@box7 bobg]# xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync [root@box7 bobg]# xrandr --addmode VGA1 1680x1050_60.00 [root@box7 bobg]# xrandr --output VGA1 --mode 1680x1050_60.00 Which produces a working Modeline and display. Now it appears I need a working xorg.conf display section so it will survive rebooting. When I do, again from Google: Xorg :1 -configure The display crashes and says "Starting Terminate Plymouth Boot Screen" Does anyone have an example of a working config file that I can use? Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-20/64bit Linux/XFCE

9 years, 6 months

3
6
0 / 0

How do WiFi repeaters work?

by Timothy Murphy

I have a no-name chinese repeater (model WN518N) which by sheer fluke I have got working. As far as I can see, I have now lost contact with the repeater itself, as packets simply pass through it. (Wireshark shows a lot of STP packets passing through.) But I'm not sure if I set it up correctly. My WiFi LAN is on 192.168.2.* and I set this repeater's IP address to 192.168.2.40 . Should I actually have set it to a different LAN, eg 192.168.10.* ? (I guess I could press the Reset button and start again.) Any elucidation gratefully received. -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

9 years, 6 months

2
1
0 / 0

ps -ef stack overflow fedora 20 fully updated

by Ger van Dijck

Hi Folks, When doing a ps -ef on a fully updated Fedora 20 OS I get the following message: /usr/bin/abrt-watch-log -F BUG : WARNING : at WARNING : CPU :INFO: possoble recurcive locking detected kernel BUG at list_del corruption list_add corruption do_IRQ :stack overflow : ear stack overflow (cur: general protection fault enable to handle kernel double fault : RTNL : assertion failed eek! page_mapcount(page) went nagative! madness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Machine Chek Exeption : Machine check events logged devide error : bounds : coprosessor overrun : invalid TSS : segment not present : invalid upcode : aligment check : stack segment : fpu exeption : simd exeption : iret exeption : /var/log/messages -- /usr/bin/abrt-dump-oops -xtD You want more ?? Suddenly I cannot scan (HP4620) anymore and the Dell Inspiron Laptop is behaving unpredictabel I have not been encountered with a slach overflow for years I cannot imagine that nobody has not seen this error doing ps -ef Any help or commend would be usefull Greetings Ger van Dijck. -- Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/

9 years, 6 months

4
3
0 / 0

Renumbering partitions on an external drive

by Robert Moskowitz

I have been messing around with partitions on a drive and now physically they are sdb2,sdb3,sdb1. I want to get them in order. the fdisk xpert fiw does NOT renumber them; it seems to be happy with things as they are. Is there anyway to fix this short of rebuilding the partition table, carefully pointing each new entry to the right block? parted and gparted don't have any help either. Yes, I know this is cosmetic, but hey, it SHOULD LOOK nice and neat...

9 years, 6 months

2
4
0 / 0

Keyboard language settings at startup

by Paul Anzel

Good afternoon, I'm having a bit of an interesting problem, and wanted to ask how I could change my keyboard setup at the initial log-in screen? The basic situation is this: I've got a couple of desktops that I installed a new copy of Fedora on, and did so using an English (USA) keyboard I had on hand. However, these computers are in Switzerland, and I'd like them to work with the Swiss German keyboards my lab has around. I've set the system up to use a Swiss German keyboard layout, and for the most part it works as expected. HOWEVER, at the first log-in screen (when you first put in your password) the keyboard set up is still in English configuration. It's only after you log in that it properly changes to the Swiss German layout. As you can imagine, this makes entering in your password a little bit more tricky. So, would anyone please be able to tell me how to resolve this issue? Thank you for your help, Paul

9 years, 6 months

1
0
0 / 0

Two disk kickstart

by CLOSE Dave

I'm having a little trouble with kickstart when the target box has more than one disk. In the %pre section of the kickstart file, I create a temporary file based on the number of disks present, then %include that file in the normal part of the kickstart file. The logic is this. > d= > declare -i i=0 > while read maj min blk nam; do > if [[ $nam =~ ^sd.$ ]]; then > d="$d,$nam" > i+=1 > fi > done </proc/partitions > if [[ $i -eq 0 ]]; then > shutdown -H now > fi > d=${d#,} > ( > echo bootloader --driveorder=$d --location=mbr --boot-drive=${d%%,*} > echo clearpart --all --initlabel --drives=$d > echo part /boot --fstype=ext4 --size=500 --ondisk=${d%%,*} > echo part pv.01 --grow --size=500 --ondisk=${d%%,*} > if [[ $i -eq 1 ]]; then > echo volgroup vg_me pv.01 --pesize=32768 > else > echo part pv.02 --grow --size=500 --ondisk=${d##*,} > echo volgroup vg_me pv.01 pv.02 --pesize=32768 > fi > echo -n logvol /home --fstype=ext4 --name=lv_home --vgname=vg_me > echo \ --grow --size=100 > echo -n logvol / --fstype=ext4 --name=lv_root --vgname=vg_me > echo \ --grow --size=1024 --maxsize=51200 > echo -n logvol swap --name=lv_swap --vgname=vg_me --grow --size=1008 > echo \ --maxsize=2016 > ) >/tmp/diskpart When I have two disks (I've haven't had more thus far), the logic works perfectly. Except... When the machine reboots, it tries to boot from the second disk, sdb, not from sda where the boot loader is. Of course, that doesn't work and the machine hangs. My cure for this at this time is manual. I use the BIOS to disable the second disk, boot (which starts but fails), then use the BIOS to re-enable the second disk and everything works as it should. But why does the box think it should boot from the second disk? The box is a Dell R510 server. I understand this might be peculiar to the R510. But if there is anything I can do in the kickstart file to avoid the problem, I'd sure like to do it. -- Dave Close

9 years, 6 months

2
1
0 / 0

tracking down crash/error in app running on fed/centos

by bruce

Hi guys. running an app in both fed/centos test machines and getting a seg fault. I know this is a bit off topic, but it does related to segfault crashes, and how to get/setup the data to analyze track down the offending code! to begin, the system has /var/log/messages with Sep 30 11:40:57 dell2 kernel: courseSectionDa[3270]: segfault at 868 ip 00007f80e8e1e410 sp 00007fffe404d0c8 error 4 in libgearman.so.8.0.0[7f80e8e18000+26000] isn't this saying the crash is coming from the libgearman.so.8.0.0 as opposed to the parent php app which uses the gearman lib?? and assuming that this is the case, and i installed the gearman so with yum (without source) is there a way I can setup the system to capture the crash data to do an analysis of the crash?? the parent app runs multiple (1000s) of times, and somewhere the crash occurs.. thanks guys..

9 years, 6 months

2
1
0 / 0

Please keep F20 up-to-date (if you can't hold release dates)

by Gerhard Hueller

Hello, A few days ago, Mesa-10.3 has been released, while Mesa 10.2 now marks the "stable" version. The version which currently ships as part of Fedora-20 is 10.1, which receuived its last update in June. Guys, if you can't hold release dates, please keep at least the current distribution up-to-date. It is done with the kernel, so why aren't other critical parts of the system handled in a rolling-release like way? Greetings, Gerhard

9 years, 6 months

5
7
0 / 0

UCB keybord curiosity

by Geoffrey Leach

I have a system that functions as a PVR, and is re-booted daily. There have been no recent updates. On yesterday's reboot (and subsequently) the kernel does not recognize A/N keystrokes from the KBD. Mousepad motions and clicks work fine. Looking at the dmesg output, there appears to be nothing amiss. When I move the USB transceiver to another system, everything works as it should. Suggestions? Thanks.

9 years, 6 months

3
7
0 / 0

Jump to page: