I concluded that the description was related to the use of the
us+dvorak-alt-intl layout, and not to g-c-c setting incorrect options.
Observations from use of the us+intl layout:
Alternate Characters Key to None
$ gsettings get org.gnome.desktop.input-sources
This may be a duplicate of https://launchpad.net/bugs/1969162
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1968845
Title:
Upgrade to 22.04 from 20.04 ends with dbus
> And AFAICT gnome-control-center sets the expected XKB options,
> so it's not a g-c-c bug. Maybe an xkeyboard-config bug.
>From my initial bug report:
Setting Alternate Characters Key to None, and moving the Compose Key
setting around between different options (and then back to Right Alt),
the
Public bug reported:
wine installed but recieving wine 32 not installed error cuz of dependenceis
but the dependecies goes into rabbit hole like 6 or more, it just doesnt end
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgstreamer-plugins-good1.0-0 1.16.2-1ubuntu2.1
Hello Mikko, thanks for the report; I believe that's working as
intended, those bytes are part of the DER encoding; there's an excellent
answer at https://crypto.stackexchange.com/a/19982/1400 that describes
the meanings of each of those bytes.
Thanks
** Information type changed from Private
Here's the postinst I've got for that package. Maybe the
reload_dbus_config() could use a --reply-timeout=5000 or something?
Thanks
$ cat /fst/trees/ubuntu/main/d/dbus/dbus_1.12.20-2ubuntu4/debian/dbus.postinst
#!/bin/sh
# Copyright © 2003 Colin Walters
# Copyright © 2006 Sjoerd Simons
set
Found more specific terms of the problem. I have the keepassxc password
manager version 2.7.1 compiled from source, it stores the keys and it
adds them to ssh-agent, under such conditions this error appears. The
problem arose only after updating openssh to 8.9p1 and only on arm. With
version 8.8p1
Yikes, does it actually *stop* at that point? That's .. not ideal.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1968845
Title:
Upgrade to 22.04 from 20.04 ends
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
>> 1. Which keyboard layout are you using?
>
> English (Dvorak, alt. intl.)
There is something with that layout. With that enabled I can reproduce
the problem. Both on jammy and impish.
>> 2. What happens if you drop the 'lv3:none' option, so you only have:
>> ['altwin:menu', 'compose:ralt']
>
You have been subscribed to a public bug:
I noticed after upgrade from impish to jammy that my compose key is not
working correctly.
Going into gnome-control-center -> Keyboard, I see that 'Alternate
Characters Key' and 'Compose Key' are both set to Right Alt.
Setting Alternate Characters Key
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1877194
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags added: lubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1969291
Title:
apport-collect & ubuntu-bug failing to switch to firefox
Status in apport package in
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194
** This bug is no longer a duplicate of bug 1899962
Wrong audio output device selected on Raspberry Pi Desktop
** This bug has been marked a duplicate of bug 1877194
switch-on-connect mistakes startup
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194
Looks like this fell off my radar, but looking at vanvugt's comment this
is indeed a duplicate of bug 1877194 (and still occurs in Jammy). I'll
mark it as such
** This bug has been marked a duplicate of
>If direct access to Launchpad is blocked how was a bug report filed in
the first place?
Clicking the "Report a Bug" link on any project's page in LP. This is
done from a machine outside of the airgapped or restricted access lab
where the hardware sits.
Also, I should point out (which I
If direct access to Launchpad is blocked how was a bug report filed in
the first place? apport-collect is designed to gather information from a
system about an existing bug report. Additionally, apport-collect looks
at the bug report in Launchpad to determine which package is affected
and to to
Public bug reported:
We very often tell our hardware partners to "file a bug" when they
encounter issues. This requires them to run apport-collect to gather
and submit logs for the bug.
However, very often, the hardware that has the problem is in a lab that
has tight security restrictions and
I'm working on a SRU for apparmor and evince to introduce the snap_browsers
abstraction on apparmor as a workaround for this issue.
It is based on these two merge requests from upstream:
https://gitlab.com/apparmor/apparmor/-/merge_requests/806
it sounds like something that we should fix one way or another at least
for the LTS, maybe in the futur we will have evince as a snap instead
and the situation will be different. Could you suggest a patch for
review with the change you described?
--
You received this bug notification because you
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1959475
Title:
"machinectl shell" connections immediately terminated
Status in systemd package in
Public bug reported:
Found linux image: /boot/vmlinuz-5.14.0-1032-oem
Found initrd image: /boot/initrd.img-5.14.0-1032-oem
Found linux image: /boot/vmlinuz-5.14.0-1031-oem
Found initrd image: /boot/initrd.img-5.14.0-1031-oem
Adding boot menu entry for UEFI Firmware Settings
done
Processing
** Description changed:
- 1) Ubuntu 22.04
- 2) software-properties-gtk 0.99.22
- 3) No crash when using Additional Drivers with
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
- 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any
problem.
+ 1) The release of Ubuntu
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1969460
Title:
software-properties-gtk crashed with TypeError in
Public bug reported:
1) Ubuntu 22.04
2) software-properties-gtk 0.99.22
3) No crash when using Additional Drivers with
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.
** Affects: oem-priority
I tried reproducing the issue on a Rpi4, cloning a repository via ssh
using pubkey authentication with a rsa2048 key stored in ssh-agent, it
worked fine. If you believe there's actually a bug here please provide
some steps we can follow to reproduce the issue from a clean Jammy
system, and we'll
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1968912
Title:
vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
in default
the recent update suggests the white rendering was indeed bug #1966418
which is resolved now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1924251
Title:
Embedded
It seems that view, as provided by vim.tiny now attempts to load
defaults.vim, which is shipped in the large vim-runtime package. All
vims depend on vim-common. It would seem to me that we should move
defaults.vim from vim-runtime to vim-common.
--
You received this bug notification because you
Not an apt bug in either case if it crashes your system
** Package changed: apt (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I also noticed this by launching "view /var/log/installer/syslog" on a
freshly installed Ubuntu desktop system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1968912
Title:
Another quick update: in recent days we've gone from "blank white space"
back to "incorrect stride corruption" in all documented cases (embedded
browsers, help windows, MiniBrowser, etc).
I note in the dpkg logs, libglx-mesa0 got updated a few days ago, but
unfortunately I'm unsure exactly when
[Impact]
* Cannot use ucf to install templated configuration when using
dpkg-divert with the destination config file
* Affects various packages including dovecot and any custom config
packages using both config-package-dev and ucf
[Test Plan]
* Create a config-package-dev based
Divert related fixes from ucf 3.0040 and also from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354
Allows ucf to work when using dpkg-divert or config-package-dev for
diverts
eg
ucf --three-way
ucfr
Tested and working as expected
Note: ucf does not working with --debconf-ok flag
** Patch removed: "patches from ucf 3.0040 to fix diversions issue with
config-package-dev"
https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5400552/+files/honor-dpkg-diversions-1+2+3.patch
--
You received this bug notification because you are a member of Ubuntu
Touch
unattended-upgrades in jammy did not need a change, we'll see if SRUs
will need changes, hence keeping the task so we can add them later on
without having to reset to launchpad API shenanigans.
** Description changed:
[Impact]
APT currently keeps 3 kernels or even 4 in some releases. Our
Thanks for the bug report.
Please open the 'Additional Drivers' app to install the correct Nvidia
driver. If you still have problems after that then please explain what
the issue is in more detail.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New =>
Hi Shyam, I am closer to getting this to work on 22.04 (22.10 should be
easier once we've sorted out 22.04). I'll be off this week (tomorrow
onward!) and will definitely have something for you by the next week.
Let me know if you have any questions or concerns. TIA. \o/
--
You received this bug
What file or binary package does this bug report related to?
Also what version of Ubuntu are you using?
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
39 matches
Mail list logo
