Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xdg-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net
(In reply to eggert from comment #24)
> Sure, feel free to file it as a new bug.
Bug 29560.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1940996
Title:
test failure - test
> systemd-udevd[455717]: ethtool: autonegotiation is unset or enabled,
the speed and duplex are not writable.
This is not an error, but an informational message. This just means that
speed and duplex settings are read-only because autonegotiation is
enabled. Please see [1] for more detail.
Can yo
I was also looking for this to fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705437
Title:
Upstream 'column' is newer than bsdmainutils'
Status in util-linux pac
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
This very same bug was filed against Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977360
and fixed by this commit in version 2.1.28+dfsg-4:
https://salsa.debian.org/debian/cyrus-
sasl2/-/commit/510c8609
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/429655
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1988994
Titl
The autopkgtest regressions were resolved by retries.
I have verified this fix on focal using the test plan above:
nr@clean-focal-amd64:~$ apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.18
Candidate: 245.4-4ubuntu3.18
Version table:
*** 245.4-4ubuntu3.18 500
500 http:/
The focal autopkgtest regressions were all resolved by retries.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1978079
Title:
EFI pstore not cleared on boot
Status in sys
The thing is `apport-bug` is just a wrapper script. It doesn't process
any of its arguments and just passes over all positional parameters to
one of `apport-cli`, `apport-gtk` and `apport-kde`. The reason `apport-
bug --help` shows a minimal subset of options is that in this mode only
a handful of
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1988657
Title:
VLAN gets IP address assignment from parent d
** Tags removed: rls-kk-incoming
** Tags added: rls-kk-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1988657
Title:
VLAN gets IP address assignment from parent
Public bug reported:
This started happening after installing vmware
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager 1.36.6-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
App
I am also affected by this bug, un Ubuntu 22.04. Can somebody at least release
a script that fixes it?
Porting it to Jammy would be great!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launc
All autopkgtest regressions resolved with loguru/0.6.0-1ubuntu1 and
mypy/0.942-1ubuntu1.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults i
** Description changed:
[Impact]
With systemd 249.11-0ubuntu3.5 in jammy-proposed, which enables systemd-
repart, the TEST-58-REPART fails on ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/ppc64el/s/systemd/20220906_165335_6dd88@/log.gz.
- This is due to a
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
** Changed in: heimdal (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/667809
Title:
cannot create forwardable kerberos ti
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/429491
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/194
Since it's early and there's no reverse depends indeed, I don't see any
reason not to proceed (especially with autopkgtests present). Please
feel free to upload.
** Changed in: mir (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Tou
Thank you for your bug report, the choice of the city to display for
Ecuador is coming from tzdata, you can see an old similar report on
https://bugzilla.redhat.com/show_bug.cgi?id=131320 for example
** Changed in: systemsettings (Ubuntu)
Status: New => Invalid
** No longer affects: system
if you want to report it upstream the right place would be
https://mm.icann.org/mailman/listinfo/tz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1988667
Title:
Quito isn'
You have been subscribed to a public bug:
On Ubuntu 22.04.1 (and 20.04.x) there is no option available for Quito.
On GNOME
Settings > Date & Time > (A map is displayed)
Type Quito on the search field.
There are no matches.
On KDE
==
System Settings > Regional Settings > Date &
Same here with 22.04 still. The solution by @lyckeleb appears to be
working.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1448657
Title:
isc-dhcp-server: Can't create P
** Summary changed:
- Brightness bar not working properly
+ Brightness bar not working properly on HP EliteBook 8460p
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg i
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1989054
Title:
Brightness bar not working properly on HP EliteBook 8460p
Status in
You have been subscribed to a public bug:
My brightness doesn't change and stays at lowest brightness level till
about 70% of the slider, after that the brightness starts increasing
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.4
Hi,
I had the same problem.
First you can check if your file is "immutable" via:
#> lsattr /etc/passwd
i /etc/passwd
If is not immutable you dont have any reason for not edit via sudo, so the
problem can be, like my case, the antivirus.
I kill all mcafee process multiple time, every 2
could you clean /var/crash, trigger the issue again and resubmit the
crash? the bot failing to recover debug information on the current
report
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://
Please describe the problem you would like to report in more detail. And
if you have multiple problems to report then please ensure each is
logged as a separate bug.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notif
51 matches
Mail list logo
