** Description changed:
- Just like in regular Lu 18.04 the "eject" key doesn't open the optical
- drive tray, but running a command in the console will open the tray.
+ The default configuration in both Lubuntu 18.04 and upstream Openbox
+ does not include a definition for the eject media key.
+
@walter:
Thanks for the reply . . . haven't had to do an update/upgrade recently,
checked a few days ago and apt said, "nothing to do at this time" . . . .
Sometimes over in one of my "rolling" distros there can be a lot of
"dependency" issues that crop up with updates, requiring actual thought .
The system won't clobber over your config files on update/upgrade, at
least not the ones in your home. It will ask you if it notices that
things have changed on systemwide stuff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Success!!! I did use sudo, but using the "lxqt" option brought me to the
"744 lines" and I used your shortcut to get me to line 192 and then
scrolled down to the end right before "mouse" and I dropped your code in
and . . . seems like I must have done "OK" because hitting the eject key .
. .
The file is ~/.config/openbox/lxqt-rc.xml. Since it's in your home
folder (~), you don't need to sudo anything. I'm not sure what file
you're looking at but it's most certainly not the right one based on
what you're explaining or unless you broke something. That said, there's
no reason why nano
Thanks for the reply . . . but, no, I didn't figure anything out . . . I
just copy/pasted what you provided after the "sudo nano" . . . and what I
pasted here is what was there . . . I tried to arrow down or up, but the
scroll bar was "full" . . . i.e., what was showing was the full show . . .
and
That can't be the end as that's not even a complete and valid config
file. Openbox would complain at you when you tried to run it. My guess
is that you're not arrowing down enough. Nano should say "Read 744
lines" in its status when you open it. That doesn't look like 744 lines.
:)
The sections
Ran the suggested commands, but it didn't show anything like ???
Operator error?? I copied/pasted your data with "sudo nano" in front of it and
got:
[code]
http://openbox.org/3.4/rc;
xmlns:xi="http://www.w3.org/2001/XInclude;>
10
20
yes
[end code]
Ran out of
@walter:
Alrighty, thanks for that data, I'll check into it in a day or so . . .
and post back on results.
As far as the "eject" . . . I think I might have tried that alone, there
is only one optical drive, but possibly it didn't work . . . . Some of
this might be posted on the regular Lu 18.04
Actually `eject` is a standard part of the install and doesn't even
require the device name. Obviously if there's more than one device and
you want to open one over the other, it needs to be specific, but
there's always a default device. That said, the solution is fairly easy:
1. Open up
"Thomas Schmitt scdbac...@gmx.net via canonical.com
Apr 10
to me
Hi,
what happens if you perform one of these shell commands:
eject /dev/sr0
xorriso -outdev /dev/sr0 -eject all
In case of failure please report all error messages of the programs.
Have a nice day :)"
O . . . wow . . . (putting bong down now) . . . didn't know that was a
question . . . sorry . . . (cough, cough) . . . .
I have those commands written down at home and I'm away at work . . . but,
a gentleman posted his command options on my bug report for regular Lu
18.04 . . . it's pretty simple
The question I was trying to ask was what specific command you use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768294
Title:
"eject" key doesn't open optical drive tray in Openbox
To manage
That is what I am doing now in Lu, using the console command . . . minor
inconvenience factor, but considering that Lu Next is like "next gen" in
appearance it would be value added to have keyboard full function . . .
.
But, interesting and educational to see how each and every action in the
gUI
Actually, yeah, that 204 I got from some wiki page. It seems the
possible keycodes are:
$ xmodmap -pke | grep Eject
keycode 169 = XF86Eject NoSymbol XF86Eject
keycode 170 = XF86Eject XF86Eject XF86Eject XF86Eject
keycode 174 = XF86AudioStop XF86Eject XF86AudioStop XF86Eject
The fact that 174 is
** Changed in: lubuntu-default-settings (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768294
Title:
"eject" key doesn't open optical drive tray in
This is the last "KeyRelease event" . . . and then there was a **bunch**
of "EnterNotify event" and possibly "MotionEvent"??? As far as I recall
I just hit the eject key and released it.
code: KeyRelease event, serial 48, synthetic NO, window 0x2a1,
root 0x4d6, subw 0x0, time 245022,
1. Open up the terminal
2. Type xev
3. Hit enter
4. Press the eject key
5. Close the window that was opened by xev
6. Copy and paste the last "KeyRelease event" from the terminal here
You should have something like (except this is for a different key):
KeyRelease event, serial 40, synthetic
"As long as hitting the key in `xev` produces a named keysym (should be
XF86Eject), I'd feel relatively comfortable with that. Hopefully you get
keycode 204, too."
@walter:
Assuming you are referring to this data . . . I don't know what "xev"
is, I am happy to check whatever you would like
Regardless of how it works elsewhere, in Openbox it depends on the name
of the key and optionally the keycode. It may be different and perhaps
more flexible in other window managers. That said, I still need the
above information to get this implemented in Lubuntu.
--
You received this bug
@walter:
Sure, this one isn't a death sentence, I found the same issue in regular
Lu 18.04 and filed a bug on it there. I'm over in Gecko right now and
in that OS the eject key works . . . possibly I checked it in U-MATE and
possibly it works there as well??
--
You received this bug
21 matches
Mail list logo
