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
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
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
** 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
** 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.
** 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.
** 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
** 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
** 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
** 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:
-
** 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.
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
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
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'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
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
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
** 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
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
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
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
** 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,
** 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
** 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
** 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,
** 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
** 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
** Description changed:
- install xterm in, and fully update, a lubuntu 20.04 system.
- boot it up (into sddm).
+ boot up a fully updated lubuntu 20.04 system (into sddm).
press ctl-alt-F2.
login (on the VT).
- startx /bin/xterm&
- move mouse into the xterm.
+ startx /bin/x-terminal-emulator
** Description changed:
- 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
** 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
** 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
** 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
** 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
+
** 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.
+
** 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.
** 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
** Description changed:
- boot up (a fully updated) lubuntu 20.04 (into sddm).
+ install xterm in, and fully update, a lubuntu 20.04 system.
+ boot it up (into sddm).
press ctl-alt-F2.
login (on the VT).
- install xterm if you haven't already.
startx /bin/xterm&
- in the xterm: startlxqt&
** Description changed:
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
** 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
** 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
** 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).
+
** 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
** 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,
** 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
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
Public bug reported:
on a plain, fully updated lubuntu system, or in the lubuntu live iso,
startlxqt fails in a VT.
on a system with kubuntu-desktop also installed, or in the kubuntu live
iso after installing lubuntu-desktop, startlxqt works in a VT.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Public bug reported:
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
** 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
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 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
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
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
** 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*
** 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
** 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
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
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'
** 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
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
** 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
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.
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
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.
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.
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,
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.
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
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
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
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.
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:
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
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:
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
** 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
** 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
** 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
** 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:
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
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
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.
** 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
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
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
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
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
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
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
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
** 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
** 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
+ $
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"
$
** 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:
** 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
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
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
** 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
>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
** 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
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
1 - 100 of 469 matches
Mail list logo
