Ah, great, thank you for the details you've provided! I think this bug
can be closed, then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909879
Title:
taskwarrior-2.5.2 is out
To manage
Public bug reported:
After several years, a new release of TaskWarrior is out - 2.5.2 (with
2.5.3 maybe coming soon). This release brings four years worth of
bugfixes.
https://github.com/GothenburgBitFactory/taskwarrior/releases/tag/v2.5.2
I know maintainers usually spot new releases, but in
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:
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
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
>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
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
Public bug reported:
Trying to run i3 in Focal Fossa, login fails. The screen goes black
briefly, then returns to the login screen. I expect this is
reproducible by just installing `i3`, selecting it on the settings in
the login screen, and logging in.
I see the following in the log:
```
May
https://bugs.launchpad.net/ubuntu/+source/kickseed/+bug/537421/comments/9
may be relevant
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/420903
Title:
Ubuntu Kickstart/Kickseed does not work with
