[Bug 1962718] Re: Firefox snap crashes on every upgrade
While the problem might be in snapd, Firefox is still very much impacted, when it comes to the decision to ship 22.04 LTS without a deb version of Firefox to fall back to. In my experience, this is just one of many ways the experience with the snap version of Firefox is not on par with the traditional package time - yet. Lots of serious problems exist, that have still not been sorted out since the beginning of the 21.10 lifecycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962718 Title: Firefox snap crashes on every upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1962718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963697] Re: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" due to python changes
Everyone posting 'installation failure' cases, please open separate bugs. The underlying issue that *this* bug was referring to is fixed, and the new failures are due to other problems, so please open different bugs. ** Summary changed: - Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" + Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" due to python changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" due to python changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966476] [NEW] Netplan does not provide "key" parameter to GRE tunnel configuration via systemd-networkd
Public bug reported:
The following example should configure a GRE tunnel between 172.16.4.2
and 172.16.1.2, with key 33490175. The effect should be like manually
configured with: sudo ip tunnel add test1 mode gre local 172.16.4.2
remote 172.16.1.2 key 33490175.
However, the following Netplan configuration fails under Ubuntu 22.04
(latest development version, March 25, 2022):
network:
version: 2
renderer: networkd
tunnels:
gre1-255-255:
mode: gre
ttl: 255
local: 172.16.4.2
remote: 172.16.1.2
key: 33490175
addresses:
- 172.20.82.94/30
Result of "sudo netplan generate": Error in network definition:
gre1-255-255: 'input-key' is not required for this tunnel type
Note: There should be no input and output keys. There is just one single
key!
Trying to change the configuration:
keys:
input: 33490175
# key: 33490175
Result of "sudo netplan generate": Error in network definition:
gre1-255-255: 'input-key' is not required for this tunnel type
Some investigation into the sources of Netplan (src/validation.c ->
https://github.com/canonical/netplan/blob/main/src/validation.c):
static gboolean
validate_tunnel_backend_rules(NetplanNetDefinition* nd, yaml_node_t* node,
GError** error)
{
/* Backend-specific validation rules for tunnels */
switch (nd->backend) {
case NETPLAN_BACKEND_NETWORKD:
switch (nd->tunnel.mode) {
case NETPLAN_TUNNEL_MODE_VTI:
case NETPLAN_TUNNEL_MODE_VTI6:
case NETPLAN_TUNNEL_MODE_WIREGUARD:
break;
/* TODO: Remove this exception and fix ISATAP handling with the
* networkd backend.
* systemd-networkd has grown ISATAP support in 918049a.
*/
case NETPLAN_TUNNEL_MODE_ISATAP:
return yaml_error(node, error,
"%s: %s tunnel mode is not supported by
networkd",
nd->id,
g_ascii_strup(tunnel_mode_to_string(nd->tunnel.mode), -1));
break;
default:
if (nd->tunnel.input_key)
return yaml_error(node, error, "%s: 'input-key' is not
required for this tunnel type", nd->id);
if (nd->tunnel.output_key)
return yaml_error(node, error, "%s: 'output-key' is not
required for this tunnel type", nd->id);
break;
}
break;
It seems that the cases NETPLAN_TUNNEL_MODE_GRE and
NETPLAN_TUNNEL_MODE_IP6GRE are missing for systemd-networkd. According
to https://github.com/systemd/systemd/issues/12144, systemd-networkd
should support configuration with keys since ca. 2 years.
** Affects: netplan
Importance: Undecided
Status: New
** Affects: systemd
Importance: Unknown
Status: Unknown
** Affects: ubuntu
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #12144
https://github.com/systemd/systemd/issues/12144
** Also affects: systemd via
https://github.com/systemd/systemd/issues/12144
Importance: Unknown
Status: Unknown
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966476
Title:
Netplan does not provide "key" parameter to GRE tunnel configuration
via systemd-networkd
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1966476/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966372] [NEW] kubuntu 22.04 installer crash
Public bug reported: I am trying to install a VM (vmware workstation) using kubuntu 22.04 (20220324.3). But the installer crashes all the time. Traceback (most recent call last): File "/usr/lib/ubiquity/bin/ubiquity", line 668, in main(oem_config) File "/usr/lib/ubiquity/bin/ubiquity", line 652, in main install(args[0], query=options.query) File "/usr/lib/ubiquity/bin/ubiquity", line 268, in install wizard = ui.Wizard(distro) File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 246, in __init__ mod.ui = mod.ui_class(mod.controller) File "/usr/lib/ubiquity/plugins/ubi-wireless.py", line 214, in __init__ self._setup_page() File "/usr/lib/ubiquity/plugins/ubi-wireless.py", line 220, in _setup_page self.nmwidget = nmwidgets.NetworkManagerWidget() File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 367, in __init__ self.view = NetworkManagerTreeView(self._on_state_changed) File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 224, in __init__ model = QtNetworkStore(self) File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 110, in __init__ self._init_icons() File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 208, in _init_icons secure_pix = secure_icon.pixmap(ICON_SIZE / 2, ICON_SIZE / 2) TypeError: arguments did not match any overloaded call: pixmap(self, QSize, mode: QIcon.Mode = QIcon.Normal, state: QIcon.State = QIcon.Off): argument 1 has unexpected type 'float' pixmap(self, int, int, mode: QIcon.Mode = QIcon.Normal, state: QIcon.State = QIcon.Off): argument 1 has unexpected type 'float' pixmap(self, int, mode: QIcon.Mode = QIcon.Normal, state: QIcon.State = QIcon.Off): argument 1 has unexpected type 'float' pixmap(self, QWindow, QSize, mode: QIcon.Mode = QIcon.Normal, state: QIcon.State = QIcon.Off): argument 1 has unexpected type 'float' ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: KDE Date: Fri Mar 25 04:38:27 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220323) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ubiquity-22.04.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966372 Title: kubuntu 22.04 installer crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1966372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1965676] [NEW] virt-manager looses connection to virtualization hosts at moderate loads
Thomas Schweikle schrieb am Sonntag 20 März 2022 14:22:09 (+01:00): > Public bug reported: > > virt-manager looses connection to virtualization hosts on desktop systems at > low to moderate loads. For dedicated virtualization hosts at moderate hosts. > If the load persists it is difficult to reconnect. > If the load drops it is in all cases possible to reconnect to the running > systems and virtual systems on them. > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: virt-manager 1:3.2.0-3 > ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 > Uname: Linux 5.13.0-37-generic x86_64 > ApportVersion: 2.20.11-0ubuntu71 > Architecture: amd64 > CasperMD5CheckResult: unknown > Date: Sun Mar 20 14:15:49 2022 > InstallationDate: Installed on 2011-10-19 (3804 days ago) > InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) > PackageArchitecture: all > SourcePackage: virt-manager > UpgradeStatus: Upgraded to impish on 2019-04-27 (1057 days ago) > > ** Affects: virt-manager (Ubuntu) > Importance: Undecided > Status: New > > > ** Tags: amd64 apport-bug impish third-party-packages > -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com herunter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965676 Title: virt-manager looses connection to virtualization hosts at moderate loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1965676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831220] Re: Add hexchat by default on all ubuntu flavours
** Changed in: lubuntu-meta (Ubuntu) Status: Opinion => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831220 Title: Add hexchat by default on all ubuntu flavours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hexchat/+bug/1831220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831220] Re: Add hexchat by default on all ubuntu flavours
Like Studio, Lubuntu ships quassel. We have no intention on the Lubuntu Team to ship hexchat instead at this time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831220 Title: Add hexchat by default on all ubuntu flavours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hexchat/+bug/1831220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831220] Re: Add hexchat by default on all ubuntu flavours
** Changed in: lubuntu-meta (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831220 Title: Add hexchat by default on all ubuntu flavours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hexchat/+bug/1831220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965800] Re: debhelper in focal-backports not usable for i386 package building (missing dependency)
archive admins dont think i386ing the RPM source is a good idea based on my brief discussiom in #ubuntu-release debugedit has splitsource in later versions, perhaps a split-source is needed here. However I would suggest we defer to archive admins for best approach here -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1965800 Title: debhelper in focal-backports not usable for i386 package building (missing dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 1965800] Re: debhelper in focal-backports not usable for i386 package building (missing dependency)
archive admins dont think i386ing the RPM source is a good idea based on my brief discussiom in #ubuntu-release debugedit has splitsource in later versions, perhaps a split-source is needed here. However I would suggest we defer to archive admins for best approach here -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965800 Title: debhelper in focal-backports not usable for i386 package building (missing dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1964400] Re: host crashes with SIGABRT in isc_assertion_failed()
Hi Sergio,
I will test it as soon as possible, right now I am travelling.
Cheers
TB
El 21 de marzo de 2022 20:05:58 ART, Sergio Durigan Junior
<1964...@bugs.launchpad.net> escribió:
>Hello Thomas,
>
>I still cannot reproduce this issue, so I would like to know if you
>could test the bind9 package from the following PPA and let me know if
>it fixes your problem:
>
>https://launchpad.net/~sergiodj/+archive/ubuntu/bind9-bugfix
>
>It contains the backported patches from the upstream Merge Request
>mentioned above.
>
>Thanks in advance.
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1964400
>
>Title:
> host crashes with SIGABRT in isc_assertion_failed()
>
>Status in bind9 package in Ubuntu:
> Triaged
>Status in bind9 package in Debian:
> Confirmed
>
>Bug description:
> LP: #1964264 reported `host` intermittent crashes when performing
> numeric lookups.
>
> I could reproduce the issue by running the command below a few times
> in a new jammy installation. I was also able to reproduce the issue in
> Debian.
>
> Since LP: #1964264 is private and contains a user's core dump. I am
> filing a new bug report so we can publicly address the issue.
>
> # host -v 192.108.254.91
> Trying "91.254.108.192.in-addr.arpa"
> netmgr/netmgr.c:1731: REQUIREhandle) != ((void *)0) && ((const
> isc__magic_t *)(handle))->magic == ((('N') << 24 | ('M') << 16 | ('H') << 8 |
> ('D' && __extension__ ({ __auto_type __atomic_load_ptr =
> (&(handle)->references); __typeof__ ((void)0, *__atomic_load_ptr)
> __atomic_load_tmp; __atomic_load (__atomic_load_ptr, &__atomic_load_tmp,
> (5)); __atomic_load_tmp; }) > 0)) failed, back trace
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(+0x32953)[0x7fbb5b941953]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(isc_assertion_failed+0x10)[0x7fbb5b940e40]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(isc__nmhandle_attach+0x67)[0x7fbb5b92a7e7]
> host(+0xea22)[0x55e9ea129a22]
> host(+0xee85)[0x55e9ea129e85]
> host(+0x117c0)[0x55e9ea12c7c0]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(isc__nm_async_readcb+0xb1)[0x7fbb5b92fff1]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(isc__nm_readcb+0x9b)[0x7fbb5b93012b]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(+0x2f980)[0x7fbb5b93e980]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(isc__nm_udp_read_cb+0x4a)[0x7fbb5b93eb1a]
> /lib/x86_64-linux-gnu/libuv.so.1(+0x23e6b)[0x7fbb5b457e6b]
> /lib/x86_64-linux-gnu/libuv.so.1(+0x2511e)[0x7fbb5b45911e]
> /lib/x86_64-linux-gnu/libuv.so.1(uv_run+0x678)[0x7fbb5b442c88]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(+0x2622e)[0x7fbb5b93522e]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2ubuntu2-Ubuntu.so(isc__trampoline_run+0x1a)[0x7fbb5b96822a]
> /lib/x86_64-linux-gnu/libc.so.6(+0x98b43)[0x7fbb5b4feb43]
> /lib/x86_64-linux-gnu/libc.so.6(+0x12ab80)[0x7fbb5b590b80]
> Aborted (core dumped)
>
> Same in Debian unstable with bind 9.18.0-2:
>
> # host -v 192.108.254.91
> Trying "91.254.108.192.in-addr.arpa"
> Host 91.254.108.192.in-addr.arpa not found: 2(SERVFAIL)
> Received 45 bytes from 10.46.19.1#53 in 912 ms
> Trying "91.254.108.192.in-addr.arpa"
> Host 91.254.108.192.in-addr.arpa not found: 2(SERVFAIL)
> Received 45 bytes from 10.46.19.1#53 in 804 ms
> Trying "91.254.108.192.in-addr.arpa"
> netmgr/netmgr.c:1731: REQUIREhandle) != ((void *)0) && ((const
> isc__magic_t *)(handle))->magic == ((('N') << 24 | ('M') << 16 | ('H') << 8 |
> ('D' && __extension__ ({ __auto_type __atomic_load_ptr =
> (&(handle)->references); __typeof__ ((void)0, *__atomic_load_ptr)
> __atomic_load_tmp; __atomic_load (__atomic_load_ptr, &__atomic_load_tmp,
> (5)); __atomic_load_tmp; }) > 0)) failed, back trace
> /lib/x86_64-linux-gnu/libisc-9.18.0-2-Debian.so(+0x358df)[0x7fce568e68df]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2-Debian.so(isc_assertion_failed+0xa)[0x7fce568e683a]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2-Debian.so(isc__nmhandle_attach+0x63)[0x7fce568d0bd3]
> host(+0xe39a)[0x559b350c939a]
> host(+0xf295)[0x559b350ca295]
> host(+0x1173b)[0x559b350cc73b]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2-Debian.so(isc__nm_async_readcb+0xad)[0x7fce568d408d]
>
> /lib/x86_64-linux-gnu/libisc-9.18.0-2-Debian.so(isc__nm_readcb+0x97)[0x7fce568d41b7]
> /lib/x86_64-linux-gnu/libisc-9.18.0-2-Debian.so(+0x31098)[0x7fce568e2098]
>
> /lib/x86_64-linux
[Bug 1965141] Re: openssl: package the new bugfix release 3.0.2
[ubuntu/jammy-proposed] openssl 3.0.2-0ubuntu1 (Accepted) Uploaded to proposed, it has to go through the usual process of passing autopkgtests and such. It shouldn't need any additional package rebuilds because of no ABI changes but expect autopkgtests to run hot a while ** Changed in: openssl (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965141 Title: openssl: package the new bugfix release 3.0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1965141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965773] [NEW] fatal error grub-install in /dev/sda
Public bug reported: Fresh install from bootable usb fails with ubuntu 21.10 regardless of how I setup the partitions in the "something else" section of install process. Expected install to work. Install fails every time at the final stage. ProblemType: Bug DistroRelease: Ubuntu 21.10 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 23:33:41 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity acpi=off --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965773 Title: fatal error grub-install in /dev/sda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1965773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965141] Re: openssl: package the new bugfix release 3.0.2
I've got some extra cycles later today, so I'll happily help the Security team out and get this uploaded later today (Eastern US time for clarity sake when I say "later today") ** Changed in: openssl (Ubuntu) Assignee: (unassigned) => Thomas Ward (teward) ** Changed in: openssl (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965141 Title: openssl: package the new bugfix release 3.0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1965141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
Then this should be trivial to backport, if you need it backported waveform and you don't want to handle the actual backport uploads, I'll take this on, I have some spare cycles today this afternoon. -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
Then this should be trivial to backport, if you need it backported waveform and you don't want to handle the actual backport uploads, I'll take this on, I have some spare cycles today this afternoon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal
waveform: Paride: given this bug, wouldn't this be more suited for full SRU and rebuilds? I'm wondering whether this is truly a backportable case because this requires rebuild of all affected packages, and if anyone builds with debhelper in backports (which is NOT available in standard build envs I believe easily) that will lead to the upgrade breakage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal
waveform: Paride: given this bug, wouldn't this be more suited for full SRU and rebuilds? I'm wondering whether this is truly a backportable case because this requires rebuild of all affected packages, and if anyone builds with debhelper in backports (which is NOT available in standard build envs I believe easily) that will lead to the upgrade breakage. -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal
Whoops looks like we had some collission in terms of assignments. Reassigning to waveform. Once this is looked at and looks OK at the Canonical level, then the Backports Team will take over backporting this. Keep in mind that since the original Backports process is mostly scrapped, the Backports Team does have primary jurisdiction for these packages in the backports pocket under the new process under "Special Cases". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal
Whoops looks like we had some collission in terms of assignments. Reassigning to waveform. Once this is looked at and looks OK at the Canonical level, then the Backports Team will take over backporting this. Keep in mind that since the original Backports process is mostly scrapped, the Backports Team does have primary jurisdiction for these packages in the backports pocket under the new process under "Special Cases". -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: Increasing user base of Ubuntu desktop.
On 3/21/22 09:21, Amit wrote: On Mon, Mar 21, 2022, 6:36 PM Joel Rees wrote: On Mon, Mar 21, 2022 at 11:55 AM Amit wrote: > >[...] > > There is no menu in the default Ubuntu desktop GUI. Menu? I suppose it is not technically a menu, but there is that vertical task-bar-like thing at the left of the screen, and at the bottom of that is a pinpad thingy that brings up screens full of whatever applications are installed. Unless you remove it, there's a suitcase in the task-bar-like thing that allows you to install more. Applications menu have categories (sub-menus) also like internet, system, office, etc. which makes it much easier to find an application. Which is why **variants of Ubuntu as flavors** for different DEs, etc. exist. Bashing the 'vanilla Ubuntu' on that point alone is not going to help 'improve market share'. Take Kubuntu Focus, a group that is trying to drive getting Kubuntu used on to-market systems. Those individuals are bypassing the "Ubuntu is missing some of these features and pretty stuff" to push KDE and Kubuntu onto to-market systems. When discussing 'market share' and 'user base' you have to expand "Ubuntu Desktop" to be "All Official Flavors of Ubuntu" because with the exception of Server they all have different DEs that meet the criterion you're stating. Amit Thomas -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: updated charter and policies wiki pages
Looks good to me. Thomas On 3/21/22 08:55, Mattia Rizzolo wrote: (thanks for the prod on IRC) On Thu, Mar 10, 2022 at 04:33:05PM -0500, Dan Streetman wrote: so, if i'm being totally pedantic, the exact version of the charter and policies is: https://wiki.ubuntu.com/UbuntuBackports/Charter?action=recall=5 https://wiki.ubuntu.com/UbuntuBackports/Policies?action=recall=6 let me know if either of you have any comments or concerns, otherwise if the charter looks ok to you, we can send it up to the TB sometime next week. I'm good with those 2 versions, thank you. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 1965688] Re: package nginx-core 1.18.0-6ubuntu14 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
Not a bug, you just have bad config. From your logs: > Mar 20 13:32:34 spark nginx[68287]: nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/embracehealth.io:209 So you need to figure out where else you've defined default_server and remove it from the other one. Or remove it from the embracehealth.io domain config. ** Changed in: nginx (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965688 Title: package nginx-core 1.18.0-6ubuntu14 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1965688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Increasing user base of Ubuntu desktop.
s post-install and unable to get downloads (hint: the laptops / mobile computing markets nowadays **generally do not ship systems with Ethernet anymore**, leaving "Connect your cable for Internet to get drivers" more or less the dinosaur). When you visit Ask Ubuntu and look at the most active posts, you see a huge portion of them are nVidia, AMD, or networking driver problems. The drivers issue there is the key problem, solving the problems is not as straightforward as downloading the updated drivers via Windows Update which needs no user intervention other than connecting to a network connection, and because of the 'driver problems' and 'hardware compatibility' (which i'll give you recent use case problems about!) issues, it's deemed that "Ubuntu is too hard for the average use case" by the broader world at large. And then people expand that to be "Linux" because they don't know the differences between systems / environments. I mentioned 'hardware compatibility'. At my FT job at the beginning of the COVID pandemic, we needed to come up with a way to keep systems secure so intel analysts at my job could access Corporate resources *and* non-corporate resources in a secure way. We're a Windows house with session hosts typically, but we have Linux environments for research systems. We have a mix of Dell and HP systems that are mobile systems / laptops at this time. We rolled a 'hybrid' solution - RDWeb for remote desktop web access on the session hosts on the web browser, coupled with an NGINX frontend in front of it that required SSL Client Certificates to even get access. Those client certs were issued by IT per-system and installed accordingly. And voila, that solution worked. We've since moved to MS365 and Azure gateways with Microsoft + 2FA auth, but the point still stands - we came up with an Ubuntu driven solution for the endpoint systems. However, while the Dell laptops behaved swimmingly, the HP systems took at least 3 days of me as a sysadmin beating it into submission to get it to behave, and it came to a roundabout way to make it work with the UEFI stuff. Once we got that working, though, forcing it into legacy mode (the HP UEFI did not support UEFI mode with Ubuntu, and we couldn't turn off secure boot because of the way HP did their BIOS) allowed us to deploy the solution in mass. However, getting those systems working was a pain, and it required training of our IT support guy and the windows sysadmin and a few other volunteers to mass image the systems and set them up. We finally got it all done though, and up until late last year that was the "work from home" solution during COVID. We've since moved on, but you can imagine the difficulty an 'average user' might have installing Ubuntu in those situations where the hardware is not default compatible and needs 'technical experience' to find the solution. And that solution worked for FT job but might not work the next day for new people. The current default GUI of Ubuntu desktop is not very user friendly. I think you need to justify this argument. The Ubuntu desktop *is* quite user friendly nowadays, and with an assortment of other DEs to use with flavors of Ubuntu, there's other UIs they can use. But, it is for certain that if we want to increase the user base of Ubuntu desktop then we have to make it (GUI, etc.) easy to use just like Windows or even easier than Windows. It's not just a GUI/UI issue, there's legal issues and concerns, and 'hardware' level concerns from certain hardware that make this a large hurdle. Not to mention the long-standing compatibility and marketing agreements between Microsoft and off the shelf vendors to ship Microsoft. Regards, Amit Thomas -- (NOTE: The statements and opinions in the above email, unless otherwise stated, do not reflect any specific role or leadership position I hold, nor any positions I hold as a developer or elsewhere - the roles are mentioned here which I have only to reflect the scope of my 'reach' and observations) Ubuntu Member Ask Ubuntu Moderator Lubuntu Council Member and Lubuntu Team Lead Ubuntu Core Developer Ubuntu Developer Membership Board Member Ubuntu Server Team Member Ubuntu Community Council Member -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
[Bug 1965676] [NEW] virt-manager looses connection to virtualization hosts at moderate loads
Public bug reported: virt-manager looses connection to virtualization hosts on desktop systems at low to moderate loads. For dedicated virtualization hosts at moderate hosts. If the load persists it is difficult to reconnect. If the load drops it is in all cases possible to reconnect to the running systems and virtual systems on them. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: virt-manager 1:3.2.0-3 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Mar 20 14:15:49 2022 InstallationDate: Installed on 2011-10-19 (3804 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: Upgraded to impish on 2019-04-27 (1057 days ago) ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965676 Title: virt-manager looses connection to virtualization hosts at moderate loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1965676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965675] [NEW] qemu-system looses network connectivity even at low loads
Public bug reported: qemu-system-x86 looses network connectivity even at low loads. Using qemu running VM with - FreeBSD 11, 12, 13, 14 - Ubuntu 20.04, 20.10, 21.04, 21.10, 22.04(beta) - Fedora 34, 35, rawhide - debian stable, testing, unstable, debian-kfreebsd, debian-hurd - gentoo - haiku - OpenBSD 6.9, 7.0 - NetBSD 9, 10 - kali - OpenIndiana - openSUSE leap, tumbleweed After starting a simple task like updating the VMs system with - apt update; apt upgrade; apt full-upgrade - zypper update; zypper upgrade - dup upgrade The established ssh-session gets lost and it is not possible to establish it again. The further running VM does not act on ping -- it does not even receive the icmp echo request. Seems the bridge is the problem. The VM looses connection to the virtual bridge and it is impossible to reenable it. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: qemu-system-x86 1:6.0+dfsg-2expubuntu1.2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Mar 20 13:55:42 2022 InstallationDate: Installed on 2011-10-19 (3804 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 SourcePackage: qemu UpgradeStatus: Upgraded to impish on 2019-04-27 (1057 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965675 Title: qemu-system looses network connectivity even at low loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1965675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965643] [NEW] nfs mounts fail
Public bug reported: Any nfs4 mounts fail from nfs-servers with lower or same version. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: autofs 5.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 19 22:40:53 2022 InstallationDate: Installed on 2021-12-11 (98 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: autofs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: autofs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965643 Title: nfs mounts fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1965643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Hi, > > *Do you experience the problem with CD-R or CD-RW media ?* > Yes. The exact same error message as when I tried to make a DVD. Then it is not exactly the same problem as with the DRW-24D5MT of Mauro Sacchetto and my BW-16D1HT as of Debian bug 998718. Your Brasero version 3.12.1-4ubuntu2 seems slightly younger than the 3.12.3-1 of Mauro and the 3.12.2-5 which i tested. But there was no visible development in Brasero since quite a while. So i would not blame the difference on the versions ... for now. > > Does it help to blank the CD medium before using it with Brasero: > > xorriso -outdev /dev/sr0 -blank as_needed* > Unfortunately No. What about other burn programs (with a power-cycle between the last Brasero run and the the new experiment) ? Like: ISO="...path.to.your.iso.image.file..." xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO" Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
Because impish did not receive the commit that broke our build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: script rsync
Le 13 mars 2022 à 21:15, Thomas De Contes a écrit : > > Le 1 mars 2022 à 20:36, Steve Nadeau a écrit : > >> 2: la redirection devrait fonctionner, j'utilise personnellement "2>&1 >> >fichier.log" afin de récupérer le contenu de la console standard ainsi que >> de la console d'erreurs. Si le texte résultant du script s'inscrit seulement >> dans la console d'erreurs, rien ne se retrouvera dans le fichier de log. > > C'est bizarre : > - déjà je trouve ça bizarre que "&>" ne marche pas, > - mais ensuite j'ai remplacé "&>" par "2>&1 >", et j'ai cru que ça marchait, > - et maintenant on dirait que ça redirige bien stdout mais pas stderr ... > > Maintenant, j'en suis à l'équivalent de : > ( commande ) 2>&1 > "fichier.log" & > > Est-ce que c'est bien ça qu'il fallait faire ? > >> >> Le contenu du fichier script pourrait aider aussi à comprendre. > > Je ne crois pas. Pardon, je viens de m'apercevoir qu'au début du fichier il y a : #!/bin/sh - qui peut importer. Et je viens de m'apercevoir aussi que `man sh` dirige sur dash au lieu de bash, est-ce qu'il y a un lien avec mes problèmes ? -- RAPID maintainer http://savannah.nongnu.org/projects/rapid/ -- Liste de diffusion ubuntu-fr ubuntu-fr@lists.ubuntu.com Pour s'abonner ou se désabonner : https://lists.ubuntu.com/mailman/listinfo/ubuntu-fr Charte de la liste: http://doc.ubuntu-fr.org/groupes/ubuntu-fr-ml/charte
[Bug 1964836] [NEW] package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig
Public bug reported: happened while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-libc-dev 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4900 F pulseaudio /dev/snd/controlC0: tmk4900 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Mar 14 23:15:42 2022 Dependencies: ErrorMessage: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (899 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964836 Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: script rsync
Le 1 mars 2022 à 20:36, Steve Nadeau a écrit : > Bonjour Danielle, (C'est ma mère, j'etais sur son ordinateur pour faire les sauvegardes - pas d'importance.) > > sans que ce soit l'absolue bonne réponse, il est probable de vérifier les > points suivants: > > 1: lorsque des caractères internationaux sont inclus dans les noms de > fichiers, il est toujours difficile de prédire les incidences, il existe des > options de conversions des caractères dans les noms de fichiers par défaut, > mais vaut mieux s'en assurer afin d'obtenir les résultats souhaités. Dommage que ça ne soit pas encore rodé ce truc là ... enfin tant pis, au boulot ! > > l'option "--no-iconv" permet d'annuler toutes les conversions de caractères, > cela ne veut pas dire que ça va corriger votre situation Effectivement, le problème est toujours là. > > sinon il s'agirait d'ajuster l'option "--iconv" avec des paramètres de > conversion désirés. Par contre j'aurais besoin d'une doc (et peut-être d'explications supplémentaires) pour savoir quels paramètres je dois lui mettre. > > à la base, il est toujours préférables d'éviter les caractères internationaux > ainsi que les espaces et certains caractères spéciaux dans les noms de > fichiers. Comme cet ordinateur a un usage domestique, ça me parait impossible d'imposer ça à ses usagers (notamment parce qu'il y a beaucoup de fichiers venus de l'extérieur qu'il faudrait avoir la discipline de renommer). Par contre ça ne me dérange pas si la solution implique que (dans la sauvegarde) les caractères problématiques soient transformés ou supprimés, du moment que c'est reconnu à chaque fois de manière à optimiser la sauvegarde à chaque fois que c'est approprié. (J'espère juste qu'en cas de collision on peut être averti dans les logs, de manière à y remédier.) > > Aussi, il serait bien de connaître le système de fichiers source ainsi que > celui de destination. Source : par défaut sous Ubuntu, je crois bien que c'est ext4. Destination : par défaut sous Mac OS X, HFS+. > > Il serait aussi intéressant de voir la commande utilisée. rsync -azv --chmod=u+rwX --delete-after --delete-excluded --partial --stats --progress "--exclude-from=$DossierParent/../../donnees/exclusions-rsync-local" "--exclude-from=$DossierParent/../../donnees/exclusions-rsync-distant" ~/ 'pierre:~/'\'"$racineDestination/$nomDossier/"\' || exit "$?" > > > 2: la redirection devrait fonctionner, j'utilise personnellement "2>&1 > >fichier.log" afin de récupérer le contenu de la console standard ainsi que > de la console d'erreurs. Si le texte résultant du script s'inscrit seulement > dans la console d'erreurs, rien ne se retrouvera dans le fichier de log. C'est bizarre : - déjà je trouve ça bizarre que "&>" ne marche pas, - mais ensuite j'ai remplacé "&>" par "2>&1 >", et j'ai cru que ça marchait, - et maintenant on dirait que ça redirige bien stdout mais pas stderr ... Maintenant, j'en suis à l'équivalent de : ( commande ) 2>&1 > "fichier.log" & Est-ce que c'est bien ça qu'il fallait faire ? > > Le contenu du fichier script pourrait aider aussi à comprendre. Je ne crois pas. Le but à cette étape est seulement de mettre les sorties dans le fichier, et en même temps de ne pas bloquer le script appelant. Il me semble que le reste ne te ferais que te poser des questions alors que ça n'a rien a voire. > > > 3: avec la commande "hostname" ou dans le fichier "/etc/hostname" Impeccable, merci beaucoup :-) As tu une preference entre les 2 pour remplir une variable sh ? > > > Bonne journée! À toi aussi, merci :-) > > Steve > > > Le 2022-03-01 à 13 h 19, Danielle De Contes a écrit : >> bonjour :-) >> >> >> j'ai 3 pbs avec un script rsync >> >> >> 1) >> l'option '--delete-after' m'efface tous les fichiers dont le nom contient >> des caractères non-ascii, aussitôt après les avoir copiés. >> >> >> 2) >> sh me crée un fichier de log, mais ce fichier reste vide. >> >> mon script est de la forme : >> ( commande ) &> "fichier.log" & >> >> >> 3) >> comment obtenir le nom de l'ordi, qui apparaît dans le terminal ? >> >> sur cet ordi l'invite du terminal est de la forme : >> @:$ >> >> ce qui m’intéresse c'est . -- J'espère que ma manière de répondre ne vous dérange pas trop : http://marc.herbert.free.fr/mail/#citation -- Liste de diffusion ubuntu-fr ubuntu-fr@lists.ubuntu.com Pour s'abonner ou se désabonner : https://lists.ubuntu.com/mailman/listinfo/ubuntu-fr Charte de la liste: http://doc.ubuntu-fr.org/groupes/ubuntu-fr-ml/charte
[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Hi, C. Clear wrote: > What does doing a power off/on cycle entail ??? Just a shutdown so that the burner drive has no electrical power. If in doubt whether the power is really off, press the drive's eject button. The drive should not react. Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Hi, C. Clear wrote: > Drive type : vendor 'ASUS' product 'BW-16D1HT' revision '3.10' That would match the Debian bug of last year. > Did try Nero for Linux and had the same > result as I did with Brasero. Keep in mind that in the Debian bug scenario Brasero's bad read attempt spoiled the two ASUS drives until they got a power-off-on cycle. If the drive is built into the computer this means a power-off-on cycle of the computer, i fear. (I have mine in a USB box. That eases the problem.) It was enough to show Brasero a CD burnt with wite type TAO to let the drive go mad. It was not necessary to make a burn attempt. The only workaround was to blank CD-RW by other programs before giving them to Brasero for being re-written. Unfortunately TAO is the write type used by Brasero itself. Other programs may choose SAO with the consequence that those CDs don't let the drive go mad, even when they get shown to Brasero. Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Call for nominations: Developer Membership Board
On 3/9/22 09:18, Sebastien Bacher wrote: Hey Robie and DMB members, Le 01/03/2022 à 16:51, Robie Basak a écrit : Candidates must expect to be able to attend the majority of DMB meetings. Currently these take place on IRC, are scheduled on alternate Mondays with each meeting alternating between 1600 UTC and 1900 UTC, and last around an hour. Following the recent emails stating that we don't have enough candidate I'm going to drop a note about ^ I was pondering sending my application, I'm busy but I think it's important that we have a function DMB, but that 'must expect' statement convinced me to not. I try to lock the 17h30-20h to be able to have some family time and that's not something I'm wanting to compromise on at this point. I might not be the only one in that situation, since we are short on candidate maybe it would help to try to be less rigid on that requirement? (being open to different times? allow members to skip and vote via email? ...) With my DMB hat on: There is no 'requirement' on those time slots - we are capable of adjusting our meeting times according to our availability in the DMB by simple vote, and we've done this before. From my insight into the structure of DMB and how things're delegated, the DMB can change the timing to make sure we can all meet at least one of the meeting times every week. Currently, the DMB attempts to use real-time interviews where possible because sometimes we have questions that we can ask and then let people respond to those questions. The standard case - backed by me as well - is that real-time meetings where possible is preferred as we can get a better idea of someone's statements and opinions and knowledge more easily because it's real-time. While we have the occasional cases we need to get people into an email based process - usually due to timezones or other obligations - we usually prefer the real-time approach, because we can ask real-time questions without providing any extra time to 'research' the proper answer just to get things right. I agree with the general consensus that we have a problem with attendance - either because we're busy or because of other things. When those cases come up, with logical reasons for not attending it can be made sense why we might not be in the meetings. When people are not in the meeting and we aren't quorate, the issue we've had in the past is nobody responding in a timely manner to those messages - therefore a lack of participation. However, going email-only is going to be problematic because there's no guarantee for this to get handled. Similarly, with IRC meetings, if we are not available for a meeting, we usually do not have it and have to reschedule. The DMB in the past has experimented with email-only processes, and again timely responses have never been received so an application hung for way too long. Which is why we have a general rule on attendance and participation. It's insufficient to require just email votes on an application, in my opinion, and it's more effective to discuss items in a meeting that we carve an hour of time out for, rather than overwhelm everyone with just emails. This shouldn't block you, Sebastien, on the application process. In fact, I would strongly recommend you apply for the position regardless of the current time slots, the DMB when it's fully staffed can bring up the meeting change times itself, and we've done it before multiple times. Cheers, Sebastien Bacher -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Hi, the error message stems from the burner drive and was forwarded by libburn to Brasero. Strangely the code ASC=21 , ASCQ=04 is not specified in in the SCSI specs for optical drives (MMC). In the overall error code list https://www.t10.org/lists/asc-num.htm it is listed for other device classes as 21h/04h DZ UNALIGNED WRITE COMMAND I know this error code from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718 with Drive type : vendor 'ASUS' product 'DRW-24D5MT' revision '2.00' Brasero crashed at that occasion before it could start to write. The indirect reason seems to be a bad READ CD command which Brasero emitted on its own (i.e. not via libburn). It brings the firmware of two ASUS drives to a state from where it throws that error code. (Mine is a BW-16D1HT with firmware 1.01.) It happens only with CD media which were written by write type TAO. So (assuming that the drive has address /dev/sr0): - What is the vendor, model, revision of your drive. You may obtain it from the empty drive by xorriso -outdev /dev/sr0 -toc | grep 'Drive type' - Do you experience the problem with CD-R or CD-RW media ? If so: - What happens if you use a writable DVD medium instead ? - Does it help to blank the CD medium before using it with Brasero: xorriso -outdev /dev/sr0 -blank as_needed - Do you experience the problem with other GUI programs like K3B or Xfburn ? - Do you experience the problem with a run of xorriso ? ISO="...path.to.your.iso.image.file..." xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO" Have a nice day :) Thomas ** Bug watch added: Debian Bug tracker #998718 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964469] [NEW] Changes file extension when shared to phone
Public bug reported: When I share a file whose extension is '.asc' it ends up on the phone as '.txt'. This is confusing: I exported my encryption keys from DeltaChat desktop, shared them to my phone, and was then unable to import them into DeltaChat on the phone (which was expecting '.asc'). ** Affects: kdeconnect (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964469 Title: Changes file extension when shared to phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1964469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962614] Re: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
I agree with mapreri. Backports is not how to get bug fixes for crashes and such into older releases. Please follow the procedure for SRU, not Backports. -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1962614 Title: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1962614/+subscriptions -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 1962614] Re: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
I agree with mapreri. Backports is not how to get bug fixes for crashes and such into older releases. Please follow the procedure for SRU, not Backports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962614 Title: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1962614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/416586 ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
** Description changed: + [Impact] Commit 245f7772bdb743547e4d2f7df2475afc0eb5ec1e aborts the build when a snap still depends on core (16.04 runtime). - That's fine for Ubuntu but the CPC team builds images which still depend on core (that will be fixed soon). - So adding an option to allow those builds will fix the problem. + That's fine for Ubuntu but the CPC team builds images which still depend on core (that will be fixed soon). So currently those CPC builds are failing. + Adding an option to allow those builds will fix the problem. + + [Test Plan] + The bug can be reproduced with: + + $ ./scripts/ubuntu-bartender/ubuntu-bartender --hook-extras-dir + ~/devel/canonical/cloudware/cpc_packaging.extra --livecd-rootfs-branch + ubuntu/focal --livecd-rootfs-dir ~/devel/livecd-rootfs/ -- --series + focal --project ubuntu-cpc --image-target ec2-anbox + + So getting this command passing validated that the bug is fixed + + [Where problems could occur] + Other builds could get broken due to this change but it's unlikely because the change is relatively small and the change is tested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959452] Re: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64
** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Invalid ** Changed in: snappy Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959452 Title: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1959452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959452] Re: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64
It's a pi3 with 1 GB so my fault. sorry for the useless bug report. please close -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959452 Title: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1959452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959452] Re: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64
root@ubuntu:~# cat /proc/cpuinfo processor : 0 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 1 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 2 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 3 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 Hardware: BCM2835 Revision: a22082 Serial : d642db6b Model : Raspberry Pi 3 Model B Rev 1.2 root@ubuntu:~# head -1 /proc/meminfo MemTotal: 929936 kB root@ubuntu:~# uname -r 5.4.0-1053-raspi root@ubuntu:~# snap list Name VersionRevTracking Publisher Notes core20 20220215 1360 latest/stable canonical✓ base pi 20-1 97 20/stable canonical✓ gadget pi-kernel 5.4.0-1053.60 41220/stable canonical✓ kernel snapd 2.54.3 14982 latest/stable canonical✓ snapd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959452 Title: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1959452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] [NEW] Optionally allow building CPC images with core (16.04) based snaps
Public bug reported: Commit 245f7772bdb743547e4d2f7df2475afc0eb5ec1e aborts the build when a snap still depends on core (16.04 runtime). That's fine for Ubuntu but the CPC team builds images which still depend on core (that will be fixed soon). So adding an option to allow those builds will fix the problem. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Team charter
Notes in-line below. On 3/8/22 16:53, Dan Streetman wrote: On Mon, Mar 7, 2022 at 8:20 AM Mattia Rizzolo wrote: * you say that the chair can be replaced at any time, but I propose that such change require a supermajority (3/4th of the team) and since the team is owned by the TB, that also needs to be accepted by them agreed on requiring TB approval - but I'm not sure about requiring a supermajority of votes? I feel like if a majority of team members aren't happy with the chair, then the chair probably should be replaced, no? And the TB will have final approval to keep or allow replacement of the chair. I don't think we need supermajority for this. TB vote on this just needs a simple majority at the TB level to be a change. * require that the team has at least a quarterly meeting (despite currently being fortnight) ack, added. * you haven't specified *who* can apply. I recommend to require MOTUs. i think we should move the specific membership requirements and process into simple team policies, don't you? there is the requirement in the charter for the team to document membership requirements and application process in our public docs. re: MOTU, i agree, but also ~sru-developers I suggest? MOTUs, Core Devs, SRU developers, my 2 cents. (This will be the vast majority of people who will have tech skills to know if they can do the work backporters needs) * what's with the "may 1st" thing about the chair? especially if somebody is "promoted" to chair, that would make for an awkward situation, so what's the reason behind that? * so you think we should vote to extend everybody's membership? That sounds like too much work, wouldn't it? also I don't really see a need for it. And if you think it'd be useful, then everybody should expire the same date so that we can just hold one yearly meeting renewing (or not) everybody at once. yeah all this isn't needed for our team - i was thinking more of issues with some other teams. * 7.1.5 "at the chair’s discretion" - here I suppose you are referring to the meeting chair, not the team chair, right? (which could be different) yep, added the clarification. overall if feels more complicated than it needs to be, but effectively it's what we've been doing, so it should be fine. indeed, i agree it's unfortunately far more complicated than i would like it to be. And yes, I basically just tried to write up in painful detail what we already do. The draft is updated with these changes now, can you take another look? Thomas -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 1852994] Re: samba creates temporary files in /tmp, but never deletes them
It is fixed with the latest samba-version (4.15.5~dfsg-0ubuntu1) available within Ubuntu-Repositories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852994 Title: samba creates temporary files in /tmp, but never deletes them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1852994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd
sshd is started by systemd. No special configurations besides defaults by Ubuntu/xUbuntu. Only change in /etc/ssh/sshd_config: "PermitRootLogin prohibit-password" -> "PermitRootLogin yes" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963825] [NEW] udev does not create devices plugged into USB 3.0 ports
Public bug reported: Hotplugging devices into USB 3.0/1/2 Ports does not create devices in /dev. The plugged device is not accessible afterwards. This is for all of them: USB-Disks (HD, CDROM, Tapes), USB to serial converters, Audio, Video, Cameras. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udev 248.3-1ubuntu8.2 ProcVersionSignature: Ubuntu 5.13.0-32.35-generic 5.13.19 Uname: Linux 5.13.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 49-micronucleus.rules 70-snap.core.rules 51-android.rules 70-snap.chromium.rules Date: Sun Mar 6 16:55:19 2022 InstallationDate: Installed on 2011-10-19 (3790 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-32-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to impish on 2019-04-27 (1044 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963825 Title: udev does not create devices plugged into USB 3.0 ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1963825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963753] [NEW] Install alongside Windows 10 crashed during Xubuntu install
Public bug reported: I was installing Xubuntu 21.10 alongside Windows 10 on a Dell Optiplex 9020 minitower. Both installations are new. The Xubuntu installer divided the WD 1 terabyte SSD in half, which I thought would be fair to both operating systems. Near the end of the install a fatal error message popped up. I believe it said there was a problem with Grub. Unfortunately I cannot append the logs in this email: the running Xubuntu won't let me access or copy the logs. If you email me at tomre...@earthlink.net, I'll get into this computer, and copy the log files /var/log/syslog and var/log/partman and mail them from my own regular Linux Mint computer. Thank you for whatever help you can provide me, and I'll check for email from you tonight after work. ProblemType: Bug DistroRelease: Ubuntu 21.10 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Sat Mar 5 07:17:55 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.10 xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963753 Title: Install alongside Windows 10 crashed during Xubuntu install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963697] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1963697/+attachment/5565880/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963697] UbiquityDebug.txt
apport information ** Attachment added: "UbiquityDebug.txt" https://bugs.launchpad.net/bugs/1963697/+attachment/5565878/+files/UbiquityDebug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963697] UbiquityDm.txt
apport information ** Attachment added: "UbiquityDm.txt" https://bugs.launchpad.net/bugs/1963697/+attachment/5565879/+files/UbiquityDm.txt -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1963697] Casper.txt
apport information ** Attachment added: "Casper.txt" https://bugs.launchpad.net/bugs/1963697/+attachment/5565874/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963697] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1963697/+attachment/5565877/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1963697] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1963697/+attachment/5565876/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963697] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1963697/+attachment/5565875/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963697] apport information
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220304) Package: ubiquity 22.04.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy ubiquity-22.04.6 kubuntu Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963697] Re: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu"
I offered to test and assist too, this is the Python TraceBack from the crash I currently see/get: Traceback (most recent call last): File "/usr/lib/ubiquity/bin/ubiquity", line 668, in main(oem_config) File "/usr/lib/ubiquity/bin/ubiquity", line 652, in main install(args[0], query=options.query) File "/usr/lib/ubiquity/bin/ubiquity", line 268, in install wizard = ui.Wizard(distro) File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 246, in __init__ mod.ui = mod.ui_class(mod.controller) File "/usr/lib/ubiquity/plugins/ubi-wireless.py", line 214, in __init__ self._setup_page() File "/usr/lib/ubiquity/plugins/ubi-wireless.py", line 220, in _setup_page self.nmwidget = nmwidgets.NetworkManagerWidget() File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 367, in __init__ self.view = NetworkManagerTreeView(self._on_state_changed) File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 224, in __init__ model = QtNetworkStore(self) File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 110, in __init__ self._init_icons() File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 208, in _init_icons secure_pix = secure_icon.pixmap(ICON_SIZE / 2, ICON_SIZE / 2) TypeError: arguments did not match any overloaded call: pixmap(self, QSize, mode: QIcon.Mode = QIcon.Normal, state: QIcon.State = QIcon.Off): argument 1 has unexpected type 'float' pixmap(self, int, int, mode: QIcon.Mode = QIcon.Normal, state: QIcon.State = QIcon.Off): argument 1 has unexpected type 'float' pixmap(self, int, mode: QIcon.Mode = QIcon.Normal, state: QIcon.State = QIcon.Off): argument 1 has unexpected type 'float' pixmap(self, QWindow, QSize, mode: QIcon.Mode = QIcon.Normal, state: QIcon.State = QIcon.Off): argument 1 has unexpected type 'float' Looks like a TypeError somewhere. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Confirmed ** Tags added: apport-collected jammy kubuntu ubiquity-22.04.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963697 Title: Ubiquity crashes Kubuntu Jammy after selecting "install Kubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1963697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: CVE-2022-0543 also applies to Ubuntu
Is there a Debian or Ununtu bug for this? For tracking purposes for a fix and such. Sent from my Galaxy Original message From: Reginaldo Silva Date: 3/3/22 11:59 (GMT-05:00) To: ubuntu-devel-discuss@lists.ubuntu.com Subject: CVE-2022-0543 also applies to Ubuntu Hi, Ubuntu team. Back in January I discovered that there's a redis sandbox escape on Debian and Debian-derived distributions. It also affects Ubuntu. Please update from the Debian sources (it's a one-line patch to debian/rules). I plan to publish a blog post with a Proof of Concept exploit, but will give time for Ubuntu to release a fix first. https://lists.debian.org/debian-security-announce/2022/msg00048.html Best regards, Reginaldo -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
[Bug 1479148] Re: reprepro includedsc option does not work with multiple dsc files
I can confirm the issue. It still exists in the current Ubuntu 20.04.4. Adding multiple .deb files works fine, trying to add multiple .dsc and .changes files fails. $ lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 $ apt-show-versions | grep reprepro reprepro:amd64/focal-updates 5.3.0-1.3~ubuntu20.04 uptodate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479148 Title: reprepro includedsc option does not work with multiple dsc files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1479148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Yes, going back to this version solves this bug. But it needs to go back to older versions of a variety of dependencies too. On Wed, Feb 23, 2022 at 3:40 AM Daniel van Vugt <1961...@bugs.launchpad.net> wrote: > > In case the cause is > https://launchpad.net/ubuntu/+source/pipewire/0.3.47-1ubuntu1 can you > please try reinstalling the previous version's packages from > https://launchpad.net/ubuntu/+source/pipewire/0.3.47-1/+build/23181674 ? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1961849 > > Title: > bluetooth connects with headset, deconects, connects, deconnects > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1961849/+subscriptions > -- Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1961849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962363] [NEW] package linux-modules-extra-5.13.0-30-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg-new
Public bug reported: happens while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-modules-extra-5.13.0-30-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4880 F pulseaudio /dev/snd/controlC0: tmk4880 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Feb 26 14:31:26 2022 ErrorMessage: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (882 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-modules-extra-5.13.0-30-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962363 Title: package linux-modules-extra-5.13.0-30-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg- new« kann nicht geöffnet werden: Vorgang nicht zulässig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration
I'm on 20.04 and this is still an issue for me. I know this bug is considered invalid and won't be fixed, but is there still hope this can be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425000 Title: Cannot set right monitor as primary in dual monitor configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1425000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961852] Re: PRIME profiles is missing in nvidia-settings
** Attachment added: "Screenshot_2022-02-23_01-00-47.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1961852/+attachment/5562855/+files/Screenshot_2022-02-23_01-00-47.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961852 Title: PRIME profiles is missing in nvidia-settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1961852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961852] [NEW] PRIME profiles is missing in nvidia-settings
Public bug reported: Usually I used the on-demand profile. Somehow this is gone in latest 510 version. I also tried 460 but no success. I only can switch between internal graphics and nvidia. (Power Saving and Performance). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.16~0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-55-lowlatency x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 23 00:56:00 2022 Dependencies: InstallationDate: Installed on 2019-12-19 (796 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot_2022-02-23_01-00-47.png" https://bugs.launchpad.net/bugs/1961852/+attachment/5562852/+files/Screenshot_2022-02-23_01-00-47.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961852 Title: PRIME profiles is missing in nvidia-settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1961852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Start-Date: 2022-02-21 01:16:18 Commandline: apt -y upgrade Requested-By: tps (1000) Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1, 97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf-nobfd0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), systemd-container:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libqmi-proxy:amd64 (1.30.2-1, 1.30.4-1), gir1.2-snapd-1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), systemd-timesyncd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libpam-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libarchive13:amd64 (3.5.2-1, 3.5.2-1ubuntu1), openmpi-bin:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), libbinutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libfwupd2:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libsnapd-glib1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), openmpi-common:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), liblvm2cmd2.03:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libsystemd0:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libsystemd0:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), binutils-x86-64-linux-gnu:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libnss-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), lvm2:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libnss-mymachines:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), dmsetup:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), python3-pil.imagetk:amd64 (9.0.0-1, 9.0.1-1), libhypre-2.22.1:amd64 (2.22.1-6, 2.22.1-7), libdevmapper-event1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils-common:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libqmi-glib5:amd64 (1.30.2-1, 1.30.4-1), python3-pil:amd64 (9.0.0-1, 9.0.1-1), libopenmpi3:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), systemd-sysv:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libfwupdplugin5:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libdevmapper1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), fwupd:amd64 (1.7.4-1ubuntu1, 1.7.5-3) End-Date: 2022-02-21 01:18:20 Start-Date: 2022-02-21 01:18:24 Commandline: apt -y dist-upgrade Requested-By: tps (1000) Install: libnfsidmap1:amd64 (1:2.6.1-1~exp1ubuntu1, automatic) Upgrade: nfs-common:amd64 (1:1.3.4-6ubuntu1, 1:2.6.1-1~exp1ubuntu1) Remove: libnfsidmap2:amd64 (0.25-6build1) End-Date: 2022-02-21 01:18:28 Start-Date: 2022-02-22 07:07:20 Commandline: apt -y upgrade Requested-By: tps (1000) Install: polkitd:amd64 (0.105-32, automatic), pkexec:amd64 (0.105-32, automatic) Upgrade: libpolkit-agent-1-0:amd64 (0.105-31.1, 0.105-32), libsmartcols1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), debconf-i18n:amd64 (1.5.79, 1.5.79ubuntu1), apt:amd64 (2.3.15, 2.3.15build1), packagekit-tools:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libxcb-image0:amd64 (0.4.0-1build2, 0.4.0-2), zfs-zed:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libpipewire-0.3-common:amd64 (0.3.45-1, 0.3.47-1ubuntu1), zfs-initramfs:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libaom3:amd64 (3.2.0-2, 3.3.0-1), libjpeg-turbo8:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libjpeg-turbo8:i386 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libnvpair3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), grub-pc-bin:amd64 (2.06-2ubuntu4, 2.06-2ubuntu5), libapt-pkg6.0:amd64 (2.3.15, 2.3.15build1), libuutil3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), debconf:amd64 (1.5.79, 1.5.79ubuntu1), libmount1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libmount1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libzpool5linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), system-config-printer-udev:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), pipewire:amd64 (0.3.45-1, 0.3.47-1ubuntu1), libqpdf28:amd64 (10.5.0-1, 10.6.2-1), gir1.2-packagekitglib-1.0:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), util-linux:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libjpeg-turbo-progs:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), fdisk:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libfdisk1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), system-config-printer-common:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), eject:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), packagekit:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libturbojpeg:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libuuid1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libuuid1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), make:amd64 (4.3-4ubuntu2, 4.3-4.1build1), uuid-runtime:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), grub-efi-amd64-signed:amd64 (1.177+2.06-2ubuntu4, 1.178+2.06-2ubuntu5), libjpeg-turbo8-dev:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libpolkit-gobject-1-0:amd64 (0.105-31.1, 0.105-32), gir1.2-polkit-1.0:amd64 (0.105-31.1, 0.105-32), libpackagekit-glib2-18:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), pipewire-bin:amd64 (0.3.45-1, 0.3.47-1ubuntu1), system-config-printer:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3),
[Bug 1961849] [NEW] bluetooth connects with headset, deconects, connects, deconnects
Public bug reported: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1961849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
Maybe unset INTEL_IOMMU_DEFAULT_ON -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959041 Title: STR (suspend-to-RAM) freezes at suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
** Bug watch added: Linux Kernel Bug Tracker #197029 https://bugzilla.kernel.org/show_bug.cgi?id=197029 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959041 Title: STR (suspend-to-RAM) freezes at suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
So, now I could find a little more detail about my issue: I tested with other mainline kernel from 5.15 series and the problem started with 5.15.5 And it is also present on 5.15.10 and 5.15.24 (thats what I have also tested) STR works with 5.15.0, 5.15.3, 5.15.4 (thats what I have tested) After knowing the version I could find this on the net: https://www.reddit.com/r/pop_os/comments/radfeg/psa_kernel_5155_and_intel_6th_gen_cpus_issue_with/ And so after adding intel_iommu=off as kernel option STR works also with linux-image-5.15.0-18-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959041 Title: STR (suspend-to-RAM) freezes at suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
So, now I could find a little more detail about my issue: I tested with other mainline kernel from 5.15 series and the problem started with 5.15.5 And it is also present on 5.15.10 and 5.15.24 (thats what I have also tested) STR works with 5.15.0, 5.15.3, 5.15.4 (thats what I have tested) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959041 Title: STR (suspend-to-RAM) freezes at suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
Today I also tested with linux-image-5.15.0-18-generic but the problem still persists. Anything else I can test? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959041 Title: STR (suspend-to-RAM) freezes at suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961305] [NEW] Cannot boot into Xen dom0
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 The linux-generic-hwe-20.04 5.13 Kernels are compiled with #CONFIG_KERNEL_GZIP is not set CONFIG_KERNEL_ZSTD=y preventing Xen 4.13.x / 4.14.x from booting into Dom0. After compiling the kernel by myself using CONFIG_KERNEL_GZIP=y #CONFIG_KERNEL_ZSTD is not set it works as expected. Kernel boots and Xen is working as intended. Please revert to CONFIG_KERNEL_GZIP=y like in the former HWE (5.11?) series not having this problem. Thank you ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961305 Title: Cannot boot into Xen dom0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1961305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961108] [NEW] network options greyed out in paprefs
Public bug reported:
I installed Kubuntu 21.10 which comes with pulseaudio
1:15.0+dfsg1-1ubuntu2.2. When I start paprefs all network options are
greyed out. The problem seems to be, that the directory with the modules
is called /usr/lib/pulse-15.0+dfsg1, but paprefs expects the modules in
/usr/lib/pulse-15.0
$ strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-15.0/modules/module-esound-protocol-tcp.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-native-protocol-tcp.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-raop-discover.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-recv.so", F_OK) = -1 ENOENT (No
such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-send.so", F_OK) = -1 ENOENT (No
such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rygel-media-server.so", F_OK) = -1
ENOENT (No such file or directory)
Creating a symlink /usr/lib/pulse-15.0 solves the problem
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961108
Title:
network options greyed out in paprefs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1961108/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960922] [NEW] Executable lbzip2 is missing in Debian package
Public bug reported: The package seems to be incomplete, as the executable itself (/usr/bin/lbzip2) and maybe other files are missing in the Debian package. ** Affects: lbzip2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960922 Title: Executable lbzip2 is missing in Debian package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbzip2/+bug/1960922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960892] [NEW] Starting "obs" creates a core dump
Public bug reported: This is on Jammy: $ dpkg -l|grep obs-studio ii obs-studio 27.1.3+dfsg1-2 amd64recorder and streamer for live video content $ obs Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted (core dumped) tom@thymian:~/devel/canonical/cloudware/cpc_jenkins/wt1$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: obs-studio 27.1.3+dfsg1-2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 07:01:51 2022 InstallationDate: Installed on 2020-12-08 (433 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: obs-studio UpgradeStatus: Upgraded to jammy on 2021-11-30 (76 days ago) ** Affects: obs-studio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960892 Title: Starting "obs" creates a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1960892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960892] Re: Starting "obs" creates a core dump
workaround - install from flathub . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960892 Title: Starting "obs" creates a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1960892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954544] Re: No OpenSSL 3.0 support
This was fixed in 2.4.0-2 from Debian which was synced down with the OpenSSL 3.0 patches. ** Changed in: xca (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954544 Title: No OpenSSL 3.0 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xca/+bug/1954544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I also have this issue on a Thinkpad T14s, AMD Ryzen 7 PRO 4750U. The issue is not present with kernels 5.9.10 or 5.15.23. It is present with the default kernel from the most recent KDE Neon (5.13). Here's a short video, it's the same pattern (static and vertical lines on the right) as the other video in this thread: https://twitter.com/tlhunter/status/1493107390731874305 The pattern is reminiscent to an HDMI desync issue but the vertical lines do make it distinct. It appeared to affect the laptop screen but not an external display. The static appeared after the screen went to sleep and woke back up, though I don't believe the system went to sleep. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960722] Re: ubiquity-zsys crashes when ZFS-encryption is chosen
*** This bug is a duplicate of bug 1960717 *** https://bugs.launchpad.net/bugs/1960717 ** This bug has been marked a duplicate of bug 1960717 zsys-setup fails when ZFS-encryption chosen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960722 Title: ubiquity-zsys crashes when ZFS-encryption is chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960717] Re: zsys-setup fails when ZFS-encryption chosen
** Summary changed: - zsys-setup fails on nvme drive. + zsys-setup fails when ZFS-encryption chosen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960717 Title: zsys-setup fails when ZFS-encryption chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960722] Re: ubiquity-zsys crashes when ZFS-encryption is chosen
** Summary changed: - ubiquity-zsys crashes on Thinkpad E15 Gen2 + ubiquity-zsys crashes when ZFS-encryption is chosen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960722 Title: ubiquity-zsys crashes when ZFS-encryption is chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960722] [NEW] ubiquity-zsys crashes on Thinkpad E15 Gen2
Public bug reported: Every intent to install ubuntu 22.04 with ZFS-encryption fails. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Sat Feb 12 17:19:07 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.4 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960722 Title: ubiquity-zsys crashes on Thinkpad E15 Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960717] [NEW] zsys-setup fails on nvme drive.
Public bug reported: With the exact same installation media no problem on sata drive ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.3 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Sat Feb 12 14:56:24 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.3 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960717 Title: zsys-setup fails on nvme drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954544] Re: No OpenSSL 3.0 support
I'm an evil person so I poked and prodded upstream to make sure they address this. OpenSSL 3.0 compat is in a branch here - https://github.com/chris2511/xca/compare/xca-240-ossl3 - which succeeded passing the build tests in my 'junk drawer' PPA which is used for build tests on all archs with proposed enabled (https://launchpad.net/~teward/+archive/ubuntu/junk-drawer/+packages). There was no FTBFS and I have committed a patch containing the upstream branch changes to the Debian Salsa, and will be uploading that to Mentors shortly for them to include there in Unstable (it's seemingly reverse-compatible with teh older OpenSSL as well in unstable); once this is there I'll sync it down to Ubuntu and we'll see if it succeeds in Jammy like it does in the PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954544 Title: No OpenSSL 3.0 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xca/+bug/1954544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Should we remove chromium-browser from the archive?
Not to mention, the rdepends of the package:
# apt-cache rdepends chromium-browser
chromium-browser
Reverse Depends:
chromium-browser-l10n
gnome-shell-extension-gsconnect-browsers
|gnome-core
chromium-chromedriver
chrome-gnome-shell
chrome-gnome-shell
We'd have to do some erasure of some packages (potentially transitional)
and some other packages as well as a few shell extensions in order to
make this removal work I think.
Thomas
On 2/8/22 14:29, Gunnar Hjalmarsson wrote:
Hi Olivier!
On 2022-02-08 19:33, Olivier Tilloy wrote:
The chromium-browser package has been a "transitional" package that
installs the chromium snap since Ubuntu 19.10. Full-fledged deb
packages are still being built for 18.04.
The question of whether to remove this transitional package from the
archive altogether has come up, so I'm sharing it here to get insights
and feedback from a wider audience before making an informed decision.
Some features of the deb package that are worth taking into account:
- /usr/bin/{chromium-browser,chromedriver} symlinks to their snap
counterparts
- a postinst script that installs alternatives for x-www-browser and
gnome-www-browser (unfortunately snapd doesn't have any mechanism for
this yet)
- a custom apport hook that collects additional information about the
snap and its dependencies
- did I miss any other features?
Can't tell, but those are important enough, aren't they?
Your message made me think of bugs like these:
https://launchpad.net/bugs/1947600
https://launchpad.net/bugs/1950550
And today I had a reason to install xsane.
$ apt-cache show xsane | grep Recommends
Recommends: cups-client, firefox | www-browser
As you see it pulled the Firefox .deb even if I have the Firefox snap
installed.
So as long as there is no other mechanism to make the system recognize
the FF snap and/or the Chromium snap as a www-browser, I suppose we
need such transitional packages. (Waiting for the FF equivalent.)
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Hello, Thanks for the help! :) Are these cifs patches present in 5.13.0.27? I got similar issues with 5.4.0.97 and 5.13.0.27, and moving to previous releases fixed the issues in both cases! :) Cheers! Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959511] [NEW] New omniORB package in debian unstable
Public bug reported: Debian unstable got a new version of omniORB, 4.2.4-3, see https://tracker.debian.org/pkg/omniorb-dfsg. This version would allow people to built C++ applications using C++17 as the current omniORB version does not work with C++17, see https://launchpadlibrarian.net/553363492/buildlog_ubuntu-impish- amd64.tango_9.3.4+dfsg1-1ubuntu1_BUILDING.txt.gz. It is already fixed in debian, see https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=984267. ** Affects: omniorb-dfsg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959511 Title: New omniORB package in debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/omniorb-dfsg/+bug/1959511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956177] Re: battery not detected by ACPI
Hello Patrick, having time today I've applied your patch to my system, but the battery is still not recognized by OS. According to my BIOS rev. I've copied- renamed the one .aml file starting with "12_" to /boot/dsdt.aml, copied and chmod'ed 01_acpi to /etc/grub.d/ and ran update-grub, which told me that it "Found custom ACPI table: /boot/dsdt.aml". After rebooting the system (and being curious what happens), there is no battery symbol but text as before stating "No Batteries Available". Any idea what went wrong? Anyway, thanks a lot for your assistance so far. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956177 Title: battery not detected by ACPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959488] Re: Error loading key ".../id_ed25519.pub": error in libcrypto
curl -s https://launchpadlibrarian.net/582802175/Dependencies.txt | awk
'{print $1}' | xargs -L1 debsums -lc
Reports also nothing, so all Dependencies are okay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959488
Title:
Error loading key ".../id_ed25519.pub": error in libcrypto
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1959488/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959488] [NEW] Error loading key ".../id_ed25519.pub": error in libcrypto
Public bug reported: I can't add my ED25519 ssh-key to my ssh-agent. I am getting this error message: user@pc:~$ ssh-add ~/.ssh/id_ed25519.pub Error loading key "/home/user/.ssh/id_ed25519.pub": error in libcrypto I have setup key agent for KDE like this: user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh #!/bin/bash [ -n "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -s)" user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh #!/bin/bash [ -n "$SSH\_ASKPASS" ] || export SSH\_ASKPASS=/usr/bin/ksshaskpass user@pcc:~$ cat ~/.config/plasma-workspace/shutdown/ssh-agent-shutdown.sh #!/bin/bash [ -z "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -k)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.7p1-4 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jan 29 16:43:55 2022 InstallationDate: Installed on 2022-01-21 (7 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.7p1 Ubuntu-4, OpenSSL 3.0.1 14 Dec 2021 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: - I cant add my ED25519 ssh key to my ssh-agent. I am getting this error + I can't add my ED25519 ssh-key to my ssh-agent. I am getting this error message: user@pc:~$ ssh-add ~/.ssh/id_ed25519.pub Error loading key "/home/user/.ssh/id_ed25519.pub": error in libcrypto + I have setup key agent for KDE like this: - user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh + + user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh #!/bin/bash [ -n "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -s)" - user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh + + + user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh #!/bin/bash [ -n "$SSH\_ASKPASS" ] || export SSH\_ASKPASS=/usr/bin/ksshaskpass + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.7p1-4 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jan 29 16:43:55 2022 InstallationDate: Installed on 2022-01-21 (7 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: - ssh-askpass N/A - libpam-sshN/A - keychain N/A - ssh-askpass-gnome N/A + ssh-askpass N/A + libpam-sshN/A + keychain N/A + ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.7p1 Ubuntu-4, OpenSSL 3.0.1 14 Dec 2021 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I can't add my ED25519 ssh-key to my ssh-agent. I am getting this error message: user@pc:~$ ssh-add ~/.ssh/id_ed25519.pub Error loading key "/home/user/.ssh/id_ed25519.pub": error in libcrypto - I have setup key agent for KDE like this: - user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh #!/bin/bash [ -n "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -s)" - user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh #!/bin/bash [ -n "$SSH\_ASKPASS" ] || export SSH\_ASKPASS=/usr/bin/ksshaskpass + + user@pcc:~$ cat ~/.config/plasma-workspace/shutdown/ssh-agent-shutdown.sh + #!/bin/bash + + [ -z "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -k)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.7p1-4 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jan 29 16:43:55 2022 InstallationDate: Installed on 2022-01-21 (7 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.7p1 Ubuntu-4, OpenSSL 3.0.1 14 Dec 2021 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959488 Title: Error loading key ".../id_ed25519.pub": error in libcrypto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1959488/+subscriptions -- ubuntu-bugs mailing list
[Bug 1959177] [NEW] missing manpage for kscreen-doctor
Public bug reported: I am missing a manpage for kscreen-doctor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libkf5screen-bin 4:5.23.90-0ubuntu1 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jan 27 08:27:18 2022 InstallationDate: Installed on 2022-01-21 (5 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) SourcePackage: libkscreen UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libkscreen (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy manpage wayland-session ** Tags added: manpage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959177 Title: missing manpage for kscreen-doctor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libkscreen/+bug/1959177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959138] Re: pls raise package version to 0.40.0
** Tags added: needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959138 Title: pls raise package version to 0.40.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-wacom/+bug/1959138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959140] Re: pls raise libwacom to 2.0.0 for new device support
** Tags added: needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959140 Title: pls raise libwacom to 2.0.0 for new device support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1959140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
** Tags added: regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959041 Title: STR (suspend-to-RAM) freezes at suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959140] [NEW] pls raise libwacom to 2.0.0 for new device support
Public bug reported: It would be nice to have up to date libwacom in Ubuntu 22.04 to support current hardware. https://github.com/linuxwacom/libwacom/releases/tag/libwacom-2.0.0 ** Affects: libwacom (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Description changed: - It would be nice to have up to date libwacom in Ubuntu 22.04 + It would be nice to have up to date libwacom in Ubuntu 22.04 to support + current hardware. https://github.com/linuxwacom/libwacom/releases/tag/libwacom-2.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959140 Title: pls raise libwacom to 2.0.0 for new device support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1959140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959138] Re: pls raise package version to 0.40.0
** Summary changed: - raise package version to 0.40.0 + pls raise package version to 0.40.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959138 Title: pls raise package version to 0.40.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-wacom/+bug/1959138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959138] [NEW] raise package version to 0.40.0
Public bug reported: It would be nice to raise package version to current 0.40.0 for Ubuntu 22.04. https://github.com/linuxwacom/xf86-input-wacom/releases/tag/xf86-input- wacom-0.40.0 ** Affects: xserver-xorg-input-wacom (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959138 Title: raise package version to 0.40.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-wacom/+bug/1959138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
