[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946366] Re: TigerVNC fullscreen is stretched and split across both screens on kubuntu 20.04
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1946366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883742] Re: funky character placement when kubuntu-settings-desktop installed
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 kubuntu-settings-desktop installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1883742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** 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 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:
+ see my attached syslog extracts at comments #6 thru #11. i extracted
+ them thus:
egrep -i "l2tp|swan|ipsec|charon|XFRM|layer 2|\/var/run/xl2tpd/l2tp-control c myvp7&&
while i=$(ip route) j=${i#*3.i.p.}
[[ $j = "$i" ]]
do echo -n .;sleep .3
done
i="ip route add 3.i.p.0/21 via 3.i.p.${j%% *}"
echo $i;$i
er-x /etc/ipsec.conf:
config setup
conn %default
keyexchange=ikev1
conn remote-access
authby=secret
type=transport
keyexchange=ikev1
left=2.i.p.7
leftprotoport=17/1701
right=%any
rightprotoport=17/%any
auto=add
dpddelay=15
dpdtimeout=45
dpdaction=clear
rekey=no
ikelifetime=3600
keylife=3600
er-x /etc/ipsec.secrets:
2.i.p.7 %any : PSK ...
er-x /etc/xl2tpd/xl2tpd.conf:
[global]
listen-addr = 2.i.p.7
[lns default]
ip range = 3.i.p.4-3.i.p.9
local ip = 10.255.255.0
refuse pap = yes
require authentication = yes
name = VyattaL2TPServer
ppp debug = yes
pppoptfile = /etc/ppp/options.xl2tpd
length bit = yes
er-x /etc/ppp/options.xl2tpd:
name xl2tpd
linkname l2tp
ipcp-accept-local
ipcp-accept-remote
ms-dns 8.8.8.8
ms-dns 8.8.4.4
noccp
auth
nodefaultroute
debug
proxyarp
connect-delay 5000
idle 1800
** 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 thru #11. i extracted
- them thus:
+ see my attached syslog extracts at comments #6 thru #11. the er-x
+ extracts were simple, the ubuntu extracts were thus:
egrep -i "l2tp|swan|ipsec|charon|XFRM|layer 2|\/var/run/xl2tpd/l2tp-control c myvp7&&
while i=$(ip route) j=${i#*3.i.p.}
[[ $j = "$i" ]]
do echo -n .;sleep .3
done
i="ip route add 3.i.p.0/21 via 3.i.p.${j%% *}"
echo $i;$i
er-x /etc/ipsec.conf:
config setup
conn %default
keyexchange=ikev1
conn remote-access
authby=secret
type=transport
keyexchange=ikev1
left=2.i.p.7
leftprotoport=17/1701
right=%any
rightprotoport=17/%any
auto=add
dpddelay=15
dpdtimeout=45
dpdaction=clear
rekey=no
ikelifetime=3600
keylife=3600
er-x /etc/ipsec.secrets:
2.i.p.7 %any : PSK ...
er-x /etc/xl2tpd/xl2tpd.conf:
[global]
listen-addr = 2.i.p.7
[lns default]
ip range = 3.i.p.4-3.i.p.9
local ip = 10.255.255.0
refuse pap = yes
require authentication = yes
name = VyattaL2TPServer
ppp debug = yes
pppoptfile = /etc/ppp/options.xl2tpd
length bit = yes
er-x /etc/ppp/options.xl2tpd:
name xl2tpd
linkname l2tp
ipcp-accept-local
ipcp-accept-remote
ms-dns 8.8.8.8
ms-dns 8.8.4.4
noccp
auth
nodefaultroute
debug
proxyarp
connect-delay 5000
idle 1800
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** 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.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** 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.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** 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|ipsec|charon|XFRM|layer 2|\/var/run/xl2tpd/l2tp-control c myvp7&&
while i=$(ip route) j=${i#*3.i.p.}
[[ $j = "$i" ]]
do echo -n .;sleep .3
done
i="ip route add 192.168.128.0/21 via 192.168.128.${j%% *}"
echo $i;$i
+
+ er-x /etc/ipsec.conf:
+ config setup
+
+ conn %default
+ keyexchange=ikev1
+
+ conn remote-access
+ authby=secret
+ type=transport
+ keyexchange=ikev1
+ left=2.i.p.7
+
+ leftprotoport=17/1701
+ right=%any
+ rightprotoport=17/%any
+ auto=add
+ dpddelay=15
+ dpdtimeout=45
+ dpdaction=clear
+ rekey=no
+ ikelifetime=3600
+ keylife=3600
+
+ er-x /etc/ipsec.secrets:
+ 2.i.p.7 %any : PSK ...
+
+ er-x /etc/xl2tpd/xl2tpd.conf:
+ [global]
+ listen-addr = 2.i.p.7
+
+ [lns default]
+ ip range = 3.i.p.4-3.i.p.9
+ local ip = 10.255.255.0
+ refuse pap = yes
+ require authentication = yes
+ name = VyattaL2TPServer
+ ppp debug = yes
+ pppoptfile = /etc/ppp/options.xl2tpd
+ length bit = yes
+
+ er-x /etc/ppp/options.xl2tpd:
+ name xl2tpd
+ linkname l2tp
+ ipcp-accept-local
+ ipcp-accept-remote
+ ms-dns 8.8.8.8
+ ms-dns 8.8.4.4
+ noccp
+ auth
+ nodefaultroute
+ debug
+ proxyarp
+ connect-delay 5000
+ idle 1800
** 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|ipsec|charon|XFRM|layer 2|\/var/run/xl2tpd/l2tp-control c myvp7&&
while i=$(ip route) j=${i#*3.i.p.}
[[ $j = "$i" ]]
do echo -n .;sleep .3
done
- i="ip route add 192.168.128.0/21 via 192.168.128.${j%% *}"
+ i="ip route add 3.i.p.0/21 via 3.i.p.${j%% *}"
echo $i;$i
er-x /etc/ipsec.conf:
config setup
conn %default
- keyexchange=ikev1
+ keyexchange=ikev1
conn remote-access
- authby=secret
- type=transport
- keyexchange=ikev1
- left=2.i.p.7
+ authby=secret
+ type=transport
+ keyexchange=ikev1
+ left=2.i.p.7
- leftprotoport=17/1701
- right=%any
- rightprotoport=17/%any
- auto=add
- dpddelay=15
- dpdtimeout=45
- dpdaction=clear
- rekey=no
- ikelifetime=3600
- keylife=3600
+ leftprotoport=17/1701
+ right=%any
+ rightprotoport=17/%any
+ auto=add
+ dpddelay=15
+ dpdtimeout=45
+ dpdaction=clear
+ rekey=no
+ ikelifetime=3600
+ keylife=3600
er-x /etc/ipsec.secrets:
2.i.p.7 %any : PSK ...
er-x /etc/xl2tpd/xl2tpd.conf:
[global]
listen-addr = 2.i.p.7
[lns default]
ip range = 3.i.p.4-3.i.p.9
local ip = 10.255.255.0
refuse pap = yes
require authentication = yes
name = VyattaL2TPServer
ppp debug = yes
pppoptfile = /etc/ppp/options.xl2tpd
length bit = yes
er-x /etc/ppp/options.xl2tpd:
name xl2tpd
linkname l2tp
ipcp-accept-local
ipcp-accept-remote
ms-dns 8.8.8.8
ms-dns 8.8.4.4
noccp
auth
nodefaultroute
debug
proxyarp
connect-delay 5000
idle 1800
** Attachment added: "er-x charon.log when 20.04 connects"
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+attachment/5543179/+files/fcha
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** 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|charon|XFRM|layer 2|\/var/run/xl2tpd/l2tp-control c myvp7&&
while i=$(ip route) j=${i#*3.i.p.}
[[ $j = "$i" ]]
do echo -n .;sleep .3
done
i="ip route add 192.168.128.0/21 via 192.168.128.${j%% *}"
echo $i;$i
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** 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 xl2tpd is...still
working on it?
- see my attached syslog extracts. i extracted them thus:
+ see my attached syslog extracts at comments #6 and #7. i extracted them
+ thus:
egrep "l2tp|swan|ipsec|charon|XFRM|layer 2|\/var/run/xl2tpd/l2tp-control c myvp7&&
while i=$(ip route) j=${i#*3.i.p.}
-[[ $j = "$i" ]]
+ [[ $j = "$i" ]]
do echo -n .;sleep .3
done
i="ip route add 192.168.128.0/21 via 192.168.128.${j%% *}"
echo $i;$i
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** 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:
- initiating Main Mode IKE_SA myvp7[1] to 2.i.p.7
- generating ID_PROT request 0 [ SA V V V V V ]
- sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (180 bytes)
- received packet: from 2.i.p.7[500] to 1.i.p.2[500] (136 bytes)
- parsed ID_PROT response 0 [ SA V V V ]
- received XAuth vendor ID
- received DPD vendor ID
- received NAT-T (RFC 3947) vendor ID
- selected proposal: IKE:AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_2048
- generating ID_PROT request 0 [ KE No NAT-D NAT-D ]
- sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (372 bytes)
- received packet: from 2.i.p.7[500] to 1.i.p.2[500] (372 bytes)
- parsed ID_PROT response 0 [ KE No NAT-D NAT-D ]
- no shared key found for '1.i.p.2'[1.i.p.2] - '2.i.p.7'[2.i.p.7]
- no shared key found for 1.i.p.2 - 2.i.p.7
- generating INFORMATIONAL_V1 request 402437601 [ N(INVAL_KE) ]
- sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (56 bytes)
- establishing connection 'myvp7' failed
+ see my attached syslog extracts. i extracted them thus:
- This is the output i get in 20.04:
- initiating Main Mode IKE_SA myvp7[1] to 2.i.p.7
- generating ID_PROT request 0 [ SA V V V V V ]
- sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (180 bytes)
- received packet: from 2.i.p.7[500] to 1.i.p.2[500] (136 bytes)
- parsed ID_PROT response 0 [ SA V V V ]
- received XAuth vendor ID
- received DPD vendor ID
- received NAT-T (RFC 3947) vendor ID
- selected proposal: IKE:AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_2048
- generating ID_PROT request 0 [ KE No NAT-D NAT-D ]
- sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (372 bytes)
- received packet: from 2.i.p.7[500] to 1.i.p.2[500] (372 bytes)
- parsed ID_PROT response 0 [ KE No NAT-D NAT-D ]
- local host is behind NAT, sending keep alives
- generating ID_PROT request 0 [ ID HASH N(INITIAL_CONTACT) ]
- sending packet: from 1.i.p.2[4500] to 2.i.p.7[4500] (108 bytes)
- received packet: from 2.i.p.7[4500] to 1.i.p.2[4500] (76 bytes)
- parsed ID_PROT response 0 [ ID HASH ]
- IKE_SA myvp7[1] established between 1.i.p.2[1.i.p.2]...2.i.p.7[2.i.p.7]
- scheduling reauthentication in 3397s
- maximum IKE_SA lifetime 3577s
- generating QUICK_MODE request 3605139670 [ HASH SA No ID ID NAT-OA NAT-OA ]
- sending packet: from 1.i.p.2[4500] to 2.i.p.7[4500] (204 bytes)
- received packet: from 2.i.p.7[4500] to 1.i.p.2[4500] (204 bytes)
- parsed QUICK_MODE response 3605139670 [ HASH SA No ID ID NAT-OA NAT-OA ]
- selected proposal: ESP:AES_CBC_128/HMAC_SHA1_96/NO_EXT_SEQ
- CHILD_SA myvp7{1} established with SPIs ce997cf9_i ccdb93e8_o and TS
1.i.p.2/32[udp/l2f] === 2.i.p.7/32[udp/l2f]
- connection 'myvp7' established successfully
+ egrep "l2tp|swan|ipsec|charon|XFRM|layer 2|\/var/run/xl2tpd/l2tp-control c myvp7&&
+ while i=$(ip route) j=${i#*3.i.p.}
+[[ $j = "$i" ]]
+ do echo -n .;sleep .3
+ done
+ i="ip route add 192.168.128.0/21 via 192.168.128.${j%% *}"
+ echo $i;$i
** Attachment added: "syslog extract from 20.04"
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+attachment/5543173/+files/fks
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: no shared key found in 22.04
** 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/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952026] [NEW] jammy kubuntu ubiquity crashed, booted from thumb drive, today's iso
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 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Tue Nov 23 22:06:57 2021 InstallCmdLine: BOOT_IMAGE=(j)/casper/vmlinuz boot=casper iso-scan/filename=/boo/jk/jammy-desktop-amd64.iso panic=30 -- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211123) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-21.10.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952026 Title: jammy kubuntu ubiquity crashed, booted from thumb drive, today's iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1952026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952019] [NEW] jammy kubuntu ubiquity crashed, booted from thumb drive, no toram
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 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Tue Nov 23 20:33:44 2021 InstallCmdLine: BOOT_IMAGE=(j)/casper/vmlinuz boot=casper iso-scan/filename=/boo/kubuntu/jammy-desktop-amd64.iso panic=30 -- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2023) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-21.10.10 ** Summary changed: - ubiquity crashed, no toram this time + jammy kubuntu ubiquity crashed, booted from thumb drive, no toram ** Description changed: - same as a few minutes ago, but this time i omitted toram + 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 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Tue Nov 23 20:33:44 2021 InstallCmdLine: BOOT_IMAGE=(j)/casper/vmlinuz boot=casper iso-scan/filename=/boo/kubuntu/jammy-desktop-amd64.iso panic=30 -- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2023) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952019 Title: jammy kubuntu ubiquity crashed, booted from thumb drive, no toram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1952019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952017] [NEW] jammy kubuntu ubiquity crashed, booted from thumb drive, with toram
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
i=/boo/kubuntu/jammy-desktop-amd64.iso
search --no-floppy --set=root --fs-uuid ADDA-F0B9
loopback j $i
linux (j)/casper/vmlinuz boot=casper iso-scan/filename="$i" panic=30 toram
--
initrd (j)/casper/initrd
}
Ran to completion of "copying files", tho i didn't see anything about
the bootloader, when it crashed.
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
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
Date: Tue Nov 23 19:53:24 2021
InstallCmdLine: BOOT_IMAGE=(j)/casper/vmlinuz boot=casper
iso-scan/filename=/boo/kubuntu/jammy-desktop-amd64.iso panic=30 toram --
LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2023)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy ubiquity-21.10.10
** Summary changed:
- ubiquity crashed, running from thumb drive, with toram, jammy kubuntu
+ jammy kubuntu ubiquity crashed, running from thumb drive, with toram
** Summary changed:
- jammy kubuntu ubiquity crashed, running from thumb drive, with toram
+ jammy kubuntu ubiquity crashed, booted from thumb drive, with toram
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952017
Title:
jammy kubuntu ubiquity crashed, booted from thumb drive, with toram
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1952017/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: no shared key found in 22.04
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.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: no shared key found in 22.04
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 the following section in my ipsec.conf:
conn %default
ikelifetime=60m
keylife=20m
rekeymargin=3m
keyingtries=1
keyexchange=ikev1
authby=secret
ike=...
esp=...
if you want to see any of the "..." let's find a way less public.
the extent of my configuration is ipsec.conf, ipsec.secrets,
xl2tpd.conf, options.l2tpd.client, and issuing a couple commands to open
the connection. as it's the first stage that fails, i presume only the
ipsec.conf, ipsec.secrets, and the command "ipsec up myvp7" are
relevant.
--
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.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1951832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] [NEW] no shared key found in 22.04
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 V V V V ]
sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (180 bytes)
received packet: from 2.i.p.7[500] to 1.i.p.2[500] (136 bytes)
parsed ID_PROT response 0 [ SA V V V ]
received XAuth vendor ID
received DPD vendor ID
received NAT-T (RFC 3947) vendor ID
selected proposal: IKE:AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_2048
generating ID_PROT request 0 [ KE No NAT-D NAT-D ]
sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (372 bytes)
received packet: from 2.i.p.7[500] to 1.i.p.2[500] (372 bytes)
parsed ID_PROT response 0 [ KE No NAT-D NAT-D ]
no shared key found for '1.i.p.2'[1.i.p.2] - '2.i.p.7'[2.i.p.7]
no shared key found for 1.i.p.2 - 2.i.p.7
generating INFORMATIONAL_V1 request 402437601 [ N(INVAL_KE) ]
sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (56 bytes)
establishing connection 'myvp7' failed
This is the output i get in 20.04:
initiating Main Mode IKE_SA myvp7[1] to 2.i.p.7
generating ID_PROT request 0 [ SA V V V V V ]
sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (180 bytes)
received packet: from 2.i.p.7[500] to 1.i.p.2[500] (136 bytes)
parsed ID_PROT response 0 [ SA V V V ]
received XAuth vendor ID
received DPD vendor ID
received NAT-T (RFC 3947) vendor ID
selected proposal: IKE:AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_2048
generating ID_PROT request 0 [ KE No NAT-D NAT-D ]
sending packet: from 1.i.p.2[500] to 2.i.p.7[500] (372 bytes)
received packet: from 2.i.p.7[500] to 1.i.p.2[500] (372 bytes)
parsed ID_PROT response 0 [ KE No NAT-D NAT-D ]
local host is behind NAT, sending keep alives
generating ID_PROT request 0 [ ID HASH N(INITIAL_CONTACT) ]
sending packet: from 1.i.p.2[4500] to 2.i.p.7[4500] (108 bytes)
received packet: from 2.i.p.7[4500] to 1.i.p.2[4500] (76 bytes)
parsed ID_PROT response 0 [ ID HASH ]
IKE_SA myvp7[1] established between 1.i.p.2[1.i.p.2]...2.i.p.7[2.i.p.7]
scheduling reauthentication in 3397s
maximum IKE_SA lifetime 3577s
generating QUICK_MODE request 3605139670 [ HASH SA No ID ID NAT-OA NAT-OA ]
sending packet: from 1.i.p.2[4500] to 2.i.p.7[4500] (204 bytes)
received packet: from 2.i.p.7[4500] to 1.i.p.2[4500] (204 bytes)
parsed QUICK_MODE response 3605139670 [ HASH SA No ID ID NAT-OA NAT-OA ]
selected proposal: ESP:AES_CBC_128/HMAC_SHA1_96/NO_EXT_SEQ
CHILD_SA myvp7{1} established with SPIs ce997cf9_i ccdb93e8_o and TS
1.i.p.2/32[udp/l2f] === 2.i.p.7/32[udp/l2f]
connection 'myvp7' established successfully
my ipsec.conf:
conn myvp7
right=2.i.p.7
rightprotoport=17/1701
leftprotoport=17/1701
left=%defaultroute
keyexchange=ikev1
type=transport
authby=secret
auto=add
my ipsec.secrets:
: PSK ...
** Affects: strongswan (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/1951832
Title:
no shared key found in 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1951832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951661] Re: Charge Limit section disappears upon changing the settings
** 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 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 kubuntu live ISOs, 3666923520 2021-11-19 Fri 15:13:58 kubuntu/jammy-desktop-amd64.iso and 3667288064 2021-11-13 Sat 14:10:03 kubuntu/jammy-desktop-amd64.iso. On a recent morning i had found a third section in [Advanced Power - Settings] called Battery Optimization or something quite like that, and - if memory serves me correctly i set it to begin charging at 40% and stop - charging at 60%. But ever since, i only see the two sections in - [Advanced Power Settings]. + Settings] called "Charge Limit", and if memory serves me correctly i set + it to begin charging at 40% and stop charging at 60%. But ever since, i + only see the two sections in [Advanced Power Settings]. it makes sense that the panel icon is saying "Battery at 57%, not Charging" because that fits what i asked for, and not discharging either because as htop says it's "Running on A/C". i just unplugged the lappy momentarily and htop tracked it as it steadily dropped from "57.1%" to - "56.6% (Running on battery)", so apart from the missing Battery - Optimization settings it all seems sensible. i was a bit surprised to - see it remembering the settings from a prior live session, but it makes - sense if the settings were set in the firmware. + "56.6% (Running on battery)", so apart from the missing Charge Limit + settings it all seems sensible. i was a bit surprised to see it + remembering the settings from a prior live session, but it makes sense + if the settings were set in the firmware. in addition to what's currently (nearly) implemented in jammy kubuntu i'm curious about optimizing battery lifetimes in general, and specifically for my specific devices (see sig). Pointers to reasonably reliable specific information would be appreciated. Like, what's best overall, a full charge occasionally, a full discharge occasionally, both, neither, or more specifically what? greg (ThinkPad e540, Pixel 3 XL (android 12), Arctis 7, Sennheiser GSP 670, Bose SoundLink iii, Kindle Fire HD 3rd Gen 2013 with Evervolv rom) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemsettings 4:5.23.3-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Fri Nov 19 17:25:02 2021 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2029) SourcePackage: systemsettings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951661 Title: Charge Limit section disappears upon changing the settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1951661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951661] Re: Battery Optimization section missing
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 or something to that effect. Fascinating. So i clicked around within System Settings a bunch. Charge Limit still there. Changed focus settings, changed monitor settings, Charge Limit section still there. Changed Charge Limit settings like i did before, stop at 60%, start at 40%, clicked Energy Saving, answered "Apply" to the dialog, clicked right back to Advanced Power Settings, and the Charge Limit section is gone again now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951661 Title: Battery Optimization section missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1951661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951661] [NEW] Battery Optimization section missing
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 kubuntu live ISOs, 3666923520 2021-11-19 Fri 15:13:58 kubuntu/jammy-desktop-amd64.iso and 3667288064 2021-11-13 Sat 14:10:03 kubuntu/jammy-desktop-amd64.iso. On a recent morning i had found a third section in [Advanced Power Settings] called Battery Optimization or something quite like that, and if memory serves me correctly i set it to begin charging at 40% and stop charging at 60%. But ever since, i only see the two sections in [Advanced Power Settings]. it makes sense that the panel icon is saying "Battery at 57%, not Charging" because that fits what i asked for, and not discharging either because as htop says it's "Running on A/C". i just unplugged the lappy momentarily and htop tracked it as it steadily dropped from "57.1%" to "56.6% (Running on battery)", so apart from the missing Battery Optimization settings it all seems sensible. i was a bit surprised to see it remembering the settings from a prior live session, but it makes sense if the settings were set in the firmware. in addition to what's currently (nearly) implemented in jammy kubuntu i'm curious about optimizing battery lifetimes in general, and specifically for my specific devices (see sig). Pointers to reasonably reliable specific information would be appreciated. Like, what's best overall, a full charge occasionally, a full discharge occasionally, both, neither, or more specifically what? greg (ThinkPad e540, Pixel 3 XL (android 12), Arctis 7, Sennheiser GSP 670, Bose SoundLink iii, Kindle Fire HD 3rd Gen 2013 with Evervolv rom) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemsettings 4:5.23.3-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Fri Nov 19 17:25:02 2021 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2029) SourcePackage: systemsettings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemsettings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951661 Title: Battery Optimization section missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1951661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951655] [NEW] new windows (and popups) get focus even when "Focus new windows" is de-selected
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.04 on a dead product? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: obconf-qt 0.16.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Fri Nov 19 15:56:55 2021 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211108) SourcePackage: obconf-qt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: obconf-qt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951655 Title: new windows (and popups) get focus even when "Focus new windows" is de-selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obconf-qt/+bug/1951655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947505] Re: lxqt-panel ignores shutdown in a VT
** 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, and invoking reboot from the lxqt menu works well in a VT, but if i chose to login on a VT *and* if i choose to use /sbin/reboot, eg in a script, or if two sessions are open, then shutdown proceeds only part way. apparently lxqt-panel ignores the shutdown, and we're left watching a message like [ *** ] a stop job is running for session 20 of lubuntu (15s / 1min 30s) - workaround: kill lxqt-panel + workaround: pkill -9 lxqt-panel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:10:18 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1947505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946366] Re: TigerVNC fullscreen is stretched and split across both screens on kubuntu 20.04
** 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 on lubuntu just once, but so far - haven't managed to reproduce that on lubuntu. + workaround: kill kwin, launch openbox ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kwin-x11 4:5.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 7 08:08:00 2021 InstallationDate: Installed on 2021-08-03 (64 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: kwin UpgradeStatus: No upgrade log present (probably fresh install) -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1946366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947482] Re: can't change VT after starting X in lubuntu
** 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-F1 nor 'chvt 1' seem able to change back to sddm, tho after a rather long time, or some other change in circumstances, it works again. this bug shows up in a fully updated lubuntu system as long as nobody has yet logged in at sddm. this bug shows up on the lubuntu iso (wherein sddm has already auto- logged-in to 'lubuntu'). this bug does not seem to show up on a regular lubuntu system if someone is slready logged in at sddm. this bug does not seem to show up in kubuntu regardless whether anyone is logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sddm 0.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 16 21:09:14 2021 InstallationDate: Installed on 2021-09-30 (16 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947482 Title: can't change VT after starting X in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1947482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947505] Re: lxqt-panel ignores shutdown in a VT
** 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, and invoking reboot from the lxqt menu works well in a VT, but if i chose to login on a VT *and* - if i choose to use /sbin/reboot, eg in a script, then shutdown proceeds - only part way. apparently lxqt-panel ignores the shutdown, and we're - left watching a message like + if i choose to use /sbin/reboot, eg in a script, or if two sessions are + open, then shutdown proceeds only part way. apparently lxqt-panel + ignores the shutdown, and we're left watching a message like [ *** ] a stop job is running for session 20 of lubuntu (15s / 1min 30s) workaround: kill lxqt-panel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:10:18 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1947505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947482] Re: can't change VT after starting X in lubuntu
** 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 change back to + sddm, tho after a rather long time, or some other change in + circumstances, it works again. this bug shows up in a fully updated lubuntu system as long as nobody has yet logged in at sddm. this bug shows up on the lubuntu iso (wherein sddm has already auto- logged-in to 'lubuntu'). - this bug does not show up on a regular lubuntu system if someone is - slready logged in at sddm. + this bug does not seem to show up on a regular lubuntu system if someone + is slready logged in at sddm. - this bug does not show up in kubuntu regardless whether anyone is logged - in. + this bug does not seem to show up in kubuntu regardless whether anyone + is logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sddm 0.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 16 21:09:14 2021 InstallationDate: Installed on 2021-09-30 (16 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947482 Title: can't change VT after starting X in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1947482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946366] Re: TigerVNC fullscreen is stretched and split across both screens on kubuntu 20.04
** 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 called before launching vnc, but - vice versa trips this bug in lubuntu. + On lubuntu 20.04 it usually does fullscreen on just one screen. i have + seen it stretch across both screens on lubuntu just once, but so far + haven't managed to reproduce that on lubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kwin-x11 4:5.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 7 08:08:00 2021 InstallationDate: Installed on 2021-08-03 (64 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: kwin UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1946366 Title: TigerVNC fullscreen is stretched and split across both screens on kubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1946366/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1947500] Re: lxqt-config-monitor crashes in VTs
** 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 + move mouse into the terminal. startlxqt& launch "monitor settings" from the app menu. it starts displaying its window for a split second then crashes. however if you also first login at sddm, then it works in the VT. tho meanwhile you may well run into Bug #1947504 or Bug #1947482 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-config 0.14.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 08:14:34 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-config UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947500 Title: lxqt-config-monitor crashes in VTs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1947500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947505] Re: lxqt-panel ignores shutdown in a VT
** 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 (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, and invoking reboot from + the lxqt menu works well in a VT, but if i chose to login on a VT *and* + if i choose to use /sbin/reboot, eg in a script, then shutdown proceeds + only part way. apparently lxqt-panel ignores the shutdown, and we're + left watching a message like [ *** ] a stop job is running for session 20 of lubuntu (15s / 1min 30s) workaround: kill lxqt-panel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:10:18 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1947505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947505] Re: lxqt-panel ignores shutdown in a VT
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1947505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947504] Re: second lubuntu session won't launch
** 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-terminal-emulator + move mouse into the terminal. startlxqt& lxqt doesn't come up. or maybe comes up after a long wait. however if you omit logging in at sddm, then it comes up in the VT right away. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:04:48 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947504 Title: second lubuntu session won't launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1947504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947482] Re: can't change VT after starting X in 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-alt-F1 nor 'chvt 1' is able to change back to sddm. this bug shows up in a fully updated lubuntu system as long as nobody has yet logged in at sddm. this bug shows up on the lubuntu iso (wherein sddm has already auto- logged-in to 'lubuntu'). this bug does not show up on a regular lubuntu system if someone is slready logged in at sddm. this bug does not show up in kubuntu regardless whether anyone is logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sddm 0.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 16 21:09:14 2021 InstallationDate: Installed on 2021-09-30 (16 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to sddm in Ubuntu. https://bugs.launchpad.net/bugs/1947482 Title: can't change VT after starting X in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1947482/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1946366] Re: TigerVNC fullscreen is stretched and split across both screens on kubuntu 20.04
** 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 too. it's fine if xrandr is called before launching vnc, but + vice versa trips this bug in lubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kwin-x11 4:5.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 7 08:08:00 2021 InstallationDate: Installed on 2021-08-03 (64 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: - LC_TIME=en_DK.utf8 - TERM=screen - PATH=(custom, no user) - LANG=en_US.utf8 - SHELL=/bin/bash + LC_TIME=en_DK.utf8 + TERM=screen + PATH=(custom, no user) + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: kwin UpgradeStatus: No upgrade log present (probably fresh install) -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1946366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947505] Re: lxqt-panel ignores shutdown
** 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. + apparently lxqt-panel ignores the shutdown, and we're left watching a + message like - [ *** ] a stop job is running for session 20 of lubuntu (NNs / 1m30s) + [ *** ] a stop job is running for session 20 of lubuntu (15s / 1min 30s) + + workaround: kill lxqt-panel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:10:18 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1947505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947505] Re: in a VT lubuntu takes a long time to shutdown
** 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.net/bugs/1947505 Title: lxqt-panel ignores shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1947505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947482] Re: can't change VT after starting X in lubuntu
** 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-alt-F1 nor 'chvt 1' is able to change back to sddm. this bug shows up in a fully updated lubuntu system as long as nobody has yet logged in at sddm. this bug shows up on the lubuntu iso (wherein sddm has already auto- logged-in to 'lubuntu'). this bug does not show up on a regular lubuntu system if someone is slready logged in at sddm. this bug does not show up in kubuntu regardless whether anyone is logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sddm 0.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 16 21:09:14 2021 InstallationDate: Installed on 2021-09-30 (16 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947482 Title: can't change VT after starting X in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1947482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947500] Re: lxqt-config-monitor crashes in VTs
** 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& + move mouse into the xterm. + startlxqt& launch "monitor settings" from the app menu. it starts displaying its window for a split second then crashes. however if you also first login at sddm, then it works in the VT. + + tho meanwhile you may well run into Bug #1947504 or Bug #1947482 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-config 0.14.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 08:14:34 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-config UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947500 Title: lxqt-config-monitor crashes in VTs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1947500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947504] Re: second lubuntu session won't launch
** 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 comes up after a long wait. - however if you omit logging in at sddm, then it does come up in the VT. + however if you omit logging in at sddm, then it comes up in the VT right + away. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:04:48 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947504 Title: second lubuntu session won't launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1947504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947504] Re: startlxqt fails in VT
** 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 perhaps this is fixed already. in a fully updated lubuntu system, - it works. + lxqt doesn't come up. + + however if you omit logging in at sddm, then it does come up in the VT. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:04:48 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - startlxqt fails in VT + multiple lubuntu sessions sometimes won't launch ** Summary changed: - multiple lubuntu sessions sometimes won't launch + second lubuntu session won't launch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947504 Title: second lubuntu session won't launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1947504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947500] Re: lxqt-config-monitor crashes in VTs
** 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 VT). + install xterm if you haven't already. + startx /bin/xterm& + in the xterm: startlxqt& + launch "monitor settings" from the app menu. + + it starts displaying its window for a split second then crashes. + + however if you also first login at sddm, then it works in the VT. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-config 0.14.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 08:14:34 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-config UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947500 Title: lxqt-config-monitor crashes in VTs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1947500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947482] Re: can't change VT after starting X in lubuntu
** 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). + startx /bin/xterm& thereafter neither ctl-alt-F1 nor 'chvt 1' is able to change back to sddm. this bug shows up in a fully updated lubuntu system as long as nobody has yet logged in at sddm. this bug shows up on the lubuntu iso (wherein sddm has already auto- logged-in to 'lubuntu'). this bug does not show up on a regular lubuntu system if someone is slready logged in at sddm. this bug does not show up in kubuntu regardless whether anyone is logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sddm 0.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 16 21:09:14 2021 InstallationDate: Installed on 2021-09-30 (16 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947482 Title: can't change VT after starting X in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1947482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947505] Re: in a VT lubuntu takes a long time to shutdown
** 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 lubuntu (NNs / 1m30s) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:10:18 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) -- 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: in a VT lubuntu takes a long time to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1947505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947504] Re: startlxqt fails in VT
** 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, startlxqt works in a VT. + but perhaps this is fixed already. in a fully updated lubuntu system, + it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:04:48 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947504 Title: startlxqt fails in VT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1947504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947482] Re: can't change VT after starting X in lubuntu
** 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 you launch a WM or a desktop instead or after just starting X with an xterm). thereafter neither ctl-alt-F1 nor 'chvt 1' is able to change back to sddm. this bug shows up in a fully updated lubuntu system as long as nobody has yet logged in at sddm. this bug shows up on the lubuntu iso (wherein sddm has already auto- logged-in to 'lubuntu'). this bug does not show up on a regular lubuntu system if someone is slready logged in at sddm. this bug does not show up in kubuntu regardless whether anyone is logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sddm 0.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 16 21:09:14 2021 InstallationDate: Installed on 2021-09-30 (16 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947482 Title: can't change VT after starting X in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1947482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947505] [NEW] in a VT lubuntu takes a long time to shutdown
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.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:10:18 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxqt-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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: in a VT lubuntu takes a long time to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1947505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947504] [NEW] startlxqt fails in VT
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 Package: lxqt-session 0.14.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 10:04:48 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxqt-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947504 Title: startlxqt fails in VT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1947504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947500] [NEW] lxqt-config-monitor crashes in VTs
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 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 17 08:14:34 2021 InstallationDate: Installed on 2021-09-30 (17 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: lxqt-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxqt-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947500 Title: lxqt-config-monitor crashes in VTs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1947500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947482] Re: can't change VT after starting X in lubuntu
** 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 fully updated lubuntu system as long as nobody + has yet logged in at sddm. + + this bug shows up on the lubuntu iso (wherein sddm has already auto- + logged-in to 'lubuntu'). + + this bug does not show up on a regular lubuntu system if someone is + slready logged in at sddm. + + this bug does not show up in kubuntu regardless whether anyone is logged + in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sddm 0.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 16 21:09:14 2021 InstallationDate: Installed on 2021-09-30 (16 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947482 Title: can't change VT after starting X in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1947482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947482] [NEW] can't change VT after starting X in lubuntu
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 Package: sddm 0.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 16 21:09:14 2021 InstallationDate: Installed on 2021-09-30 (16 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947482 Title: can't change VT after starting X in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1947482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883742] Re: funky character placement when kubuntu-settings-desktop installed
** 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-settings-desktop installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1883742/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1946366] [NEW] TigerVNC fullscreen is stretched and split across both screens on kubuntu 20.04
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 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 7 08:08:00 2021 InstallationDate: Installed on 2021-08-03 (64 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: kwin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kwin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1946366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891785] Re: choose-w misaligned (regression)
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 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"
but more recent versions produce an annoyingly misaligned list due to the new
session line:
(0) - 0: 4 windows (attached)
(1) ├─> 0: man- (1 panes) "e540"
(2) ├─> 1: bash (1 panes) "e540"
(3) ├─> 2: ssh* (1 panes) "e540"
(4) ├─> 3: bash (1 panes) "e540"
so when you choose a window from the new choose-window list, you have to
look carefully and choose "the wrong window" or you get the wrong
window! is there a way to fix or workaround this problem?
because this shows 0 on windows other than window 2:
$ tmux bi w choose-t -wF'#{==:#{window_index},2}'
(0) - 0: 1
(1) ├─> 0: 0
(2) ├─> 1: 0
(3) ├─> 2: 1
(4) ├─> 3: 0
thus this eliminates windows other than window 2:
$ tmux bi w choose-t -wf'#{==:#{window_index},2}'
(0) - 0: 6 windows (attached)
(1) └─> 2: ssh* (1 panes) "e540"
so similarly since this shows 0 on the session line and 1 on each window:
$ tmux bi w choose-t -wF'#{window_format}'
(0) - 0: 0
(1) ├─> 0: 1
(2) ├─> 1: 1
(3) ├─> 2: 1
(4) ├─> 3: 1
you'd expect this to eliminate the session line, and restore proper alignment
of the choose-window listing, but strangely it just doesn't:
$ tmux bi w choose-t -wf'#{window_format}'
(0) - 0: 4 windows (attached)
(1) ├─> 0: man- (1 panes) "e540"
(2) ├─> 1: bash (1 panes) "e540"
(3) ├─> 2: ssh* (1 panes) "e540"
(4) ├─> 3: bash (1 panes) "e540"
so a fix or workaround would be greatly appreciated!
+ A solution is available, see:
+ https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1891785/comments/7
+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: tmux 3.0a-2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Aug 15 21:05:07 2020
InstallationDate: Installed on 2020-03-15 (153 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
ProcEnviron:
LC_TIME=en_DK.utf8
TERM=screen
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: tmux
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891785
Title:
choose-w misaligned (regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1891785/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891785] Re: choose-w misaligned (regression)
** 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"
but more recent versions produce an annoyingly misaligned list due to the new
session line:
(0) - 0: 4 windows (attached)
(1) ├─> 0: man- (1 panes) "e540"
(2) ├─> 1: bash (1 panes) "e540"
(3) ├─> 2: ssh* (1 panes) "e540"
(4) ├─> 3: bash (1 panes) "e540"
so when you choose a window from the new choose-window list, you have to
look carefully and choose "the wrong window" or you get the wrong
window! is there a way to fix or workaround this problem?
because this shows 0 on windows other than window 2:
$ tmux bi w choose-t -wF'#{==:#{window_index},2}'
(0) - 0: 1
(1) ├─> 0: 0
(2) ├─> 1: 0
(3) ├─> 2: 1
(4) ├─> 3: 0
thus this eliminates windows other than window 2:
$ tmux bi w choose-t -wf'#{==:#{window_index},2}'
(0) - 0: 6 windows (attached)
(1) └─> 2: ssh* (1 panes) "e540"
so similarly since this shows 0 on the session line and 1 on each window:
$ tmux bi w choose-t -wF'#{window_format}'
(0) - 0: 0
(1) ├─> 0: 1
(2) ├─> 1: 1
(3) ├─> 2: 1
(4) ├─> 3: 1
you'd expect this to eliminate the session line, and restore proper alignment
of the choose-window listing, but strangely it just doesn't:
$ tmux bi w choose-t -wf'#{window_format}'
(0) - 0: 4 windows (attached)
(1) ├─> 0: man- (1 panes) "e540"
(2) ├─> 1: bash (1 panes) "e540"
(3) ├─> 2: ssh* (1 panes) "e540"
(4) ├─> 3: bash (1 panes) "e540"
so a fix or workaround would be greatly appreciated!
- A solution is available, see:
- https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1891785/comments/7
+ A solution is available, see comment #7.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: tmux 3.0a-2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Aug 15 21:05:07 2020
InstallationDate: Installed on 2020-03-15 (153 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
ProcEnviron:
LC_TIME=en_DK.utf8
TERM=screen
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: tmux
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891785
Title:
choose-w misaligned (regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1891785/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883742] Re: funky character placement when kubuntu-settings-desktop installed
** 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 on the other side, making one word look like two words. And the funky character placement often shifts around, sometimes spuriously, and sometimes when interacting, for example when i tick or untick a gmail conversation, as in the the 2nd and 3rd screenshots. Note how all the "t"'s move over in "Opportunities", "Youth", "item", and "interest". The 3 screenshots are all of the same conversation in my gmail inbox. One screenshot was taken on a Focal Ubuntu install, where the character placement is fine. The other two screenshots were taken on a Focal Kubuntu install where the character placement is funky. Using Chromium (Version 83.0.4103.61 Official Build snap 64-bit), the font spacing on my gmail inbox is fine, thus i first reported this as http://github.com/webcompat/web-bugs/issues/53474 They conclude it's not a firefox issue. i still consider it an open question. i have only a faint memory of having also seen the funky character placement in kubuntu in some context outside of firefox. The funky character placement shows up when all 3 of these factors converge: using kubuntu, using either firefox or firefox nightly, and viewing either gmail or google voice. Otherwise, eg using chromium on kubuntu, or firefox on lubuntu, or browsing other sites, character placement is fine. Within gmail, the funky character placement shows up when viewing conversation lists or settings pages, but character placement seems fine when viewing a conversation/message body. Within google voice, both message lists and message body show funky character placement. 'Binary search' thru specific situations: -good running lubuntu-20.04.3-desktop-amd64.iso live. -good install from lubuntu-20.04.3-desktop-amd64.iso live, - then startx startlxqt. - funky running kubuntu-20.04.2.0-desktop-amd64.iso live. - funky install from kubuntu-20.04.2.0-desktop-amd64.iso, - then startx startplasma-x11. - funky install from kubuntu-20.04.2.0-desktop-amd64.iso, - then apt-get install lubuntu-desktop, - then startx startlxqt. - funky install from lubuntu-20.04.3-desktop-amd64.iso, - then apt-get install kubuntu-desktop, - then startx startplasma-x11. + good running lubuntu-20.04.3-desktop-amd64.iso live. + good install from lubuntu-20.04.3-desktop-amd64.iso live, + then startx startlxqt. + funky running kubuntu-20.04.2.0-desktop-amd64.iso live. + funky install from kubuntu-20.04.2.0-desktop-amd64.iso, + then startx startplasma-x11. + funky install from kubuntu-20.04.2.0-desktop-amd64.iso, + then apt-get install lubuntu-desktop, + then startx startlxqt. + funky install from lubuntu-20.04.3-desktop-amd64.iso, + then apt-get install kubuntu-desktop, + then startx startplasma-x11. Continuing with the most recent install above: -good apt-get --auto-remove purge kubuntu-desktop + good apt-get --auto-remove purge kubuntu-desktop -good apt-get --auto-remove purge gpm+ htop+ xterm+ xzoom+ xl2tpd+ + good apt-get --auto-remove purge gpm+ htop+ xterm+ xzoom+ xl2tpd+ strongswan-starter+ keepassxc+ libevent-dev+ tigervnc-viewer+ sddm ofono thunderbird xscreensaver bind9-libs samba-libs unattended-upgrades apt- xapian-index ubuntu-release-upgrader-core python3-update-manager cups- common cups-daemon cups-ipp-utils foomatic-filters openprinting-ppds libpaps0 libcupsimage2 -good apt-get --auto-remove --purge install kate kpat krdc lame + good apt-get --auto-remove --purge install kate kpat krdc lame cryfs elisa encfs kross kamera kmines dolphin ksudoku signond go-mtpfs gwenview ktorrent libraw19 baloo-kf5 kmahjongg libgeoip1 plasma-nm kate5-data ksystemlog kio-audiocd thunderbird ffmpegthumbs freerdp2-x11 konversation print-manager geoip-database gstreamer-qapt session- migration kimageformat-plugins whoopsie-preferences kaccounts- integration fonts-noto-color-emoji signond signon-ui-x11 signon-ui- service signon-plugin-password signon-kwallet-extension - funky apt-get --auto-remove --purge install kubuntu-web-shortcuts + funky apt-get --auto-remove --purge install kubuntu-web-shortcuts kubuntu-settings-desktop kubuntu-wallpapers kubuntu-wallpapers-focal plasma-workspace-wallpapers - So that's narrowed down to 5 packages. After installing those 5 - packages, firefox character placement in gmail and google voice goes - funky. +
[Bug 1883742] Re: funky character placement on kubuntu
** 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 seems fine. The other two screenshots - were taken running Firefox Nightly on a Focal Kubuntu install where the - rendering is funky. - - This only happens on Kubuntu, eg running kubuntu-20.04.2.0-desktop- - amd64.iso live. Lubuntu-20.04.2.0-desktop-amd64.iso live is fine, no - funky font rendering. - - Even on Kubuntu, when using Chromium (Version 83.0.4103.61 Official Build snap 64-bit), the font spacing on my gmail inbox looks fine, thus i first reported this as - http://github.com/webcompat/web-bugs/issues/53474 - But they conclude it's not a Firefox issue. - - The funky font rendering only happens with the combination of Kubuntu - (with all package updates as of 9/20) with either Firefox or Firefox - Nightly eg version 94.0a1 (2021-09-24) (64-bit). Letters are often - mispositioned, jammed into the adjacent letter on one side and/or far - away from the adjacent letter on the other side. And the font - placement/spacing often shifts around, sometimes spuriously, and - sometimes when interacting, for example when i tick or untick the gmail + Funky character placement, letters often mispositioned, jammed into the + adjacent letter on one side and/or far away from the adjacent letter on + the other side, making one word look like two words. And the funky + character placement often shifts around, sometimes spuriously, and + sometimes when interacting, for example when i tick or untick a gmail conversation, as in the the 2nd and 3rd screenshots. Note how all the "t"'s move over in "Opportunities", "Youth", "item", and "interest". + + The 3 screenshots are all of the same conversation in my gmail inbox. + One screenshot was taken on a Focal Ubuntu install, where the character + placement is fine. The other two screenshots were taken on a Focal + Kubuntu install where the character placement is funky. + + Using Chromium (Version 83.0.4103.61 Official Build snap 64-bit), the font spacing on my gmail inbox is fine, thus i first reported this as + http://github.com/webcompat/web-bugs/issues/53474 + + They conclude it's not a firefox issue. i still consider it an open + question. i have only a faint memory of having also seen the funky + character placement in kubuntu in some context outside of firefox. + + The funky character placement shows up when all 3 of these factors + converge: using kubuntu, using either firefox or firefox nightly, and + viewing either gmail or google voice. Otherwise, eg using chromium on + kubuntu, or firefox on lubuntu, or browsing other sites, character + placement is fine. Within gmail, the funky character placement shows up + when viewing conversation lists or settings pages, but character + placement seems fine when viewing a conversation/message body. Within + google voice, both message lists and message body show funky character + placement. + + 'Binary search' thru specific situations: +good running lubuntu-20.04.3-desktop-amd64.iso live. +good install from lubuntu-20.04.3-desktop-amd64.iso live, + then startx startlxqt. + funky running kubuntu-20.04.2.0-desktop-amd64.iso live. + funky install from kubuntu-20.04.2.0-desktop-amd64.iso, + then startx startplasma-x11. + funky install from kubuntu-20.04.2.0-desktop-amd64.iso, + then apt-get install lubuntu-desktop, + then startx startlxqt. + funky install from lubuntu-20.04.3-desktop-amd64.iso, + then apt-get install kubuntu-desktop, + then startx startplasma-x11. + + Continuing with the most recent install above: +good apt-get --auto-remove purge kubuntu-desktop + +good apt-get --auto-remove purge gpm+ htop+ xterm+ xzoom+ xl2tpd+ + strongswan-starter+ keepassxc+ libevent-dev+ tigervnc-viewer+ sddm ofono + thunderbird xscreensaver bind9-libs samba-libs unattended-upgrades apt- + xapian-index ubuntu-release-upgrader-core python3-update-manager cups- + common cups-daemon cups-ipp-utils foomatic-filters openprinting-ppds + libpaps0 libcupsimage2 + +good apt-get --auto-remove --purge install kate kpat krdc lame + cryfs elisa encfs kross kamera kmines dolphin ksudoku signond go-mtpfs + gwenview ktorrent libraw19 baloo-kf5 kmahjongg libgeoip1 plasma-nm + kate5-data ksystemlog kio-audiocd thunderbird ffmpegthumbs freerdp2-x11 + konversation print-manager geoip-database gstreamer-qapt session- + migration kimageformat-plugins whoopsie-preferences kaccounts- + integration fonts-noto-color-emoji signond signon-ui-x11 signon-ui- + service signon-plugin-password signon-kwallet-extension + + funky apt-get --auto-remove --purge install kubuntu-web-shortcuts
[Bug 1871884] Re: "EFI system partition flag not set" - false pop-up
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 manual partitioning, edit "/dev/sda1", select "/boot/efi", "bios- grub" is already ticked, i tick "boot", click "OK", edit "/dev/sda2", select "/", click "OK", click "Next", and see EFI system partition flag not set An EFI system partition is necessary to start Lubuntu. A partition was configured with mount point /boot/efi but its esp flag is not set. To set the flag, go back and edit the partition. You can continue without setting the flag but your system may fail to start. which as noted in the OP is entirely confusing and bogus. there's no "esp" flag available in the calamares gui. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871884 Title: "EFI system partition flag not set" - false pop-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1871884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873950] Re: Calamares failed: command 'mount' returned non-zero exit status 32.
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' returned non-zero exit status 32. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1873950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883742] Re: funky font rendering 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 seems fine. The other two screenshots - were taken running Firefox Nightly on a Focal Kubuntu install. + were taken running Firefox Nightly on a Focal Kubuntu install where the + rendering is funky. - Even on Kubuntu, the font spacing on my gmail inbox looks right on - Chromium (Version 83.0.4103.61 Official Build snap 64-bit), but is funky - (extra spaces within words) on Firefox Nightly, thus this was first - reported as http://github.com/webcompat/web-bugs/issues/53474 + This only happens on Kubuntu, eg running kubuntu-20.04.2.0-desktop- + amd64.iso live. Lubuntu-20.04.2.0-desktop-amd64.iso live is fine, no + funky font rendering. - In Firefox Nightly on Kubuntu, the font placement/spacing often shifts - around, sometimes spuriously, and sometimes when interacting, for - example when i tick or untick the conversation as in the the 2nd and 3rd - screenshots. Note how all the "t"'s move over in "Opportunities", - "Youth", "item", and "interest". + Even on Kubuntu, when using Chromium (Version 83.0.4103.61 Official Build snap 64-bit), the font spacing on my gmail inbox looks fine, thus i first reported this as + http://github.com/webcompat/web-bugs/issues/53474 + But they conclude it's not a Firefox issue. + + The funky font rendering only happens with the combination of Kubuntu + (with all package updates as of 9/20) with either Firefox or Firefox + Nightly eg version 94.0a1 (2021-09-24) (64-bit). Letters are often + mispositioned, jammed into the adjacent letter on one side and/or far + away from the adjacent letter on the other side. And the font + placement/spacing often shifts around, sometimes spuriously, and + sometimes when interacting, for example when i tick or untick the gmail + conversation, as in the the 2nd and 3rd screenshots. Note how all the + "t"'s move over in "Opportunities", "Youth", "item", and "interest". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Tue Jun 16 10:33:36 2020 InstallationDate: Installed on 2020-04-05 (71 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) -- 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 font rendering on kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1883742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944455] [NEW] kde launcher won't open with high or extreme focus stealing prevention
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.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 21 11:47:55 2021 InstallationDate: Installed on 2021-08-03 (48 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: systemsettings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemsettings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944455 Title: kde launcher won't open with high or extreme focus stealing prevention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1944455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867561] Re: regression: twm won't launch in focal
** 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 had surfaced in earlier ubuntu - releases, tho sadly the solutions offered in + the same failure had surfaced in earlier ubuntu releases, tho sadly the + solutions offered in https://ubuntuforums.org/showthread.php?t=1596636 aren't helping. + + the bionic version of twm works fine, even if invoked in focal. also + the focal versions of ctwm and vtwm work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: twm 1:1.0.10-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Sun Mar 15 17:41:33 2020 InstallationDate: Installed on 2020-03-15 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) SourcePackage: twm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.X11.twm.system.twmrc-menu: 2018-12-13T11:37:49 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867561 Title: regression: twm won't launch in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twm/+bug/1867561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938228] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1938228/+attachment/5514306/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938228 Title: installer says it will format when i specify not to format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1938228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938228] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1938228/+attachment/5514305/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938228 Title: installer says it will format when i specify not to format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1938228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938228] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1938228/+attachment/5514304/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938228 Title: installer says it will format when i specify not to format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1938228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938228] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1938228/+attachment/5514303/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938228 Title: installer says it will format when i specify not to format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1938228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938228] Re: installer says it will format when i specify not to format
apport information ** Tags added: apport-collected focal third-party-packages ** Description changed: i'm running the installer on the Kubuntu 20.04 iso downloaded today and dated 2021-2-9. it's presenting me the following dialog: Write changes to disks? If you continue, the changes listed below will be written to the disks. Otherwise, you will be able to make further changes manually. WARNING: This will destroy all data on any partitions you have removed as well as on the partitions that are going to be formatted. The partition tables of the following devices are changed: SCSI1 (0,0,0)(sda) The following partitions are going to be formatted: partition #1 of SCSI1 (0,0,0)(sda) as ext3 i carefully chose neither to change the size of my partition, nor to format it, and up until the above message, the installer seemed to have accepted these choices. (1) if it is actually going to honor my choice not to format, then the message is wrong. Or if it's actually going to format, then it's not honoring my choice. (2) if it is actually going to honor my choice not to change the size of the partition, nor create nor delete any partition, then it shouldn't need to change the partition table. So again either the message, or the ensuing action, is incorrect. - (3) since i'm choosing not to format a partition, i shouldn't be - presented with a menu of how to format it. Presenting the menu makes - sense once i choose to check/tick the box to format the partition. How - about put the checkbox to the left of the menu, and enable the menu when - the checkbox gets checked/ticked. + (3) since i'm choosing not to format a partition, i shouldn't be presented with a menu of how to format it. Presenting the menu makes sense once i choose to check/tick the box to format the partition. How about put the checkbox to the left of the menu, and enable the menu when the checkbox gets checked/ticked. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + CasperMD5CheckResult: pass + CasperVersion: 1.445.1 + DistroRelease: Ubuntu 20.04 + InstallCmdLine: BOOT_IMAGE=(j)/casper/vmlinuz boot=casper iso-scan/filename=/fu/home/greg/Downloads/kubuntu-20.04.2.0-desktop-amd64.iso panic=30 toram -- + LiveMediaBuild: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) + Package: ubiquity 20.04.15.10 [origin: unknown] + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 + Tags: third-party-packages focal + Uname: Linux 5.8.0-43-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "Casper.txt" https://bugs.launchpad.net/bugs/1938228/+attachment/5514302/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938228 Title: installer says it will format when i specify not to format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1938228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938228] Re: installer says it will format when i specify not to format
i tried 'ubuntu-bug ubiquity' on the iso, it said something like 'ubiquity is not part of ubuntu' ** Package changed: partman-basicfilesystems (Ubuntu) => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938228 Title: installer says it will format when i specify not to format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1938228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938228] [NEW] installer says it will format when i specify not to format
Public bug reported: i'm running the installer on the Kubuntu 20.04 iso downloaded today and dated 2021-2-9. it's presenting me the following dialog: Write changes to disks? If you continue, the changes listed below will be written to the disks. Otherwise, you will be able to make further changes manually. WARNING: This will destroy all data on any partitions you have removed as well as on the partitions that are going to be formatted. The partition tables of the following devices are changed: SCSI1 (0,0,0)(sda) The following partitions are going to be formatted: partition #1 of SCSI1 (0,0,0)(sda) as ext3 i carefully chose neither to change the size of my partition, nor to format it, and up until the above message, the installer seemed to have accepted these choices. (1) if it is actually going to honor my choice not to format, then the message is wrong. Or if it's actually going to format, then it's not honoring my choice. (2) if it is actually going to honor my choice not to change the size of the partition, nor create nor delete any partition, then it shouldn't need to change the partition table. So again either the message, or the ensuing action, is incorrect. (3) since i'm choosing not to format a partition, i shouldn't be presented with a menu of how to format it. Presenting the menu makes sense once i choose to check/tick the box to format the partition. How about put the checkbox to the left of the menu, and enable the menu when the checkbox gets checked/ticked. ** Affects: partman-basicfilesystems (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/1938228 Title: installer says it will format when i specify not to format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/1938228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930995] Re: snapd too heavy for lubuntu
i don't even want auto updates. i've already removed unattended- upgrades. i would hope there's some way to turn them off for snaps too. perhaps stop and disable snapd would do it. but that would of course need to be undone to update chromium. which is why i shouldn't need to disable snapd and snapd ought to exit by itself. in my opinion the removal of unattended-upgrades should by default also avert auto updates by snap. fwiw i checked, and actually snapd does appear to be already installed as part of lubuntu-desktop. when i installed chromium-browser it didn't need to pull in anything else along with it. if i were to remove snapd now, along with it that would take out libsnapd-qt1 plasma-discover- backend-snap chromium-browser libpipewire-0.2-1 squashfs-tools xdg- desktop-portal* xdg-desktop-portal-kde. of those all i want is chromium, tho i only use chromium on rare occasions when firefox doesn't handle something properly. i may yet try to see if removing the lot of them would somehow cripple my system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930995 Title: snapd too heavy for lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1930995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930995] Re: snapd too heavy for lubuntu
seems like tunnel vision to me, no concern for getting out of the way (exiting) when there's really nothing to be done. chromium isn't even running. if it, or snap, were invoked, that would be a reasonable time to re-launch. if such reasonable analysis is not in the scope of the project, i'd say the project ought not be in the scope of lubuntu. hmm, actually, perhaps it already isn't, perhaps i only got stuck to the tarbaby by installing chromium. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930995 Title: snapd too heavy for lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1930995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930995] [NEW] snapd too heavy for lubuntu
Public bug reported: when my lubuntu focal box gets heavy into thrashing, snapd sits there and hangs on to 20mb of resident memory. why so heavy? reminds me of zfs. wonderful features. but way too heavy. snapd is too heavy for lubuntu. lubuntu is supposed to work well with not so much ram. why is snapd even a daemon? i get that it installs and updates chromium for me. why does it need to be a daemon to do that? it would be great if snapd gets redesigned to exit the daemon when i don't need it. which is almost always for me. i could probably do what i want by killing off snapd, and putting it back when i need to update chromium. but it ought to take care of all that by itself, and mostly be out of my hair, by itself. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: snapd 2.48.3+20.04 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 5 23:09:43 2021 InstallationDate: Installed on 2020-03-15 (447 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=g TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-08-27T20:37:28.010487 ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930995 Title: snapd too heavy for lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1930995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926680] [NEW] apache2 won't restart after installing nagios4
Public bug reported: the issue is described here: https://wiki.debian.org/Nagios4 in summary, after installing nagios4, apache2 won't restart, until: a2enmod auth_digest a2enmod authz_groupfile ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nagios4 (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 29 21:33:16 2021 InstallationDate: Installed on 2020-11-30 (150 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nagios4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nagios4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926680 Title: apache2 won't restart after installing nagios4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios4/+bug/1926680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621203] Re: evolution/totem/gthumb crashes when run in vnc session
been bothered by this for years with gthumb. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621203 Title: evolution/totem/gthumb crashes when run in vnc session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1621203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903057] Re: vim confused by \~/
see https://github.com/vim/vim/issues/8015 ** Bug watch added: github.com/vim/vim/issues #8015 https://github.com/vim/vim/issues/8015 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903057 Title: vim confused by \~/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1903057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902643] Re: tmux drops out of copy mode (regression)
see https://github.com/tmux/tmux/issues/2538 ** Bug watch added: github.com/tmux/tmux/issues #2538 https://github.com/tmux/tmux/issues/2538 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902643 Title: tmux drops out of copy mode (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1902643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912330] Re: regression: non-X VTs stopped using energy star after xenial
** Summary changed: - non-X VTs should use energy star + regression: non-X VTs stopped using energy star after xenial ** Description changed: - it's simple. it's easy. let's get our servers being good energy star - citizens shall we? + as of xenial, non-X VTs timed out and powered down even if nobody ever + logged in. but that's no longer true in bionic and focal. if a VT is running X at all, whether that's running sddm and never logged in, or sddm and logged-in, or not running sddm and simply logged- in and running X started with startx, that VT will timeout and - powerdown. so far so good. + powerdown, even on bionic and focal. no problem there. but a VT that's either running getty, or logged in and just running - bash, will stay powered up and blazing away forever, whether it's ubuntu - server 20.04, lubuntu 20.04, or centos 8. + bash, will stay powered up and blazing away forever, if it's ubuntu + 18.04 or 20.04, server or lubuntu. or centos 8. so probably RHEL 8 too, so probably most servers, aren't being good - energy star citizens! boo! + energy star citizens anymore. something happened since xenial. the util-linux package is used by both centos 8 and ubuntu 20.04, and contains both getty and setterm. - thus getty seems to me to be the sensible place to call: + probably getty would be the place, that either used to call, or should + now call: setterm -term=linux -powersave=powerdown -powerdown=15 -store>/dev/tty0https://bugs.launchpad.net/bugs/1912330 Title: regression: non-X VTs stopped using energy star after xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1912330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912330] Re: non-X VTs should use energy star
** Description changed: it's simple. it's easy. let's get our servers being good energy star citizens shall we? if a VT is running X at all, whether that's running sddm and never logged in, or sddm and logged-in, or not running sddm and simply logged- in and running X started with startx, that VT will timeout and powerdown. so far so good. but a VT that's either running getty, or logged in and just running bash, will stay powered up and blazing away forever, whether it's ubuntu server 20.04, lubuntu 20.04, or centos 8. so probably RHEL 8 too, so probably most servers, aren't being good energy star citizens! boo! the util-linux package is used by both centos 8 and ubuntu 20.04, and contains both getty and setterm. thus getty seems to me to be the sensible place to call: - setterm -powersave=powerdown -powerdown=15 -store + setterm -term=linux -powersave=powerdown -powerdown=15 + -store>/dev/tty0https://bugs.launchpad.net/bugs/1912330 Title: non-X VTs should use energy star To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1912330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912330] Re: non-X VTs should use energy star
** Summary changed: - ubuntu server not a good energy star citizen apparently + non-X VTs should use energy star ** Description changed: - Something like + it's simple. it's easy. let's get our servers being good energy star + citizens shall we? - setterm -powersave=powerdown -powerdown=15 -store + if a VT is running X at all, whether that's running sddm and never + logged in, or sddm and logged-in, or not running sddm and simply logged- + in and running X started with startx, that VT will timeout and + powerdown. so far so good. - ought to do it, probably right whenever/wherever a VT is activated. + but a VT that's either running getty, or logged in and just running + bash, will stay powered up and blazing away forever, whether it's ubuntu + server 20.04, lubuntu 20.04, or centos 8. - tho when i try that command i get + so probably RHEL 8 too, so probably most servers, aren't being good + energy star citizens! boo! - setterm: cannot (un)set powersave mode: Inappropriate ioctl for device + the util-linux package is used by both centos 8 and ubuntu 20.04, and + contains both getty and setterm. - is that the problem, something lacking in a device driver or whatever? + thus getty seems to me to be the sensible place to call: - or does the HP EliteDesk Pro 800 G1 SFF actually lack dpms energy star - features? seems dubious that it would. + setterm -powersave=powerdown -powerdown=15 -store - or is it just a case of finger pointing? ubuntu saying systemd should - do it, systemd saying getty should do it? - - whatever, i shouldn't walk up to a server terminal that's had nobody - there for hours and hours and see it's display still burning away, - right? + such that a VT running getty, or logged in and running bash, would then + timeout and powerdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 19 05:13:35 2021 InstallationDate: Installed on 2020-12-28 (21 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteDesk 800 G1 SFF ProcEnviron: - TERM=screen - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/fs/boot/vmlinuz ro root=UUID=a671d866-a05f-4b83-8714-0b448b1eeac4 subroot=/fs init=/fs/etc/g/subroot SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.33 dmi.board.name: 1998 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.33:bd07/15/2014:svnHewlett-Packard:pnHPEliteDesk800G1SFF:pvr:rvnHewlett-Packard:rn1998:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 SFF dmi.product.sku: J6D79UT#ABA dmi.sys.vendor: Hewlett-Packard ** Package changed: systemd (Ubuntu) => util-linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912330 Title: non-X VTs should use energy star To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1912330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912330] Re: ubuntu server not a good energy star citizen apparently
** Summary changed: - ubuntu server not a good energy star citizen? really? + ubuntu server not a good energy star citizen apparently -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912330 Title: ubuntu server not a good energy star citizen apparently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912330] Re: ubuntu server not a good energy star citizen? really?
no, i say it's a bug. We shouldn't have to "figure out how to use" energy star features! they should just work out of the box. Especially on a server console that hasn't even been logged into! ** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912330 Title: ubuntu server not a good energy star citizen apparently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912330] [NEW] ubuntu server not a good energy star citizen? really?
Public bug reported: Something like setterm -powersave=powerdown -powerdown=15 -store ought to do it, probably right whenever/wherever a VT is activated. tho when i try that command i get setterm: cannot (un)set powersave mode: Inappropriate ioctl for device is that the problem, something lacking in a device driver or whatever? or does the HP EliteDesk Pro 800 G1 SFF actually lack dpms energy star features? seems dubious that it would. or is it just a case of finger pointing? ubuntu saying systemd should do it, systemd saying getty should do it? whatever, i shouldn't walk up to a server terminal that's had nobody there for hours and hours and see it's display still burning away, right? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 19 05:13:35 2021 InstallationDate: Installed on 2020-12-28 (21 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteDesk 800 G1 SFF ProcEnviron: TERM=screen PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/fs/boot/vmlinuz ro root=UUID=a671d866-a05f-4b83-8714-0b448b1eeac4 subroot=/fs init=/fs/etc/g/subroot SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.33 dmi.board.name: 1998 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.33:bd07/15/2014:svnHewlett-Packard:pnHPEliteDesk800G1SFF:pvr:rvnHewlett-Packard:rn1998:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 SFF dmi.product.sku: J6D79UT#ABA dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912330 Title: ubuntu server not a good energy star citizen? really? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902643] Re: tmux drops out of copy mode (regression)
i just saw this happen on tmux-3.1b-x86_64.AppImage (from https://github.com/tmux/tmux/wiki/Installing at "Prebuilt AppImage packages") so i'll report it there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902643 Title: tmux drops out of copy mode (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1902643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909480] Re: ubuntu installer wont probe block devices if invoked via ssh
** Description changed: - While groping for a workaround to bug #1909478 i tried logging into the - ubiquity installer via ssh. This looks like a very nice feature, but - unfortunately, when logged in thusly via ssh, the installer says "Guided - storage configuration...Block probing did not discover any disks. - Unfortunately this means that installation will not be possible." + While groping for a workaround to bug #1909478 i tried setting the + password on the 'installer' account and logging in via ssh, whereupon + the installer works via ssh. This looks to be a very nice feature, but, + sadly, when logged in thusly via ssh, the installer oddly fails to probe + the discs, saying "Guided storage configuration...Block probing did not + discover any disks. Unfortunately this means that installation will not + be possible." ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Mon Dec 28 06:35:11 2020 InstallCmdLine: BOOT_IMAGE=(i)/casper/vmlinuz iso-scan/filename=/home/greg/ubuntu-20.04.1-live-server-amd64.iso boot=casper panic=30 toram -- LiveMediaBuild: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: - TERM=screen - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909480 Title: ubuntu installer wont probe block devices if invoked via ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1909480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909478] [NEW] ubuntu installer Create LVM volume group Devices are invisible
Public bug reported: Booted ubuntu installer live iso, got as far as "Create LVM volume group", which presents a list of Devices which are invisible. The tab key clearly steps through the invisible devices, but as they are invisible i cant see which to choose. As a sometimes workaround, by hitting the spacebar on each invisible choice, the size is shown, and i can sometimes deduce from that which device it is, tho if several devices are the same size even that doesn't help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Mon Dec 28 06:44:19 2020 InstallCmdLine: BOOT_IMAGE=(i)/casper/vmlinuz iso-scan/filename=/home/greg/ubuntu-20.04.1-live-server-amd64.iso boot=casper panic=30 toram -- LiveMediaBuild: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909478 Title: ubuntu installer Create LVM volume group Devices are invisible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1909478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909480] [NEW] ubuntu installer wont probe block devices if invoked via ssh
Public bug reported: While groping for a workaround to bug #1909478 i tried logging into the ubiquity installer via ssh. This looks like a very nice feature, but unfortunately, when logged in thusly via ssh, the installer says "Guided storage configuration...Block probing did not discover any disks. Unfortunately this means that installation will not be possible." ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Mon Dec 28 06:35:11 2020 InstallCmdLine: BOOT_IMAGE=(i)/casper/vmlinuz iso-scan/filename=/home/greg/ubuntu-20.04.1-live-server-amd64.iso boot=casper panic=30 toram -- LiveMediaBuild: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909480 Title: ubuntu installer wont probe block devices if invoked via ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1909480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903057] [NEW] vim confused by \~/
Public bug reported: $ cd $ mkdir \~ $ echo content a>\~/a $ echo content b>b $ less \~/a b :n :e# :q $ vim \~/a b :n :e# less is not confused, but vim has forgotten where the first file was. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Nov 5 08:50:54 2020 InstallationDate: Installed on 2019-11-16 (354 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903057 Title: vim confused by \~/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1903057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902643] Re: tmux drops out of copy mode (regression)
Caught centos8 tmux (2.7-1.el8.x86_64) a couple times dropping out of
copy mode apparently in response to window size changes while showing a
different tmux window, tho now when i repeat what i thought was the
trigger sequence i can't repeat it again. Of course i was hoping to
catch focal tmux in the act of dropping out of copy mode, but not yet
today.
Meanwhile i do observe focal tmux (3.0a-2ubuntu0.1) oddly changing the
window size by one line and changing it right back again in response to
window size changes while showing a different tmux window. to wit:
$ alias ws='c=;while ((c==COLUMNS&==LINES))||{ c=$COLUMNS l=$LINES;echo
$(date +%F%a%T) ${l}x$c;};do sleep .05;done' #track window size changes
$ ws
2020-11-04Wed15:43:52 57x226
2020-11-04Wed15:44:00 24x80
2020-11-04Wed15:44:01 57x226
2020-11-04Wed15:44:15 56x226
2020-11-04Wed15:44:15 57x226
'24x80' was when i unmaximized the xterm, and '57x226' when i
remaximized it a second later, without changing the tmux window
meanwhile. However then i switched to show a different tmux window,
unmaximized, remaximized, and then when i switched the tmux window back,
you see the odd little dance where tmux changes by one line to '56x226'
and immediately back to '57x226'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902643
Title:
tmux drops out of copy mode (regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1902643/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902643] Re: tmux drops out of copy mode (regression)
Yes indeed copy mode as per the manpage, which i use frequently not for copy paste but simply for review. And yes i typically run tmux in an xterm. i haven't tweaked or created any config files for either xterm or tmux. For xterm i use the following variables and aliases, occasionally the xt alias for starting an additional xterm, but more typically just the x alias to start X with a single xterm (from which i launch a window manager according to preference or need, usually twm, occasionally openbox). xk='xterm -bg black -fg white -xrm "*"'charClass:33:48,37-38:48,43:48,45-47:48,58:48,63-64:48,92:48,94:48,126:48 #doubleclick group ! %& + -./ : ?@ \ ^ ~ xt=$xk\ -rightbar #xk knoppix rxvt no -rightbar alias xt="$xt&" alias xk="$xk&" alias x='startx /usr/bin/$xt' For tmux i just use the following aliases, all 5 are identical except for setting the escape char to one of ^a ^q ^b ^x ^e, which i use for stacking sessions (eg my phone on the first level, ssh to my laptop on the next level, ssh to a server on the next level, ssh to other servers on the next level, etc). alias ta='tmux h 2>/dev/null||tmux new -d;tmux bi w choose-w 2>/dev/null||tmux bi w choose-t -w;tmux set status off\; set visual-b on\; set display-t \; set prefix ^A\; bi ^A last\; bi a send-p\; bi k killp\; bi . detac\; bi _ sp\; bi \| sp -h\; bi \" set status\; bi Tab selectp -t :.+\; a -d' alias tq='tmux h 2>/dev/null||tmux new -d;tmux bi w choose-w 2>/dev/null||tmux bi w choose-t -w;tmux set status off\; set visual-b on\; set display-t \; set prefix ^Q\; bi ^Q last\; bi q send-p\; bi k killp\; bi . detac\; bi _ sp\; bi \| sp -h\; bi \" set status\; bi Tab selectp -t :.+\; a -d' alias tb='tmux h 2>/dev/null||tmux new -d;tmux bi w choose-w 2>/dev/null||tmux bi w choose-t -w;tmux set status off\; set visual-b on\; set display-t \; set prefix ^B\; bi ^B last\; bi b send-p\; bi k killp\; bi . detac\; bi _ sp\; bi \| sp -h\; bi \" set status\; bi Tab selectp -t :.+\; a -d' alias tx='tmux h 2>/dev/null||tmux new -d;tmux bi w choose-w 2>/dev/null||tmux bi w choose-t -w;tmux set status off\; set visual-b on\; set display-t \; set prefix ^X\; bi ^X last\; bi x send-p\; bi k killp\; bi . detac\; bi _ sp\; bi \| sp -h\; bi \" set status\; bi Tab selectp -t :.+\; a -d' alias te='tmux h 2>/dev/null||tmux new -d;tmux bi w choose-w 2>/dev/null||tmux bi w choose-t -w;tmux set status off\; set visual-b on\; set display-t \; set prefix ^E\; bi ^E last\; bi e send-p\; bi k killp\; bi . detac\; bi _ sp\; bi \| sp -h\; bi \" set status\; bi Tab selectp -t :.+\; a -d' One prospect is the bug might be related to window size change (it's one of the reasons i prefer tmux, screen will immediately drop copy mode in response to a window size change, thankfully tmux doesn't). i recall several occurrences happening very soon after returning to a window from another. in the meantime i might have changed the xterm size, or reattached from my phone, or rotated the phone... But i think i've also seen it happen without any window size change, can't promise tho, i'll watch for further occurrences. Let me know if there's more i can clarify or share with you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902643 Title: tmux drops out of copy mode (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1902643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902595] Re: Unit strongswan.service could not be found. (regression)
yes that works (systemctl status strongswan-starter) thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902595 Title: Unit strongswan.service could not be found. (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1902595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902643] [NEW] tmux drops out of copy mode (regression)
Public bug reported: After what might be about a minute, or other times many minutes, tmux drops out of copy mode. if the elapsed time were consistent i'd presume it's an intentional feature, and if it were an intentional feature i'd be asking for a way to opt out of that behavior, but as the timing is random i presume it's a bug, and a regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tmux 3.0a-2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 2 22:17:39 2020 InstallationDate: Installed on 2020-03-15 (232 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: tmux UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-08-27T20:37:28.010487 ** Affects: tmux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902643 Title: tmux drops out of copy mode (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1902643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902595] Re: Unit strongswan.service could not be found. (regression)
** Description changed: - # systemctl status strongswan + # systemctl status strongswan Unit strongswan.service could not be found. $ dpkg-query -W strongswan strongswan 5.8.2-1ubuntu3.1 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ - no such problem in bionic. + No such problem in bionic. Or if this is an intentional new design, + please advise new instructions to follow superseding "service strongswan + restart" and related instructions at http://github.com/hwdsl2/setup- + ipsec-vpn/blob/master/docs/clients.md#configure-linux-vpn-clients-using- + the-command-line ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: strongswan 5.8.2-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 2 17:36:49 2020 InstallationDate: Installed on 2020-03-15 (232 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) PackageArchitecture: all ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: strongswan UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-08-27T20:37:28.010487 ** Description changed: - # systemctl status strongswan + # systemctl status strongswan Unit strongswan.service could not be found. $ dpkg-query -W strongswan strongswan 5.8.2-1ubuntu3.1 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ No such problem in bionic. Or if this is an intentional new design, please advise new instructions to follow superseding "service strongswan restart" and related instructions at http://github.com/hwdsl2/setup- ipsec-vpn/blob/master/docs/clients.md#configure-linux-vpn-clients-using- the-command-line ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: strongswan 5.8.2-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 2 17:36:49 2020 InstallationDate: Installed on 2020-03-15 (232 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) PackageArchitecture: all ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: strongswan UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-08-27T20:37:28.010487 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902595 Title: Unit strongswan.service could not be found. (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1902595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902595] Re: Unit strongswan.service could not be found. (regression)
** Summary changed: - Unit strongswan.service could not be found. + Unit strongswan.service could not be found. (regression) ** Description changed: - # status strongswan + # systemctl status strongswan Unit strongswan.service could not be found. - $ dpkg-query -W strongswan + $ dpkg-query -W strongswan strongswan 5.8.2-1ubuntu3.1 - $ cat /etc/lsb-release + $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" - $ + $ no such problem in bionic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: strongswan 5.8.2-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 2 17:36:49 2020 InstallationDate: Installed on 2020-03-15 (232 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) PackageArchitecture: all ProcEnviron: - LC_TIME=en_DK.utf8 - TERM=screen - PATH=(custom, no user) - LANG=en_US.utf8 - SHELL=/bin/bash + LC_TIME=en_DK.utf8 + TERM=screen + PATH=(custom, no user) + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: strongswan UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-08-27T20:37:28.010487 ** Description changed: - # systemctl status strongswan + # systemctl status strongswan Unit strongswan.service could not be found. $ dpkg-query -W strongswan strongswan 5.8.2-1ubuntu3.1 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ no such problem in bionic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: strongswan 5.8.2-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 2 17:36:49 2020 InstallationDate: Installed on 2020-03-15 (232 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) PackageArchitecture: all ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: strongswan UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-08-27T20:37:28.010487 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902595 Title: Unit strongswan.service could not be found. (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1902595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902595] [NEW] Unit strongswan.service could not be found. (regression)
Public bug reported: # systemctl status strongswan Unit strongswan.service could not be found. $ dpkg-query -W strongswan strongswan 5.8.2-1ubuntu3.1 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ no such problem in bionic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: strongswan 5.8.2-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 2 17:36:49 2020 InstallationDate: Installed on 2020-03-15 (232 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) PackageArchitecture: all ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: strongswan UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-08-27T20:37:28.010487 ** Affects: strongswan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902595 Title: Unit strongswan.service could not be found. (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1902595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460362] Re: "a week ago last thu" wrong
** Tags added: bionic focal xenial ** Tags added: amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460362 Title: "a week ago last thu" wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1460362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883742] Re: funky font rendering on kubuntu
** Summary changed: - funky font rendering on kubuntu and lubuntu + funky font rendering 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 seems fine. The other two screenshots were taken running Firefox Nightly on a Focal Kubuntu install. Even on Kubuntu, the font spacing on my gmail inbox looks right on Chromium (Version 83.0.4103.61 Official Build snap 64-bit), but is funky (extra spaces within words) on Firefox Nightly, thus this was first reported as http://github.com/webcompat/web-bugs/issues/53474 - In Firefox Nightly on Kubuntu or Lubuntu, the font placement/spacing - often shifts around, sometimes spuriously, and sometimes when - interacting, for example when i tick or untick the conversation as in - the the 2nd and 3rd screenshots. Note how all the "t"'s move over in - "Opportunities", "Youth", "item", and "interest". + In Firefox Nightly on Kubuntu, the font placement/spacing often shifts + around, sometimes spuriously, and sometimes when interacting, for + example when i tick or untick the conversation as in the the 2nd and 3rd + screenshots. Note how all the "t"'s move over in "Opportunities", + "Youth", "item", and "interest". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Tue Jun 16 10:33:36 2020 InstallationDate: Installed on 2020-04-05 (71 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) ProcEnviron: - LC_TIME=en_DK.utf8 - TERM=screen - PATH=(custom, no user) - LANG=en_US.utf8 - SHELL=/bin/bash + LC_TIME=en_DK.utf8 + TERM=screen + PATH=(custom, no user) + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) -- 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 font rendering on kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1883742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894400] Re: Establishing connection to PulseAudio. Please wait...
Attaching as requested. fyi i was rather busy yesterday and was able to overlook the fact that pavucontrol said "Establishing connection to PulseAudio. Please wait..." all day because even so sound was working and the volume was tolerable. i didn't even shut the box off last night. i finally got around to launching the additional pulseaudio process this morning whereupon i observe that this manifestation differs from prior manifestations in that pavucontrol only then displayed the built-in audio with no mention of my arctis 7 headset which meanwhile was working! so i killed both pulseaudio processes owned by me (tho not the third one owned by sddm, i didn't login via sddm) and launched another. whereupon pulseaudio showed all the devices, but the youtube player was stuck as if it was paused but wasn't. so i killed my pulseaudio processes again, whereupon the youtube player proceeded as if it was no longer paused, but i could no longer hear the audio! so i paused the youtube player, this time killed All the pulseaudio processes, unpaused the youtube player, i could then hear audio again and another pulseaudio process had somehow spawned, but pavucontrol was still stuck saying "Establishing connection to PulseAudio. Please wait..." so i launched another pulseaudio process which made pavucontrol happy again but the youtube player again stayed stuck as if paused again. so again i killed all pulseaudio processes, the youtube player plays, i can hear it, but pavucontrol says "Establishing connection to PulseAudio. Please wait...". so i killed pulseaudio again, and now i can hear the youtube but there's no pulseaudio process! after a tad longer of listening another pulseaudio process appeared, and again pavucontrol-qt is stuck saying "Establishing...". i launched pavucontrol (no -qt) at this point, they're both stuck saying "Establishing...". i then launched another pulseaudio process, whereupon both pavucontrols immediately showed the controls but the youtube player is stuck again. so i'll finally give up and reboot, after attaching the journalctl report, which should span from yesterday morning through this morning... ** Attachment added: "see my 9/28 comment" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+attachment/5415004/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894400 Title: Establishing connection to PulseAudio. Please wait... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894400] Re: Establishing connection to PulseAudio. Please wait...
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894400 Title: Establishing connection to PulseAudio. Please wait... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894400] Re: Establishing connection to PulseAudio. Please wait...
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894400 Title: Establishing connection to PulseAudio. Please wait... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894400] Re: Establishing connection to PulseAudio. Please wait...
>On the affected machine, please: >1. Check for any crashes in /var/crash/ None. >2. Reproduce the problem again and verify there is a pulseaudio process running while the problem is occuring. Yes there was. >3. Reboot, reproduce the problem again and while it is happening run: >journalctl -b0 > journal.txt >and attach the resulting text file here. i believe what you are asking for is already in comment #3, in the attachment, immediately following "CurrentDmesg:". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894400 Title: Establishing connection to PulseAudio. Please wait... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894400] Re: Establishing connection to PulseAudio. Please wait...
** Attachment added: "ubuntu-bug report from the proper computer" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+attachment/5407983/+files/apport.pulseaudio.hg6b4xhv.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894400 Title: Establishing connection to PulseAudio. Please wait... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894400] Re: Establishing connection to PulseAudio. Please wait...
Sorry i launched ubuntu-bug on the wrong box. And upon running it on the proper box just now, it said '*** It seems you have modified the contents of "/etc/apport/crashdb.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C):'. i answered 'y'. But, no, i didn't modify that file! But whatever, tho bizarre, hopefully that's irrelevant. Anyway, see the attachment for the report from the proper box. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894400 Title: Establishing connection to PulseAudio. Please wait... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
