On Mon, Oct 12, 2020 at 3:32 PM Samuel Sieb wrote:
> On 10/12/20 12:12 PM, Richard Shaw wrote:
> > I figured out the what, but not the why!
> >
> > Apparently having my Logitech USB dongle inserted locked up grub, but
> > that's a strange issue...
>
> You aren't the first to run into that. There
On 10/12/20 12:12 PM, Richard Shaw wrote:
I figured out the what, but not the why!
Apparently having my Logitech USB dongle inserted locked up grub, but
that's a strange issue...
You aren't the first to run into that. There are some suggestions
around. Try upgrading the firmware on the rec
I figured out the what, but not the why!
Apparently having my Logitech USB dongle inserted locked up grub, but
that's a strange issue...
Thanks,
Richard
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le.
I used my laptop all weekend without issue, I don't recall updating, but
this morning when I boot I see grub but no buttons work and the 5s
countdown doesn't change.
Ideas?
Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsub
Broken links return immediately and don't hang. on Production systems
the symlink to /mnt/nfsfs from wherever it needs to look like it is at
correctly allows pwd to work when the filesystem it is pointing at is
not responding.
On Sun, Dec 8, 2019 at 2:31 PM Patrick Dupre wrote:
>
> Thank for the
Thank for the suggestion.
Actually, I did the ssh mount in /mnt which avoids the mentioned issue.
However, I am reluctant to put a symbolic link on this directory, because
a ln on a "broken" link will probably generate the same issue.
>
> Hi.
>
> On Thu, 28 Nov 2019 12:27:53 +0100 "Patrick Dupre
Hi.
On Thu, 28 Nov 2019 12:27:53 +0100 "Patrick Dupre" wrote:
> To reproduce the bug (fedora 30)
> 1) Create a sshfs on a remote machine from your home directory
> (sshfs user@machine:/home/dir ~/SSHFS)
Using a subdir of your homedir as a network mountpoint if risky.
Roger Heflin indicated t
On 2019-11-28 22:39, Patrick Dupre wrote:
> Yes, probably, but if the network is never back correctly (time out, or
> "bad" network), then, it never recovers.
FWIW, I locked the screen and disconnected the network at 01:52. Then at 06:01
I reconnected
the network. I then was able to unlock the
> Sent: Thursday, November 28, 2019 at 3:25 PM
> From: "Ed Greshko"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome frozen when ssfhs stall
>
> On 2019-11-28 22:00, Patrick Dupre wrote:
> > But, just try to login when the cable is off.
> > If you
On 2019-11-28 22:00, Patrick Dupre wrote:
> But, just try to login when the cable is off.
> If you have a network of good quality, when you replug the cable
> to recover the connection easily.
> With a DSL connection, the network stalls periodically, and then does not
> recover.
I locked the scree
ent: Thursday, November 28, 2019 at 2:54 PM
> From: "Ed Greshko"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome frozen when ssfhs stall
>
> On 2019-11-28 21:24, Patrick Dupre wrote:
> > I made a mistake, in point 4). to be sure that is "work", you n
f the sshfs is in your homedir) must not be
> accomplished.
>
> In my opinion the same thing happen under gnome, frozen the login.
I just retested. I waited 5 minutes after disabling the NIC before enabling it
again.
No problem. I was able to unlock the screen and the mount was maintained.
I
ppen under gnome, frozen the login.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
T
On 2019-11-28 19:27, Patrick Dupre wrote:
> To reproduce the bug (fedora 30)
> 1) Create a sshfs on a remote machine from your home directory (sshfs
> user@machine:/home/dir ~/SSHFS)
> 2) Lock the screen (I use gnome)
> 3) Unplug the internet cable of your machine for example (the connection
> st
Bug #
1731645
To reproduce the bug (fedora 30)
1) Create a sshfs on a remote machine from your home directory (sshfs
user@machine:/home/dir ~/SSHFS)
2) Lock the screen (I use gnome)
3) Unplug the internet cable of your machine for example (the connection stalls
pretty often with a ADSL connection
On 2019-11-27 17:00, Patrick Dupre wrote:
> I already complained about the following issue, and I submitted the bug to
> bugzilla
> without feedback.
> If I have an open gnome session which turns to sleep because of a lack of
> activity. Then, if a sshfs connection stalls, there is no way to relog
In general if critical filesystems quit responding then everything
using them will hang.
Is critical files on the filesystem that gnome would need? if it is
the home dir then it is critical.
An old trick with nfs was do not ever mount it directly on /, as the
pwd command works by checking all fi
Hello,
I already complained about the following issue, and I submitted the bug to
bugzilla
without feedback.
If I have an open gnome session which turns to sleep because of a lack of
activity. Then, if a sshfs connection stalls, there is no way to relogin
through the gnome-session.
The only opti
> On 7/15/19 10:35 AM, Samuel Sieb wrote:
> > On 7/14/19 2:46 AM, Patrick Dupre wrote:
> >> OK, it works,
> >> 1) I have a sshfs connection to an external machine
> >> 2) I unplug the network
> >> 3) I lock the screen
> >> 4) I try to unclok the screen, but I cannot unlock
> >> 5) I log in a text t
On 7/15/19 10:35 AM, Samuel Sieb wrote:
> On 7/14/19 2:46 AM, Patrick Dupre wrote:
>> OK, it works,
>> 1) I have a sshfs connection to an external machine
>> 2) I unplug the network
>> 3) I lock the screen
>> 4) I try to unclok the screen, but I cannot unlock
>> 5) I log in a text terminal, and use
On 7/14/19 2:46 AM, Patrick Dupre wrote:
OK, it works,
1) I have a sshfs connection to an external machine
2) I unplug the network
3) I lock the screen
4) I try to unclok the screen, but I cannot unlock
5) I log in a text terminal, and use kill -HUP
6) I can unlock the screen
7) I replug the netw
>
> On 7/11/19 1:23 AM, Patrick Dupre wrote:
> > My interpretation is that gnome stuck only
> > gnome stuck when I try to leave the lock mode (no screensaver is activated)
> > and when the sshfs is stalled.
> >
> > What I cold try:
> > 1) stall the sshfs, how?
>
> Unplugging the network of the moun
On 7/11/19 1:23 AM, Patrick Dupre wrote:
My interpretation is that gnome stuck only
gnome stuck when I try to leave the lock mode (no screensaver is activated)
and when the sshfs is stalled.
What I cold try:
1) stall the sshfs, how?
Unplugging the network of the mounted system should do it. O
> On 7/10/19 2:28 PM, Patrick Dupre wrote:
> >> On 6/16/19 2:24 PM, Patrick Dupre wrote:
> >>> I though that it may be due to a mounted filesystem.
> >>> But it is not the case.
> >>
> >> You don't have any mounts that might become stale after an extended
> >> period of time?
> >
> > I noted that w
On 7/10/19 2:28 PM, Patrick Dupre wrote:
On 6/16/19 2:24 PM, Patrick Dupre wrote:
I though that it may be due to a mounted filesystem.
But it is not the case.
You don't have any mounts that might become stale after an extended
period of time?
I noted that when I make a sshfs to a machine thr
> On 7/10/19 2:07 PM, a...@clueserver.org wrote:
perl -pe 's/^\s+//g' *.py
>>> Am I supposed to run this command?
>>
>> That is a sig line joke. It removes leading white space from Python
>> programs. Don't run that.
>
> That is a very dangerous joke with no indication that it is your sig.
>
> On 6/16/19 2:24 PM, Patrick Dupre wrote:
> > Since I upgraded to fc30, if I do not use the PC for a while
> > the screen turns to lock (no screensaver is used).
> > Is this time is long, I may not be able to log in.
> > The screen remains frozen after I provide th
On 7/10/19 2:07 PM, a...@clueserver.org wrote:
perl -pe 's/^\s+//g' *.py
Am I supposed to run this command?
That is a sig line joke. It removes leading white space from Python
programs. Don't run that.
That is a very dangerous joke with no indication that it is your sig.
Yes, I realize tha
On 7/10/19 1:50 PM, a...@clueserver.org wrote:
I have seen this happen before. If you have nvidia-settings installed, but
do not have the commercial nvidia driver running, nvidia-settings makes a
whole bunch of duplicate connections to the xserver. Once it is full, you
cannot open new windows. (T
On 6/16/19 2:24 PM, Patrick Dupre wrote:
Since I upgraded to fc30, if I do not use the PC for a while
the screen turns to lock (no screensaver is used).
Is this time is long, I may not be able to log in.
The screen remains frozen after I provide the password.
Have you tried disabling the
On 7/10/19 1:33 PM, Patrick Dupre wrote:
On 6/17/19 1:03 PM, Patrick Dupre wrote:
From: "Samuel Sieb"
Where are you entering this? From a console or ssh?
Yes
That wasn't intended to be a yes or no question. I assume from the
answer below that it's a terminal console.
Try using "kill -HU
>> I have seen this happen before. If you have nvidia-settings installed,
>> but
>> do not have the commercial nvidia driver running, nvidia-settings makes
>> a
>> whole bunch of duplicate connections to the xserver. Once it is full,
>> you
>> cannot open new windows. (Things get very strange.)
>
>
> >>
> >> On 6/17/19 1:03 PM, Patrick Dupre wrote:
> >> >> From: "Samuel Sieb"
> >> >> Where are you entering this? From a console or ssh?
> >> > Yes
> >>
> >> That wasn't intended to be a yes or no question. I assume from the
> >> answer below that it's a terminal console.
> >>
> >> >> Try u
>>
>> On 6/17/19 1:03 PM, Patrick Dupre wrote:
>> >> From: "Samuel Sieb"
>> >> Where are you entering this? From a console or ssh?
>> > Yes
>>
>> That wasn't intended to be a yes or no question. I assume from the
>> answer below that it's a terminal console.
>>
>> >> Try using "kill -HUP" on t
>
> On 6/17/19 1:03 PM, Patrick Dupre wrote:
> >> From: "Samuel Sieb"
> >> Where are you entering this? From a console or ssh?
> > Yes
>
> That wasn't intended to be a yes or no question. I assume from the
> answer below that it's a terminal console.
>
> >> Try using "kill -HUP" on the gnome-she
On 6/17/19 1:03 PM, Patrick Dupre wrote:
From: "Samuel Sieb"
Where are you entering this? From a console or ssh?
Yes
That wasn't intended to be a yes or no question. I assume from the
answer below that it's a terminal console.
Try using "kill -HUP" on the gnome-shell process.
From a t
===
> Sent: Monday, June 17, 2019 at 7:40 AM
> From: "Samuel Sieb"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome frozen
>
> On 6/16/19 2:24 PM, Patrick Dupre wrote:
> > Since I upgraded to
On 6/16/19 2:24 PM, Patrick Dupre wrote:
Since I upgraded to fc30, if I do not use the PC for a while
the screen turns to lock (no screensaver is used).
Is this time is long, I may not be able to log in.
The screen remains frozen after I provide the password.
The only way to get access to a
Hello,
Since I upgraded to fc30, if I do not use the PC for a while
the screen turns to lock (no screensaver is used).
Is this time is long, I may not be able to log in.
The screen remains frozen after I provide the password.
The only way to get access to a graphics mode is to run
kill -9 -1
I
Hello,
Since I upgrade to fedora 30, I experience very often a frozen of the
graphics login process (gnome).
Actually, if I am inactive, the screen turn to lock, and I cannot
unlock it.
The only way to do something is to log in terminal mode and run
kill -9 -1
Also, it may be linked.
I lost
On 2017-01-04 23:40, Patrick O'Callaghan wrote:
On Wed, 2017-01-04 at 17:23 +0100, M. Fioretti wrote:
On 2017-01-04 16:22, M. Fioretti wrote:
...
I have noticed only now that the KDE toolbar is REALLY frozen: if I
type
"date" in a terminal, I get the current date (5:17pm
the fedora icon, it does not open the menu (it only did
> > once,
> > right after I logged in). If I click on the hour, it does not show the
> > calendar,
> > etc...
> >
> > No idea of what is happening, and if this and the keyboard thing are
> > related.
of what is happening, and if this and the keyboard thing are
related.
How could I debug this better?
I have noticed only now that the KDE toolbar is REALLY frozen: if I type
"date" in
a terminal, I get the current date (5:17pm as I write this). But the
clock widget
is stuck at 1:58p
On Sat, 2014-05-24 at 18:01 -0700, pat...@aracnet.com wrote:
> Playing back video (at least xine and mythtv), I get sound as
> expected, but the video just appears as a snapshot - no moving image.
I've had a similar problems, for a *very* long time, part way through
Fedora 9's lifecycle, with almo
On Sat, 24 May 2014 18:01:21 -0700
pat...@aracnet.com wrote:
> I'm using Intel integrated graphics via my motherboard:
Intel is the key: https://bugzilla.redhat.com/show_bug.cgi?id=1094519
Fiddling with acceleration settings in intel driver fixed
it for me:
https://bugs.freedesktop.org/show_bug
On Sat, May 24, 2014 at 06:01:21PM -0700, pat...@aracnet.com wrote:
> Hi -
>
> Playing back video (at least xine and mythtv), I get sound as expected,
> but the video just appears as a snapshot - no moving image.
>
> Booting back to kernel-3.13.11-100.fc19.x86_64, it works fine.
>
> Anyone else
Hi -
Playing back video (at least xine and mythtv), I get sound as expected,
but the video just appears as a snapshot - no moving image.
Booting back to kernel-3.13.11-100.fc19.x86_64, it works fine.
Anyone else having issues with 3.14.4 kernels, or know what might be wrong?
I'm using Intel int
On Fri, 07 Feb 2014 13:30:41 -0800
Ian Kelling wrote:
> I did
> /bin/yum -y install samba
My current favorite bug to blame all mysterious failures
on (especially if they occur at a yum install time or
during cron runs) is this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1043212
That mentio
I did
/bin/yum -y install samba
My screen immediately went to the fedora logo boot animation, then just
sat there frozen after the animation finished with a screen like this
http://fedoraproject.org/w/uploads/3/3b/F11_Snap_37.png. Ctrl-alt-f2 did
not work, and I had to hold the power button down
On Dec 13, 2013, at 4:08 AM, Patrick Dupre wrote:
>
> Dec 13 11:08:33 Homere kernel: [129085.227982] EXT4-fs (sdc5): error count: 34
> Dec 13 11:08:33 Homere kernel: [129085.228000] EXT4-fs (sdc5): initial error
> at 1375170459: ext4_mb_generate_buddy:755
> Dec 13 11:08:33 Homere kernel: [12908
Hello,
If I have an usb plugged in, if the screen move to lock, than I cannot
recover my gnome session.
On the key, there are 1 FAT parttion
1 NTFS partition,
2 ext4 partition (one is encripted luks)
Here is part of the /var/og/messages file:
Dec 13 11:03:33 Homere kernel: [128785.258833] EXT4-f
On 11/11/2013 01:05 PM, Carlos "casep" Sepulveda wrote:
On 11 November 2013 17:58, Patrick Dupre wrote:
Every time that I have an USB key plugged inside my computer, if it switches
to screensaver mode, I lost the access to the graphics session.
gnome3 on fedora18
Hi:
That's odd.
Anything int
On 11 November 2013 17:58, Patrick Dupre wrote:
> Every time that I have an USB key plugged inside my computer, if it switches
> to screensaver mode, I lost the access to the graphics session.
> gnome3 on fedora18
Hi:
That's odd.
Anything interesting in
/var/log/messages
or
/var/log/Xorg.0.log
?
Hello,
Every time that I have an USB key plugged inside my computer, if it switches
to screensaver mode, I lost the access to the graphics session.
gnome3 on fedora18
The only way that I found to recover is to open a text session and to kill the
graphic session.
Thank for your help.
===
Hello,
Every time that I have an USB key plugged inside my computer, if it switches
to screensaver mode, I lost the access to the graphics session.
gnome3 on fedora18
The only way that I found to recover is to open a text session and to kill the
graphic session.
Thank for your help.
===
On Thu, 8 Aug 2013, Patrick Dupre wrote:
Thank,
Here more information
Hello,
On a fedora 19 laptop, I use to experience frosing of the screen.
It may have different matter, like unable to compose in a terminal
window (but sill able to use the mouse), or in the worst situation,
the screen
Thank,
Here more information
>
> > Hello,
> >
> > On a fedora 19 laptop, I use to experience frosing of the screen.
> > It may have different matter, like unable to compose in a terminal
> > window (but sill able to use the mouse), or in the worst situation,
> > the screen remains black (no way t
On Thu, 8 Aug 2013, Patrick Dupre wrote:
Hello,
On a fedora 19 laptop, I use to experience frosing of the screen.
It may have different matter, like unable to compose in a terminal
window (but sill able to use the mouse), or in the worst situation,
the screen remains black (no way to use the ke
Hello,
On a fedora 19 laptop, I use to experience frosing of the screen.
It may have different matter, like unable to compose in a terminal
window (but sill able to use the mouse), or in the worst situation,
the screen remains black (no way to use the keyboard), ie. I need to
unpluck the laptop an
s 0x1 dmafis 0x1 sdbfis 0x0
>> [15523.867834] ata3: ATA_REG 0x40 ERR_REG 0x0
>> [15523.867840] ata3: tag : dhfis dmafis sdbfis sactive
>> [15523.867846] ata3: tag 0x0: 1 1 0 1
>> [15523.867868] ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0
>> action 0x6 frozen [15523.867876] ata
; [15523.867840] ata3: tag : dhfis dmafis sdbfis sactive
> [15523.867846] ata3: tag 0x0: 1 1 0 1
> [15523.867868] ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0
> action 0x6 frozen [15523.867876] ata3.00: failed command: WRITE
> FPDMA QUEUED [15523.867891] ata3.00: cmd
> 61/08:00:80
t_issue_tag 0x0
dhfis 0x1 dmafis 0x1 sdbfis 0x0
[15523.867834] ata3: ATA_REG 0x40 ERR_REG 0x0
[15523.867840] ata3: tag : dhfis dmafis sdbfis sactive
[15523.867846] ata3: tag 0x0: 1 1 0 1
[15523.867868] ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x6 frozen
[15523.867876] ata3.00: failed
On Fri, Mar 22, 2013 at 2:55 PM, Ian Malone wrote:
> On 22 March 2013 15:05, Patrick Dupre wrote:
> > Hello,
> >
> > In average, once a day my gnome session freezes. Only one option,
> > open a text session and try to kill the gnome-session!
> >
> > Any idea how to debug this?
> >
>
> Run top an
On 22 March 2013 15:05, Patrick Dupre wrote:
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
>
Run top and see what's going on. Should help answer the 'not enough
resources' que
On Fri, Mar 22, 2013 at 11:27 AM, Patrick Dupre wrote:
> On 2013-03-22 17:15, Dale Dellutri wrote:
>>
>> On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre wrote:
>>>
>>> Hello,
>>>
>>> In average, once a day my gnome session freezes. Only one option,
>>> open a text session and try to kill the gnom
On 2013-03-22 17:15, Dale Dellutri wrote:
On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre
wrote:
Hello,
In average, once a day my gnome session freezes. Only one option,
open a text session and try to kill the gnome-session!
Any idea how to debug this?
If this is a limited resource problem,
On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre wrote:
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
If this is a limited resource problem, then you'll need to run something w
On Fri, 22 Mar 2013 16:56:06 +0100
Patrick Dupre wrote:
> Frozen means, the mouse works but every thing else is frozen: all the
> displays in the top panel,
> no way to graphically interact.
> Do way to move to another workspace. Fortunately Ctl F2 works.
> It usually happens w
could possibly go in and shut down some
programs, but the system may need these to keep running.
You could get a faster computer, or more RAM, else there is no fix
for
a freeze, as far as I am aware. Though I too experience freezes in
f18.
I have 4 processors at 3.2 GHz and 8Go of RAM, what el
On Mar 22, 2013 8:06 AM, "Patrick Dupre" wrote:
>
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
>
> Thank.
>
> --
>
Hello,
In average, once a day my gnome session freezes. Only one option,
open a text session and try to kill the gnome-session!
Any idea how to debug this?
Thank.
--
==
Patrick DUPRÉ | | email: pdu...@kegtu
On 27 June 2011 05:56, L wrote:
<--SNIP-->
> thanks, I will give pidigin a go. my suspicions were firefox, or VirtualBox。
<--SNIP-->
Well, under gnome 3 it lacks damned pop-up windows but I like it for
simplicity and prefer it over empathy since the last was chosen as
default for gnome installati
On Mon, Jun 27, 2011 at 10:19 AM, Hiisi wrote:
> On 24 June 2011 10:24, L wrote:
>> Hi
>> After upgraded to fedora 15, most are working well. The gnome 3
>> desktop are weired. It frequently freeze, not responding to mouse or
>> keyboard. I have to login a virtual term (alt+ctrl+F2) to restart gd
On 24 June 2011 10:24, L wrote:
> Hi
> After upgraded to fedora 15, most are working well. The gnome 3
> desktop are weired. It frequently freeze, not responding to mouse or
> keyboard. I have to login a virtual term (alt+ctrl+F2) to restart gdm
> (init 3; init 5). I checked Xorg.0.log file and ou
On 06/24/2011 11:18 AM, L wrote:
> On Sat, Jun 25, 2011 at 4:14 AM, Dr. Michael J. Chudobiak
> wrote:
> After upgraded to fedora 15, most are working well. The gnome 3
> desktop are weired. It frequently freeze, not responding to mouse or
> keyboard. I have to login a virtual term (alt
On Sat, Jun 25, 2011 at 4:14 AM, Dr. Michael J. Chudobiak
wrote:
After upgraded to fedora 15, most are working well. The gnome 3
desktop are weired. It frequently freeze, not responding to mouse or
keyboard. I have to login a virtual term (alt+ctrl+F2) to restart gdm
(init 3; i
>>> After upgraded to fedora 15, most are working well. The gnome 3
>>> desktop are weired. It frequently freeze, not responding to mouse or
>>> keyboard. I have to login a virtual term (alt+ctrl+F2) to restart gdm
>>> (init 3; init 5). I checked Xorg.0.log file and output of dmesg, I
>>> can't spo
On Fri, Jun 24, 2011 at 9:34 PM, Stephen Gallagher wrote:
> On Fri, 2011-06-24 at 16:24 +1000, L wrote:
>> Hi
>> After upgraded to fedora 15, most are working well. The gnome 3
>> desktop are weired. It frequently freeze, not responding to mouse or
>> keyboard. I have to login a virtual term (alt+
On Fri, 2011-06-24 at 16:24 +1000, L wrote:
> Hi
> After upgraded to fedora 15, most are working well. The gnome 3
> desktop are weired. It frequently freeze, not responding to mouse or
> keyboard. I have to login a virtual term (alt+ctrl+F2) to restart gdm
> (init 3; init 5). I checked Xorg.0.log
Hi
After upgraded to fedora 15, most are working well. The gnome 3
desktop are weired. It frequently freeze, not responding to mouse or
keyboard. I have to login a virtual term (alt+ctrl+F2) to restart gdm
(init 3; init 5). I checked Xorg.0.log file and output of dmesg, I
can't spot any hint.
Linu
80 matches
Mail list logo
