Re: sound
On Tue, 2013-06-11 at 21:12 -0700, Richard Vickery wrote: > On Tue, Jun 11, 2013 at 7:36 PM, Adam Williamson wrote: > > On Tue, 2013-06-11 at 10:38 -0700, Richard Vickery wrote: > > > >> Thanks for the reply, I may likely have needed them had I not figured > >> out the solution; although Mr. Guomundsson's solution returned the > >> following: > >> > >> $ pulseaudio > >> E: [pulseaudio] pid.c: Daemon already running. > >> E: [pulseaudio] main.c: pa_pid_file_create() failed. > >> $ pulseaudio -k && sleep 5 && pulseaudio -D > >> E: [pulseaudio] main.c: Daemon startup failed. > >> > >> and I may have needed more information. > > > > PA respawns, by default, when it dies. You have to create a > > ~/.pulse/client.conf file with: > > > > autospawn = no > > > > if you want to run it manually to get debugging output. I guess Johann > > already did this and then forgot it was necessary :) > Is it necessary to do this since I have fixed the problem? Not at all, just if you ever need to debug a PA issue in future. Thought I'd mention it for General Educational Purposes. :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: errors upgrading to 2
On Tue, Jun 11, 2013 at 7:12 PM, Adam Williamson wrote: > On Sun, 2013-06-09 at 11:42 -0700, Richard Vickery wrote: >> In the middle of updating , I got these; how important are they? and,I >> supopose, is the command to recover "db_runrecovery"? >> >> error: rpmdb: BDB0113 Thread/process 3820/139765024729088 failed: >> BDB1507 Thread died in Berkeley DB library >> error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: >> Fatal error, run database recovery >> error: cannot open Packages index using db5 - (-30973) >> error: cannot open Packages database in >> >> error: rpmdb: BDB0113 Thread/process 4155/139803070191616 failed: >> BDB1507 Thread died in Berkeley DB library 28 kB/s | 15 MB 01:57:16 >> ETA >> error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: >> Fatal error, run database recovery >> error: cannot open Packages index using db5 - (-30973) >> error: cannot open Packages database in >> error: rpmdb: BDB0113 Thread/process 4198/140301288781824 failed: >> BDB1507 Thread died in Berkeley DB library 20 kB/s | 17 MB 02:38:16 >> ETA >> error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: >> Fatal error, run database recovery >> error: cannot open Packages index using db5 - (-30973) >> error: cannot open Packages database in >> error: rpmdb: BDB0113 Thread/process 4438/140296451778560 failed: >> BDB1507 Thread died in Berkeley DB library8.0 kB/s | 86 MB 04:15:19 >> ETA >> error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: >> Fatal error, run database recovery >> error: cannot open Packages index using db5 - (-30973) >> error: cannot open Packages database in >> error: rpmdb: BDB0113 Thread/process 4526/140586095818752 failed: >> BDB1507 Thread died in Berkeley DB library109 kB/s | 101 MB 00:16:13 >> ETA >> error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: >> Fatal error, run database recovery >> error: cannot open Packages index using db5 - (-30973) >> error: cannot open Packages database in >> error: rpmdb: BDB0113 Thread/process 4656/139997326555136 failed: >> BDB1507 Thread died in Berkeley DB library311 kB/s | 114 MB 00:05:00 >> ETA >> error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: >> Fatal error, run database recovery >> error: cannot open Packages index using db5 - (-30973) >> error: cannot open Packages database in >> error: rpmdb: BDB0113 Thread/process 4689/140320299190272 failed: >> BDB1507 Thread died in Berkeley DB library492 kB/s | 122 MB 00:02:54 >> ETA >> error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: >> Fatal error, run database recovery >> error: cannot open Packages index using db5 - (-30973) >> error: cannot open Packages database in >> error: rpmdb: BDB0113 Thread/process 4733/140155315288064 failed: >> BDB1507 Thread died in Berkeley DB library325 kB/s | 138 MB 00:03:34 >> ETA >> error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: >> Fatal error, run database recovery >> error: cannot open Packages index using db5 - (-30973) >> error: cannot open Packages database in >> >> Thanks for the feedback, if any? Should I even reboot the computer >> before I correct it? > > The old-school dodge for this was 'rm -f /var/lib/rpm/__db*' then 'rpm > --rebuilddb'. I am, of course, not responsible for data loss, emotional > or physical pain, unexpected pregnancy or the end of this and/or any > other universe which may result ;) > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora > http://www.happyassassin.net > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test (laughing) pregnancy...end of the universe...hilarious! Thanks! -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: sound
On Tue, Jun 11, 2013 at 7:36 PM, Adam Williamson wrote: > On Tue, 2013-06-11 at 10:38 -0700, Richard Vickery wrote: > >> Thanks for the reply, I may likely have needed them had I not figured >> out the solution; although Mr. Guomundsson's solution returned the >> following: >> >> $ pulseaudio >> E: [pulseaudio] pid.c: Daemon already running. >> E: [pulseaudio] main.c: pa_pid_file_create() failed. >> $ pulseaudio -k && sleep 5 && pulseaudio -D >> E: [pulseaudio] main.c: Daemon startup failed. >> >> and I may have needed more information. > > PA respawns, by default, when it dies. You have to create a > ~/.pulse/client.conf file with: > > autospawn = no > > if you want to run it manually to get debugging output. I guess Johann > already did this and then forgot it was necessary :) > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora > http://www.happyassassin.net > Is it necessary to do this since I have fixed the problem? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Schr@*!dinger*#@s Cat
On 06/11/2013 07:46 PM, Richard Vickery wrote:
On Tue, Jun 11, 2013 at 10:31 AM, Chuck Forsberg WA7KGX N2469R
wrote:
It seems the name of the Fedora 19 release is getting corrupted in various
places.
It might be breaking some scripts as well.
It might be wise to eliminate the special characters (including the ' )
before final release.
--
Chuck Forsberg WA7KGX c...@omen.com www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
I don't think I have any issues with the accents. Rather, I'm sure
that I don't.
I am facing similar issues as Chuck has.
During bootup, bootlogs report to be booting "Schrôdingerüs Cat"
("o circumflex" instead of "o umlaut" and "u umlaut" instead of ').
Same on console prompts: "Fedora release 19 (Schrôdingerüs Cat)"
Are you sure that the corruption issues that you're
having are not due to something else?
No, I am not sure. localectl on VCs also seems not to work.
# localectl
System Locale: LANG=en_US.UTF-8
VC Keymap: de-latin1
X11 Layout: de
X11 Model: pc105
X11 Options: terminate:ctrl_alt_bksp,
This setting works for me on F18, but it apparently doesn't on F19
consoles (The special German keys of my German keyboards don't seem to
be honored correctly - e.g. pressing 'ö' (o umlaut) produces a '[').
Ralf
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 18 updates-testing report
The following Fedora 18 Security updates need testing: Age URL 154 https://admin.fedoraproject.org/updates/FEDORA-2013-0416/fedora-business-cards-1-0.1.beta1.fc18 88 https://admin.fedoraproject.org/updates/FEDORA-2013-3935/puppet-3.1.1-1.fc18 81 https://admin.fedoraproject.org/updates/FEDORA-2013-4243/stunnel-4.55-1.fc18 68 https://admin.fedoraproject.org/updates/FEDORA-2013-4823/microcode_ctl-2.0-3.fc18 53 https://admin.fedoraproject.org/updates/FEDORA-2013-6117/eucalyptus-3.2.2-1.fc18 25 https://admin.fedoraproject.org/updates/FEDORA-2013-8381/varnish-3.0.3-5.fc18 11 https://admin.fedoraproject.org/updates/FEDORA-2013-9707/livecd-tools-18.16-2.fc18 7 https://admin.fedoraproject.org/updates/FEDORA-2013-9950/perl-Dancer-1.3100-3.fc18 7 https://admin.fedoraproject.org/updates/FEDORA-2013-9962/subversion-1.7.10-1.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-10136/xen-4.2.2-6.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-10138/gallery3-3.0.8-1.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-10097/libguestfs-1.20.8-1.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-10309/rrdtool-1.4.8-2.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-10255/php-5.4.16-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-10440/owncloud-4.5.12-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-10430/perl-Module-Signature-0.73-1.fc18 The following Fedora 18 Critical Path updates have yet to be approved: Age URL 122 https://admin.fedoraproject.org/updates/FEDORA-2013-2192/nautilus-3.6.3-5.fc18 12 https://admin.fedoraproject.org/updates/FEDORA-2013-9635/cogl-1.12.2-2.fc18 11 https://admin.fedoraproject.org/updates/FEDORA-2013-9710/xorg-x11-drv-qxl-0.1.0-2.fc18 11 https://admin.fedoraproject.org/updates/FEDORA-2013-9681/perl-threads-1.87-1.fc18 11 https://admin.fedoraproject.org/updates/FEDORA-2013-9707/livecd-tools-18.16-2.fc18 10 https://admin.fedoraproject.org/updates/FEDORA-2013-9851/ModemManager-0.6.2.0-1.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-10112/dosfstools-3.0.17-1.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-10151/bind-dyndb-ldap-2.6-2.fc18,dnsperf-2.0.0.0-4.fc18,dhcp-4.2.5-12.fc18,bind-9.9.3-3.P1.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-6209/ibus-1.5.2-4.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-10318/system-config-keyboard-1.3.1-14.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-10428/NetworkManager-0.9.8.2-1.fc18,network-manager-applet-0.9.8.2-1.fc18 0 https://admin.fedoraproject.org/updates/FEDORA-2013-10635/emacs-24.2-19.fc18 0 https://admin.fedoraproject.org/updates/FEDORA-2013-10643/dnsmasq-2.65-6.fc18 The following builds have been pushed to Fedora 18 updates-testing EekBoek-2.02.02-1.fc18 abi-compliance-checker-1.99.1-1.fc18 ansible-1.2-1.fc18 dnsmasq-2.65-6.fc18 emacs-24.2-19.fc18 fes-0.1-4.fc18 ghc-setenv-0.1.0-1.fc18 gksu-polkit-0.0.3-7.fc18 gparted-0.16.1-2.fc18 grads-2.0.2-1.fc18 heimdall-1.4.0-1.fc18 jets3t-0.9.0-1.fc18 jtoaster-1.0.5-1.fc18 libteam-1.3-1.fc18 libtommath-0.41-16.fc18 mate-icon-theme-1.6.1-1.fc18 mate-settings-daemon-1.6.0-2.fc18 mate-window-manager-1.6.2-2.fc18 maven-native-1.0-0.3.alpha.7.fc18 perl-Text-CSV-1.30-1.fc18 pkgdiff-1.6-1.fc18 python-urllib3-1.5-6.fc18 pytorctl-0-0.12.20130611git68bc5de.fc18 screenruler-0.96-1.fc18 shellinabox-2.14-24.git88822c1.fc18 texmaker-4.0.2-1.fc18 tomcat6-6.0.37-2.fc18 transmission-remote-gtk-1.1.1-1.fc18 vino-3.6.2-3.fc18 Details about builds: EekBoek-2.02.02-1.fc18 (FEDORA-2013-10619) Bookkeeping software for small and medium-size businesses Update Information: Here is where you give an explanation of your update. ChangeLog: * Tue Jun 11 2013 Johan Vromans - 2.02.02-1 - Upgrade to upstream 2.02.02. References: [ 1 ] Bug #973157 - Problem with date calculation https://bugzilla.redhat.com/show_bug.cgi?id=973157 abi-compliance-checker-1.99.1-1.fc18 (FEDORA-2013-10640) An ABI Compliance Checker Update Information: * abi-compliance-checker Improvements - Support for ABI Dumper 0.97 - Show added/removed inline virtual functions in the binary compatibility report - Added "this"
Re: F19 Final criteria revamp
On Tue, 2013-06-11 at 19:17 -0700, Samuel Sieb wrote: > On 06/11/2013 12:37 AM, "Jóhann B. Guðmundsson" wrote: > > Installing to a freespace should be uncontroversial indeed it's the > > resize I was referring to and as afaik when you buy a set of hardware > > with windows installed it does not come with "freespace" available > > and we should only be "supporting" dealing with factory defaults but as > > Samuel points out earlier in the thread > > > The criteria specifically refers to installing to freespace, so other > than the single partition reference what is the problem? If the user > wants to install alongside a default windows install, they will either > have to resize the partitions on their own or risk letting the installer > resize it (if it will). I can kinda see Johann's point, which is that - since most dual boot installs will require a resize - if we don't 'support' resize, we're really not 'supporting' dual boot installs. He's not wrong. But overall, I think it's worthwhile having the criterion to ensure that, as cmurf said, we at least make sure we get the bootloader stuff right at release time. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: sound
On Tue, 2013-06-11 at 10:38 -0700, Richard Vickery wrote: > Thanks for the reply, I may likely have needed them had I not figured > out the solution; although Mr. Guomundsson's solution returned the > following: > > $ pulseaudio > E: [pulseaudio] pid.c: Daemon already running. > E: [pulseaudio] main.c: pa_pid_file_create() failed. > $ pulseaudio -k && sleep 5 && pulseaudio -D > E: [pulseaudio] main.c: Daemon startup failed. > > and I may have needed more information. PA respawns, by default, when it dies. You have to create a ~/.pulse/client.conf file with: autospawn = no if you want to run it manually to get debugging output. I guess Johann already did this and then forgot it was necessary :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Final criteria revamp
On Tue, 2013-06-11 at 08:51 -0400, Chris Murphy wrote: > On Jun 11, 2013, at 3:37 AM, Jóhann B. Guðmundsson wrote: > > here's what Adam sait about that " if ntfsresize fails for some reason, > > that wouldn't be a blocker." which kinda beats the purpose of the criteria > > right ( since no factory install of windows comes with available free space > > so the user always has to resize before or during the installation phaze ) > > Users installing Windows into a discrete space that's less than max > available is the minority case, but that doesn't obviate the need for > the criterion. Further, historically the part of the criterion that > causes hold ups is the boot loader aspect, not resizing problems. > > If the anaconda team really considers resizing inherently risky and > unpredictable, the operation needs to come with a warning to the user. > Insofar as I'm aware, there is no such warning, or suggestion of > alternatives: boot Windows and use its utility for resizing the file > system. Then an install into free space is also possible. I think the old anaconda did have a warning about resize operations. If newUI doesn't, then yeah, maybe it should. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Final criteria revamp
On Tue, 2013-06-11 at 08:50 -0400, Kamil Paral wrote: > > Hey folks - so just ahead of the blocker meeting tomorrow, I'm done with > > the Final criteria rewrite. > > Thanks a lot, I reviewed them and they seem to be fine. Some comments below. > > I noticed that the upgrade criterion went missing. But we already have > one in Beta, and it seems to be the same. What am I missing? Sorry, I should have noted that. You're missing that the 'old' criteria were tuned for the pre-F18 situation where we had multiple possible 'recommended' upgrade methods, to whit, preupgrade and 'boot an image and pick upgrade'. The Beta criteria required any single 'recommended' method to work. The Final criteria required all 'recommended' upgrade methods to work. Now we only have one 'recommended' upgrade method, so it seems unnecessary to keep that complexity. We can always add it back if we grow another 'recommended' upgrade method, which I sincerely hope we don't :) > > * I wrote an exception for hardware-based services when the hardware > > isn't present into the 'services' criterion: we waived a couple of > > 'blockers' for F18 on the basis that it's okay if a service fails if > > it's for hardware that isn't present, so I thought it made sense to > > write that into the criterion. (Obviously it's best if we can make the > > service not fire unless the hardware is present, but I don't think it > > makes sense to block the release on that kind of thing). > > The "unless they require hardware which is not present" phrase could > be separated into a comment box, so that the original sentence is > cleaner. Just an idea. True, it could. I'll try writing it up both ways and see which one looks best... > > SELinux and crash notifications > > There must be no SELinux denial notifications or crash notifications > after boot of a release-blocking live image or at first login after a > default install of a release-blocking desktop. > > Should we add "during installation" as well? Wrt the bug discussed in > the last blocker bug meeting. Hum, somehow I thought I had, but I must've got confused (I was juggling a few things while I was doing the rewrite). Indeed we should add that. Thanks. The non-live installer does not have the facility to display AVC alerts so we're covered there, but can crop up during live installs. > > * I watered down the 'desktop' criteria quite a bit. Looking at them > > afresh I really think we were kind of over-reaching when we wrote them > > for F13: I remember we were thinking about 'polish criteria', but now > > we've had this process in place for a while, it really doesn't make > > sense to block the release on fairly trivial 'polish' issues (especially > > when we happily ship with much bigger issues in slightly different other > > areas). So I nuked the 'icons can't be fuzzy' requirement, the > > requirement for Help and About menus to be present, and the bit about > > apps not showing up twice in the menus. Those are all nice things to > > check, but I really don't think we need to be blocking releases on them. > > I agree. These issues were too trivial to block release on. Still, I'd > like to see /someone/ to ensure the polish. It would be great to have > both QA team and Polish (UX) team. At present, we need to handle that. > But this change is fine. I'm looking forward to simplifying the test > cases. Yes, I agree we shouldn't lose the goal of trying to take care of polish entirely. Pity the desktop team isn't going to be at Flock :( > > * I watered down the artwork criterion yet further: the initial idea was > > that we were going to be super-keen about having a consistent background > > graphic from bootloader to desktop, but that's really fallen by the > > wayside since F14 or so. Given our overall boot process nowadays, it > > only seems particularly important to make sure we use the right image > > for the desktop background. It'd be great if the project goes back to > > that goal, but clearly so far there hasn't been the development > > commitment to keep it going. > > " All Fedora artwork visible in critical path actions on > release-blocking desktops must be consistent with the proposed final > theme." > > Maybe "must not be inconsistent"? They are hardly consistent now. > Plymouth theme is the same for years, GDM background has nothing to do > with desktop background. > > Maybe drop the sentence completely? Probably best to run it by the artwork team. I thought the 'must be consistent' wording was sufficiently weaselly to let us wave through stuff that isn't outrageously incongruent, but maybe it doesn't serve much of a purpose any more. Thanks for your thoughts! I'm planning to go back through and twiddle it based on all the feedback from various people at some point this week, then present a revised draft for review. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing
Re: what could screw up login credentials? [selinux, that's what]
On Tue, 2013-06-11 at 11:24 -0400, Tom Horsley wrote: > On Tue, 11 Jun 2013 11:16:27 -0400 > Daniel J Walsh wrote: > > > Sounds like you had a labeling issue. No reason that SELinux should block > > starting syslog, unless the system was mislabeled. > > I'm sure I did - I installed gazillions of updates while > booted into f18 by chrooting into the f19 partition to > do the updates and installs. Then instead of disabling SELinux, you should really just have forced a relabel. I think there's a kernel parameter to do it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Installer a little better, but...
On Tue, 2013-06-11 at 06:27 -0400, Tom Horsley wrote: > On Mon, 10 Jun 2013 19:09:47 -0700 > Adam Williamson wrote: > > > "They will be left untouched until you click on the > > main menu's "Begin Installation" button. > > Yea, but then what happens? You still have no idea. It ought to make it pretty clear that it's safe to just go ahead and click 'Done' and see what happens. > > we tried two other layouts before this one and > > people found both of those confusing too > > How about just starting directly in a screen listing > all the disks and partitions in a tree? I've never > understood what good the "select disks" step > is (especially if I have a pair of identical disks > in the system I can't possibly distinguish between > unless I have the serial numbers memorized :-). It is very useful if you want to be absolutely sure that a given disk will not be used at all, without using custom partitioning. We don't want to show everyone in the world a treeview of disks and partitions. In fact we don't want to show anyone a treeview of disks and partitions, because for everyone but those of us who've been looking at tree views of disks and partitions long enough that we have Stockholm Syndrome, it's a horrible and incomprehensible interface. And remember, it's 2013, we don't just care about partitions any more. We have RAID sets, LVM containers and btrfs containers to worry about. The newUI storage workflow is pretty clearly defined: pick some disks (or network storage devices or whatever), then pick what to do with their contents. I would like to take one more shot at the 'Done' button for F20, and I do think there are some issues with how the 'Installation Options' dialog behaves in complex cases, but overall I think the workflow is pretty good in F19, and once you're used to it, if you go back to F17, it seems like a mess. At least, it does to me. I don't really _enjoy_ creating LVM layouts or software RAID sets from scratch, the partition-by-partition way... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Final criteria revamp
On 06/11/2013 12:37 AM, "Jóhann B. Guðmundsson" wrote: Installing to a freespace should be uncontroversial indeed it's the resize I was referring to and as afaik when you buy a set of hardware with windows installed it does not come with "freespace" available and we should only be "supporting" dealing with factory defaults but as Samuel points out earlier in the thread The criteria specifically refers to installing to freespace, so other than the single partition reference what is the problem? If the user wants to install alongside a default windows install, they will either have to resize the partitions on their own or risk letting the installer resize it (if it will). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RAT mouse clicking problem
On Mon, 2013-06-10 at 18:12 +0800, Frederic Muller wrote: > Hi! > > I've installed TC2 and everything seems to run fine so far. I am however > running into an issue I had randomly under F18 (when the mouse was new) > where the (left) clicking seems to lock the mouse into the application > into which it clicks. The issue seems to be more systematic now but > maybe it's just the same. > > I did an extensive web search a few month back and came up with an added > /etc/X11/xorg.conf.d/03-rat.conf file which read this: > Section "InputClass" > Identifier "Mouse Remap" > MatchProduct "Saitek Cyborg R.A.T.7 Mouse" > MatchDevicePath "/dev/input/event*" > Option "Buttons" "17" > Option "ButtonMapping" "1 2 3 4 5 0 0 8 9 7 6 12 13 13 13 16 17 > 18 19 20 21" > Option "AutoReleaseButtons" "13 14 15" > Option "ZAxisMapping" "4 5 6 7" > EndSection > > On my first login the problem systematically appears, I then go to any > application that has a setting window that will come over the main > window, adjust the click to work properly (by clicking on the mode > button) and then log out and back in. I often use the > "Settings/Displays" app, disable a monitor, apply and then cancel the > changes. Canceling the changes doesn't initially work until switching > modes (by clicking on the "mode/preset" button 1/2 or 3 times). > > This fixes this issue. > > What would be the best way to get rid of this problem? Well, the first thing I'd do is figure out if my mouse was broken, by trying another one? I have to admit I don't _quite_ grok your mail, but it sure sounds like a weird/busted mouse issue. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: errors upgrading to 2
On Sun, 2013-06-09 at 11:42 -0700, Richard Vickery wrote: > In the middle of updating , I got these; how important are they? and,I > supopose, is the command to recover "db_runrecovery"? > > error: rpmdb: BDB0113 Thread/process 3820/139765024729088 failed: > BDB1507 Thread died in Berkeley DB library > error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: > Fatal error, run database recovery > error: cannot open Packages index using db5 - (-30973) > error: cannot open Packages database in > > error: rpmdb: BDB0113 Thread/process 4155/139803070191616 failed: > BDB1507 Thread died in Berkeley DB library 28 kB/s | 15 MB 01:57:16 > ETA > error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: > Fatal error, run database recovery > error: cannot open Packages index using db5 - (-30973) > error: cannot open Packages database in > error: rpmdb: BDB0113 Thread/process 4198/140301288781824 failed: > BDB1507 Thread died in Berkeley DB library 20 kB/s | 17 MB 02:38:16 > ETA > error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: > Fatal error, run database recovery > error: cannot open Packages index using db5 - (-30973) > error: cannot open Packages database in > error: rpmdb: BDB0113 Thread/process 4438/140296451778560 failed: > BDB1507 Thread died in Berkeley DB library8.0 kB/s | 86 MB 04:15:19 > ETA > error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: > Fatal error, run database recovery > error: cannot open Packages index using db5 - (-30973) > error: cannot open Packages database in > error: rpmdb: BDB0113 Thread/process 4526/140586095818752 failed: > BDB1507 Thread died in Berkeley DB library109 kB/s | 101 MB 00:16:13 > ETA > error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: > Fatal error, run database recovery > error: cannot open Packages index using db5 - (-30973) > error: cannot open Packages database in > error: rpmdb: BDB0113 Thread/process 4656/139997326555136 failed: > BDB1507 Thread died in Berkeley DB library311 kB/s | 114 MB 00:05:00 > ETA > error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: > Fatal error, run database recovery > error: cannot open Packages index using db5 - (-30973) > error: cannot open Packages database in > error: rpmdb: BDB0113 Thread/process 4689/140320299190272 failed: > BDB1507 Thread died in Berkeley DB library492 kB/s | 122 MB 00:02:54 > ETA > error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: > Fatal error, run database recovery > error: cannot open Packages index using db5 - (-30973) > error: cannot open Packages database in > error: rpmdb: BDB0113 Thread/process 4733/140155315288064 failed: > BDB1507 Thread died in Berkeley DB library325 kB/s | 138 MB 00:03:34 > ETA > error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: > Fatal error, run database recovery > error: cannot open Packages index using db5 - (-30973) > error: cannot open Packages database in > > Thanks for the feedback, if any? Should I even reboot the computer > before I correct it? The old-school dodge for this was 'rm -f /var/lib/rpm/__db*' then 'rpm --rebuilddb'. I am, of course, not responsible for data loss, emotional or physical pain, unexpected pregnancy or the end of this and/or any other universe which may result ;) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Schr@*!dinger*#@s Cat
On Tue, 2013-06-11 at 10:31 -0700, Chuck Forsberg WA7KGX N2469R wrote: > It seems the name of the Fedora 19 release is getting corrupted in > various places. > It might be breaking some scripts as well. > > It might be wise to eliminate the special characters (including the ' ) > before final release. Welcome to March, Chuck. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Late Gnome Test Day report
On Tue, 2013-06-11 at 10:22 -0400, Martin Holec wrote: > Hi, > > this is quick summary of Fedora 19 Gnome[1] Test Day. > Thanks to everybody who joined this event. Especially developers and QEs who > were available during all day on IRC and were assisting users with their > testing. > > [1] https://fedoraproject.org/wiki/Test_Day:2013-03-21_Gnome_3.8 > > = Fedora 19 Gnome Test Day report = > Please developers have a look at the following bugs (if you didn't > yet) as one of motivations for users to attend Test Days is that found > bugs will be fixed soon via updates after installation. > > Note, after almost 3 months there are lot of NEW bugs in Red Hat > Bugzilla in contrast to many RESOLVED in Gnome Bugzilla. If you need > any help with triaging bugs and testing bugfixes, feel free to contact > me. Thanks Martin! I just did a quick triage run through the RH bugs, and now it looks like this: 923102 CLOSED ERRATA - crash in intel_pstate_timer_func on virtualization 923364 CLOSED ERRATA - [3.7.92] Despite moving mouse in Black Screen(Blank Screen), gnome-shell doesn't switch to unlock screen 923994 CLOSED ERRATA - gdm has no user list 924229 NEW - unabel to boot fedora installed from liveCD - propably EFI bootloader? 924264 NEW - cannot be selected as a default app 924266 NEW - Cannot close an application in Activities if a modal window is currently blocking it (for Shotwell and Revelation) 924273 NEW - crash when viewing shotwell imported image 924277 CLOSED DUPLICATE - crash when scrolling 924285 CLOSED ERRATA - crash when doing organizing 924290 CLOSED NOTABUG - no quit super menu item 924295 CLOSED ERRATA - print option does nothing 924303 NEW - searching photos cannot be turned on/off 924306 CLOSED CURRENTRELEASE - SELinux is preventing /usr/lib/systemd/systemd-localed from 'search' accesses on the directory xorg.conf.d. 924312 CLOSED ERRATA - favourite icon is sooo ugly and should be placed better 924315 CLOSED ERRATA - no options bar after first right click on picture 924329 NEW - print test page does nothing 924343 NEW - after switching on/off stealth mode the other options state is not preserved 924360 NEW - Keyboard layout set on login screen doesn't persist after login 924368 NEW - svg not supported 924370 NEW - combo box disappears after first click 924371 CLOSED ERRATA - Set keyboard layout on one place only 924376 NEW - cannot zoom 924378 NEW - Unable to login as another user from the lock screen if the current user has no password 924379 NEW - cannot zoom with numerical +/- 924385 NEW - nouveau: graphic corruption after while 924392 CLOSED CURRENTRELEASE - Seahorse segfaults on startup 924396 CLOSED RAWHIDE - gnome-shell switching to All applications is very slow 924403 NEW - dragging icon of running Firefox to new workspace creates and destroys the workspace 924409 NEW - The master volume slider is not updated when changing volume 924699 CLOSED DUPLICATE - SELinux is preventing /usr/libexec/gdm-session-worker from 'write' accesses on the file .pwd.lock. 924776 CLOSED ERRATA - SELinux is preventing /usr/lib/systemd/systemd-localed from 'unlink' accesses on the file 00-keyboard.conf. 924795 NEW - No users on gdm when using "switch user" feature 924800 CLOSED ERRATA - root account in "User" dialog 924808 NEW - Shotwell is always opened on firs workspace 924813 NEW - Hide "enable account" for users with no password 924816 CLOSED ERRATA - Weird behavior of lock screen / gdm 927327 NEW - gnome-settings-daemon should cap maximum resolution at 2048 pixels in either dimension on Intel adapters that lose 3D acceleration above 2048 950051 NEW - I can add multiple alarms on same time 950062 NEW - Alarm doesn't run in background Closed some more out, but confirmed quite a lot more are still valid 3 months later (some are NEEDINFO, unfortunately my dumb 'bug list' command doesn't identify needinfo'ed bugs). Desktop team...I know you have this thing about not reading RH bugs...but it really does mean you miss out on what looks like some valuable information. Can't it be re-considered? Couldn't you at least task someone to take a sweep through the Test Day bugs? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anaconda grub install options?
On Jun 11, 2013, at 5:25 PM, Tom Horsley wrote: > On Tue, 11 Jun 2013 13:53:36 -0400 > Chris Murphy wrote: > >> The easier way to do this is to use one instance of GRUB 2 in the MBR gap, >> and then use configfile to load the grub.cfg for each distribution. Each >> distribution updates its respective grub.cfg when there are kernel updates, >> while static "master" grub.cfg uses configfile to forward to those >> distribution specific grub.cfg files. > > The configfile directive works only if all the modules and wot-not are > identical > in the different versions of grub. Current versions of GRUB should read past versions of GRUB2 going back to 1.97 using configfile. And it can read GRUB legacy (0.97) grub.conf files using legacy_configfile. > As the closest thing to "chainload" that is > actually officially supported by grub2, I prefer to use "multiboot". It seems > less likely to become incompatible when (not if :-) changes are made in new > versions of grub2. If the distribution with the newest version of GRUB has grub2-install run, such that the grub core.img and *.mod files it loads are also current, you shouldn't have an issue using just that copy of grub and loading the various grub.cfg or grub.conf files. If you do, it's a bug and should be fixed rather than coming up with Rube Goldberg methods of booting the computer. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anaconda grub install options?
On Tue, 11 Jun 2013 13:53:36 -0400 Chris Murphy wrote: > The easier way to do this is to use one instance of GRUB 2 in the MBR gap, > and then use configfile to load the grub.cfg for each distribution. Each > distribution updates its respective grub.cfg when there are kernel updates, > while static "master" grub.cfg uses configfile to forward to those > distribution specific grub.cfg files. The configfile directive works only if all the modules and wot-not are identical in the different versions of grub. As the closest thing to "chainload" that is actually officially supported by grub2, I prefer to use "multiboot". It seems less likely to become incompatible when (not if :-) changes are made in new versions of grub2. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: OK, How do I enable rsh now?
On Tue, 11 Jun 2013 13:54:07 -0400 Tom Horsley wrote: > But now it only appears to accept connections on localhost > (and I don't really need a remote connection to localhost :-). Finally figured it out - it was only listening on IPv6. https://bugzilla.redhat.com/show_bug.cgi?id=973348 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anaconda grub install options?
On 2013-06-11 11:00 (GMT-0500) David Lehman composed: https://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/s1-diskpartsetup-x86.html#s1-x86-bootloader Feel free to refer to the rest of that document to answer other questions you may have in the future -- that's what it's for. Would be nice if it was accessible while legible text size is passively enforced: Last July: http://fm.no-ip.com/SS/fedoradocs01.png Now: http://fm.no-ip.com/SS/fedoradocs02.png Lacking both passive legibility enforcement and zoom: http://fm.no-ip.com/SS/fedoradocs03.png -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Schr@*!dinger*#@s Cat
On Ter, 2013-06-11 at 10:31 -0700, Chuck Forsberg WA7KGX N2469R wrote: > It seems the name of the Fedora 19 release is getting corrupted in > various places. Could you specify where ? to fix it > It might be breaking some scripts as well. > > It might be wise to eliminate the special characters (including the ' ) > before final release. Is not a ' is a utf-8 character, decided by Fesco This subject was discussed at devl ML thread "fedora release name problem" : https://lists.fedoraproject.org/pipermail/devel/2013-March/thread.html > -- > Chuck Forsberg WA7KGX c...@omen.com www.omen.com > Developer of Industrial ZMODEM(Tm) for Embedded Applications >Omen Technology Inc "The High Reliability Software" > 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 > -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: OK, How do I enable rsh now?
On Tue, 11 Jun 2013 10:57:55 -0400 Tom Horsley wrote: > There are funny systemd rsh files now, not an /etc/xinetd.d/rsh > script to edit, but it doesn't seem to be a "real" systemd > service either. I finally found "systemctl enable rsh.socket" But now it only appears to accept connections on localhost (and I don't really need a remote connection to localhost :-). Does it start the service before the network is up or something? (I have NetworkManager off and am using network). I have all of firewalld, iptables, ip6tables turned off as well. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anaconda grub install options?
On Jun 11, 2013, at 9:06 AM, Tom Horsley wrote:
> Anyone know if there are plans to provide an option to
> anaconda so I can have it install all the needed files
> in /boot, but don't screw with the MBR?
No current plans, the --force option for grub2-install was removed in anaconda
18.x for F18. The option to install to /boot partition could safely be done to
/boot on Btrfs since it has such a large boot loader pad. But I think this is a
feature request down the road once /boot is no longer ext4 by default.
>
> I have just setup a nice stand alone grub2 partition
> where I can do stuff like this:
>
> menuentry 'Fedora 19 via multiboot' {
> insmod part_msdos
> insmod ext2
> set root='hd0,msdos2'
> multiboot /boot/grub2/i386-pc/core.img
> }
If this configuration file is to get GRUB Legacy to chain load GRUB 2, I'll
briefly wonder why you don't just bite the bullet and move to GRUB 2 and drop
an unmaintained boot loader.
If this configuration file is for GRUB 2 to chain load another instance of
GRUB2, I'll think you don't understand that a core.img has already been loaded
in order to understand the grub.cfg above in the first place.
>
> With just the right stuff in /boot and no screwing
> around with MBRs or partition boot sectors, I can boot
> multiple versions of fedora this way,
The easier way to do this is to use one instance of GRUB 2 in the MBR gap, and
then use configfile to load the grub.cfg for each distribution. Each
distribution updates its respective grub.cfg when there are kernel updates,
while static "master" grub.cfg uses configfile to forward to those distribution
specific grub.cfg files.
> but the way
> anaconda works (as near as I can tell, anyway) it
> will trash my stand-alone grub2 when I install a
> new fedora version.
Well it's fakaked in that if you install a boot loader, it will break the
function of the current boot loader. If you don't install a boot loader, then
it fails to create core.img, grub.cfg, and the various *.mod files in
/boot/grub2/i386. So yes, it's not very elegant.
Chris Murphy
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: Late Gnome Test Day report
-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Schr@*!dinger*#@s Cat
On Tue, Jun 11, 2013 at 10:31 AM, Chuck Forsberg WA7KGX N2469R wrote: > It seems the name of the Fedora 19 release is getting corrupted in various > places. > It might be breaking some scripts as well. > > It might be wise to eliminate the special characters (including the ' ) > before final release. > > -- > Chuck Forsberg WA7KGX c...@omen.com www.omen.com > Developer of Industrial ZMODEM(Tm) for Embedded Applications > Omen Technology Inc "The High Reliability Software" > 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test I don't think I have any issues with the accents. Rather, I'm sure that I don't. Are you sure that the corruption issues that you're having are not due to something else? Email accepts the accents? One could clearly conclude that accents in a release name ought neither produce problems? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: sound
"Adam Williamson" wrote: > the 'TC' numbers are only really relevant for the media, for an issue > like this it doesn't mean a lot. So, um - what did you 'upgrade' from, > exactly? Are you talking about going from F18 to F19, here? Or just > regular updates on F19? On Mon, Jun 10, 2013 at 11:47 PM, "Jóhann B. Guðmundsson" wrote: > On 06/11/2013 02:22 AM, Richard Vickery wrote: >> >> Hi gang: >> >> It may be my ignorance - I probably know this but am unaware of it at >> the moment; since upgrading to tc2 (and perhaps tc1), I lost my sound. >> Any hints on how to get it back? >> >> Thanks, >> Richard > > > Try running "pulseaudio -k && sleep 5 && pulseaudio -vvv" which kills the > pulseaudio daemon, sleeps for 5 seconds then start's it with verbose mode > then you can run "pulseaudio -k && sleep 5 && pulseaudio -D" to daemon-ized > it once again. > > JBG > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test Hi Adam, Johann: Adam, I was / am running the tc2 for F19 Johann and Adam, I found the solution later in the day - don't know the command but found it through X - by changing the output speakers; and this damn gmail system doesn't allow me to get mail from the Fedora lists until someone replies, so I couldn't really alert you and others of the updated situation. Thanks for the reply, I may likely have needed them had I not figured out the solution; although Mr. Guomundsson's solution returned the following: $ pulseaudio E: [pulseaudio] pid.c: Daemon already running. E: [pulseaudio] main.c: pa_pid_file_create() failed. $ pulseaudio -k && sleep 5 && pulseaudio -D E: [pulseaudio] main.c: Daemon startup failed. and I may have needed more information. Thanks again, Richard -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Schr@*!dinger*#@s Cat
It seems the name of the Fedora 19 release is getting corrupted in various places. It might be breaking some scripts as well. It might be wise to eliminate the special characters (including the ' ) before final release. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anaconda grub install options?
On Tue, 2013-06-11 at 09:06 -0400, Tom Horsley wrote:
> Anyone know if there are plans to provide an option to
> anaconda so I can have it install all the needed files
> in /boot, but don't screw with the MBR?
There is no option to install the bootloader to /boot, but there is an
option to not install any bootloader. See here:
https://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/s1-diskpartsetup-x86.html#s1-x86-bootloader
Feel free to refer to the rest of that document to answer other
questions you may have in the future -- that's what it's for.
>
> I have just setup a nice stand alone grub2 partition
> where I can do stuff like this:
>
> menuentry 'Fedora 19 via multiboot' {
> insmod part_msdos
> insmod ext2
> set root='hd0,msdos2'
> multiboot /boot/grub2/i386-pc/core.img
> }
>
> With just the right stuff in /boot and no screwing
> around with MBRs or partition boot sectors, I can boot
> multiple versions of fedora this way, but the way
> anaconda works (as near as I can tell, anyway) it
> will trash my stand-alone grub2 when I install a
> new fedora version.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Late Graphics Test Week report
Hi, this is quick summary of Fedora 19 Intel[1], Nouveau[2] and Radeon[3] Test Days. Thanks to everybody who joined this event. Especially developers and QEs who were available during all week on IRC and were assisting users with their testing. [1] https://fedoraproject.org/wiki/Test_Day:2013-04-23_Intel [2] https://fedoraproject.org/wiki/Test_Day:2013-04-24_Nouveau [3] https://fedoraproject.org/wiki/Test_Day:2013-04-25_Radeon = Fedora 19 Graphics Test Week report = Intel: 234567 CLOSED ERRATA - gdm crashes constantly in Parallels F7 install 924708 NEW - SELinux is preventing /usr/libexec/gdm-session-worker from 'remove_name' accesses on the directory nshadow. 927327 NEW - gnome-settings-daemon should cap maximum resolution at 2048 pixels in either dimension on Intel adapters that lose 3D acceleration above 2048 928741 CLOSED ERRATA - Totem crashes when I try to play ogv (ogg) 951810 NEW - [abrt] totem-3.8.0-1.fc19: oc_dec_init: Process /usr/bin/totem-video-thumbnailer was killed by signal 11 (SIGSEGV) 955785 NEW - VDrift game crashes on Intel graphics 955820 NEW - Laptop screen reset to minimum brightness when switching users 956389 NEW - SEGV in pymol doing Intel driver test case from test live CD 956746 NEW - Backlight minimum on resume (only when using Suspend from system menu) Nouveau: 234567 CLOSED ERRATA - gdm crashes constantly in Parallels F7 install 858503 NEW - display shows garbage after suspend/resume on W520 861939 NEW - [Nouveau] Missing some textures in fbo_firecube, teapot and reflect mesa demos 891505 NEW - Install of F18 not possible with GeForce GT 240 hardware 928741 CLOSED ERRATA - Totem crashes when I try to play ogv (ogg) 956171 NEW - Graphic doesn't resume correctly after suspend 956184 NEW - Resume failed on T430 956193 NEW - Rendering issues after fast user switching 956311 NEW - User Switching; X Win hang; render problem; button rendering 956362 NEW - circular locking dependency 956528 NEW - Strange window placing and resizing using multihead Radeon: 234567 CLOSED ERRATA - gdm crashes constantly in Parallels F7 install 924317 NEW - [r600, HD6570] Non-fatal crash: "KWin (kwin), signal: Bus error" 928741 CLOSED ERRATA - Totem crashes when I try to play ogv (ogg) 960138 NEW - Multihead: flickering on external display for HD 3450 Please developers have a look at the following bugs (if you didn't yet) as one of motivations for users to attend Test Days is that found bugs will be fixed soon via updates after installation. Note, after almost 2 months there are still lot of NEW bugs. If you need any help with triaging bugs and testing bugfixes, feel free to contact me. Best Regards, Martin Holec Desktop QE, Red Hat Brno -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Current status of previous F18 Graphics Test Week bugs
Current status of previous Fedora 18 Graphics Test Week bugreports: Nouveau: 745202 NEW - gnome-shell does not display correctly with NV3x adapters - multicolor corruption of panel, Shell-style menus and text [nvfx] -752613 NEW - Nivida 100M on Lenovo W520 Wont boot if using Discrete Graphics -806491 ON_QA - systemd-logind not tracking startx sessions -835648 NEW - kernel freeze after [drm] Initialized drm 1.1.0 20060810 on T520 with Quadro NVS 4200M +752613 NEW - Nvidia 100M on Lenovo W520 Wont boot if using Discrete Graphics +806491 CLOSED ERRATA - systemd-logind not tracking startx sessions +835648 CLOSED DUPLICATE - kernel freeze after [drm] Initialized drm 1.1.0 20060810 on T520 with Quadro NVS 4200M 848488 NEW - [abrt] extremetuxracer-0.4-9.fc17: size: Process /usr/bin/etracer was killed by signal 11 (SIGSEGV) -855560 NEW - F18 Live Alpha : nVidia GeForce 8600M GT, graphic driver (nouveau): very poor performance (vesa is fluid) -857267 ON_QA - SELinux is preventing /usr/bin/totem-video-thumbnailer from 'create' accesses on the directory gstreamer-1.0. +855560 CLOSED ERRATA - F18 Live Alpha : nVidia GeForce 8600M GT, graphic driver (nouveau): very poor performance (vesa is fluid) +857267 CLOSED ERRATA - SELinux is preventing /usr/bin/totem-video-thumbnailer from 'create' accesses on the directory gstreamer-1.0. 857662 CLOSED DUPLICATE - [mesa] libGL error: failed to open drm device 858503 NEW - display shows garbage after suspend/resume on W520 860215 NEW - [abrt]: WARNING: at kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90() @@ -16,13 +15,13 @@ 860265 NEW - NV44 Xorg segfault after suspend 860270 NEW - pure virtual function called crash 860360 NEW - Distorted text after system booted -860389 NEW - NVC8 wont suspend +860389 CLOSED DUPLICATE - NVC8 wont suspend 860405 NEW - Video with nVidia Corporation G73 [GeForce 7300 GT] does not come back after suspend 860407 NEW - system hangs while playing a video via totem and on pressing the windows key 860477 NEW - nouveau Xorg crash following boot (GTX 580) 860584 NEW - Incorrect video wake up with Nvidia G72M (Geforce Go 7300) and nouveau after suspend 860611 NEW - Freezed and/or black Xorg output (with cursor) on G72M with nouveau on 2nd display configuration (multihead) -860624 NEW - Gnome-shall hangs when requested activities +860624 NEW - Gnome-shell hangs when requested activities 860628 NEW - [abrt] mesa-demos-7.10-8.20101028.fc18: exit: Process /usr/lib64/mesa/fbo_firecube was killed by signal 6 (SIGABRT) 860637 NEW - Gnome-shell is slow after suspend-resume 860660 NEW - Transparency rendering problems on PyMOL with HD4890 and radeon driver @@ -39,6 +38,7 @@ 861946 NEW - Slow rendering in OpenArena 861951 NEW - Resume from suspend slowly freezes input. 861960 NEW - Disabling primary display when secondary is enabled blanks both of them -861969 NEW - Rendering glitch after resume from suspend +861969 CLOSED DUPLICATE - Rendering glitch after resume from suspend 862026 NEW - Rendering glitch after opening kickoff application launcher 862363 CLOSED UPSTREAM - OpenGL rendering on Quadro 310 10de:107d is not supported 882680 NEW - Since at least fedora-17, nouveau spawns black screen Radeon: 790365 NEW - Can't resume from suspend to RAM: Black screen and laptop frozen -847818 NEW - Radeon RS690M/X1200 screen corruption beyond kernel-3.4.6-2.fc17.i686 +847818 CLOSED CURRENTRELEASE - Radeon RS690M/X1200 screen corruption beyond kernel-3.4.6-2.fc17.i686 848488 NEW - [abrt] extremetuxracer-0.4-9.fc17: size: Process /usr/bin/etracer was killed by signal 11 (SIGSEGV) -849347 NEW - radeon driver cannot handle restarting xorg server sometimes (fails with: *ERROR* Failed to parse relocation -35!) +849347 CLOSED ERRATA - radeon driver cannot handle restarting xorg server sometimes (fails with: *ERROR* Failed to parse relocation -35!) 860451 NEW - Artifact between apply and rotated screen 860628 NEW - [abrt] mesa-demos-7.10-8.20101028.fc18: exit: Process /usr/lib64/mesa/fbo_firecube was killed by signal 6 (SIGABRT) 860660 NEW - Transparency rendering problems on PyMOL with HD4890 and radeon driver 860668 NEW - artifacts on xrestart with rv710 -860712 ASSIGNED - [6550D SUMO] problems with second monitor on VGA, causing GPU lockups +860712 CLOSED INSUFFICIENT_DATA - [6550D SUMO] problems with second monitor on VGA, causing GPU lockups 860779 NEW - Radeon HD6570 hangs on VT switching 860783 NEW - Radeon HD6570 GLX test failed (radeon test day) 860789 NEW - Multihead displays shows artifacts @@ -18,3 +20,7 @@ 861831 NEW - GNOME 3 Activities panel takes several minutes to appear after login on ATI FirePro V4800 861946 NEW - Slow rendering in OpenArena 862372 NEW - etracer killed with SIGABRT on quit 863281 NEW - Rendering / performance issues with polymol on ATI FirePro V4800 863302 NEW - Multiple screen desktop mirrored and corrupted after running
Re: what could screw up login credentials? [selinux, that's what]
On Tue, 11 Jun 2013 11:16:27 -0400 Daniel J Walsh wrote: > Sounds like you had a labeling issue. No reason that SELinux should block > starting syslog, unless the system was mislabeled. I'm sure I did - I installed gazillions of updates while booted into f18 by chrooting into the f19 partition to do the updates and installs. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: what could screw up login credentials? [selinux, that's what]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/11/2013 08:09 AM, Tom Horsley wrote: > On Mon, 10 Jun 2013 14:59:51 -0700 Samuel Sieb wrote: > >> Check the logs for selinux errors or boot with selinux in permissive >> mode. You may need to relabel the filesystem. > > Yep, it was definitely selinux. I couldn't check the logs though because > one of the services selinux prevented from starting was syslog :-). Once I > disabled selinux everything started working again. > Sounds like you had a labeling issue. No reason that SELinux should block starting syslog, unless the system was mislabeled. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3P0sACgkQrlYvE4MpobOvEgCfSs8THL2XdmwFRIoT87GYwqLw XlUAoN6oqG5QtRBBqOcBJGdc0wRMl7iR =+jMr -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
OK, How do I enable rsh now?
There are funny systemd rsh files now, not an /etc/xinetd.d/rsh script to edit, but it doesn't seem to be a "real" systemd service either. [Yes, yes, I know my hair will fall out and my teeth will turn blue if I use an insecure service like rsh - I don't care, OK?] -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Late KDE Test Day report
Hi, this is quick summary of Fedora 19 KDE[1] Test Day. Thanks to everybody who joined this event. Especially developers and QEs who were available during all day on IRC and were assisting users with their testing. [1] https://fedoraproject.org/wiki/Test_Day:2013-03-14_KDE_4.10 = Fedora 19 KDE Test Day report = RHBZ: 908380 CLOSED ERRATA - qt-at-spi module doesn't load due to kdeinit4 startup module linking issues 921632 NEW - wrong dpi in VM 921735 NEW - bad permissions after dragging from trash directly w/o restore 921742 NEW - DPMS control error from AC profile in VM 921778 NEW - fast user switching gives wrong hotkey help 921781 NEW - desktop effects are very slow with intel graphics and two monitors 922661 NEW - Calligra Words crashed when trying to save document 922668 NEW - Exporting simple spreadsheet to LibreOffice format made Calligra Sheets exhaust resources 922682 NEW - Calligra Flow is unable to save document in other than default format 922715 NEW - Recently Accessed files/folders are empty 922727 NEW - Google Chrome keeps popping up KDE Wallet dialogue 924767 NEW - kwin crashes after an external display is disconnected KDE BZ: 307990 CONFIRMED - Auto join jabber conference rooms 310162 ASSIGNED - Rekonq isn't usable with screen reader Orca 310166 UNCONFIRMED - Navigation by arrow in kickstarter menu isn't consistent in "Application" sub-menu. 310316 UNCONFIRMED - Rekonq won't resize flash-plugin frame when changing player size 318152 RESOLVED FIXED - Rekonq remembers previously closed tabs on next startup 318184 UNCONFIRMED - KMail crash after removing recipient 319313 UNCONFIRMED - Select KDE accounts file 'text field' overflows Please developers have a look at the following bugs (if you didn't yet) as one of motivations for users to attend Test Days is that found bugs will be fixed soon via updates after installation. Note, after 3 months there are lot of NEW and UNCONFIRMED bugs in both bugzillas and only two bugs are actually RESOLVED or CLOSED. If you need any help with triaging bugs and testing bugfixes, feel free to contact me. Best Regards, Martin Holec Desktop QE, Red Hat Brno -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Late Gnome Test Day report
Hi, this is quick summary of Fedora 19 Gnome[1] Test Day. Thanks to everybody who joined this event. Especially developers and QEs who were available during all day on IRC and were assisting users with their testing. [1] https://fedoraproject.org/wiki/Test_Day:2013-03-21_Gnome_3.8 = Fedora 19 Gnome Test Day report = RHBZ: 923102 CLOSED ERRATA - crash in intel_pstate_timer_func on virtualization 923364 NEW - [3.7.92] Despite moving mouse in Black Screen(Blank Screen), gnome-shell doesn't switch to unlock screen 923994 NEW - gdm has no user list 924229 NEW - unabel to boot fedora installed from liveCD - propably EFI bootloader? 924264 NEW - cannot be selected as a default app 924266 NEW - Cannot close an application in Activities 924273 NEW - crash when viewing shotwell imported image 924277 NEW - crash when scrolling 924285 CLOSED ERRATA - crash when doing organizing 924290 CLOSED NOTABUG - no quit super menu item 924295 CLOSED ERRATA - print option does nothing 924303 NEW - searching photos cannot be turned on/off 924306 CLOSED CURRENTRELEASE - SELinux is preventing /usr/lib/systemd/systemd-localed from 'search' accesses on the directory xorg.conf.d. 924312 CLOSED ERRATA - favourite icon is sooo ugly and should be placed better 924315 NEW - no options bar after first right click on picture 924329 NEW - print test page does nothing 924343 NEW - after switching on/off stealth mode the other options state is not preserved 924360 NEW - Keyboard layout set on login screen doesn't persist after login 924368 NEW - svg not supported 924370 NEW - combo box disappears after first click 924371 NEW - Set keyboard layout on one place only 924376 NEW - cannot zoom 924378 NEW - Unable to login as another user from the lock screen if the current user has autologin enabled 924379 NEW - cannot zoom with numerical +/- 924385 NEW - nouveau: graphic corruption after while 924392 CLOSED CURRENTRELEASE - Seahorse segfaults on startup 924396 CLOSED RAWHIDE - gnome-shell switching to All applications is very slow 924403 NEW - dragging icon of running Firefox to new workspace creates and destroys the workspace 924409 NEW - The master volume slider is not updated when changing volume 924699 CLOSED DUPLICATE - SELinux is preventing /usr/libexec/gdm-session-worker from 'write' accesses on the file .pwd.lock. 924776 CLOSED ERRATA - SELinux is preventing /usr/lib/systemd/systemd-localed from 'unlink' accesses on the file 00-keyboard.conf. 924795 NEW - No users on gdm when using "switch user" feature 924800 NEW - root account in "User" dialog 924808 NEW - Shotwell is always opened on firs workspace 924813 NEW - Hide "enable account" for users with no password 924816 NEW - Weird behavior of lock screen / gdm 927327 NEW - gnome-settings-daemon should cap maximum resolution at 2048 pixels in either dimension on Intel adapters that lose 3D acceleration above 2048 950051 NEW - I can add multiple alarms on same time 950062 NEW - Alarm doesn't run in background Gnome BZ: 693910 NEW - power: Don't change the brightness on inactive sessions 694914 RESOLVED FIXED - classic mode: add a workspace indicator 696271 NEEDINFO - Complicated setting of keyboard layout 696280 UNCONFIRMED - Cannot change Bluetooth handset from HSP/HFP to A2DP 696284 UNCONFIRMED - 'Internal error' on connecting to Facebook 696285 RESOLVED FIXED - ownCloud: Check addressbook even if calendar fails 696293 RESOLVED DUPLICATE - Can't use the mouse scroller to zoom web content 696303 RESOLVED NOTGNOME - timezone setting is ignored 696304 RESOLVED FIXED - Can't create a new keyring with empty password 696308 RESOLVED INVALID - gnome-welcome-tour runs on every login 696317 UNCONFIRMED - Reloading a HTML5 video resets sound volume to 100% 696368 UNCONFIRMED - "Sort folders before files" is disabled by default 696371 RESOLVED DUPLICATE - Allow recording sound when using the integrated recorder 696372 RESOLVED FIXED - Changing file association makes the original default application disappear from properties, but not from menu 696374 RESOLVED FIXED - Display the same names in file context menu and file association properties 696377 UNCONFIRMED - Can't switch keyboard layout in gdm 696378 UNCONFIRMED - Dragged application from desktops overview shows on a wrong place. 696390 RESOLVED DUPLICATE - Nautilus crashes when setting background Please developers have a look at the following bugs (if you didn't yet) as one of motivations for users to attend Test Days is that found bugs will be fixed soon via updates after installation. Note, after almost 3 months there are lot of NEW bugs in Red Hat Bugzilla in contrast to many RESOLVED in Gnome Bugzilla. If you need any help with triaging bugs and testing bugfixes, feel free to contact me. Best Regards, Martin Holec Desktop QE, Red Hat Brno -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anaconda grub install options?
On Tue, 11 Jun 2013 09:46:48 -0400 Felix Miata wrote: > I've been installing Fedora sans bootloader ever since Grub Legacy was > dropped from installation media. But how? What option did I not see in the installer? It seems to be determined to install grub2 and overwrite MBR with no way to prevent it. Maybe I just missed going down the right spoke of the wheel :-). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anaconda grub install options?
On 2013-06-11 09:06 (GMT-0400) Tom Horsley composed: I have just setup a nice stand alone grub2 partition I've been installing Fedora sans bootloader ever since Grub Legacy was dropped from installation media. ... but the way anaconda works (as near as I can tell, anyway) it will trash my stand-alone grub2 when I install a new fedora version. If it's truly stand-alone, it shouldn't be mounted to /boot after it's been initialized. In such a scenario, there's no reason for it to get touched by any upgrade process. Once you have such a partition functional, short of a previously unsupported filesystem type from which kernels need to be loaded, there's no reason to upgrade it. If you symlink kernels and initrds to static names, it doesn't need maintenance either unless to add additional systems to boot or you rearrange partitioning. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-19 Branched report: 20130611 changes
Compose started at Tue Jun 11 09:15:03 UTC 2013 Broken deps for x86_64 -- [deltacloud-core] deltacloud-core-rhevm-1.1.3-1.fc19.noarch requires rubygem(rbovirt) >= 0:0.0.18 [dragonegg] dragonegg-3.1-19.fc19.x86_64 requires gcc = 0:4.7.2-9.fc19 [freeipa] freeipa-server-strict-3.2.0-2.fc19.x86_64 requires krb5-server = 0:1.11.2 [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.x86_64 requires servlet25 [koji] koji-vm-1.8.0-1.fc19.noarch requires python-virtinst [libkolab] php-kolab-0.4.1-3.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-kolab-0.4.1-3.fc19.x86_64 requires php(api) = 0:20100412-x86-64 [llvm] clang-3.3-0.4.rc2.fc19.i686 requires libstdc++-devel = 0:4.8.0 clang-3.3-0.4.rc2.fc19.i686 requires gcc = 0:4.8.0 clang-3.3-0.4.rc2.fc19.x86_64 requires libstdc++-devel = 0:4.8.0 clang-3.3-0.4.rc2.fc19.x86_64 requires gcc = 0:4.8.0 [nodejs-tilelive] nodejs-tilelive-4.4.3-2.fc19.noarch requires npm(optimist) < 0:0.4 [openbox] gdm-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel gnome-panel-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [ovirt-guest-agent] ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.x86_64 requires libgdmsimplegreeter.so.1()(64bit) [perl-Bio-ASN1-EntrezGene] perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) [perl-Bio-SamTools] perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) [postgresql-plparrot] postgresql-plparrot-0.05-4.fc19.x86_64 requires libparrot.so.5.0.0()(64bit) [python-TraitsBackendQt] python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI [scala] scala-2.9.2-2.fc19.noarch requires osgi(org.scala-ide.scala.library) [spacewalk-web] spacewalk-dobby-1.9.22-2.fc19.noarch requires perl(Spacewalk::Setup) [zarafa] php-mapi-7.0.13-1.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-mapi-7.0.13-1.fc19.x86_64 requires php(api) = 0:20100412-x86-64 Broken deps for i386 -- [deltacloud-core] deltacloud-core-rhevm-1.1.3-1.fc19.noarch requires rubygem(rbovirt) >= 0:0.0.18 [dragonegg] dragonegg-3.1-19.fc19.i686 requires gcc = 0:4.7.2-9.fc19 [freeipa] freeipa-server-strict-3.2.0-2.fc19.i686 requires krb5-server = 0:1.11.2 [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.i686 requires servlet25 [koji] koji-vm-1.8.0-1.fc19.noarch requires python-virtinst [libkolab] php-kolab-0.4.1-3.fc19.i686 requires php(zend-abi) = 0:20100525-x86-32 php-kolab-0.4.1-3.fc19.i686 requires php(api) = 0:20100412-x86-32 [llvm] clang-3.3-0.4.rc2.fc19.i686 requires libstdc++-devel = 0:4.8.0 clang-3.3-0.4.rc2.fc19.i686 requires gcc = 0:4.8.0 [nodejs-tilelive] nodejs-tilelive-4.4.3-2.fc19.noarch requires npm(optimist) < 0:0.4 [openbox] gdm-control-3.5.0-11.20121001git782b28.fc19.i686 requires gnome-panel gnome-panel-control-3.5.0-11.20121001git782b28.fc19.i686 requires gnome-panel [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [ovirt-guest-agent] ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.i686 requires libgdmsimplegreeter.so.1 [perl-Bio-ASN1-EntrezGene] perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) [perl-Bio-SamTools] perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::PrimarySeq) [postgresql-plparrot] postgresql-plparrot-0.05-4.fc19.i686 requires libparrot.so.5.0.0 [python-TraitsBackendQt] python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI [scala] scala-2.9.2-2.fc19.noarch requires osgi(org.scala-ide.scala.library) [spacewalk-web] spacewalk-dobby-1.9.22-2.fc19.noarch requires perl(Spacewalk::Setup) [zarafa] php-mapi-7.0.13-1.fc19.i686 requires php(zend-abi) = 0:20100525-x86-32 php-mapi-7.0.13-1.fc19.i686 requires php(api) = 0:20100412-x86-32 Summary: Added Packages: 0 Removed Packages: 0 Upgraded Packages: 0 Size of added packages: 0 (0 ) Size change of modified packages: 0 (0 ) Size of removed packages: 0 (0 ) Size change: 0 (0 ) Compose finished at Tue Jun 11 13:02:20 UTC 2013 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Anaconda grub install options?
Anyone know if there are plans to provide an option to
anaconda so I can have it install all the needed files
in /boot, but don't screw with the MBR?
I have just setup a nice stand alone grub2 partition
where I can do stuff like this:
menuentry 'Fedora 19 via multiboot' {
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
multiboot /boot/grub2/i386-pc/core.img
}
With just the right stuff in /boot and no screwing
around with MBRs or partition boot sectors, I can boot
multiple versions of fedora this way, but the way
anaconda works (as near as I can tell, anyway) it
will trash my stand-alone grub2 when I install a
new fedora version.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Final criteria revamp
On Jun 11, 2013, at 3:37 AM, Jóhann B. Guðmundsson wrote: > here's what Adam sait about that " if ntfsresize fails for some reason, that > wouldn't be a blocker." which kinda beats the purpose of the criteria right > ( since no factory install of windows comes with available free space so the > user always has to resize before or during the installation phaze ) Users installing Windows into a discrete space that's less than max available is the minority case, but that doesn't obviate the need for the criterion. Further, historically the part of the criterion that causes hold ups is the boot loader aspect, not resizing problems. If the anaconda team really considers resizing inherently risky and unpredictable, the operation needs to come with a warning to the user. Insofar as I'm aware, there is no such warning, or suggestion of alternatives: boot Windows and use its utility for resizing the file system. Then an install into free space is also possible. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Final criteria revamp
> Hey folks - so just ahead of the blocker meeting tomorrow, I'm done with > the Final criteria rewrite. Thanks a lot, I reviewed them and they seem to be fine. Some comments below. I noticed that the upgrade criterion went missing. But we already have one in Beta, and it seems to be the same. What am I missing? > * I wrote an exception for hardware-based services when the hardware > isn't present into the 'services' criterion: we waived a couple of > 'blockers' for F18 on the basis that it's okay if a service fails if > it's for hardware that isn't present, so I thought it made sense to > write that into the criterion. (Obviously it's best if we can make the > service not fire unless the hardware is present, but I don't think it > makes sense to block the release on that kind of thing). The "unless they require hardware which is not present" phrase could be separated into a comment box, so that the original sentence is cleaner. Just an idea. > SELinux and crash notifications > There must be no SELinux denial notifications or crash notifications after > boot of a release-blocking live image or at first login after a default > install of a release-blocking desktop. Should we add "during installation" as well? Wrt the bug discussed in the last blocker bug meeting. > > * I watered down the 'desktop' criteria quite a bit. Looking at them > afresh I really think we were kind of over-reaching when we wrote them > for F13: I remember we were thinking about 'polish criteria', but now > we've had this process in place for a while, it really doesn't make > sense to block the release on fairly trivial 'polish' issues (especially > when we happily ship with much bigger issues in slightly different other > areas). So I nuked the 'icons can't be fuzzy' requirement, the > requirement for Help and About menus to be present, and the bit about > apps not showing up twice in the menus. Those are all nice things to > check, but I really don't think we need to be blocking releases on them. I agree. These issues were too trivial to block release on. Still, I'd like to see /someone/ to ensure the polish. It would be great to have both QA team and Polish (UX) team. At present, we need to handle that. But this change is fine. I'm looking forward to simplifying the test cases. > > * I watered down the artwork criterion yet further: the initial idea was > that we were going to be super-keen about having a consistent background > graphic from bootloader to desktop, but that's really fallen by the > wayside since F14 or so. Given our overall boot process nowadays, it > only seems particularly important to make sure we use the right image > for the desktop background. It'd be great if the project goes back to > that goal, but clearly so far there hasn't been the development > commitment to keep it going. " All Fedora artwork visible in critical path actions on release-blocking desktops must be consistent with the proposed final theme." Maybe "must not be inconsistent"? They are hardly consistent now. Plymouth theme is the same for years, GDM background has nothing to do with desktop background. Maybe drop the sentence completely? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Final criteria revamp
On Jun 10, 2013, at 12:27 PM, Adam Williamson wrote: > On Mon, 2013-06-10 at 08:38 -0400, Chris Murphy wrote: > >> b. For BIOS installs, the requirement for the bootloader to boot both >> Windows and Fedora is reasonable. It's probably not reasonable, still, >> for UEFI. GRUB2+os-prober really isn't acting as a suitable >> replacement Boot Manager, so the user either needs to use the firmware >> boot manager to choose a bootloader (bootmgr.efi for Windows, >> grubx64.efi for Fedora), or some other boot manager (rEFInd or >> gummiboot). > > Well, I see the point, but at the same time, we are finding out that in > the Real World, it's a really bad idea to depend on the EFI boot manager > because it just isn't being presented to the user in a sane way in > enough of the real UEFI implementations. So we might actually want to > keep that requirement, and fix up os-prober (which we're currently > working on). > > We'll have to see what pjones' take on that is. The state of affairs with EFI boot managers being is not good, that's true. But GRUB doesn't fix this problem. It's a totally inadequate boot manager replacement on EFI right now. And it's unclear to me if that is even an eventual design goal of a future GRUB. Not only is Windows not added to the GRUB menu, grub-mkconfig is presently unfriendly to prior Fedora and other Linux installations by displaying them differently (and their entries don't even work, Bug 964828). Further, GRUB still depends 100% on a static grub.cfg which can be totally disconnected from the actual boot options for the computer. GRUB doesn't produce menu entries from NVRAM, or from available boot loaders on the available EFI System partitions. Despite highly variable interfaces, the built-in firmware boot managers do better than this. gummiboot does better. And rEFInd better still. So I don't see the point of parity in the criterion for GRUB BIOS and GRUB EFI when it comes to the requirement to show both Fedora and Windows options. >> >> I've only recently BIOS installed Windows 7, and it's two partitions >> to an unpartitioned disk. I think for EFI installing Windows 7, it's >> three partitions. For Windows 8 EFI, it's four partitions, so I'll >> guess it's one less for BIOS. > > What are the partitions? For BIOS Win 7 installs, one is a Microsoft reserved partition. Windows 8 on UEFI, one such system's partition map is in bug 971255 and looks like this: Number Start (sector)End (sector) Size Code Name 12048 616447 300.0 MiB 2700 Basic data partition 2 616448 819199 99.0 MiBEF00 EFI system partition 3 819200 1081343 128.0 MiB 0C01 Microsoft reserved part 4 1081344 12287 58.1 GiB0700 Basic data partition The Windows on a single partition case is pretty rare in any case. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: what could screw up login credentials? [selinux, that's what]
On Mon, 10 Jun 2013 14:59:51 -0700 Samuel Sieb wrote: > Check the logs for selinux errors or boot with selinux in permissive > mode. You may need to relabel the filesystem. Yep, it was definitely selinux. I couldn't check the logs though because one of the services selinux prevented from starting was syslog :-). Once I disabled selinux everything started working again. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20130611 changes
Compose started at Tue Jun 11 08:15:02 UTC 2013 Broken deps for x86_64 -- [bind10] bind10-1.0.0-3.fc20.i686 requires liblog4cplus-1.1.so.5 bind10-1.0.0-3.fc20.x86_64 requires liblog4cplus-1.1.so.5()(64bit) bind10-dhcp-1.0.0-3.fc20.i686 requires liblog4cplus-1.1.so.5 bind10-dhcp-1.0.0-3.fc20.x86_64 requires liblog4cplus-1.1.so.5()(64bit) bind10-dns-1.0.0-3.fc20.i686 requires liblog4cplus-1.1.so.5 bind10-dns-1.0.0-3.fc20.x86_64 requires liblog4cplus-1.1.so.5()(64bit) [ekiga] ekiga-4.0.1-1.fc19.x86_64 requires libedata-book-1.2.so.17()(64bit) [gdb-heap] gdb-heap-0.5-12.fc19.x86_64 requires glibc(x86-64) = 0:2.17 [glibc] glibc-utils-2.17.90-1.fc20.x86_64 requires libgd.so.2()(64bit) [gnuplot] gnuplot-4.6.2-2.fc20.x86_64 requires libgd.so.2()(64bit) gnuplot-minimal-4.6.2-2.fc20.x86_64 requires libgd.so.2()(64bit) [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.x86_64 requires servlet25 [koji] koji-vm-1.8.0-1.fc20.noarch requires python-virtinst [lancet] lancet-1.0.1-6.fc19.noarch requires ant-nodeps >= 0:1.7.1 [libgphoto2] libgphoto2-2.5.2-1.fc20.i686 requires libgd.so.2 libgphoto2-2.5.2-1.fc20.x86_64 requires libgd.so.2()(64bit) [libpst] libpst-0.6.59-1.fc20.x86_64 requires libgd.so.2()(64bit) [libpuzzle] libpuzzle-0.11-17.fc20.i686 requires libgd.so.2 libpuzzle-0.11-17.fc20.x86_64 requires libgd.so.2()(64bit) php-libpuzzle-0.11-17.fc20.x86_64 requires libgd.so.2()(64bit) [libst2205] libst2205-tools-1.4.3-5.fc19.x86_64 requires libgd.so.2()(64bit) [lutok] lutok-devel-0.2-4.fc19.i686 requires lua-devel < 0:5.2 lutok-devel-0.2-4.fc19.x86_64 requires lua-devel < 0:5.2 [m17n-lib] m17n-lib-tools-1.6.4-8.fc20.i686 requires libgd.so.2 m17n-lib-tools-1.6.4-8.fc20.x86_64 requires libgd.so.2()(64bit) [mapserver] mapserver-6.2.1-1.fc20.x86_64 requires libgd.so.2()(64bit) mapserver-java-6.2.1-1.fc20.x86_64 requires libgd.so.2()(64bit) mapserver-python-6.2.1-1.fc20.x86_64 requires libgd.so.2()(64bit) php-mapserver-6.2.1-1.fc20.x86_64 requires libgd.so.2()(64bit) [mrtg] mrtg-2.17.4-8.fc19.x86_64 requires libgd.so.2()(64bit) [mscgen] mscgen-0.20-6.fc19.x86_64 requires libgd.so.2()(64bit) [nagios] nagios-3.5.0-3.fc20.x86_64 requires libgd.so.2()(64bit) [nessus-core] nessus-client-2.2.11-11.fc20.x86_64 requires libgd.so.2()(64bit) nessus-gui-2.2.11-11.fc20.x86_64 requires libgd.so.2()(64bit) [nginx] 1:nginx-1.4.1-1.fc20.x86_64 requires libgd.so.2()(64bit) [nut] nut-cgi-2.6.5-12.fc20.x86_64 requires libgd.so.2()(64bit) [oggvideotools] oggvideotools-0.8-12.fc20.x86_64 requires libgd.so.2()(64bit) [openbox] gdm-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel gnome-panel-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel [openlierox] openlierox-0.59-0.11.beta10.fc20.x86_64 requires libgd.so.2()(64bit) [openscada] openscada-0.7.1-10.fc19.i686 requires libgd.so.2 openscada-0.7.1-10.fc19.x86_64 requires libgd.so.2()(64bit) openscada-UI-WebCfgd-0.7.1-10.fc19.x86_64 requires libgd.so.2()(64bit) openscada-UI-WebVision-0.7.1-10.fc19.x86_64 requires libgd.so.2()(64bit) [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [ovirt-guest-agent] ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.x86_64 requires libgdmsimplegreeter.so.1()(64bit) [oyranos] oyranos-libs-0.4.0-7.fc19.i686 requires libraw.so.5 oyranos-libs-0.4.0-7.fc19.x86_64 requires libraw.so.5()(64bit) [pcb] pcb-0.20110918-8.fc19.x86_64 requires libgd.so.2()(64bit) [perl-Bio-ASN1-EntrezGene] perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) [perl-Bio-SamTools] perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) [perl-GD] perl-GD-2.46-3.fc19.x86_64 requires libgd.so.2()(64bit) [perl-PDL] perl-PDL-2.4.10-6.fc19.x86_64 requires libgd.so.2()(64bit) [pstoedit] pstoedit-3.62-1.fc20.i686 requires libgd.so.2 pstoedit-3.62-1.fc20.x86_64 requires libgd.so.2()(64bit) [python-TraitsBackendQt] python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI [python-flask-admin] python-flask-admin-1.0.5-3.fc20.noarch requires python-wtf-peewee [python-gd] python-gd-0.56-5.fc19.x86_64 requires libgd.so.2()(64bit) [qpid-cpp] qpid-cpp-server-xml-0.20-6.fc20.x86_64 requires libxqilla.so.5()(64bit) [recoll] recoll-1.19.4-1.fc20.x86_64 requires librecoll.so.1.19.4()(64bit) [rmap] rmap-1.2-15.fc19.x86_64 r
Re: F19 - network instead NM is working now, but I have a question
On Tue, 2013-06-11 at 06:22 -0400, fla...@dailybrood.com wrote: > If you're using vlan would this work? "ip link add link eth0 name > eth0.10 type vlan id 10 (Creates a new vlan device eth0.10 on device > eth0)." > http://rpm.pbone.net/index.php3/stat/45/idpl/20307932/numer/8/nazwa/ip-link It should do. Anyway you will have to make ifcfg-... by hand and do things accordingly. ip link ... is for use in rc.local. Cristian Sava -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 - network instead NM is working now - alias interfaces are working!!!
I can also confirm that something like DEVICE=p2p1:0 in ifcfg-enp0s3:0 is now working with both NetworkManager or network!!! Congrats! Great work done! Cristian Sava -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 - network instead NM is working now, but I have a question
On Tue, 2013-06-11 at 10:59 +0300, Cristian Sava wrote: > I am testing F19-TC2 LXDE in a VirtualBox. > Now "network" instead NM is working as expected. > > We do not have the "device" mentioned in > /etc/sysconfig/network-scripts/ifcfg-enp0s3 > > How is advised to add an alias interface? > Do we have to get the interface name from "route" or whatever and add it > in ifcfg-enp0s3:0 as DEVICE=p2p1:0 ? > Do we still need to use /etc/rc.d/rc.local for that? > I did not find any obvious hint on the net, so an advice is welcome. I can confirm that something like DEVICE=p2p1:0 in ifcfg-enp0s3:0 is now working!!! Congrats! Good work done! [root@localhost network-scripts]# cat ifcfg-enp0s3 PEERROUTES="yes" IPV6INIT="yes" UUID="e4e1bc69-70c3-49d2-a991-68a8e7533485" IPV6_PEERDNS="yes" DEFROUTE="yes" PEERDNS="yes" IPV4_FAILURE_FATAL="no" HWADDR="08:00:27:88:5C:09" BOOTPROTO="dhcp" IPV6_DEFROUTE="yes" IPV6_AUTOCONF="yes" IPV6_FAILURE_FATAL="no" IPV6_PEERROUTES="yes" TYPE="Ethernet" ONBOOT="yes" NAME="enp0s3" [root@localhost network-scripts]# cat ifcfg-enp0s3:0 DEVICE="p2p1:0" PEERROUTES="yes" IPV6INIT="yes" UUID="e4e1bc69-70c3-49d2-a991-68a8e7533485" IPV6_PEERDNS="yes" DEFROUTE="yes" PEERDNS="yes" IPV4_FAILURE_FATAL="no" HWADDR="08:00:27:88:5C:09" #BOOTPROTO="dhcp" BOOTPROTO="none" IPADDR=10.0.2.246 NETMASK=255.255.255.0 IPV6_DEFROUTE="yes" IPV6_AUTOCONF="yes" IPV6_FAILURE_FATAL="no" IPV6_PEERROUTES="yes" TYPE="Ethernet" ONBOOT="yes" NAME="enp0s3:0" [root@localhost network-scripts]# ifup ifcfg-enp0s3:0 [root@localhost network-scripts]# route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default 10.0.2.20.0.0.0 UG0 00 p2p1 10.0.2.0* 255.255.255.0 U 0 00 p2p1 link-local * 255.255.0.0 U 1002 00 p2p1 [root@localhost network-scripts]# ifconfig lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 0 (Local Loopback) RX packets 12 bytes 720 (720.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12 bytes 720 (720.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 p2p1: flags=4163 mtu 1500 inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::a00:27ff:fe88:5c09 prefixlen 64 scopeid 0x20 ether 08:00:27:88:5c:09 txqueuelen 1000 (Ethernet) RX packets 65 bytes 8826 (8.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 110 bytes 12346 (12.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 p2p1:0: flags=4163 mtu 1500 inet 10.0.2.246 netmask 255.255.255.0 broadcast 10.0.2.255 ether 08:00:27:88:5c:09 txqueuelen 1000 (Ethernet) [root@localhost network-scripts]# Cristian Sava -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Installer a little better, but...
On Mon, 10 Jun 2013 19:09:47 -0700 Adam Williamson wrote: > "They will be left untouched until you click on the > main menu's "Begin Installation" button. Yea, but then what happens? You still have no idea. > we tried two other layouts before this one and > people found both of those confusing too How about just starting directly in a screen listing all the disks and partitions in a tree? I've never understood what good the "select disks" step is (especially if I have a pair of identical disks in the system I can't possibly distinguish between unless I have the serial numbers memorized :-). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 - network instead NM is working now, but I have a question
On 2013-06-11 03:59, Cristian Sava wrote: I am testing F19-TC2 LXDE in a VirtualBox. Now "network" instead NM is working as expected. We do not have the "device" mentioned in /etc/sysconfig/network-scripts/ifcfg-enp0s3 How is advised to add an alias interface? Do we have to get the interface name from "route" or whatever and add it in ifcfg-enp0s3:0 as DEVICE=p2p1:0 ? Do we still need to use /etc/rc.d/rc.local for that? I did not find any obvious hint on the net, so an advice is welcome. [cristi@localhost network-scripts]$ sudo systemctl disable NetworkManager.service [sudo] password for cristi: rm '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' rm '/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service' [cristi@localhost network-scripts]$ sudo systemctl stop NetworkManager.service [cristi@localhost network-scripts]$ sudo systemctl enable network.service network.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig network on [cristi@localhost network-scripts]$ sudo systemctl start network.service [cristi@localhost network-scripts]$ route Kernel IP routing table Destination GatewayGenmask Flags Metric RefUse Iface default 10.0.2.2 0.0.0.0 UG0 00 p2p1 10.0.2.0 * 255.255.255.0 U 1 00 p2p1 link-local* 255.255.0.0 U 1002 00 p2p1 [cristi@localhost network-scripts]$ ping fw.xx.yy.ro PING fw.xx.yy.ro (193.x.y.253) 56(84) bytes of data. 64 bytes from fw.xx.yy.ro (193.x.y.253): icmp_seq=1 ttl=63 time=2.06 ms 64 bytes from fw.xx.yy.ro (193.x.y.253): icmp_seq=2 ttl=63 time=0.801 ms 64 bytes from fw.xx.yy.ro (193.x.y.253): icmp_seq=3 ttl=63 time=0.808 ms ^C --- fw.xx.yy.ro ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 0.801/1.223/2.061/0.593 ms [cristi@localhost network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-enp0s3 PEERROUTES="yes" IPV6INIT="yes" UUID="e4e1bc69-70c3-49d2-a991-68a8e7533485" IPV6_PEERDNS="yes" DEFROUTE="yes" PEERDNS="yes" IPV4_FAILURE_FATAL="no" HWADDR="08:00:27:88:5C:09" BOOTPROTO="dhcp" IPV6_DEFROUTE="yes" IPV6_AUTOCONF="yes" IPV6_FAILURE_FATAL="no" IPV6_PEERROUTES="yes" TYPE="Ethernet" ONBOOT="yes" NAME="enp0s3" [cristi@localhost network-scripts]$ Cristian Sava If you're using vlan would this work? "ip link add link eth0 name eth0.10 type vlan id 10 (Creates a new vlan device eth0.10 on device eth0)." http://rpm.pbone.net/index.php3/stat/45/idpl/20307932/numer/8/nazwa/ip-link -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 18 updates-testing report
The following Fedora 18 Security updates need testing: Age URL 153 https://admin.fedoraproject.org/updates/FEDORA-2013-0416/fedora-business-cards-1-0.1.beta1.fc18 87 https://admin.fedoraproject.org/updates/FEDORA-2013-3935/puppet-3.1.1-1.fc18 80 https://admin.fedoraproject.org/updates/FEDORA-2013-4243/stunnel-4.55-1.fc18 67 https://admin.fedoraproject.org/updates/FEDORA-2013-4823/microcode_ctl-2.0-3.fc18 52 https://admin.fedoraproject.org/updates/FEDORA-2013-6117/eucalyptus-3.2.2-1.fc18 25 https://admin.fedoraproject.org/updates/FEDORA-2013-8381/varnish-3.0.3-5.fc18 11 https://admin.fedoraproject.org/updates/FEDORA-2013-9707/livecd-tools-18.16-2.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-9950/perl-Dancer-1.3100-3.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-9962/subversion-1.7.10-1.fc18 5 https://admin.fedoraproject.org/updates/FEDORA-2013-10136/xen-4.2.2-6.fc18 5 https://admin.fedoraproject.org/updates/FEDORA-2013-10138/gallery3-3.0.8-1.fc18 5 https://admin.fedoraproject.org/updates/FEDORA-2013-10130/analitza-4.10.4-1.fc18,ark-4.10.4-1.fc18,audiocd-kio-4.10.4-1.fc18,blinken-4.10.4-1.fc18,bomber-4.10.4-1.fc18,bovo-4.10.4-1.fc18,cantor-4.10.4-1.fc18,dragon-4.10.4-1.fc18,filelight-4.10.4-1.fc18,granatier-4.10.4-1.fc18,gwenview-4.10.4-1.fc18,jovie-4.10.4-1.fc18,juk-4.10.4-1.fc18,kaccessible-4.10.4-1.fc18,kactivities-4.10.4-1.fc18,kajongg-4.10.4-1.fc18,kalgebra-4.10.4-1.fc18,kalzium-4.10.4-1.fc18,kamera-4.10.4-1.fc18,kanagram-4.10.4-1.fc18,kapman-4.10.4-1.fc18,kate-4.10.4-1.fc18,katomic-4.10.4-1.fc18,kblackbox-4.10.4-1.fc18,kblocks-4.10.4-1.fc18,kbounce-4.10.4-1.fc18,kbreakout-4.10.4-1.fc18,kbruch-4.10.4-1.fc18,kcalc-4.10.4-1.fc18,kcharselect-4.10.4-1.fc18,kcolorchooser-4.10.4-1.fc18,kdeaccessibility-4.10.4-1.fc18,kdeadmin-4.10.4-1.fc18,kdeartwork-4.10.4-1.fc18,kde-baseapps-4.10.4-1.fc18,kde-base-artwork-4.10.4-1.fc18,kdebindings-4.10.4-1.fc18,kdeedu-4.10.4-1.fc18,kdegames-4.10.4-1.fc18,kdegraphics-4.10.4-1.fc18,kdegraphics-mobipocket-4.10.4-1.fc18,kdegraphics-strigi-analyzer-4.10.4-1.fc18,kdegraphics-thumbnailers-4.10.4-1.fc18,kde-l10n-4.10.4-1.fc18,kdelibs-4.10.4-1.fc18,kdemultimedia-4.10.4-1.fc18,kdenetwork-4.10.4-1.fc18,kdepim-4.10.4-1.fc18,kdepimlibs-4.10.4-2.fc18,kdepim-runtime-4.10.4-1.fc18.1,kdeplasma-addons-4.10.4-2.fc18,kde-print-manager-4.10.4-1.fc18,kde-runtime-4.10.4-1.fc18,kdesdk-4.10.4-1.fc18,kdetoys-4.10.4-1.fc18,kdeutils-4.10.4-1.fc18,kde-wallpapers-4.10.4-1.fc18,kde-workspace-4.10.4-1.fc18,kdf-4.10.4-1.fc18,kdiamond-4.10.4-1.fc18,kfloppy-4.10.4-1.fc18,kfourinline-4.10.4-1.fc18,kgamma-4.10.4-1.fc18,kgeography-4.10.4-1.fc18,kgoldrunner-4.10.4-1.fc18,kgpg-4.10.4-1.fc18,khangman-4.10.4-1.fc18,kig-4.10.4-1.fc18,kigo-4.10.4-1.fc18,killbots-4.10.4-1.fc18,kimono-4.10.4-1.fc18,kiriki-4.10.4-1.fc18,kiten-4.10.4-1.fc18,kjumpingcube-4.10.4-1.fc18,klettres-4.10.4-1.fc18,klickety-4.10.4-1.fc18,klines-4.10.4-1.fc18,kmag-4.10.4-1.fc18,kmahjongg-4.10.4-1.fc18,kmines-4.10.4-1.fc18,kmix-4.10.4-1.fc18,kmousetool-4.10.4-1.fc18,kmouth-4.10.4-1.fc18,kmplot-4.10.4-1.fc18,knavalbattle-4.10.4-1.fc18,knetwalk-4.10.4-1.fc18,kolf-4.10.4-1.fc18,kollision-4.10.4-1.fc18,kolourpaint-4.10.4-1.fc18,konquest-4.10.4-1.fc18,konsole-4.10.4-1.fc18,kpat-4.10.4-1.fc18,kremotecontrol-4.10.4-1.fc18,kreversi-4.10.4-1.fc18,kross-interpreters-4.10.4-1.fc18,kruler-4.10.4-1.fc18,ksaneplugin-4.10.4-1.fc18,kscd-4.10.4-1.fc18,kshisen-4.10.4-1.fc18,ksirk-4.10.4-1.fc18,ksnakeduel-4.10.4-1.fc18,ksnapshot-4.10.4-1.fc18,kspaceduel-4.10.4-1.fc18,ksquares-4.10.4-1.fc18,kstars-4.10.4-1.fc18,ksudoku-4.10.4-1.fc18,ktimer-4.10.4-1.fc18,ktouch-4.10.4-1.fc18,ktuberling-4.10.4-1.fc18,kturtle-4.10.4-1.fc18,kubrick-4.10.4-1.fc18,kwallet-4.10.4-1.fc18,kwordquiz-4.10.4-1.fc18,libkcddb-4.10.4-1.fc18,libkcompactdisc-4.10.4-1.fc18,libkdcraw-4.10.4-1.fc18,libkdeedu-4.10.4-1.fc18,libkdegames-4.10.4-1.fc18,libkexiv2-4.10.4-1.fc18,libkipi-4.10.4-1.fc18,libkmahjongg-4.10.4-1.fc18,libksane-4.10.4-1.fc18,lskat-4.10.4-1.fc18,marble-4.10.4-1.fc18,nepomuk-core-4.10.4-1.fc18,nepomuk-widgets-4.10.4-1.fc18,okular-4.10.4-1.fc18,oxygen-icon-theme-4.10.4-1.fc18,pairs-4.10.4-1.fc18,palapeli-4.10.4-1.fc18,parley-4.10.4-1.fc18,picmi-4.10.4-1.fc18,pykde4-4.10.4-1.fc18,qyoto-4.10.4-1.fc18,rocs-4.10.4-1.fc18,ruby-korundum-4.10.4-1.fc18,ruby-qt-4.10.4-1.fc18,smokegen-4.10.4-1.fc18,smokekde-4.10.4-1.fc18,smokeqt-4.10.4-1.fc18,step-4.10.4-1.fc18,superkaramba-4.10.4-1.fc18,svgpart-4.10.4-1.fc18,sweeper-4.10.4-1.fc18 5 https://admin.fedoraproject.org/updates/FEDORA-2013-10097/libguestfs-1.20.8-1.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-10255/php-5.4.16-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-10309/rrdtool-1.4.8-2.fc18 2 https://admin.fedoraproject.org/updates/FEDORA-2013-10440/owncloud-4.5.12-1.fc18 2 https://admin.fedoraproject.org/updates/FEDORA-2013-10430/perl-Module-Signature-0.73-1.fc18 The following Fedora 18 Critical Path updates have ye
Fedora 17 updates-testing report
The following Fedora 17 Security updates need testing: Age URL 340 https://admin.fedoraproject.org/updates/FEDORA-2012-10269/revelation-0.4.14-1.fc17 153 https://admin.fedoraproject.org/updates/FEDORA-2013-0455/fedora-business-cards-1-0.1.beta1.fc17 80 https://admin.fedoraproject.org/updates/FEDORA-2013-4234/stunnel-4.55-1.fc17 79 https://admin.fedoraproject.org/updates/FEDORA-2013-4296/tomcat6-6.0.36-1.fc17 75 https://admin.fedoraproject.org/updates/FEDORA-2013-4501/libxslt-1.1.28-1.fc17 72 https://admin.fedoraproject.org/updates/FEDORA-2013-4581/libuser-0.57.6-2.fc17 60 https://admin.fedoraproject.org/updates/FEDORA-2013-5349/389-ds-base-1.2.11.21-1.fc17 18 https://admin.fedoraproject.org/updates/FEDORA-2013-8953/openjpeg-1.4-15.fc17 6 https://admin.fedoraproject.org/updates/FEDORA-2013-9961/perl-Dancer-1.3093-3.fc17 5 https://admin.fedoraproject.org/updates/FEDORA-2013-10128/ssmtp-2.61-20.fc17 5 https://admin.fedoraproject.org/updates/FEDORA-2013-10121/subversion-1.7.10-1.fc17 5 https://admin.fedoraproject.org/updates/FEDORA-2013-10168/gallery3-3.0.8-1.fc17 5 https://admin.fedoraproject.org/updates/FEDORA-2013-10182/analitza-4.10.4-1.fc17,ark-4.10.4-1.fc17,audiocd-kio-4.10.4-1.fc17,blinken-4.10.4-1.fc17,bomber-4.10.4-1.fc17,bovo-4.10.4-1.fc17,cantor-4.10.4-1.fc17,dragon-4.10.4-1.fc17,filelight-4.10.4-1.fc17,granatier-4.10.4-1.fc17,gwenview-4.10.4-1.fc17,jovie-4.10.4-1.fc17,juk-4.10.4-1.fc17,kaccessible-4.10.4-1.fc17,kactivities-4.10.4-1.fc17,kajongg-4.10.4-1.fc17,kalgebra-4.10.4-1.fc17,kalzium-4.10.4-1.fc17,kamera-4.10.4-1.fc17,kanagram-4.10.4-1.fc17,kapman-4.10.4-1.fc17,kate-4.10.4-1.fc17,katomic-4.10.4-1.fc17,kblackbox-4.10.4-1.fc17,kblocks-4.10.4-1.fc17,kbounce-4.10.4-1.fc17,kbreakout-4.10.4-1.fc17,kbruch-4.10.4-1.fc17,kcalc-4.10.4-1.fc17,kcharselect-4.10.4-1.fc17,kcolorchooser-4.10.4-1.fc17,kdeaccessibility-4.10.4-1.fc17,kdeadmin-4.10.4-1.fc17,kdeartwork-4.10.4-1.fc17,kde-baseapps-4.10.4-1.fc17,kde-base-artwork-4.10.4-1.fc17,kdebindings-4.10.4-1.fc17,kdeedu-4.10.4-1.fc17,kdegames-4.10.4-1.fc17,kdegraphics-4.10.4-1.fc17,kdegraphics-mobipocket-4.10.4-1.fc17,kdegraphics-strigi-analyzer-4.10.4-1.fc17,kdegraphics-thumbnailers-4.10.4-1.fc17,kde-l10n-4.10.4-1.fc17,kdelibs-4.10.4-1.fc17,kdemultimedia-4.10.4-1.fc17,kdenetwork-4.10.4-1.fc17,kdepim-4.10.4-1.fc17,kdepimlibs-4.10.4-2.fc17,kdepim-runtime-4.10.4-1.fc17,kdeplasma-addons-4.10.4-2.fc17,kde-print-manager-4.10.4-1.fc17,kde-runtime-4.10.4-1.fc17,kdesdk-4.10.4-1.fc17,kdetoys-4.10.4-1.fc17,kdeutils-4.10.4-1.fc17,kde-wallpapers-4.10.4-1.fc17,kde-workspace-4.10.4-1.fc17,kdf-4.10.4-1.fc17,kdiamond-4.10.4-1.fc17,kfloppy-4.10.4-1.fc17,kfourinline-4.10.4-1.fc17,kgamma-4.10.4-1.fc17,kgeography-4.10.4-1.fc17,kgoldrunner-4.10.4-1.fc17,kgpg-4.10.4-1.fc17,khangman-4.10.4-1.fc17,kig-4.10.4-1.fc17,kigo-4.10.4-1.fc17,killbots-4.10.4-1.fc17,kimono-4.10.4-1.fc17,kiriki-4.10.4-1.fc17,kiten-4.10.4-1.fc17,kjumpingcube-4.10.4-1.fc17,klettres-4.10.4-1.fc17,klickety-4.10.4-1.fc17,klines-4.10.4-1.fc17,kmag-4.10.4-1.fc17,kmahjongg-4.10.4-1.fc17,kmines-4.10.4-1.fc17,kmix-4.10.4-1.fc17,kmousetool-4.10.4-1.fc17,kmouth-4.10.4-1.fc17,kmplot-4.10.4-1.fc17,knavalbattle-4.10.4-1.fc17,knetwalk-4.10.4-1.fc17,kolf-4.10.4-1.fc17,kollision-4.10.4-1.fc17,kolourpaint-4.10.4-1.fc17,konquest-4.10.4-1.fc17,konsole-4.10.4-1.fc17,kpat-4.10.4-1.fc17,kremotecontrol-4.10.4-1.fc17,kreversi-4.10.4-1.fc17,kross-interpreters-4.10.4-1.fc17,kruler-4.10.4-1.fc17,ksaneplugin-4.10.4-1.fc17,kscd-4.10.4-1.fc17,kshisen-4.10.4-1.fc17,ksirk-4.10.4-1.fc17,ksnakeduel-4.10.4-1.fc17,ksnapshot-4.10.4-1.fc17,kspaceduel-4.10.4-1.fc17,ksquares-4.10.4-1.fc17,kstars-4.10.4-1.fc17,ksudoku-4.10.4-1.fc17,ktimer-4.10.4-1.fc17,ktouch-4.10.4-1.fc17,ktuberling-4.10.4-1.fc17,kturtle-4.10.4-1.fc17,kubrick-4.10.4-1.fc17,kwallet-4.10.4-1.fc17,kwordquiz-4.10.4-1.fc17,libkcddb-4.10.4-1.fc17,libkcompactdisc-4.10.4-1.fc17,libkdcraw-4.10.4-1.fc17,libkdeedu-4.10.4-1.fc17,libkdegames-4.10.4-1.fc17,libkexiv2-4.10.4-1.fc17,libkipi-4.10.4-1.fc17,libkmahjongg-4.10.4-1.fc17,libksane-4.10.4-1.fc17,lskat-4.10.4-1.fc17,marble-4.10.4-1.fc17,nepomuk-core-4.10.4-1.fc17,nepomuk-widgets-4.10.4-1.fc17,okular-4.10.4-1.fc17,oxygen-icon-theme-4.10.4-1.fc17,pairs-4.10.4-1.fc17,palapeli-4.10.4-1.fc17,parley-4.10.4-1.fc17,picmi-4.10.4-1.fc17,pykde4-4.10.4-1.fc17,qyoto-4.10.4-1.fc17,rocs-4.10.4-1.fc17,ruby-korundum-4.10.4-1.fc17,ruby-qt-4.10.4-1.fc17,smokegen-4.10.4-1.fc17,smokekde-4.10.4-1.fc17,smokeqt-4.10.4-1.fc17,step-4.10.4-1.fc17,superkaramba-4.10.4-1.fc17,svgpart-4.10.4-1.fc17,sweeper-4.10.4-1.fc17 4 https://admin.fedoraproject.org/updates/FEDORA-2013-10233/php-5.4.16-1.fc17 4 https://admin.fedoraproject.org/updates/FEDORA-2013-10247/xen-4.1.5-5.fc17 2 https://admin.fedoraproject.org/updates/FEDORA-2013-10415/perl-Module-Signature-0.73-1.fc17 0 https://admin.fedoraproject.org/updates/FEDORA-2013-9123/kernel-3.9.5-100.fc17 The following Fedora 17 Critical Path updates have yet to
F19 - network instead NM is working now, but I have a question
I am testing F19-TC2 LXDE in a VirtualBox. Now "network" instead NM is working as expected. We do not have the "device" mentioned in /etc/sysconfig/network-scripts/ifcfg-enp0s3 How is advised to add an alias interface? Do we have to get the interface name from "route" or whatever and add it in ifcfg-enp0s3:0 as DEVICE=p2p1:0 ? Do we still need to use /etc/rc.d/rc.local for that? I did not find any obvious hint on the net, so an advice is welcome. [cristi@localhost network-scripts]$ sudo systemctl disable NetworkManager.service [sudo] password for cristi: rm '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' rm '/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service' [cristi@localhost network-scripts]$ sudo systemctl stop NetworkManager.service [cristi@localhost network-scripts]$ sudo systemctl enable network.service network.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig network on [cristi@localhost network-scripts]$ sudo systemctl start network.service [cristi@localhost network-scripts]$ route Kernel IP routing table Destination GatewayGenmask Flags Metric RefUse Iface default 10.0.2.2 0.0.0.0 UG0 00 p2p1 10.0.2.0 * 255.255.255.0 U 1 00 p2p1 link-local* 255.255.0.0 U 1002 00 p2p1 [cristi@localhost network-scripts]$ ping fw.xx.yy.ro PING fw.xx.yy.ro (193.x.y.253) 56(84) bytes of data. 64 bytes from fw.xx.yy.ro (193.x.y.253): icmp_seq=1 ttl=63 time=2.06 ms 64 bytes from fw.xx.yy.ro (193.x.y.253): icmp_seq=2 ttl=63 time=0.801 ms 64 bytes from fw.xx.yy.ro (193.x.y.253): icmp_seq=3 ttl=63 time=0.808 ms ^C --- fw.xx.yy.ro ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 0.801/1.223/2.061/0.593 ms [cristi@localhost network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-enp0s3 PEERROUTES="yes" IPV6INIT="yes" UUID="e4e1bc69-70c3-49d2-a991-68a8e7533485" IPV6_PEERDNS="yes" DEFROUTE="yes" PEERDNS="yes" IPV4_FAILURE_FATAL="no" HWADDR="08:00:27:88:5C:09" BOOTPROTO="dhcp" IPV6_DEFROUTE="yes" IPV6_AUTOCONF="yes" IPV6_FAILURE_FATAL="no" IPV6_PEERROUTES="yes" TYPE="Ethernet" ONBOOT="yes" NAME="enp0s3" [cristi@localhost network-scripts]$ Cristian Sava -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 Final criteria revamp
On 06/11/2013 02:59 AM, Chris Murphy wrote: On Jun 10, 2013, at 1:51 PM, Jóhann B. Guðmundsson wrote: > >Resize and refitting another OS along with already installed one on the same hardware ( disks ) is not something I see as we should or could be "officially" supporting hence we should not be blocking our release for that. Certainly installing to free space should be uncontroversial. I don't care to understand the idea that user choice should only apply to FOSS. You either believe in user choice or you don't, it is a fairly binary position regardless of the software's license. The installer supports it, and considering the damage that could be done is in the category of data loss, yes it needs to have a suitable release blocking criterion. Installing to a freespace should be uncontroversial indeed it's the resize I was referring to and as afaik when you buy a set of hardware with windows installed it does not come with "freespace" available and we should only be "supporting" dealing with factory defaults but as Samuel points out earlier in the thread " I recently had the "fun" of installing Fedora beside Windows 7 on more than 10 different laptops. (This was for a class where the students were required to provide their own laptops.) The number of Windows partitions varied from 2 to 4. The 4 partition case required me to delete one of them because they were all primary partitions! Sorry, I don't remember what the contents were on the partitions. My guess of the options was boot, main OS, user data, system (BIOS config?), recovery. There was one Windows 8 laptop which was easier because it used GPT so I didn't have to mess with the partitions other than resizing them. " Which means today you are no longer dealing with a single partition ( atleast a rescue partition then 1 -3 windows partitions if you are using laptops ) so the user has to manually resize to fit Fedora along side it and here's what Adam sait about that " if ntfsresize fails for some reason, that wouldn't be a blocker." which kinda beats the purpose of the criteria right ( since no factory install of windows comes with available free space so the user always has to resize before or during the installation phaze ) " That is indeed the implication, it's intentional, and I wouldn't want to change it without input from the anaconda team. Their position is that resizing is inherently a risky and unpredictable operation that we cannot guarantee the functionality of, but we should be able to guarantee what's written in the criterion. I suppose we could try and come up with a tightly-worded criterion that the resize mechanism in the installer must not be broken - so it should 'do what it's supposed to do', but if ntfsresize fails for some reason, that wouldn't be a blocker." On top of that installer needs to support adding an entry for Fedora to the primary OS ( XP/Vista/Windows7/Windows8 ) already existing bootloader ( if the users chooses not to install grub but chooses using the windows bootloader in this case but the same should be apply to grub if installing alongside another linux distribution as in dualbooting ubuntu and fedora for example ) or adding a entry for the primary OS to grub ( if the user chose to install it ) to grub. And while we cant fully commit to "supporting" dual or multi booting then we should not have that in our criteria. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
