** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
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/2091657
Tested on a pristine UC24 built with a custom `core24` base that uses
noble-proposed instead of noble-updates, and ran the same sequence of
commands (updating locale, rebooting, ensuring it was the same)
$ systemctl --version
systemd 255 (255.4-1ubuntu8.6)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMAC
Thank you Nick!
The core side of things are in this PR:
https://github.com/canonical/core-base/pull/313
--
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/2091657
Title:
syst
As James pointed out that was the root of my issue, after removing the
bind-mount everything worked
--
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/2091657
Title:
systemd-l
Hey!
So tested with a new UC 24 system that includes the systemd from enr0n
ppa and has the following setup
$ systemctl --version
systemd 255 (255.4-1ubuntu8.6~ppa3)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL
+ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
It looks like this has been fixed. I will close it. If the problem
still occurs, please reopen it.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
It looks like this has been fixed upstream. I will close it. If the
problem still occurs, please reopen it.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1021516
This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/673389
Title:
Clicking on huge image locks/hangs machine (co
** Changed in: linux (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1806660
Title:
The sound from the notebook speakers sounds ra
Thank you very much for the updated info. I am taking another look with
all the updated info.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a membe
Hey!
policykit-1/124-2ubuntu1.24.10.2
- Works on Oracular and loads actions from /etc, verified with pkaction
policykit-1/124-2ubuntu1.24.04.2
- Works on Noble and loads actions from /etc as well, verified again with
pkaction
--
You received this bug notification because you are a member of
Public bug reported:
Hey!
I would like to request a SRU of the following upstream PR for Noble.
https://github.com/polkit-org/polkit/pull/499
I have applied this to ubuntu/noble-updates and produced a new patch
that is attached with identical changes. The PR does not apply directly
due to misma
** Description changed:
Hey!
We're using libpam in the Ubuntu Core rootfs for the core24 snap (which
is pam from Noble). We've run into a sitaution where we would like to
move pam.d files into /usr/lib/pam.d instead of /etc/pam.d, and looking
at man pages this should be supported. (I.
Public bug reported:
Hey!
We're using libpam in the Ubuntu Core rootfs for the core24 snap (which
is pam from Noble). We've run into a sitaution where we would like to
move pam.d files into /usr/lib/pam.d instead of /etc/pam.d, and looking
at man pages this should be supported. (I.e it always che
#x27;t git
any issue. This sounds like a config issue, or some option that is set
in the bluetooth stack.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Philip Cox (philcox)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification b
ou are now running
is not playing nicely with the VirtualBox drivers. Can you please un-
install them, and see if the problem still exists? I do not see any
other networking related problems in the kernel log.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Philip Cox (philcox)
Hey!
Sorry for the slow response from the Core team, I can verify this is now
working with passwd in proposed. I was able to add a user with
--extrausers and --groups switches together. It no longer fails on
locking /etc/groups
--
You received this bug notification because you are a member of Ub
This is a userspace utility in the util-linux package, and not a kernel
issue. Removed the kernel from the Affected projects.
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in
Just as an added information, providing the switch `-s
/run/wpa_supplicant` with the network-control interface connected should
work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bu
So I looked into this and the observations made in this post is correct.
It's because the default path of the wpa_cli client socket made is in
/tmp (they use AF_UNIX sockets, and UDP protocol - this means the client
socket must bind a visible place for the server)
/tmp is obviously not visible out
I was able to get something working on my win 11 i9-13900H discrete
RTX2000 laptop.
I used:
mks.enable3d = "TRUE"
mks.enableDX12Renderer = "TRUE"
mks.enableDX11Renderer = "FALSE"
mks.dx12.vendorID = "0x17AA"
and I also had to do:
settings->system->dislay->graphics
entries for both vmware.exe and
Also tried virtualbox this morning on a different win 11 machine with an
nvidia laptop gpu and same thing.
No 3D acceleration is not stable on vmware (crashes after a while)
With 3D acceleration black screens really fast on vmware and virtualbox (which
uses the vmware driver by default)
--
You
Microsoft Windows [Version 10.0.22631.3447]
Processor AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16
Logical Processor(s)
System ModelX570 AORUS PRO WIFI
RTX 2070
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
vmware 17.5 win 11
not fixed with todays iso. mesa is 24.0.5.
Can see gui without enable 3d acceleration, but black screen and have to task
manager kill with 3d acceleration.
rtx 2070
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: software-properties (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Public bug reported:
Press the Print Screen button, select the Record Screen option and then
press capture [1]. The screen recording works as expected however does
not display the mouse cursor making it hard to use the screen capture
for a tutorial without using a third-party capture device.
The
Public bug reported:
[ Impact ]
* It is not possible to upgrade or re-install python-apt using pip from
the git+ssh://git.launchpad.net/ubuntu/+source/python-apt git repo if
already installed and if wheel installed too.
* On initial install it also is assigned version `0.0.0` which is
incorre
Thanks all. Marking as "Won't Fix" and marked MP as Rejected.
** Changed in: ubuntu-meta (Ubuntu Noble)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launc
With only snapd snap preseeded I get boot times very similar to
```
ubuntu@cloudimg:~$ systemd-analyze
Startup finished in 3.757s (kernel) + 12.458s (userspace) = 16.216s
graphical.target reached after 12.061s in userspace.
```
Which shows we are still taking a boot time hit of ~1.5 seconds...
h
> * boot times w/ and w/o preseeded snaps
Without preseeded snaps:
```
ubuntu@cloudimg:~$ systemd-analyze
Startup finished in 3.609s (kernel) + 11.026s (userspace) = 14.636s
graphical.target reached after 10.642s in userspace.
```
With preseeded snapd and core22 snaps:
```
ubuntu@cloudimg:~$ sy
@vorlon
> Also, statically seeding a particular base snap is bad form, as soon
as lxd upgrades its base you lose your performance benefit and have to
play catch-up in a stable release.
yes I don't like this either. Even if we do change it later to core24
then the expectations people have for thei
Thank you for the detail sdeziel
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2051572
Title:
Always preseed core and snapd snap in server seed
Status in ubuntu-meta
> "other cloud cases that have preseeded snaps" (thinking like ec2 or
oracle that have snapped cloud agent
This isn't something we need to worry about as there will be no change
in this case. If any agent snaps are preseeded then so too will a core
snap and snapd snap.
--
You received this bug n
> 15 seconds vs 30 seconds, on a thing that won't affect most cloud
customers
I'll see if I can find the data to back this
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs
If we don't preseed a core snap and snapd it feels like we're failing to
prioritise the performance of snaps on server/cloud.
But if we acknowledge that knowing that we are prioritising boot speed
then that's fine and we can add it to the noble release notes.
--
You received this bug notificatio
Good points
I'll measure boot speed with and without core snap preseeded and add it
here.
time to initialize any snap was my goal but with lxd as an example as it
is such a popular snap.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
hange in the server seed @
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/tree/server#n69
[1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Assignee: Philip Roche (philroche)
Status
This has been released in Noble version 1.529
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Released
** Also affects: ubuntu-meta (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
** Changed in: ubuntu-meta (Ubuntu Noble)
Assignee: (unassigned) =>
Public bug reported:
With LXD 5.20 there is a license change to AGPL and it has been decided
to no longer seed the snap in Ubuntu 24.04 and later and instead seed
the lxd-installer package instead.
This bug is to track the work of making that change in the server seed @
https://git.launchpad.net/
> a) You state that some policy says that no ports other than 22 should
be open, which policy is that? Does it apply only to cloud images, or is
it an Ubuntu policy in general
This policy is detailed @
https://wiki.ubuntu.com/Security/Features#ports
> Default installations of Ubuntu must have no
> a) You state that some policy says that no ports other than 22 should
be open, which policy is that? Does it apply only to cloud images, or is
it an Ubuntu policy in general?
I will try find the referenced policy.
> b) This is in mantic release at the moment, and switching that option
back to "
cloud minimized and non minimized images have now been tested with
6.5.0-9 kernel from -proposed and pass our lxd-start-stop test suite
which was failing and which is the test suite which prompted this whole
thread. +1
--
You received this bug notification because you are a member of Ubuntu
Touch
I have also successfully verified that -proposed amd64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host with older hardware (ThinkPad T460
with 6th gen intel i5 which is the same hardware which we were able to
reproduce the issue on previo
@xnox I have successfully verified that -proposed arm64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host. See
https://people.canonical.com/~philroche/20231003-mantic-minimal-
proposed-kernel/ for cloud-init logs, some debug output and test
I downgraded to 249.11-0ubuntu3.9, 249.11-0ubuntu3.7 Because I know for
a Fact I had no issues with it, My last install was working with
249.11-0ubuntu3.9, you rolled out the update to 249.11-0ubuntu3.10 and
that is when all this started. I simply went back to an older version
after a fresh install
22.04.3LTS -Ubuntu
Downgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7), libudev1:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.7)
Camera any kind, I tried both my NikonD5600 and Olympus OM-D E-M5, which both
work again as they should and did before this mess started.
--
You received this
Tried all your steps, they kept breaking my system more and more. Had to
re-install ubutnu from liveusb, installed synaptic downgraded udev and
locked verison, read markings, reboot, update, upgrade reboot, get my
audio and bluetooth up and working again reboot, everything works, its
your udev upda
PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO. No I have to do a fresh
install. You guys really need to pay better attention to your updates,
this is a system break not an upgrade. Im really not happy, and as I
love ubuntu, and I really appreciate all the hard work you guys all put
into making an
More interesting info, so I just tested digiKam-8.1.0-x86-64.appimage
and it Can talk to my camera, but the Installed digikam package CAN NOT
TALK, but I still can not use gphoto2 to stream my camera, nor can I use
entangle to use my camera tethered. Because they can not talk to the
camera, I under
Dont know if this helps, but here is a complete list of installed
libnova-0.16-0 install
libgpg-error-l10n install
dpkginstall
kerneloops install
libkf5quickaddons5 install
golang-golang-x-term-devinstall
fontconfig:i386
Tried to stream with debug,
gphoto2 --stdout --capture-movie --debug | ffmpeg -i - -vcodec rawvideo
-pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0
0.000107 main(2): ALWAYS INCLUDE THE FOLLOWING LINES
WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000131 main
In order to roll back udev in Synaptic, I get
To Be Removed
libgstreamer-plugins-base1.0-dev
libgudev-1.0-dev
libnm0:i386
libpipewire-0.3-0:i386
libpipewire-0.3-modules:i386
libspa-0.2-modules:i386
libudev-dev
libudev1:i386
pipewire:i386
steam:i386
To be downgraded
libudev1
I cant roll back or lo
I downloaded your rules and used you commands to move it, I rebooted and
same issue, here is the result of gphoto2 --debug
gphoto2 --debug
0.000101 main(2): ALWAYS INCLUDE THE FOLLOWING LINES
WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000114 main
Here is some backtrace of digikam crashing after trying to import photos from
camera,
Application: digiKam (digikam), signal: Segmentation fault
[KCrash Handler]
#4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
#5 0x7f50de2a8603 in __GI___strdup (s=0x0) at ./string/strdu
YES this bug persists after (a) sudo systemctl daemon-reexec, and/or (b)
reboot
--
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/2035406
Title:
udev update has broken ubuntu
Rebooting does nothing, same issue. systemctl daemon-reexec does
nothing, same issue no one can talk to my camera, I tried a different
camera same issue, lsusb cameras show up just fine so usb's are working,
but something happens with that update that caused a roadblock between
usb and other softwa
everything was working before the updating and then I updated "
udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-
timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-
systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubunt
No I am using it for both still photography and for video streaming.
--
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/2035406
Title:
udev update has broken ubuntu's ability
Here is my output of ls -l /dev/video*
ls -l /dev/video*
crw-rw+ 1 root video 81, 0 Sep 13 18:45 /dev/video0
crw-rw+ 1 root video 81, 1 Sep 13 18:45 /dev/video1
crw-rw+ 1 root video 81, 2 Sep 13 18:45 /dev/video2
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
udev update has broken ubuntu's ability to import photos in digikam, gphoto2
can no longer see usb camera, entangle can no longer see camera
after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
Public bug reported:
This is a known issue upstream:
https://github.com/systemd/systemd/issues/28495
and indeed a fix is milestoned for v255:
https://github.com/systemd/systemd/pull/28508
It would be good to see this in the next backports build.
Note: this bug only manifests when the DHCP ser
Looking at the log reveals, that it's libgstreamer1.0-dev that fails to
install, see:
libgstreamer1.0-dev:amd64 (1.20.3-0ubuntu1) wird eingerichtet ...
»Umleitung von /usr/bin/dh_gstscancodecs zu /usr/bin/dh_gstscancodecs-gst0.10
durch libgstreamer1.0-dev« wird entfernt
dpkg-divert: Fehler: Umben
*** This bug is a duplicate of bug 1870514 ***
https://bugs.launchpad.net/bugs/1870514
As a workaround I opted for using a systemd unit file to create a loose
dependency between containerd and dockerd.
Here's how:
As root:
Make the override directory (permission 755)
mkdir /etc/systemd/sys
Public bug reported:
Its causing the computer to freeze frequntly
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-52-generic 5.4.0-52.57
ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Arch
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: philip 1327 F pulseaudio
/dev/snd/pcmC0D0c: philip
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: philip 1327 F pulseaudio
/dev/snd/pcmC0D0c: philip 1327 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 19:55:29 2020
10.10.10[4500]
Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded.
Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip.
Jul 15 11:18:03 pc systemd[1]: Removed slice
system-clean\x2dmount\x2dpoint.slice.
Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.sl
5 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper:
assertion 'node != NULL' failed
Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500]
Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded.
Jul 15 11:18:03 pc systemd[1]: Stopping
Ah, sorry. Yes, if you rebuild the focal package with f56a65f and use
openssl, then connectivity and file transfers work correctly. There does
not appear to be any other changes required. I can't vouch for all the
functionality, of course. The device backup functionality seems popular,
but I don't
So, the new builds are new enough versions but libimobiledevice is still
built against gnutls and so file transfers don't work. If I build my own
library at the 1.3.0 version against openssl and drop it in, then it all
works fine.
The new builds of libplist and libusbmuxd are very helpful as they
Upstream fix for the openssl issue is in: f56a65f in libimobiledevice.
Taking advantage of that requires switching the ubuntu build from using
gnutls to openssl.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevic
https://github.com/libimobiledevice/libimobiledevice/issues/941
** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #941
https://github.com/libimobiledevice/libimobiledevice/issues/941
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
I've upgraded to 20.04 and have checked out the installed versions. For
now, I was able to get it working "just" by upgrading libimobiledevice
to the latest git and building against gnutls (using openssl resulted in
it needing to re-trust every time I plug in because the TLS information
it is savin
Ok, so this is progress. Building against gnutls fixes the trust
pairing, but breaks file transfers. I rebuild the same source with
openssl vs gnutls and that's exactly what I see. With openssl I have to
re-pair every time I plug in but with gnutls, the file transfers don't
work.
The official ubun
e law of diminishing returns is well and truly engaged with it.I was though
rather touched to get your message and humbled that you and your colleagues
were still keeping my original post in mind over 6 years after I wrote. Thank
you for all that attention and thank you once again for the alert.
Brilliant you still pursue this after all this time. My laptop sadly died just
last week, but at 14 years of age and a life that included 2-3 years rough
gaming by an enthusiastic teenager I reckon that's not bad.
For a long time I used a workaround by buying a USB sound card which worked
perfec
I can't test the latest packages fully because I'm running eoan but I
did install the packages from focal and it didn't work, while I'm home-
built binaries from mid october do work, so maybe some regressed? The
usbmuxd upgrade is fine, but libimobiledevice/libusbmuxd is what breaks
it. I can't dis
Also in need of a fix. Trying to run a very simple and popular program
as a service and it's not working due to this.
--
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/1817627
I'll try out the focal builds when I get a chance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1854403
Title:
Need updated libimobiledevice and dependencies to
At the time I filed the bug, I did not notice an updated build in focal
- it was still the same one as in eoan, but perhaps I was just not
paying enough attention. I will try it out. That version is likely to be
new enough to work, although I know there was an update to libusbmuxd
with a version an
Apparently this will never get fixed upstream:
From
https://github.com/systemd/systemd/issues/5859#issuecomment-553377937
poettering: "So we dropped the automatic btrfs loopback file support in
machined a while back. Let's close this hence."
** Bug watch added: github.com/systemd/systemd/issues
marble@bravo:~$ sudo machinectl pull-tar
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz
Enqueued transfer job 1. Press C-c to continue download in background.
Pulling
'https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz'
This effects me on a brand new Ubuntu Server 18.04.3 Install
--
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/1510511
Title:
machinectl pull-raw fails: No space left on devi
Public bug reported:
iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd
to work correctly. Without the updates, the device appears to be
accessible but it's impossible to copy files to the devices.
** Affects: libimobiledevice (Ubuntu)
Importance: Undecided
Stat
guess an update caused issue. I decided to clean install 19.04
but still have issue from the beginning.
Ubuntu 19.04
This is my first bug report
Thanks
Philip
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager 1.16.0-0ubuntu2
ProcVersionSignature: Ubuntu
issue from the beginning.
Ubuntu 19.04
This is my first bug report
Thanks
Philip
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager 1.16.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
** Description changed:
Hello, Devs!
I found since kernel x86_64 Linux 4.15.0-60-generic at Ubuntu 18.04 my
external USB mouse in Samsung ultrabook (NP900X4C) scroll not working!
(with weel at middle mouse button)
With touchpad scroll works fine.
This is cat /proc/bus/input/de
Public bug reported:
Hello, Devs!
I found since kernel x86_64 Linux 4.15.0-60-generic at Ubuntu 18.04 my
external USB mouse in Samsung ultrabook (NP900X4C) scroll not working!
(with weel at middle mouse button)
With touchpad scroll works fine.
This is cat /proc/bus/input/devices info from 3 lat
Public bug reported:
The following bug was reported and fixed in cups 2.2.11.
https://github.com/apple/cups/issues/5484
Without the fix, it is not possible to add or use a number of Canon
printers.
Currently, 19.04 ships with 2.2.10 + some backports, but those backports
do not include the fix f
Public bug reported:
Hello
Following bug is affecting me;
https://github.com/systemd/systemd/issues/5625 and is since fixed in a
newer version of systemd. I was wondering if this is able to be
backported?
I'm using a Ubuntu Core device (using series 16).
(Got redirected here from https://forum.
No way to delete bug, thus I invalidate it
--
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/1743478
Title:
test
Status in xorg package in Ubuntu:
Invalid
Bug description:
1 - 100 of 166 matches
Mail list logo
