[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: a number of system-config-<whatever> packages do not work



On Wednesday 02 September 2009 15:31:52 Tom London wrote:
> On Wed, Sep 2, 2009 at 12:22 PM, Gene Czarcinski<gene czarc net> wrote:
> > On Wednesday 02 September 2009 15:19:13 Gene Czarcinski wrote:
> >> On Wednesday 02 September 2009 14:43:35 Michael Cronenworth wrote:
> >> > Gene Czarcinski on 09/02/2009 01:42 PM wrote:
> >> > > Specifically, the following packages do not currently work:
> >> > >
> >> > > s-c-boot
> >> > > s-c-firewall (opens window frame and then hangs)
> >> > > s-c-printer (starts defining new printer and then hangs)
> >> > > s-c-selinux (msg and then craps out)
> >> > > s-c-user (missing domain definition .. bugzilla'ed)
> >> >
> >> > Do you have the assistive technologies stuff enabled?
> >> > System>Preferences>Technologies
> >>
> >> Yes, as a matter of fact I do ... must be the default on F12 since it is
> >> not enabled on F11.
> >>
> >> Update:
> >> s-c-boot: bugzilla 520887
> >> s-c-firewall: bugzilla 520883
> >> s-c-printer: bugzilla 520885
> >> s-c-selinux (policycoreutils package) .. not a bug (sort of) .. it does
> >> start ... on F11 starting takes about 15 seconds; on F12 starting takes
> >> over a minute and locks up a processor 100%
> >>
> >> I tried disabling the assistive technologies ... no change.
> >
> > I would appreciate it if someone else also on F12-alpha+current_rawhide
> > would give these a try.
> >
> > Gene
> >
> > --
>
> I'm running latest rawhide and system-config-printer "works for me":
> complains about not finding libgnomebreakpad.so, but starts up.
Another problem when I just did not wait long enough.  When I just sat there 
and waited, it finally worked OK (bugzilla report closed).

For one jetdirect printer on same subnet as my host, it was pretty quick but 
for another jetdirect printer on a separate (wireless) subnet, it took a 
while.
>
> system-config-firewall also complains about gnomebreakpad, then
> prompts for root password, and then displays a grayed out window while
> eating up 100% of CPU:
>
> [root tlondon ~]# ps algx | grep firewall
> 0   500 10239  1913  20   0 288124 13184 poll_s Sl+  pts/1      0:00
> system-config-firewall
> 4     0 10240 10239  20   0 145368  2372 wait   S+   pts/1      0:00
> /usr/sbin/userhelper -w system-config-firewall
> 4     0 10249 10240  20   0 464624 46552 -      R+   pts/1      1:32
> /usr/bin/python
> /usr/share/system-config-firewall/system-config-firewall.py
> 0     0 10267  2285  20   0  89080   856 pipe_w S+   pts/0      0:00
> grep firewall
> [root tlondon ~]#
>
> I killed the window after about 3-4 minutes of elapsed time.

I am su'ing to root and invoking s-c-f from the command line so I have not 
seen the prompt for root's password but other than that, it is the same.

I just did the same new printer definitions on a F11 system and it was a lot 
"faster" as compared to doing it on a F12 system.  I am not sure what is going 
on but there is something adding delay (using CPU time) on F12 as compared to 
F11 for both s-c-printer and s-c-selinux.

Gene


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]