10:29 p.m.
Upgraded to F29. On KDE desktop starting EMACS in a privileged command
window locks the system. Starting EMACS with sudo locks the system. On
XFCE4 normal EMACS access with privilege.
Other file managers don't like root but there are times when cli is awkward.
11:47 p.m.
On 12/08/2018 09:29 PM, Robert McBroom via users wrote:
Upgraded to F29. On KDE desktop starting EMACS in a privileged
command
window locks the system. Starting EMACS with sudo locks the system. On
XFCE4 normal EMACS access with privilege.
Other file managers don't like root but there are times when cli is
awkward.
There are several GUI programs that prompt for a password then open a
program with root access. I use Xfce and beesu, and I know that both
Gnome KDE have their equivalents. On my panel, I have a launcher that
runs this:
beesu - thunar
for those rare occasions where a CLI would be too awkward, but I need root.
12:11 a.m.
On 12/9/18 12:29 PM, Robert McBroom via users wrote:
Upgraded to F29. On KDE desktop starting EMACS in a privileged
command window locks the
system. Starting EMACS with sudo locks the system. On
XFCE4 normal EMACS access with privilege.
Other file managers don't like root but there are times when cli is awkward.
No problems here.
Fully updated F29 system. Starting emacs after "su -" or "sudo emacs
filename" works just
fine. No lockups.
--
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme
2:34 p.m.
On Sat, 8 Dec 2018 23:29:35 -0500, Robert McBroom via users
<users(a)lists.fedoraproject.org> wrote:
Upgraded to F29. On KDE desktop starting EMACS in a privileged
command
window locks the system. Starting EMACS with sudo locks the system. On
XFCE4 normal EMACS access with privilege.
Other file managers don't like root but there are times when cli is awkward.
I'm now seeing this, too, with F29, kernel 4.19.7, on KDE. I'm pretty sure
doing this has worked as expected after the upgrade to F29, so it's a recent
change, but I don't know exactly when it started. I'm seeing this with two
different machines (a desktop and a laptop). This is
emacs-26.1.6.f29.x86_64, in case that matters, and, at the moment,
plasma-workspace-5.14.4-1.fc29.x86_64 which was upgraded to on December 5.
It doesn't actually lock the system. I can, for instance get to a virtual
terminal and kill the startkde process to get back to roughly where I was.
And I can still see the cursor and move it around (though it becomes invisible when
it's over the konsole window from which I launched emacs), but except for being able
to use, e.g., control-F3, to get to a console, I don't seem to be able to interact
with the open windows or switch to another virtual desktop (cursor won't cross the
desktop boundary).
The command "emacs -nw" seems to work fine.
George
9:19 p.m.
On 12/11/18 3:34 PM, George Avrunin wrote:
On Sat, 8 Dec 2018 23:29:35 -0500, Robert McBroom via users
<users(a)lists.fedoraproject.org> wrote:
> Upgraded to F29. On KDE desktop starting EMACS in a privileged command
> window locks the system. Starting EMACS with sudo locks the system. On
> XFCE4 normal EMACS access with privilege.
>
> Other file managers don't like root but there are times when cli is awkward.
I'm now seeing this, too, with F29, kernel 4.19.7, on KDE. I'm pretty sure
doing this has worked as expected after the upgrade to F29, so it's a recent
change, but I don't know exactly when it started. I'm seeing this with two
different machines (a desktop and a laptop). This is
emacs-26.1.6.f29.x86_64, in case that matters, and, at the moment,
plasma-workspace-5.14.4-1.fc29.x86_64 which was upgraded to on December 5.
It doesn't actually lock the system. I can, for instance get to a virtual
terminal and kill the startkde process to get back to roughly where I was.
And I can still see the cursor and move it around (though it becomes invisible when
it's over the konsole window from which I launched emacs), but except for being able
to use, e.g., control-F3, to get to a console, I don't seem to be able to interact
with the open windows or switch to another virtual desktop (cursor won't cross the
desktop boundary).
The command "emacs -nw" seems to work fine. On kernel 4.19.6
George
Same here on a desktop and a laptop. Switched to gnome-session and have access. On
kernel 4.19.6
and plasma-workspace-5.14.4-1 trouble.
Robert
5:25 a.m.
On Wed, 12 Dec 2018 at 05:22, Robert McBroom via users <
users(a)lists.fedoraproject.org> wrote:
On 12/11/18 3:34 PM, George Avrunin wrote:
> On Sat, 8 Dec 2018 23:29:35 -0500, Robert McBroom via users
> <users(a)lists.fedoraproject.org> wrote:
>
>> Upgraded to F29. On KDE desktop starting EMACS in a privileged command
>> window locks the system. Starting EMACS with sudo locks the system. On
>> XFCE4 normal EMACS access with privilege.
>>
>> Other file managers don't like root but there are times when cli is
awkward.
> I'm now seeing this, too, with F29, kernel 4.19.7, on KDE. I'm pretty
sure
> doing this has worked as expected after the upgrade to F29, so it's a
recent
> change, but I don't know exactly when it started. I'm seeing this with
two
> different machines (a desktop and a laptop). This is
> emacs-26.1.6.f29.x86_64, in case that matters, and, at the moment,
> plasma-workspace-5.14.4-1.fc29.x86_64 which was upgraded to on December
5.
>
> It doesn't actually lock the system. I can, for instance get to a
virtual
> terminal and kill the startkde process to get back to roughly where I
was.
> And I can still see the cursor and move it around (though it becomes
invisible when it's over the konsole window from which I launched emacs),
but except for being able to use, e.g., control-F3, to get to a console, I
don't seem to be able to interact with the open windows or switch to
another virtual desktop (cursor won't cross the desktop boundary).
>
> The command "emacs -nw" seems to work fine. On kernel 4.19.6
>
> George
>
>
Same here on a desktop and a laptop. Switched to gnome-session and have
access. On kernel 4.19.6
and plasma-workspace-5.14.4-1 trouble.
Robert
I'm seeing this too, but only on an IMAC with a radeon graphics card.
Kernel is 4.19.5-300.fc29.x86_64. My laptop with an intel/nvidia hybrid
card works fine. I found that killing emacs from a virtual terminal was
enough to get the desktop working again.
Chris
3:52 a.m.
On Sun, 9 Dec 2018 at 06:31, Robert McBroom via users <
users(a)lists.fedoraproject.org> wrote:
Upgraded to F29. On KDE desktop starting EMACS in a privileged
command
window locks the system. Starting EMACS with sudo locks the system. On
XFCE4 normal EMACS access with privilege.
Other file managers don't like root but there are times when cli is
awkward.
I narrowed this down to xfconf-4.13.6-2.fc29.x86_64. Using an older version
or removing it entirely makes emacs from sudo work as expected.
https://bugzilla.redhat.com/show_bug.cgi?id=1667375
Regards,
Chris
10:26 a.m.
On Friday, January 18, 2019 4:52:45 AM EST Chris Rouch wrote:
On Sun, 9 Dec 2018 at 06:31, Robert McBroom via users <
users(a)lists.fedoraproject.org> wrote:
> Upgraded to F29. On KDE desktop starting EMACS in a privileged command
> window locks the system. Starting EMACS with sudo locks the system. On
> XFCE4 normal EMACS access with privilege.
>
> Other file managers don't like root but there are times when cli is
> awkward.
I narrowed this down to xfconf-4.13.6-2.fc29.x86_64. Using an older version
or removing it entirely makes emacs from sudo work as expected.
https://bugzilla.redhat.com/show_bug.cgi?id=1667375
Regards,
Chris
That said, please *do not run Emacs as root*, but rather try to use TRAMP and
sudo to access files when you need root permissions.
--
John M. Harris, Jr. <johnmh(a)splentity.com>
Splentity
https://splentity.com/
4:27 p.m.
On Fri, 2019-01-18 at 11:26 -0500, John Harris wrote:
On Friday, January 18, 2019 4:52:45 AM EST Chris Rouch wrote:
> On Sun, 9 Dec 2018 at 06:31, Robert McBroom via users <
>
> users(a)lists.fedoraproject.org> wrote:
> > Upgraded to F29. On KDE desktop starting EMACS in a privileged command
> > window locks the system. Starting EMACS with sudo locks the system. On
> > XFCE4 normal EMACS access with privilege.
> >
> > Other file managers don't like root but there are times when cli is
> > awkward.
>
> I narrowed this down to xfconf-4.13.6-2.fc29.x86_64. Using an older version
> or removing it entirely makes emacs from sudo work as expected.
> https://bugzilla.redhat.com/show_bug.cgi?id=1667375
>
> Regards,
>
> Chris
That said, please *do not run Emacs as root*, but rather try to use TRAMP and
sudo to access files when you need root permissions.
TRAMP?
poc
5:01 p.m.
On Friday, January 18, 2019 5:27:47 PM EST Patrick O'Callaghan wrote:
TRAMP?
https://www.gnu.org/software/tramp/
--
John M. Harris, Jr. <johnmh(a)splentity.com>
Splentity
https://splentity.com/
1918
days inactive
1958
days old
9 comments
7 participants
participants (7)
-
Chris Rouch -
Ed Greshko -
George Avrunin -
Joe Zeff -
John Harris -
Patrick O'Callaghan -
Robert McBroom