On Thu, 2013-12-19 at 13:02 +1100, Ankur Sinha wrote:
> On Mon, 2013-12-16 at 13:50 -0800, Adam Williamson wrote:
> > Shell is running and "alt-f2, r" recovers, FWIW.
>
> Hrm, I tired 'alt f2 r' and it didn't recover for me. I'll try again.
Only works for Shell, of course.
> The issue Neal repor
On Mon, 2013-12-16 at 13:50 -0800, Adam Williamson wrote:
> Shell is running and "alt-f2, r" recovers, FWIW.
Hrm, I tired 'alt f2 r' and it didn't recover for me. I'll try again.
The issue Neal reported looks like the same thing?
I'll try to catch X logs next time this occurs.
--
Thanks,
Warm r
On Dec 16, 2013, at 2:50 PM, Adam Williamson wrote:
> On Mon, 2013-12-16 at 14:09 -0700, Chris Murphy wrote:
>> On Dec 16, 2013, at 1:47 PM, nonamedotc wrote:
>>
>>> On 12/11/2013 06:57 PM, Chris Murphy wrote:
On Dec 11, 2013, at 5:41 PM, Ankur Sinha wrote:
> On Wed, 2013
On Mon, 2013-12-16 at 14:09 -0700, Chris Murphy wrote:
> On Dec 16, 2013, at 1:47 PM, nonamedotc wrote:
>
> > On 12/11/2013 06:57 PM, Chris Murphy wrote:
> >>
> >> On Dec 11, 2013, at 5:41 PM, Ankur Sinha wrote:
> >>
> >>> On Wed, 2013-12-11 at 17:25 -0600, nonamedotc wrote:
>
> Is
On 12/16/2013 03:09 PM, Chris Murphy wrote:
On Dec 16, 2013, at 1:47 PM, nonamedotc wrote:
I might be **misunderstanding** - but with the kernel-3.12.5-301, the suspend
issue seems to be gone (in my tests - 3 repetitions).
Suspend *seems to work* without issues - Is this the case across
On Dec 16, 2013, at 1:47 PM, nonamedotc wrote:
> On 12/11/2013 06:57 PM, Chris Murphy wrote:
>>
>> On Dec 11, 2013, at 5:41 PM, Ankur Sinha wrote:
>>
>>> On Wed, 2013-12-11 at 17:25 -0600, nonamedotc wrote:
Is anyone still seeing this? Just curious as I have also been seeing
t
On 12/11/2013 06:57 PM, Chris Murphy wrote:
On Dec 11, 2013, at 5:41 PM, Ankur Sinha wrote:
On Wed, 2013-12-11 at 17:25 -0600, nonamedotc wrote:
Is anyone still seeing this? Just curious as I have also been seeing
this ...
I am. I can't reproduce it reliably though. It happens randomly he
On Dec 11, 2013, at 5:41 PM, Ankur Sinha wrote:
> On Wed, 2013-12-11 at 17:25 -0600, nonamedotc wrote:
>>
>> Is anyone still seeing this? Just curious as I have also been seeing
>> this ...
>
> I am. I can't reproduce it reliably though. It happens randomly here.
Maybe need to go to more ag
On Wed, 2013-12-11 at 17:25 -0600, nonamedotc wrote:
>
> Is anyone still seeing this? Just curious as I have also been seeing
> this ...
I am. I can't reproduce it reliably though. It happens randomly here.
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursi
On 12/10/2013 05:32 PM, Chris Murphy wrote:
On Dec 10, 2013, at 4:23 PM, Chris Murphy wrote:
Check systemd devel list, thread "udev rule not applied after resume from
sleep" and see if that's related.
http://lists.freedesktop.org/archives/systemd-devel/2013-December/015325.html
Chris Murp
On Dec 10, 2013, at 4:23 PM, Chris Murphy wrote:
>
> Check systemd devel list, thread "udev rule not applied after resume from
> sleep" and see if that's related.
http://lists.freedesktop.org/archives/systemd-devel/2013-December/015325.html
Chris Murphy
--
test mailing list
test@lists.fedora
On Dec 10, 2013, at 3:22 PM, Ankur Sinha wrote:
>
>> [asinha@ankur-laptop ~]$ sudo journalctl --no-pager --since="2013-12-10
>> 00:01" | egrep "systemd" | egrep "suspend|resume"
>> Dec 10 08:27:00 ankur-laptop systemd-sleep[20600]: System resumed.
>> Dec 10 08:46:35 ankur-laptop systemd-udevd[
On Tue, 2013-12-10 at 14:04 -0800, Adam Williamson wrote:
> I'm seeing something like this on my desktop lately, but I think it's
> actually suspend failing messily, not a problem on resume.
>
> Do you see something like this around the time of the attempted
> suspend?
I haven't been able to find
On Wed, 2013-12-11 at 08:39 +1100, Ankur Sinha wrote:
> On Tue, 2013-12-10 at 09:45 +1100, Ankur Sinha wrote:
> > Downgrade -> works
> >
> > Re-Upgrade to reproduce -> couldn't reproduce, started working.
> >
> > Oh well.
>
> *sigh* it happens again. Resume brought me to the fedora bubble. No
>
On Tue, 2013-12-10 at 09:45 +1100, Ankur Sinha wrote:
> Downgrade -> works
>
> Re-Upgrade to reproduce -> couldn't reproduce, started working.
>
> Oh well.
*sigh* it happens again. Resume brought me to the fedora bubble. No
gnome-shell screen lock. Any ideas on what to look for in journalctl?
--
On Tue, 2013-12-10 at 09:07 +1100, Ankur Sinha wrote:
> I'm going to try downgrading the package to see if that fixes it.
Downgrade -> works
Re-Upgrade to reproduce -> couldn't reproduce, started working.
Oh well.
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:A
Hi,
Of late, I only get the Fedora bubble when my system resumes from
suspend. The gnome-shell lock screen doesn't come up. Even heading to a
virtual terminal and restarting gnome-shell doesn't work. Is anyone else
seeing this? Any ideas on how I should go about debugging this? I didn't
find much
17 matches
Mail list logo
