Public bug reported:
this crash did happen after i successfully submitted my last report.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: apport-kde 2.20.11-0ubuntu79
ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27
Uname: Linux 5.15.0-23-lowlatency x86_64
ApportVersion:
On 100% scaling it is certainly less noticeable, though the cursor
sometimes appears slightly moved to the right of where it actually is.
The screen resolution I am using is (and always has been) 3000x2000.
Maybe it has something to do with this less common screen ratio.
--
You received this bug
With fractional scaling at 150%, it occurs only after some time. On a
fresh reboot it isn't apparent, but it gradually gets worse when
manipulating text. It's as if some error accumulates with time. After a
while it becomes really annoying when working with text. The cursor
position is correct,
Have been testing at 100% and 200% scaling - so far the problem hasn't
appeared at these scalings, which makes me suspect it is a problem with
fractional scaling. It's a new problem, as, about a month ago, there was
no such problem with the same fractional scaling - I have always
preferred 150% on
Public bug reported:
Ubuntu 20.04.2 LTS
systemd 245.4-4ubuntu3.4
The system is configured to use LDAP via nsswitch.conf:
passwd: files systemd ldap
group: files systemd ldap
shadow: files ldap
gshadow:files
Using libnss-ldap 265-5ubuntu1. When logging in with
no, not really. the alien package "fs-uae-launcher" is the cause of the
fail.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1888985
Title:
fs-uae-launcher did
I have the default number of kernels installed with unattended upgrades
& autoremove, so 3. I have configured xz compression, which normally
stops this. /boot is undersized due to this install being done with a
Xenial pre-release (before the default /boot size was increased). I
don't know what
Public bug reported:
automatic upgrades failed somehow, possibly undersized /boot
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2
ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-25-generic
All charms using snaps are currently failing, so I'm looking forward to
a snapd release with the commented out Nice. The alternative is adding
the systemd override workaround to the snap layer and making everyone
rebuild and republish their charms.
--
You received this bug notification because
** Also affects: layer-snap
Importance: Undecided
Status: New
** Changed in: layer-snap
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
It also requires a complete reinstall if your boot partition is too
small (ie. you accepted the defaults with an LVM or encrypted disk
install pre 16.04 release). Machines upgraded from 14.04 will continue
to fail and be directed here.
--
You received this bug notification because you are a
Work around is to use the trash-cli package and empty trash from the
command line.
Upstream fixes in nautilus seems stalled, per
https://bugzilla.gnome.org/show_bug.cgi?id=604015 , with no comments
from maintainers for the several months that patches have been
available.
--
You received this
I see this with IPv6 disabled completely on the laptop:
$ cat /etc/sysctl.d/99-noipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
I can confirm that both ipv4 and ipv6 settings have both 'Use this
connection only for resources
Private PPAs are accessed with basic auth using https: URLs to private-
ppa.launchpad.net.
https://stub:secretkeyfromlp@private-
ppa.launchpad.net/teamname/ppaname/ubuntu
It would be great if add-apt-repository accepted this or a similar URL,
use it to retrieve the signing key security and add
Public bug reported:
'ubuntu-bug snap' is reporting bugs against the snap package, which is
exactly what the docs say it should do, and not what users who do not
have the snap package installed want it to do. They probably want it to
report a bug against the snapd package, which owns
** Tags added: canonical-is
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1554848
Title:
Please randomise automatic updates over a longer period
Status in
I should have added that I'm on 14.04 LTS and the make version is 3.81.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to make-dfsg in Ubuntu.
https://bugs.launchpad.net/bugs/483086
Title:
Incorrect per-target ?= variable
We just spent an hour tracking down a problem only to find the bug has
been around since 2009.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to make-dfsg in Ubuntu.
https://bugs.launchpad.net/bugs/483086
Title:
Incorrect
stub@aargh:~$ sudo systemctl status lxc
● lxc.service - LXC Container Initialization and Autoboot Code
Loaded: loaded (/lib/systemd/system/lxc.service; enabled; vendor preset:
enabled)
Active: active (exited) since Mon 2015-10-12 16:57:31 ICT; 20h ago
Process: 1190
Is this Bug #1490110 ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1504496
Title:
package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess
installed
2015-09-29 10:30:55,881 INFO cache.commit()
2015-09-29 10:30:55,881 DEBUG failed to SystemUnLock() (E:Not locked)
2015-09-29 11:04:11,358 ERROR got an error from dpkg for pkg: 'lxc':
'subprocess installed post-installation script returned error exit status 100'
2015-09-29 11:04:11,358 DEBUG
Upgrade to wily failed here with this error. Possible trigger was
having juju-local installed, which seemed to create a bit of a
dependency mess with juju-local, lxc-templates and lxc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+attachment/4478083/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+attachment/4478084/+files/main.log
** Changed in: lxc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
I am interested in priming the lxc cache on new hosts, but this is
problematic because /var/cache/lxc is not world readable.
Could it become world readable?
This bug should be WONTFIX if the cache can contain secrets or 'private'
images. But ideally these would be declared
** Changed in: postgresql (Juju Charms Collection)
Status: Triaged = In Progress
** Changed in: postgresql (Juju Charms Collection)
Assignee: (unassigned) = Stuart Bishop (stub)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Also affects: postgresql (Juju Charms Collection)
Importance: Undecided
Status: New
** Changed in: postgresql (Juju Charms Collection)
Status: New = Triaged
** Changed in: postgresql (Juju Charms Collection)
Importance: Undecided = High
--
You received this bug
I still have this on Ubuntu 14.04 LTS, kernel 3.13.0-24 generic (32
bit).
Releases where this audio work are beyond EOL by now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
28 matches
Mail list logo
