Am 10.11.2013 15:44, schrieb Rex Dieter:
Mark Bidewell wrote:
On Sat, Nov 9, 2013 at 1:12 PM, Rex Dieter wrote:
Probably the same problem, slower boots causing service timeouts all
over.
Thanks do you know if any progress is being made on the performance
issues?
Yes, (generally) tracke
Mark Bidewell wrote:
> On Sat, Nov 9, 2013 at 1:12 PM, Rex Dieter wrote:
>> Probably the same problem, slower boots causing service timeouts all
>> over.
> Thanks do you know if any progress is being made on the performance
> issues?
Yes, (generally) tracked here:
https://bugzilla.redhat.com/s
On Sat, Nov 9, 2013 at 1:12 PM, Rex Dieter wrote:
> Ron Yorston wrote:
>
> > Rex Dieter wrote:
> >>Mark Bidewell wrote:
> >>
> >>> I am using Fedora 19 on older hardware, and about half the time systemd
> >>> freezes on boot. Typically the console messaging is pointing at
> Network
> >>> Manage
Ron Yorston wrote:
> Rex Dieter wrote:
>>Mark Bidewell wrote:
>>
>>> I am using Fedora 19 on older hardware, and about half the time systemd
>>> freezes on boot. Typically the console messaging is pointing at Network
>>> Manager but occasionally kdm or gdm. I can switch to another console
>>> a
Rex Dieter wrote:
>Mark Bidewell wrote:
>
>> I am using Fedora 19 on older hardware, and about half the time systemd
>> freezes on boot. Typically the console messaging is pointing at Network
>> Manager but occasionally kdm or gdm. I can switch to another console and
>> log in and network is up
Mark Bidewell wrote:
> I am using Fedora 19 on older hardware, and about half the time systemd
> freezes on boot. Typically the console messaging is pointing at Network
> Manager but occasionally kdm or gdm. I can switch to another console and
> log in and network is up and I can enter X.
>
> A
For some reason it never registered that the "OK" is on the left now.
There is an "OK" after network manager, but the behavior seems different
after the latest updates. I wonder if its a GDM vs KDM issue. KDM seems
to start earlier in the boot process than GDM. GDM does seem more reliable.
On
On 11/08/2013 04:49 PM, Mark Bidewell wrote:
I will double check the status, but I don't believe one is printed. I
checked /var/log/messages And the is a message about being on IPv6 set
4 of 5. but ip addr show lists both IPv4 and IPv6 addresses.
Generally, when you're booting, you'll see ei
I will double check the status, but I don't believe one is printed. I
checked /var/log/messages And the is a message about being on IPv6 set 4
of 5. but ip addr show lists both IPv4 and IPv6 addresses.
On Fri, Nov 8, 2013 at 7:44 PM, Joe Zeff wrote:
> On 11/08/2013 04:34 PM, Mark Bidewell wr
On 11/08/2013 04:34 PM, Mark Bidewell wrote:
Generally, "Starting Network Manager".
Thanx. The reason I ask is that I've seen things like this pop up
before on web forums, and sometimes the last line quoted ends with [OK]
meaning, of course, that whatever starts *next* is what's causing the
Generally, "Starting Network Manager".
On Fri, Nov 8, 2013 at 7:32 PM, Joe Zeff wrote:
> On 11/08/2013 04:25 PM, Mark Bidewell wrote:
>
>> Any ideas how to debug this?
>>
>
> When this happens, what is the very last message on the main screen?
> --
> users mailing list
> users@lists.fedoraproje
On 11/08/2013 04:25 PM, Mark Bidewell wrote:
Any ideas how to debug this?
When this happens, what is the very last message on the main screen?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/user
I am using Fedora 19 on older hardware, and about half the time systemd
freezes on boot. Typically the console messaging is pointing at Network
Manager but occasionally kdm or gdm. I can switch to another console and
log in and network is up and I can enter X.
Any ideas how to debug this?
Thank
13 matches
Mail list logo
