upon the next manifestation i certainly will attach journalctl -b0 for
you. meanwhile i'm curious what difference you find between that and
CurrentDmesg. To me they both appear to be a readout of messages from
the most recent boot up until the present.
--
You received this bug notification beca
Public bug reported:
boot up (lubuntu)(into sddm).
press ctl-alt-F2.
login.
start X, eg startx /usr/bin/xterm (or any WM or desktop eg startlxqt).
thereafter neither ctl-alt-F1 nor 'chvt 1' is able to change back to
sddm.
not a problem in kubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Pa
** Description changed:
boot up (lubuntu)(into sddm).
press ctl-alt-F2.
login.
start X, eg startx /usr/bin/xterm (or any WM or desktop eg startlxqt).
thereafter neither ctl-alt-F1 nor 'chvt 1' is able to change back to
sddm.
- not a problem in kubuntu.
+ this bug shows up in a fu
Public bug reported:
when lxqt-config-monitor is invoked in a VT it starts displaying its
window for a half second then crashes. usually. not always. still
trying to track down the circumstances.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lxqt-config 0.14.1-0ubuntu3
ProcVersionSigna
Public bug reported:
on a plain, fully updated lubuntu system, or in the lubuntu live iso,
startlxqt fails in a VT.
on a system with kubuntu-desktop also installed, or in the kubuntu live
iso after installing lubuntu-desktop, startlxqt works in a VT.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Public bug reported:
run lubuntu in a VT.
enter reboot command.
lubuntu shuts down part way, then shows a wobbler with a message something like
[ ***] waiting for a stop job in session 3 of lubuntu (nn seconds of
1min 30sec)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lxqt-session 0.
** Description changed:
- boot up (lubuntu)(into sddm).
+ boot up (a fully updated) lubuntu 20.04 (into sddm).
press ctl-alt-F2.
login.
- start X, eg startx /usr/bin/xterm (or any WM or desktop eg startlxqt).
+ install xterm if you haven't already.
+ startx /bin/xterm& (results may vary if yo
** Description changed:
- on a plain, fully updated lubuntu system, or in the lubuntu live iso,
- startlxqt fails in a VT.
+ in the lubuntu live iso, startlxqt fails in a VT.
- on a system with kubuntu-desktop also installed, or in the kubuntu live
- iso after installing lubuntu-desktop, startl
** Description changed:
run lubuntu in a VT.
enter reboot command.
lubuntu shuts down part way, then shows a wobbler with a message something
like
- [ ***] waiting for a stop job in session 3 of lubuntu (nn seconds of
- 1min 30sec)
+ [ *** ] a stop job is running for session 20 of lubu
** Description changed:
boot up (a fully updated) lubuntu 20.04 (into sddm).
press ctl-alt-F2.
- login.
+ login (on the VT).
install xterm if you haven't already.
- startx /bin/xterm& (results may vary if you launch a WM or a desktop instead
or after just starting X with an xterm).
+ start
** Description changed:
- when lxqt-config-monitor is invoked in a VT it starts displaying its
- window for a half second then crashes. usually. not always. still
- trying to track down the circumstances.
+ boot up (a fully updated) lubuntu 20.04 (into sddm).
+ press ctl-alt-F2.
+ login (on the
** Description changed:
- in the lubuntu live iso, startlxqt fails in a VT.
+ install xterm in, and fully update, a lubuntu 20.04 system.
+ boot it up (into sddm).
+ login (at sddm).
+ press ctl-alt-F2.
+ login (on the VT).
+ startx /bin/xterm&
+ move mouse into the xterm.
+ startlxqt&
- but pe
** Description changed:
install xterm in, and fully update, a lubuntu 20.04 system.
boot it up (into sddm).
login (at sddm).
press ctl-alt-F2.
login (on the VT).
startx /bin/xterm&
move mouse into the xterm.
startlxqt&
- lxqt doesn't come up.
+ lxqt doesn't come up. or maybe co
** Description changed:
- boot up (a fully updated) lubuntu 20.04 (into sddm).
+ install xterm in, and fully update, a lubuntu 20.04 system.
+ boot it up (into sddm).
press ctl-alt-F2.
login (on the VT).
- install xterm if you haven't already.
startx /bin/xterm&
- in the xterm: startlxqt&
+
** Description changed:
- boot up (a fully updated) lubuntu 20.04 (into sddm).
+ install xterm in, and fully update, a lubuntu 20.04 system.
+ boot it up (into sddm).
press ctl-alt-F2.
login (on the VT).
- install xterm if you haven't already.
startx /bin/xterm&
thereafter neither ctl-a
** Package changed: lxqt-session (Ubuntu) => lxqt-panel (Ubuntu)
** Summary changed:
- in a VT lubuntu takes a long time to shutdown
+ lxqt-panel ignores shutdown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Description changed:
- run lubuntu in a VT.
- enter reboot command.
- lubuntu shuts down part way, then shows a wobbler with a message something
like
+ invoking reboot from the lxqt menu works well, but if i choose to use
+ /sbin/reboot, eg in a script, shutdown proceeds only part way.
+ appar
** Description changed:
TigerVNC fullscreen is stretched and split across both screens on
kubuntu 20.04.
Looking thru all the "system settings" i don't see anything relevant.
- Not a problem on lubuntu 20.04.
+ Not a problem on lubuntu 20.04. oops, now i've seen it happen on
+ lubuntu
** Description changed:
- install xterm in, and fully update, a lubuntu 20.04 system.
- boot it up (into sddm).
+ boot up a fully updated lubuntu 20.04 system (into sddm).
press ctl-alt-F2.
login (on the VT).
- startx /bin/xterm&
+ startx /bin/x-terminal-emulator
thereafter neither ctl-al
** Description changed:
- install xterm in, and fully update, a lubuntu 20.04 system.
- boot it up (into sddm).
+ boot up a fully updated lubuntu 20.04 system (into sddm).
login (at sddm).
press ctl-alt-F2.
login (on the VT).
- startx /bin/xterm&
- move mouse into the xterm.
+ startx /bin/x-
** Summary changed:
- lxqt-panel ignores shutdown
+ lxqt-panel ignores shutdown in a VT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947505
Title:
lxqt-panel ignores shutdown in a VT
To manage n
** Description changed:
- invoking reboot from the lxqt menu works well, but if i choose to use
- /sbin/reboot, eg in a script, shutdown proceeds only part way.
- apparently lxqt-panel ignores the shutdown, and we're left watching a
- message like
+ boot up a fully updated lubuntu 20.04 system (in
** Description changed:
- install xterm in, and fully update, a lubuntu 20.04 system.
- boot it up (into sddm).
+ boot up a fully updated lubuntu 20.04 system (into sddm).
press ctl-alt-F2.
login (on the VT).
- startx /bin/xterm&
- move mouse into the xterm.
+ startx /bin/x-terminal-emulator
+
** Description changed:
TigerVNC fullscreen is stretched and split across both screens on
kubuntu 20.04.
Looking thru all the "system settings" i don't see anything relevant.
- Not a problem on lubuntu 20.04. oops, now i've seen it happen on
- lubuntu too. it's fine if xrandr is call
** Description changed:
boot up a fully updated lubuntu 20.04 system (into sddm).
press ctl-alt-F2.
login (on the VT).
startx /bin/x-terminal-emulator
- thereafter neither ctl-alt-F1 nor 'chvt 1' is able to change back to
- sddm.
+ thereafter neither ctl-alt-F1 nor 'chvt 1' seem able to
** Description changed:
boot up a fully updated lubuntu 20.04 system (into sddm).
press ctl-alt-F2.
login (on the VT).
startx /bin/x-terminal-emulator
move mouse into the terminal.
startlxqt&
(it comes up in a few seconds)
reboot
/sbin/reboot works well with an sddm session, a
** Description changed:
+ somedays this bug just doesn't show up, and other days this sequence
+ seems to reliably capture it:
+
boot up a fully updated lubuntu 20.04 system (into sddm).
press ctl-alt-F2.
login (on the VT).
startx /bin/x-terminal-emulator
thereafter neither ctl-alt-F
** Description changed:
TigerVNC fullscreen is stretched and split across both screens on
kubuntu 20.04.
Looking thru all the "system settings" i don't see anything relevant.
- On lubuntu 20.04 it usually does fullscreen on just one screen. i have
- seen it stretch across both screens
** Description changed:
regression: the focal version of twm won't launch:
twm: unable to open fontset "-adobe-helvetica-bold-r-
normal--*-120-*-*-*-*-*-*"
- the bionic version of twm works fine, even if invoked in focal.
-
- the focal version failure&message had surfaced in earlier
Public bug reported:
When "Focus stealing prevention" is set to either "High" or "Extreme",
clicking on the "Application Launcher" doesn't open it.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemsettings 4:5.18.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.
** Description changed:
The 3 screenshots are all of the same conversation in my gmail inbox.
One screenshot was taken running Firefox Nightly on a Focal Ubuntu
install, where the font rendering seems fine. The other two screenshots
- were taken running Firefox Nightly on a Focal Kubuntu in
happy to find this report, i'll try without "toram", that sounds likely
to be the workaround i need.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873950
Title:
Calamares failed: command 'mount' re
i'm seeing this bug in lubuntu-20.04.3-desktop-amd64.iso
my disc has a prior install of kubuntu-20.04.2.0-desktop-amd64.iso:
sda1: /boot/efi
sda2: /
i move all prior content in / into a subdirectory (/fk) leaving only
/lost+found, /swapfile and /fk, launch "install Lubuntu 20.04 LTS",
select ma
Public bug reported:
The Battery Optimization section has gone missing ever since i changed
the settings.
This morning i see only two sections, "Battery Levels" and "Other Settings",
under [System Settings -> Power Management -> Advanced Power Settings], having
just tried two recent jammy kubun
Ran the battery down all the way this morning, restored power, booted
into focal (on my HD), ran there most of the day, the battery charged up
to 100%, then booted the jammy live iso again. The Charge Limit section
is back now, showing the default settings, stop at 100%, always charge
when plugged
** Summary changed:
- Battery Optimization section missing
+ Charge Limit section disappears upon changing the settings
** Description changed:
- The Battery Optimization section has gone missing ever since i changed
- the settings.
+ The Charge Limit section has gone missing ever since i change
Public bug reported:
My connection works in 20.04 and fails in 22.04. Perhaps something i've
been using is now depricated? Or perhaps jammy strongswan is...still
working on it?
This is the output i get in 22.04:
initiating Main Mode IKE_SA myvp7[1] to 2.i.p.7
generating ID_PROT request 0 [ SA V
yes. focal on HD, vs a jammy iso, connecting to the same colo
("right"). i'm less familiar with the details at the colo, other than
the focal config i have on my end works for it. with some difficulty i
could likely get more details about the colo config.
sorry the description above didn't show
i've gained access to the "ER-X" which receives my connection at the
colo, if you want info from it just ask.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951832
Title:
no shared key found in 22.0
Public bug reported:
Booted from thumb drive thus:
menuentry "d07 2021-11-19 Fri 15:13:58 kubuntu/jammy-desktop-amd64.iso"
{
echo "d07 2021-11-19 Fri 15:13:58 kubuntu/jammy-desktop-amd64.iso"
#3666923520 2021-11-19 Fri 15:13:58 kubuntu/jammy-desktop-amd64.iso
Public bug reported:
same as https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1952017
but this time i omitted toram
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 21.10.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
Appor
Public bug reported:
same as https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1952019
but using today's "current" iso
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 21.10.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
App
** Package changed: strongswan (Ubuntu) => xl2tpd (Ubuntu)
** Summary changed:
- no shared key found in 22.04
+ xl2tpd "Can not find tunnel" in jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195
** Description changed:
My connection works in 20.04 and fails in 22.04. Perhaps something i've
- been using is now depricated? Or perhaps jammy strongswan is...still
+ been using is now depricated? Or perhaps jammy xl2tpd is...still
working on it?
- This is the output i get in 22.04:
-
** Attachment added: "syslog extract from jammy"
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+attachment/5543174/+files/jls
** Description changed:
My connection works in 20.04 and fails in 22.04. Perhaps something i've
been using is now depricated? Or perhaps jammy xl
** Description changed:
My connection works in 20.04 and fails in 22.04. Perhaps something i've
been using is now depricated? Or perhaps jammy xl2tpd is...still
working on it?
see my attached syslog extracts at comments #6 and #7. i extracted them
thus:
- egrep "l2tp|swan|ipsec|
** Description changed:
My connection works in 20.04 and fails in 22.04. Perhaps something i've
been using is now depricated? Or perhaps jammy xl2tpd is...still
working on it?
see my attached syslog extracts at comments #6 and #7. i extracted them
thus:
egrep -i "l2tp|swan|ips
** Attachment added: "er-x /var/log/charon.log when jammy tries to connect"
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+attachment/5543181/+files/jcha
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Attachment added: "er-x /var/log/messages when 20.04 connects"
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+attachment/5543180/+files/fmes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Attachment added: "er-x /var/log/messages when jammy tries to connect"
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+attachment/5543182/+files/jmes
** Changed in: xl2tpd (Ubuntu)
Status: Incomplete => New
** Description changed:
My connection works in 20.04 and f
The intoxicated character placement effect when kubuntu-settings is
installed is still there in jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883742
Title:
funky character placement when kub
fwiw bug does not appear in manjaro kwin(5.23.3-1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946366
Title:
TigerVNC fullscreen is stretched and split across both screens on
kubuntu 20.04
To
** Description changed:
boot up a fully updated lubuntu 20.04 system (into sddm).
press ctl-alt-F2.
login (on the VT).
startx /bin/x-terminal-emulator
move mouse into the terminal.
startlxqt&
(it comes up in a few seconds)
reboot
/sbin/reboot works well with an sddm session, a
Public bug reported:
New windows (and popups) get focus even when "Focus new windows" is de-
selected.
See these issues on github:
https://github.com/lxqt/lxqt/issues/2128#issuecomment-973339619
and
https://github.com/lxqt/obconf-qt/issues/189
Does the lubuntu team really want to base lubuntu 22
i made the jump to manjaro. rolling release, yay! and ipsec/xl2tpd
just works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951832
Title:
xl2tpd "Can not find tunnel" in jammy
To manage notific
** Summary changed:
- funky font rendering on kubuntu
+ funky character placement on kubuntu
** Description changed:
- The 3 screenshots are all of the same conversation in my gmail inbox.
- One screenshot was taken running Firefox Nightly on a Focal Ubuntu
- install, where the font rendering se
** Summary changed:
- funky character placement on kubuntu
+ funky character placement when kubuntu-settings-desktop installed
** Description changed:
Funky character placement, letters often mispositioned, jammed into the
adjacent letter on one side and/or far away from the adjacent letter
** Description changed:
choose-window produces a sensibly aligned list
on centos7 (tmux-1.8-4.el7.x86_64):
(0) 0: htop "umari"
(1) 1: bash "umari"
(2) 2: bash- "umari"
(3) 3: bash* "umari"
and ubuntu xenial (tmux 2.1-3build1):
(0) 0: [tmux]- "jocur"
(1) 1: bash* "jocur
A solution is available, with a updated copy of tmux, and a recipe, see:
http://github.com/tmux/tmux/issues/2636#issuecomment-817542083
** Bug watch added: github.com/tmux/tmux/issues #2636
https://github.com/tmux/tmux/issues/2636
** Description changed:
choose-window produces a sensibly a
Public bug reported:
TigerVNC fullscreen is stretched and split across both screens on
kubuntu 20.04.
Looking thru all the "system settings" i don't see anything relevant.
Not a problem on lubuntu 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: kwin-x11 4:5.18.5-0ubuntu0.1
ProcVers
** Package changed: kubuntu-meta (Ubuntu) => kubuntu-settings (Ubuntu)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1883742
Title:
funky character placement when kubuntu-settin
401 - 461 of 461 matches
Mail list logo
