On 2020-07-22 17:56, Wl-dustin wrote:
> At least we're seeing the same thing.
Yeah, sorry for being slow.
> I tried to experiment with this and couldn't reproduce it outside the
> Xsession environment.
Indeed, the files in /etc/X11/Xsession.d are not run automatically when
entering a Wayland ses
At least we're seeing the same thing. I tried to experiment with this
and couldn't reproduce it outside the Xsession environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879352
Title:
/usr/b
Thanks, your latest comment made me realize what the error message in
the bug description actually says.
But neither im-config nor x11-common (which provides
/etc/X11/Xsession.d/99x11-common_start) does that kind of double quoting
AFAICT. The code appears not to be more complex than:
~$ sh
$ STAR
You are correct that uninstalling `im-config` and reverting
`99x11-common_start` to its original `exec $STARTUP`. But that just
hides the issue by removing the package containing the bug, and in
particular these lines in `70im-config_launch`:
```
if [ -x "$IMLAUNCH" ]; then
STARTUP="$IMLAUNCH
Sorry,
s/install/uninstall/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879352
Title:
/usr/bin/im-launch i3 fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
Please note that 'i3' is an argument to the command /usr/bin/im-launch,
not part of a file name. So the error message incorrectly says "No such
file or directory".
It would still be good if you could try to install im-config:
sudo apt purge im-config
--
You received this bug notification becaus
Ah, I didn't get notified of Gunnar's last comment.
```
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-
[Expired for im-config (Ubuntu) because there has been no activity for
60 days.]
** Changed in: im-config (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
[Expired for i3-wm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: i3-wm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879352
T
** Changed in: im-config (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879352
Title:
/usr/bin/im-launch i3 fails
To manage notifications about this bug go
Can it be that you previously have had im-config installed on your
machine and later uninstalled it without purging? What does
dpkg -l im-config
output? Any difference if you do:
sudo apt purge im-config
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>From the first comment:
```
May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]:
/etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such
file or directory
```
it's in `/etc/X11/Xsession.d/99x11-common_start`
--
You received this bug notification because you are a m
@Wl-dustin: Where was that "exec $STARTUP" call? In some i3 config file?
** Changed in: im-config (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879352
Title
** Tags added: focal
** Package changed: xorg (Ubuntu) => im-config (Ubuntu)
** Also affects: i3-wm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I was able to fix this by changing
```
exec $STARTUP
```
to
```
$STARTUP
```
Interestingly, this doesn't leave a shell process running -- it leaves
`gdm-x-session` running. So perhaps that is emulating a shell somehow,
but gets the unquoting wrong for `exec`?
--
You received this bug notific
15 matches
Mail list logo