Hello:

Quite so ...  8^ o
Thanks - duly noted and corrected.

Seems so.

The pop-up menu is displayed as long as I hold down the right mouse button.
If I let it go, the menu recedes. 

Yes.
I right-click (at this point the pop-up menu should stay open, but it does not).
Like the previous example, the pop-up menu is displayed as long as I hold down the right mouse button.
If I let it go, the menu recedes. 

I think I have seen some strange behaviour in other apps, but it is in the browser where it is  most annoying.

I seem to recall having experienced this but I can's say much more.

Well, at least it's not just me.

It has happened with three different pointing devices: the first one, a PS/2 mouse, a very solid + well made Wise edition, the second a crappy plasticky Verbatim and the actual one a brand new Logitech M100, all optical.

All three exhibited the exact same behaviour, so IMO it's definitely not a mouse thing.

Maybe it's something to do with the mouse drivers (?) selected by the default X server settings through udev (I think that's how it works).

Thanks for your input.

Cheers,

A.

Hello:

Indeed it is.
Thanks.

Couldn't be that it did/did not work.
Something was surely amiss somewhere.

I'll drop the OP a line thanking hin for taking the time to find out what was up.

Don't we have a sticky section where these things can go and live forever?

One thing I found was that there was some sort of issue with the Wise PS2 mouse that I had plugged into my Wise USB keyboard.

Once I found the crap Verbatim USB mouse, the problem with the mouse freezing went away.
I'll get a decent mouse tomorrow ...

But I really have to brush up my cuasi non-existent keyboard skills, it's unacceptable that a bad mouse can ground you.

In any case, it seems that part of the problem was related to /dev/mouse0 not being there and the existence of /dev/psaux but I decided to give up on that.
It's probably an evdev configuration issue.

So, this is what I did:

1.
Edited xorg.conf and deleted all InputDevice entires in Section "ServerLayout" and the two "InputDevice" Sections.
X server probes and picks up what is there.

2.
Made sure that Section Section "ServerFlags" has these options to the default settings.

Section "ServerFlags"
    Option         "DontZap" "False"                # default False - "True" disables <Ctrl><Alt><BS> (server abort)
    Option         "AutoAddDevices" "True"      # default True - to use system kb, kb layout and mouse settings
    Option         "AutoEnableDevices" "True"  # default True - if "AutoAddDevices" is set to default 
EndSection

Of course, being default settings you can do away with the whole "ServerFlags" section but I have decided to keep them so I remember all this.

groucho@devuan:~$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     es
variant:    deadtilde
options:    lv3:ralt_switch,terminate:ctrl_alt_bksp
groucho@devuan:~$ 

Now Control+Alt+Backspace works as well as Control+Alt+Fx.

Really don't need the special characters or accented characters in Terminal (ç Ç ñ Ñ - ' ` ^ " ) but there's an issue with Leafpad and codeset=ANSI_X3.4-1968 which I will adress in another post.

Maybe we're on a roll and we'll solve it?   =-)

Cheers,

A.

Hello:

Here's my xorg.conf settings for input devices:

Section "ServerLayout"
Identifier     "Layout0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "InputDevice"
    # generated from default configuration
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5" 
EndSection

Section "ServerFlags"
    Option         "DontZap" "False"             # default False - "True" disables <Ctrl><Alt><BS> (server abort)
    Option         "AutoAddDevices" "False"      # default True - to use system kb, kb layout and mouse settings
    Option         "AutoEnableDevices" "True"    # default True - 
EndSection

If I check the box that says Use system defaults in Applications -> Settings -> Keyboard -> Layout + logou/login, I end up getting what seems to be a US layout on both X and the terminal and Control+Alt+Backspace will not terminate the X server.

But if I change the "AutoAddDevices" to "True" (so that it does what it is supposed to do), my mouse freezes BUT Control+Alt+Backspace works as advertised.   

Shutting down the server in these conditions does not do anything for me, I have to resort to Ctrl+Alt+F1 th sudo jed the xorg.conf file so I can have a working mouse again.

I'll have a look.

Thanks for your input.

Cheers,

A.

Hello:

Hmm ...
I think not.

I'm on ASCII and if I set up an xorg.conf (default setting enables ctrl-alt-backspace) and do Applications -> Settings -> Keyboard -> Layout, where the Use system defaults box is checked, it will work but I've been at odds with setting layouts and kbd for the longest while so I go the Xfce route.

ie: in Section "ServerFlags"
Option "DontZap" set to "False" (default "False")  - "True" setting disables <Ctrl><Alt><BS> (server abort)
Option "AutoAddDevices" set to "True" (default "True")  - "True" setting is for using system kb, kb layout and mouse settings

So, my guess is that if it does not work in ASCII it's not because of the kernel version but because of the Xfce plugin or something else related to the Kb settings in Xfce.

I'll try that.
I never used ctrl-alt-backspace much but when I learned how convenient it was, I found it very useful.

I think it should be fixed/reinstated - as it does work.

Yes it is.

Thta's what I am using.
Probably the source of the ctrl-alt-backspace problem.

Thanks for your input.

Cheers,

A.

Hello:

Yes!
That did it. =-)
And of course, this does survive a reboot.

Curiously enough (or maybe not), Switch On Wi-Fi / Switch Off Wi-Fi in the UI does not get greyed out, it just goes unresponsive.
Pity, it shouldn't be too difficult to add an Always connect Wi-Fi check-box (or something similar) in the General Settings Tab.

It's a great application but it seems to me (from what I have seen on the Launchpad page) that the maintainers are not too keen on it.
Last release 1.7.4 was on 2016-01-25.

Yes, in the event my ADSL goes dark.

Yes, but i'd have to be doing it every time I boot.

Thank you very much for your input.

Cheers,

A.

Hello:

Thank you but it should have been obvious to me. (I lost my *.ini instincts long ago ...)
The second I hit 'Submit' it dawned on me that there had to be at least one *.conf file for this app somewhere.

I looked in that file but as it was directly related to specific (AP) settings and not global ones, decided not to touch it.

I don't have it installed, will have a look.

Thanks for your input.

Cheers,

A.

Hello:

Ahh ...
Interesting.

I thought it was a system file and as such belonged to root and root only.
Good to know.

Doing chmod 755 /var/log/lost+found would allow conky to read it without needing admin credentials ie: being included in a sudoers file.
And as such, it won't get logged in auth.log.
Neat.

Nothing there that I should worry about.

I think it may also be worthwhile for the system to generate a separate /var/log/sudo.log file (editing /etc/sudoers).

Thanks you both (chris2be8 + fsmithred) for your input - learned new things today.

Best,

A.

Hello:

Indeed.  =-)

Don't know how to do that, it is a problem when I wanted to open some (not all) log files with mousepad.
But I can read them with the Log Viewer.

I have had problems opening up huge files (very slow) even though my rig holds 8Gb. RAM.

WRT the .xsession-errors file, I found a solution to keep it in check here:

http://www.daniloaz.com/en/how-to-preve … huge-size/

It sets up a line in crontab to check every 15 minutes if the file size is greater than 5 GB and if so either empty it or keep the last 10,000 lines.
I set it for every 30 minutes and 1000 lines.

Once I emptied the .xsession-errors file, I found that it was getting a Gtx error every so often about not being able to load the ATK bridge, which I fixed by installing libatk-adaptor.
Found that solution here: https://dev1galaxy.org/viewtopic.php?id=1815 -->  =-)

But what really eats up room in the .xsession-errors file is this line, constantly written up:

du: cannot read directory '/var/log/lost+found': Permission denied
du: cannot read directory '/var/log/lost+found': Permission denied
du: cannot read directory '/var/log/lost+found': Permission denied
--- snip ---

But I know where it comes from:

groucho@devuan:~$ conky
conky: desktop window (1600003) is subwindow of root window (728)
conky: drawing to desktop window
conky: No compatible double buffer extension found
conky: drawing to single buffer
du: cannot read directory '/var/log/lost+found': Permission denied
du: cannot read directory '/var/log/lost+found': Permission denied
du: cannot read directory '/var/log/lost+found': Permission denied
du: cannot read directory '/var/log/lost+found': Permission denied
du: cannot read directory '/var/log/lost+found': Permission denied
du: cannot read directory '/var/log/lost+found': Permission denied
--- snip ---

My conky.conf file is set up so I can see the evolution of my disk usage (/, /home and /var/log), and /var/log usage is checked with this line ...

/var/log ${exec du -sch /var/log | head -n1 | awk '{print $1}'}
${fs_bar /var/log}

... so every time that conky takes a reading, it generates an error message that gets logged in the .xsession-errors file.
No wonder it was huge, conky reads every 2s.   

So the question would be:

How can I get conky to be able to read lost+found?
This would need admin credentials for conky, which does not sound healthy.
And conky is not really a user, so I don't think it could be added to sudoers.

Maybe get the Xserver to not log this specific error?

Any ideas?

Thanks in advance.

A.

Hello:

That I have from Git.

Hmm ...
Thought of that too, but it's more or less the same as what I have now.

I tried doing Alien on an .rpm but on installation I got some problem in a libbarry18 (?) library.
I think that is the point where the original maintainer/developer gave up.

Thanks for your input.

Cheers,

A.