Bugzappers: requests from maintainers for special treatment
by Adam Williamson
Hi, guys. Just a general issue mail for Bugzappers: I've recently been
talking to Seth Vidal, who wants special treatment for bugs in
components he maintains (yum and createrepo): he's happy for them to be
triaged according to the usual process, but he doesn't want the bugs
changed from NEW to ASSIGNED.
As a general principle, we should accept requests like this from the
owners of components, because we're here for them and not vice versa; if
our procedure doesn't work for them we should vary it so that what we do
is helping them and not frustrating them. We have a regular triager for
yum / createrepo who is aware of this (Jon Stanley), but anyone else who
happens to touch yum / createrepo bugs in future, please follow this
request.
We used to have a Special Procedures wiki page for exceptions like this;
it seems to have got pretty much lost in the recent wiki re-design. For
now I've revised
https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers#Set_Com... to add a new 'Special' column where we can add special instructions like this - I think that should be a good way to do it, as it's a high-visibility page that everyone should be looking at before triaging any given component. I envisage that short requests (like this one) can go directly in the table, longer ones could be added as footnotes (or to a separate page) and linked from the table.
(I took out the statistics from it, as discussed at the last meeting,
because they're obsolete and not helping anyone now, and the table
would've been getting too wide with those in it).
Does this seem sensible to everyone?
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
15 years, 1 month
Can't stop log
by Bill Davidsen
After I booted my FC11 test system and did an update, I tried to
shutdown and got this failure.
I clicked system->shutdown->shutdown_button and the system hung. An
investigation of the log shows that attached behavior.
If I log out and click the shutdown button it works, so it seems to only
happen when using the button while logged in.
Running 'shutdown -h' as root also works.
I assume that this is an SElinux behavior, before I BZ it, is it intentional?
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
Apr 29 09:39:13 fc11s1 ntpd[1350]: kernel time sync status change 0001
Apr 29 09:43:42 fc11s1 ntpd[1350]: synchronized to 69.10.36.4, stratum 2
Apr 29 09:43:48 fc11s1 yum: Updated: libgcc-4.4.0-3.i586
Apr 29 09:43:49 fc11s1 yum: Updated: kernel-headers-2.6.29.1-111.fc11.i586
Apr 29 09:43:50 fc11s1 yum: Updated: kernel-firmware-2.6.29.1-111.fc11.noarch
Apr 29 09:43:51 fc11s1 init: Re-executing /sbin/init
Apr 29 09:43:51 fc11s1 yum: Updated: glibc-2.9.90-22.i686
Apr 29 09:43:52 fc11s1 yum: Updated: libstdc++-4.4.0-3.i586
Apr 29 09:43:52 fc11s1 yum: Updated: 1:cups-libs-1.4-0.b2.15.fc11.i586
Apr 29 09:43:52 fc11s1 yum: Updated: libgomp-4.4.0-3.i586
Apr 29 09:43:52 fc11s1 yum: Updated: nash-6.0.83-1.fc11.i586
Apr 29 09:43:52 fc11s1 yum: Updated: grubby-6.0.83-1.fc11.i586
Apr 29 09:43:52 fc11s1 yum: Updated: 32:bind-libs-9.6.1-0.2.b1.fc11.i586
Apr 29 09:43:58 fc11s1 dbus: Reloaded configuration
Apr 29 09:44:05 fc11s1 yum: Updated: 1:gdm-2.26.1-4.fc11.i586
Apr 29 09:44:15 fc11s1 yum: Updated: glibc-common-2.9.90-22.i586
Apr 29 09:44:15 fc11s1 yum: Updated: mkinitrd-6.0.83-1.fc11.i586
Apr 29 09:44:16 fc11s1 yum: Updated: glibc-headers-2.9.90-22.i586
Apr 29 09:44:37 fc11s1 yum: Installed: kernel-2.6.29.1-111.fc11.i586
Apr 29 09:44:37 fc11s1 yum: Updated: cpp-4.4.0-3.i586
Apr 29 09:44:38 fc11s1 yum: Updated: gupnp-0.12.7-1.fc11.i586
Apr 29 09:44:38 fc11s1 yum: Updated: xorg-x11-drv-ati-6.12.2-7.fc11.i586
Apr 29 09:44:38 fc11s1 yum: Updated: 1:gdm-user-switch-applet-2.26.1-4.fc11.i586
Apr 29 09:44:38 fc11s1 yum: Updated: 32:bind-utils-9.6.1-0.2.b1.fc11.i586
Apr 29 09:44:38 fc11s1 yum: Updated: libbdevid-python-6.0.83-1.fc11.i586
Apr 29 09:44:38 fc11s1 dbus: Reloaded configuration
Apr 29 09:44:41 fc11s1 yum: Updated: 1:cups-1.4-0.b2.15.fc11.i586
Apr 29 09:44:41 fc11s1 yum: Updated: xorg-x11-drv-mga-1.4.10-1.fc11.i586
Apr 29 09:44:41 fc11s1 yum: Updated: upstart-0.3.9-24.fc11.i586
Apr 29 09:44:41 fc11s1 yum: Updated: nscd-2.9.90-22.i586
Apr 29 09:44:42 fc11s1 yum: Updated: glibc-devel-2.9.90-22.i586
Apr 29 09:44:42 fc11s1 yum: Updated: memtest86+-2.11-9.fc11.i586
Apr 29 09:44:43 fc11s1 yum: Updated: gcc-4.4.0-3.i586
Apr 29 09:46:39 fc11s1 init: tty4 main process (1443) killed by TERM signal
Apr 29 09:46:39 fc11s1 init: tty5 main process (1444) killed by TERM signal
Apr 29 09:46:39 fc11s1 init: tty2 main process (1454) killed by TERM signal
Apr 29 09:46:39 fc11s1 init: tty3 main process (1467) killed by TERM signal
Apr 29 09:46:39 fc11s1 init: tty6 main process (1468) killed by TERM signal
Apr 29 09:46:39 fc11s1 init: rc0 main process (5306) killed by TERM signal
Apr 29 09:46:39 fc11s1 gnome-session[1652]: WARNING: Unable to stop system: Not privileged for action: org.freedesktop.consolekit.system.stop no
Apr 29 09:46:39 fc11s1 gnome-session[1652]: WARNING: Unable to stop system: Not privileged for action: org.freedesktop.consolekit.system.stop no
Apr 29 09:46:39 fc11s1 gnome-session[1652]: WARNING: Unable to stop system: Not privileged for action: org.freedesktop.consolekit.system.stop no
Apr 29 09:46:39 fc11s1 gnome-session[1652]: WARNING: Unable to stop system: Not privileged for action: org.freedesktop.consolekit.system.stop no
Apr 29 09:46:39 fc11s1 gnome-session[1652]: WARNING: Unable to stop system: Not privileged for action: org.freedesktop.consolekit.system.stop no
15 years, 1 month
Re: Can't stop log
by Allen Kistler
Antonio Olivares wrote:
> --- On Thu, 4/30/09, Allen Kistler wrote:
>> I chased ConsoleKit, gnome-session, and a few others when I
>> saw this bug on my systems. I didn't get anywhere.
>> It's a challenging bug to chase, because it doesn't
>> always happen. Although I think it may be more reproducible
>> when going from runlevel 5 to runlevel 3, maybe because if
>> something's broken, it gets killed anyway in runlevel 0
>> or runlevel 6 when shutdown or reboot actually shuts down or
>> reboots.
>>
>> Anyway, I've seen people ask about this bug on this
>> list (with various subject lines, but always essentially the
>> same thing). I've seen other people file bugs and get
>> them marked as duplicate. I've seen people add
>> themselves as CCs on existing bugs. Even if I'm really
>> stupid, I'd think at least some of the people interested
>> in this bug are pretty bright. The fact that nobody seems
>> to have a handle on exactly what's going on is kind of
>> scary.
>>
>> For me, the power button and ACPI still team up to provide
>> a graceful shutdown, but that seems a bit inelegant.
>
> If you take another look at the attachment sent by Bill, the cultprit seems to be selinux not allowing shutdown. However, the updates might have fixed it? Don't know why but I have seen several of my rawhide machines doing this, but I did not bother to check what was going on and just pressed power button so that they could shutdown all the way.
>
> I know my bad, but I see it only on two of the five machines and others do shutdown properly so it seems to me that not all users out there are experiencing the same trouble(s).
I question SELinux as the root cause, because:
1. The problem has existed for a while with no AVC denial.
2. I ran in permissive mode, anyway, and still saw the bug.
3. The bug only happens sometimes, but SELinux would be all the time.
In other words, I think SELinux is a new bug that should be fixed, and I
think we still need to keep looking. I haven't done much testing in the
last week, half because of the freeze making nothing new available to
test. Now I've got a copy of the Preview DVD, so I'll crank it up again
today or tomorrow and see what I see. I heartily encourage everyone
else to do the same.
15 years, 1 month
vmware problem in F11
by Adrin Jalali
Hi.
I'm using F11, and I've installed vmware 6.5.2 on that. The problem is that
when I run microsoft windows which was working well before with F10, it
starts reading/wriying to my hard drive, which seems to be all page faults,
because there is no direct hard disk usage. All is IO wait. Partition type
is ext3. System RAM is 4GB and 2GB is dedicated for vmware.
Best,
Adrin.
15 years, 1 month
F11 Preview problems
by Jim Bevier
Hello all,
I tried the i386 live CD and i386 install DVD. I had a Nvidia Riva TNT card
in one system (I was running RedHat 7.1, don't ask), and it could not start
X during startup. I tried vga=791 and xdriver=vesa, but X would not work.
I removed the card and used the built-in video chip, and it started up
without a problem. Anyone know of a work around for this nvidia driver
problem? This system also had a second network card that was unused. F11
assigned the built-in ethernet to eth1 and the card to eth0. Of course, I
was using the built-in ethernet. Anyway to reassign which device is eth0 &
eth1?
The second system was a dual AMD system and installation went ok. It had
two ethernet cards, and was to be configured as a server/router between two
networks. (192.168.1.0 & 192.168.0.0) After some playing around, I
finally got sshd, rcp-server, nfs, telnetd, bind, and samba to work for my
internal domain. I could not get the vnc server (TigerVNC) to work. It
says it was missing some fonts. Anyone know what font I need to install to
get it to work?
One last thing, it seems the floppy disk light remains on all the time.
This is not the case on a rawhide system I have (not preview). Is this a
new "feature"?
I like the new graphics. I think the Fedora community will make themselves
proud with this release.
Jim
15 years, 1 month
F11 monitor configuration / virtualization
by Dennis Jacobfeuerborn
Hi,
Where did the monitor configuration go in f11? I've booted a virtualized
instance of F11 using kvm but can only get a maximum resolution of 800x600.
The monitor is displayed as "unknown" and there seems to be no way to
select one (like for example a generic 1280x1024 one).
I'm also running an instance of WinXP using kvm and there I get higher
resolutions out of the box.
Regards,
Dennis
15 years, 1 month
Re: Upgrade from Beta to Preview
by cmdrUNIX
> Is there a way to change from Beta to Preview with yum ? I checked
the
> preview and the fedora-release rpm is the same as the Beta release.
>>If you are willing to go past the preview use yum update.
What do you mean. I was running Fed 10 and did a yum upgrade . I have
been yum updating since yesterday morning. My system still shows
rawhide. I was just thinking that the preview release would change the
repos from Rawhide to Fed 11 or even 10.92 but I am thinking now that
it doesn't get changed until the Final release. I just do want to be
on rawhide once I am on Fed 11. I will run the rawhide on a different
boot disk or in a VM.
15 years, 1 month
