triage June 2009

triage@lists.fedoraproject.org

1 participants
281 discussions

[Bug 356961] Consider building with --with-xft=all
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=356961 Fedora Admin XMLRPC Client <fedora-admin-xmlrpc(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ville.skytta(a)iki.fi |loganjerry(a)gmail.com --- Comment #5 from Fedora Admin XMLRPC Client <fedora-admin-xmlrpc(a)redhat.com> 2009-06-15 14:00:22 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 205910] gnome-settings-daemon wakes up for every keypress
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=205910 --- Comment #9 from Matthias Clasen <mclasen(a)redhat.com> 2009-06-15 11:15:22 EDT --- by straceing it -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #35 from Michael Schwendt <mschwendt(a)gmail.com> 2009-06-15 09:46:19 EDT --- > obviously the daemon will not start It does. Please restart at comment 1. Thank you! -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #34 from Tomas Heinrich <theinric(a)redhat.com> 2009-06-15 09:35:46 EDT --- I'm not sure whether this is the right solution. Printing all the syntax errors from the init script can be pretty ugly. Maybe it would be better to just detect errors and issue one big red warning that you should check your configuration. What's worse is that rsyslog will keep spamming the console after startup. Regarding the other reasons that can prevent rsyslog from running, obviously the daemon will not start, which is the first clue that something is wrong, and the init script will issue a failure notification. Then it's up to you to investigate. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 205910] gnome-settings-daemon wakes up for every keypress
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=205910 William Lovaton <walovaton(a)yahoo.com.mx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |walovaton(a)yahoo.com.mx --- Comment #8 from William Lovaton <walovaton(a)yahoo.com.mx> 2009-06-15 09:20:15 EDT --- Is this still a problem?? how can I verify that g-s-d is waking up with every key press? I don't really know how to do that. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 213042] gnome-terminal cursor defaults to blinking
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=213042 William Lovaton <walovaton(a)yahoo.com.mx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |walovaton(a)yahoo.com.mx --- Comment #14 from William Lovaton <walovaton(a)yahoo.com.mx> 2009-06-15 09:14:39 EDT --- Yeah, it's not blinking by default, I think this bug report should be closed. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #33 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-06-15 02:18:13 EDT --- Yes, I made a mistake. Looks like /sbin/service does not prevent stderr from showing up ;) Find a fix for the recent v3-stable here: http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=ff6232d2bee06fbbc25ad8… It keeps stdout and stderr open across fork(). Thus, error messages can be seen at wherever they point to. I would still suggest to *log* the emitted error messages, if any, via a rule, because you obviously will not see these error messages during an automated system startup. Note that there is also an additional small cleanup fix in git (or remove the fprintf(stder, ...) after main() yourself. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

1 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #31 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-06-15 02:04:04 EDT --- > It does _not_ log them. At least not in the example I offer in this ticket. > Yes, it's bad luck that an entire rule gets disabled, see comment 14, please. You almost seem to intentionally misunderstand me. Look at the code, or do a *.* /path/to/file in your rsyslog.conf and you will see that rsyslog *does* log these messages. But no point in further arguing this... I made a test with stderr. I changed rsyslogd so that it keeps fd 2 open after a fork. Then I did /sbin/service rsyslog start Nothing showed up on the terminal. Just to make sure, I added an fprintf(stderr, "rsyslogd start\n"); right as the first line of main(). Again, I did a /sbin/service rsyslog start And again, nothing showed up at the controlling terminal. My conclusion is that /sbin/service does suppress the daemon's stderr. Am I wrong here? What kind of magic do I need to do to make stderr appear? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 199812] ACPI: Unable to turn cooling device [ffff81007ffa6810] 'on' is spewed repeatedly on the console
by Red Hat Bugzilla 15 Jun '09

15 Jun '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=199812 --- Comment #35 from yakui.zhao <yakui.zhao(a)intel.com> 2009-06-14 22:33:28 EDT --- Hi Will you please try the latest kernel(2.6.30-rc7) and see whether the issue still exists? IMO this issue is related with the broken BIOS. OS will verfity the power state again in course of power device transition. If it is not the expected power state, it will complain the above the warning message. This issue can be fixed by adding the boot option of "acpi.power_nocheck=1" since the 2.6.28 kernel. Please try it and see whether it still exists. Thanks -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

triage June 2009