My issue is compounded by the fact that Ubuntu registers no network
interfaces in Ubuntu on vmwareplayer in NAT mode and it sees a
connection but can't connect in bridged mode. As a result I can't apply
updates on install or upgrade my NVIDIA drivers which may help resolve
the issue. I will try
@Timo, I have tried the latest daily with the new Mesa and there is no
change to behaviour it is still non-functional with 3D acceleration
enabled.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
The Software and Update app incorrectly shows ESM support continuing
until 31/12/99 when the machine is Pro attached. The date for basic
support displays correctly when Pro is not enabled.
Worth noting that this page does not refresh when a Pro token is
detached and needs a
On UbuntuCore the default user added by console-conf is automatically
granted passwordless sudo.
the /etc/group file is on a readonly filesystem and contains the sudo
group, this usually prevents you from accidentially adding extra sudo
users (UbuntuCore exclusively uses /var/lib/extrausers for
Both the Apparmor MR on GitLab to support 'nostrictatime', 'lazytime',
and 'nolazytime'
(https://gitlab.com/apparmor/apparmor/-/merge_requests/1005), and the
snapd PR to support 'nofail' and other userspace and fs-specific mount
options (https://github.com/snapcore/snapd/pull/12712) have been
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2012563
Title:
unsupported mount options: 'nofail',
Hi Robert,
I submitted a PR to allow userspace and filesystem-specific mount
options to be validated directly by snapd, since apparmor should only
ever see kernel mount options. It should support `nofail` and the
functionfs mount options as well as options for most other common
filesystems.
I submitted an issue and accompanying PR for this bug on the apparmor
GitLab repository.
Issue: https://gitlab.com/apparmor/apparmor/-/issues/312
PR: https://gitlab.com/apparmor/apparmor/-/merge_requests/1004
** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #312
Attached is a patch which adds support for 'nostrictatime', 'lazytime',
and 'nolazytime'.
Since 'strictatime' already existed and documentation suggested
'nostrictatime' should already be included as well, 'nostrictatime' is a
simple inclusion.
The kernel supports `MS_LAZYTIME` as `(1 << 25)`,
The bitflags for the other mount options are defined in
`include/uapi/linux/mount.h` of the Linux source tree, and there is no
such definitions for 'nofail', so I don't think adding kernel mappings
of this form (e.g. MS_RDONLY) is the solution. These options are
supported by 'mount' using
Public bug reported:
The following mount options are unsupported: 'nofail', 'nostrictatime',
'lazytime', and 'nolazytime'.
Other mount options have mappings from options to bitflags in
`parser/mount.cc`, and the bitflags themselves are defined in
`parser/mount.h`. Should the aforementioned mount
*** This bug is a duplicate of bug 2006744 ***
https://bugs.launchpad.net/bugs/2006744
Dan, that sounds good, I didn't realize it was marked as private. I made
it public now. Thanks!
** Information type changed from Private to Public
--
You received this bug notification because you are a
Public bug reported:
zmq supports vsock for communication between virtual machines and hosts.
For example, to listen on a vsock port you can specify vmci://*: for
the socket. This feature is enabled with the option '--with-vmci' for
the configure script. I have made that change in the
@Damon Does not sound like a pleasant experience.
The issue is probably related to Wayland and Nvidia drivers then.
Doesn't look to good for Ubuntu if prospect users try the live system
and one of the first experiences that they make is a corrupted screen.
--
You received this bug notification
Public bug reported:
I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the
usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
appears. When hitting "Try Ubuntu", the screen turns black for a couple
of seconds and then re-appears in yellow and brown colors, feels
This is affecting Ubuntu 20.04 with sssd integration to AD. I am seeing
massive lastlog files because of what appears to be the use of very high
UID's being assigned to AD users when they log in.
-rw-rw-r-- 1 root utmp88943346292 Jan 6 16:50
lastlog
Oliver
--
You received
will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.8.18-050818-generic x86_64
NonfreeKernelModules
ise ends (rather a little
before :-)).
I'll gladly contribute any information that could be useful and I will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelea
)
- and that definitely is where my expertise ends (rather a little
before :-)).
I'll gladly contribute any information that could be useful and I will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
)
- and that definitely is where my expertise ends (rather a little
before :-)).
I'll gladly contribute any information that could be useful and I will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
any information that could be useful and I will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.8.18-050818-generic x86_64
NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia
ApportVersion: 2.20.11
to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.8.18-050818-generic x86_64
NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia
ApportVersion
be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.8.18-050818-generic x86_64
NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia
ApportVersio
expertise ends (rather a little
before :-)).
I'll gladly contribute any information that could be useful and I will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease
:-)).
I'll gladly contribute any information that could be useful and I will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25
for people not using the official announcement channels, here is a link
to the related public announcement (with details on the reasoning and a
place for discussion and feedback):
https://discourse.ubuntu.com/t/feature-freeze-exception-seeding-the-
official-firefox-snap-in-ubuntu-desktop/24210
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.4
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date:
Public bug reported:
I have updated to usb-creator-kde using aptitude. During the update,
this warning is displayed:
/usr/lib/python3/dist-packages/usbcreator/frontends/kde/frontend.py:140:
SyntaxWarning: "is not" with a literal. Did you mean "!="?
if self.__img is not '':
(I don't know
know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
(rather a little
before :-)).
I'll gladly contribute any information that could be useful and I will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 20.04
It seems this has been addressed and fixed in kernel 5.8 by adding quirk
handling to report a fixed sample rate of 48 kHz, please cmp.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412
--
You received this bug notification because you are a
know.
Cheers,
Oliver
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.8.18-050818-generic x86_64
NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
This has been reported on the ansible module side as well as it impacts
the ability to configure ufw on Ubuntu 20.04.02 LTS servers. ufw is
essentially unusable because of this bug.
https://github.com/ansible-collections/community.general/issues/2336
@kosharskiy this is completely unrelated to this installer bug (which is
about configuring packages prior to/during install time), you should
open a new bug for your issue ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
there are various forum and askubuntu threads about this issue already
as well:
https://forum.snapcraft.io/t/ui-glitch-after-recent-update/15133
https://forum.snapcraft.io/t/some-snaps-app-have-weird-looking-window-
control-and-fonts/17859
https://askubuntu.com/q/1206868/66509
> a) On theory it compromises the throughput (the whole CPU time that will take
> for a
> process to finish will be longer) for better responsiveness, even under high
> load. So
> mouse clicks/UI events should be handled faster and say, when decompressing
> large files
> or other CPU load by
oh, and i missed, d) there is a mis-configured postfix install running
on that device too ... since it is not configured and crashing in a loop
during boot anyway, i'd recomend removing postfix ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
okay, thats quite different ...
a) you run the lowlatency kernel for whatever reason ... this is clearly
the worst choice you can pick for already slow hardware (low latency ->
do one thing as fast as you can ... ignore other things ... i.e. you
trade overall system performance for the ability to
erm ...
this is an atom/celeron laptop with 4GB that starts BOINC as a system
service during boot ?
there seems to also be a lot of broken gnome-shell extensions installed
on this system that error out during startup ...
there is ifupdown installed which is probably involved with the network
please note that the stable UbuntuCore18 images regressed due to this:
https://github.com/snapcore/core18/issues/170
** Bug watch added: github.com/snapcore/core18/issues #170
https://github.com/snapcore/core18/issues/170
--
You received this bug notification because you are a member of
for reference:
https://forum.snapcraft.io/t/parallel-installs/7679
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1895382
Title:
Ability to install 2 or more versions at
Public bug reported:
An unattended security upgrade (package dovecot-core) failed,
interrupting mailbox service. The cause was ucf replacing a custom
configuration file which had been diverted (using dpkg-divert) by a
custom configuration package.
Excerpt from /var/log/apt/term.log:
---
Setting
** Bug watch added: github.com/systemd/systemd/issues #15316
https://github.com/systemd/systemd/issues/15316
** Also affects: systemd via
https://github.com/systemd/systemd/issues/15316
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1619420 ***
https://bugs.launchpad.net/bugs/1619420
first of all the bug is a duplicate, secondly you can not install deb
packages on Ubuntu Core, snap packages (of which Ubuntu Core is built)
do use /etc/os-release. Additionally Ubuntu Core only ships the
theer we go ... thanks a lot dimitri, i opened
https://github.com/snapcore/core18/issues/157
** Bug watch added: github.com/snapcore/core18/issues #157
https://github.com/snapcore/core18/issues/157
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
i dont know where you guys track core bugs either since foundations took
over the responsibility Ubuntu Core with core 18...
i can not reproduce it on classic anywhere but on each core18 image i
have running at my house ...
the customer that initially reported it uses core18, so it is important
any fix should be SRUed into the respective LTS releases for Ubuntu
Core, added tasks for them
--
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/1885901
Title:
timedatectl
Public bug reported:
when calling timedatectl in Ubuntu Core 18 the tool reports the status of the
systemd-timesyncd.service ...
sadly it does report it wrongly (the tool reports it inactive while the
service is actually running):
ogra@pi4:~$ timedatectl
Local time: Wed
it is a hard requirement of the SRU process that fixes land in the devel
release and then propagate backwards through all other releases ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
well, rsyslog is completely gone from core after UC16 ... how would you
test that in UC18 or UC20 to verify SRUs ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1875493
WTF. I was uninstalling the ubuntu-mate-desktop task with tasksel (while
ubuntu-desktop was still checked in the list), and it removed basically
everything. Afterwards all tasks in the tasksel list were unchecked.
This is definitely not the expected behavior: when I uncheck a specific
task, I
the requirement for policykit (and dropping of gksu/gksudo) came with
the switch to gnome upstream, its a hard requirement for the desktop
nowadays.
while the default here might be wrong (and should be reviewed by someone
from the desktop team), this is definitely not a snapd related bug. i
added
policyKit does not involve sudo in any way, it uses systemd-logind from
the session to elevate privileges. if you are marked as admin in the
policyKit setup you will indeed be able to do admin things no matter
what is written in sudoers ;)
--
You received this bug notification because you are a
Hello,
We have done some further investigation.
During device pairing bluez is crashing.
>From debugging I can see the 2 hog services with the correct attributes, then
>one of the 2 hog services is reaching ref_count 0, hence it is getting freed,
>but on the next read bluez is trying to use a
This problem has not occurred on my machine for some time now. So I
think this bug can be closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netbase in Ubuntu.
https://bugs.launchpad.net/bugs/1826939
Title:
Network
Public bug reported:
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the
kernel. on a kernel level this works just fine and the system reboots
immediately ...
when in the initramfs during boot and a panic
targeting to xenial and bionic since we need this SRUed for Ubuntu Core
installs.
** Description changed:
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the
- kernel. on a kernel level this works just fine
This happens on the grounds that the PC rests with the speakers handicapped and
the earphones controlled on. To keep this from happening separate the earphones
before putting the machine to rest.
https://www.epsonprintersupport247.com/fix-epson-printer-offline/
--
You received this bug
Public bug reported:
After suspending my computer to standby and then waking it up again,
networking restarts unreliably: Sometimes it restarts fine, sometimes it
takes a few seconds to restart, and sometimes it takes more than a
minute (I didn't wait longer).
When the network wakeup is not
I have the same issue, but I just double checked, it works on my
machine with bionic, the problem only arises on my cosmic machine.
iPad version: 12.1.4
works with 18.04.01 LTS
doesn't work on 18.10
If anyone has any ideas for me to try, please let me know, I'm happy to
try.
--
You received
looks now working :(
openssl s_client -connect letsencrypt.org:443
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1808493
Title:
Let's Encrypt CA Root
Public bug reported:
Please add the Chain of trust for the Let's Encrypt CA to the ubuntu ca-
certificates
https://letsencrypt.org/certificates/
we have to add them always manually and i think it's time to accept,
that let's encrypt is now one of the bigger CA.
Missing in releases 16.04 LTS
** Description changed:
Ubuntu 16.04.5 LTS
systemd 229-4ubuntu21.9
syslog file http://locoserver.net:8080/inline/14ItB1/syslog
I had to restart one of my server. This one is ovz and the only ubuntu
16 left. All my other servers are ubuntu 18 already.
So what happened?
I
Public bug reported:
Ubuntu 16.04.5 LTS
systemd 229-4ubuntu21.9
syslog file http://locoserver.net:8080/inline/14ItB1/syslog
I had to restart one of my server. This one is ovz and the only ubuntu
16 left. All my other servers are ubuntu 18 already.
So what happened?
I restarted my server and I
Public bug reported:
# Reproduction Instructions
1. Lock screen by pressing WIN+L
2. Relogin to Ubuntu Desktop
# Current result
The application dock is invisible.
# Expected result
The application dock is visible.
HINT: I have 3 screens connected and moved the dock to the second screen.
> Now that Ubuntu has given up on Wayland by default
Ubuntu has not given up on Wayland by default but delayed it by one more
LTS (particulary because of bugs like this one).
Wayland by default is still the plan for the next LTS (and the interim
releases between 18.04 and 20.04). The incentive
feel free (i set the snappy task to fix-released too)
** Changed in: snappy
Status: Confirmed => Fix Released
--
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/1619258
well, my subtle hint would point to simply add it to /etc/environment
here, which would globally cover for everything, would allow us to drop
the profile.d snippet in ubuntu images/installs and to my knowledge
would even be used by systemd (or am i wrong here ?) ...
(and i think it would even
i meant to say above is that it would be nice to find a way that covers
all use-cases with one code path (sorry, just noticed what i wrote wasnt
clear in that regard)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
snapd ships a snippet in /etc/profile.d that sets the PATH to /snap/bin
and should theoretically work for all login shells (except for zsh which
doesn't respect the profile.d standard) ... bug 1640514 and bug 1659719
are related.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1619420 ***
https://bugs.launchpad.net/bugs/1619420
** This bug is no longer a duplicate of bug 1662357
Can't use lsb_release on Ubuntu Core 16
** This bug has been marked a duplicate of bug 1619420
snappy removal of dpkg-query breaks lsb_release --all
*** This bug is a duplicate of bug 1619420 ***
https://bugs.launchpad.net/bugs/1619420
** Changed in: lsb
Status: Confirmed => Invalid
** Changed in: lsb (Ubuntu)
Status: Confirmed => Invalid
** This bug has been marked a duplicate of bug 1619420
snappy removal of
In my case the underlying host is an ubuntu 16.04. I don't know, if that
can cause trouble?
--
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/1760848
Title:
lxc-create can't
This security fix seems to have caused some fallout ... see bug 1733557
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1677924
Title:
Local privilege escalation via guest
I have verified the xenial one with a locally created core and kernel
snap now (as mentioned before I can not verify it on artful simply
because there is no Ubuntu Core for this release, using the deb from
proposed on an artful desktop does not show any regressions though)
** Tags removed:
** Description changed:
systemd version the issue has been seen with
- 229
+ 229
- Used distribution
Ubuntu 16.04
- In case of bug report: Expected behaviour you didn't see
- systemd-detect-virt should show help text
+ systemd-detect-virt should show virtual system
Public bug reported:
systemd version the issue has been seen with
229
- Used distribution
Ubuntu 16.04
- In case of bug report: Expected behaviour you didn't see
systemd-detect-virt should show help text
- In case of bug report: Unexpected behaviour you saw
During apt-get upgrade
I rebuild the package without optimizations got some more data. The ASAN
out now matches the gdb one
READ of size 9 at 0x6040001944b8 thread T0
#0 0x14454c2 in __interceptor_strndup
Sorry I didn't think about this before, but I gave the non-ASAN version
of the application a spin with valgrind 3.13 and it doesn't report any
memory errors with it - so it's possible this is either something
valgrind won't catch or a false positive by ASAN.
--
You received this bug notification
Public bug reported:
I am running an application which has a feature which utilizes Qt5. For testing
purposes this application was built with the AddressSanitizer of the official
clang 5.0.1 binariesfor ubuntu 16.04. This was working fine until a few days
ago. It started out with another user
since we dont build ubuntu core images based on the artful archive this
would just be cosmetic ... (but yeah, technically we could also upload
it to artful ... xenial and bionic are the critical ones here though)
--
You received this bug notification because you are a member of Ubuntu
Touch
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Also affects: network-manager-applet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Also happens after adding a Microsoft account. I just upgraded from
16.04 to 17.10. It is a bit annoying but the added Accounts are working
well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
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/1724756
Title:
Updates
** Also affects: klibc (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1692494
Title:
klibc does not support
Setting snappy task to fix committed, core the ships the workaround from
https://github.com/snapcore/core/pull/60
...until systemd grows the correct defaults via an SRU
** Changed in: snappy
Status: New => Fix Committed
** Changed in: snappy
Importance: Undecided => High
** Changed
** Summary changed:
- Networkd fail to set ip address between leases if ip address changes
+ Networkd fail to set ip address between leases if ip address changes on
UbuntuCore
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snappy
Public bug reported:
the description for "upgrade" in the apt manpage says:
New packages will be installed if required to statisfy dependencies, but
existing packages will never be removed.
this should probably rather read "satisfy"
** Affects: apt (Ubuntu)
Importance: Undecided
please note that this rule will also likely be used inside the initrd to
set up the console for encyption key input and there will be no systemd
around ... you probably want to rather handle it conditionally so it is
still available when creating an initrd ...
--
You received this bug
might be that we need it on Ubuntu Core (and server) though ... so
installing the rule at all should probably be conditional ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Note that this bug is about Ubuntu Core (xenial), i dont think we use
systemd-networkd in the rest of xenial (
https://lists.ubuntu.com/archives/ubuntu-devel/2016-January/039066.html
)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@xnox
"As on the 18th systemd migrated that can set Nice in artful yet you
disabled it on the 18th."
our development focus is 16.04 and we do not have release specific
systemd units for the forward ported snapd packages so the comment will
have to stay in until xenial has a fixed systemd ...
this is in snapd since may https://github.com/snapcore/snapd/pull/3270
why did this break all of a sudden ?
--
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/1709536
Title:
The installation of the package libgles1-mesa 17.0.7-0ubuntu0.16.04.2 on
my system worked without any issue!!!
Afterwards the "intel-graphics-update-tool-linux-os-v2.0.2" ran
successfully as well.
Great work! Many, many thanks for your kind support!!!
** Tags removed: verification-needed-xenial
There you are - that is the output of 'apt-cache rdepends libgles1-mesa':
libgles1-mesa
Reverse Depends:
libgles1-mesa-dev
libgles1-mesa-dev
libgles1-mesa-lts-xenial
libgles1-mesa-lts-wily-dbg
libgles1-mesa-lts-wily
libgles1-mesa-lts-vivid-dbg
libgles1-mesa-lts-vivid
Probably I have the same problem - see bug # 1709823. Today evening
I'll try to run 'apt-cache rdepends libgles1-mesa' and paste it here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
For further explanation: I need the package libgles1-mesa, because I
want to update the graphics driver on my HP Elitebook 8440p. For this
purpose, I downloaded the "INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS
V2.0.2" from 01.org, which at least requires libgles1-mesa.
--
You received this bug
Public bug reported:
Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) on Ubuntu 16.04
LTS failed - it needs the package libglapi-mesa
(12.0.6-0buntu0.16.04.1), which does not exist. The current version of
libglapi-mesa is 17.0.7-0ubuntu0.16.04.1 (xenial-updates), which does
not support the
The File "runmbbservice" was completely empty, so i deleted the file
itself and the links to it.
After:
sudo dpkg --configure -a && sudo apt -f install
the "apt-get" command works fine.
But i have no idea where the "runmbbservice"-script comes from.
Google also found only similar cases.
Many
1 - 100 of 430 matches
Mail list logo
