The attachment "ibus debdiff for bionic" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
Please also run this in both the VM and on the host, and send us both
outputs:
lsusb
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1838227
Title:
Bluetooth "Connection
OK then, in the VM please open a Terminal (Ctrl+Alt+T) and run:
rfkill > rfkill.txt
and then attach the file 'rfkill.txt' here.
Alternatively run:
rfkill
and just take a screenshot.
** Changed in: bluez (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ibus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
** Attachment added: "newlog_kernel5.0.0-21-generic_repeateduntilitworks.txt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279955/+files/newlog_kernel5.0.0-21-generic_repeateduntilitworks.txt
--
You received this bug notification because you are a member of
Well, I see the problem also on real hardware, but it's harder to
reproduce. In any case, I don't want to install a non-standard kernel
there, so it is mixed up with the other problems with the 5.0 kernel.
However, the VM *does* indeed have bluetooth. Virtualbox allows VMs to
access any USB
Attached is the debdiff for bionic which restores ibus-
xx-f19-password.patch
** Patch added: "ibus debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+attachment/5279953/+files/lp1838358_bionic.debdiff
** Tags added: sts-sponsor
--
You received this bug
Public bug reported:
[Impact]
The following has been seen in a VMware Horizon VDI. I cannot reproduce this
issue myself.
When a user interacts with any password field in Firefox, gnome-shell
and Firefox both freeze and the system becomes unusable. If you ssh into
the system and terminate
Your Xorg log is showing that 'Microsoft Microsoft® 2.4GHz Transceiver
v8.0' is being added and removed a lot. If that's not true and you are
leaving the USB receiver plugged in, then this will be either a kernel
bug or a hardware problem.
Please try using a regular wired USB mouse and tell us if
Thanks for the bug report.
If appears your laptop is configured with language LANG=en_US.UTF-8 (US
English) so that will affect the language that apps like browsers, and
perhaps some web sites, will give you.
Please change your default language settings in:
Settings > Language and Region >
*** This bug is a duplicate of bug 1836756 ***
https://bugs.launchpad.net/bugs/1836756
When things freeze, are you still able to move the mouse?
If so then this would be a gnome-shell bug.
If not then this would be a xorg-server bug.
** Package changed: xorg (Ubuntu) => xorg-server
Hmm, you reported this bug from a virtual machine which doesn't seem to
have any Bluetooth hardware, so actually I would expect the switch to
not work.
Please submit a new bug from a real machine if that's where you are
seeing the problem.
** Changed in: bluez (Ubuntu)
Status: Incomplete
Thanks. The common factor still seems to be:
Jul 29 12:20:13 V-M-Ubuntu-Experimental bluetoothd[817]: Unable to get Headset
Voice gateway SDP record: Device or resource busy
Jul 29 12:20:13 V-M-Ubuntu-Experimental bluetoothd[817]: connect error: Device
or resource busy (16)
which is the same
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Tags removed: artful zesty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1679744
Title:
pulseaudio crashed with SIGSEGV in pa_hashmap_get() from
Public bug reported:
trying to upgrade
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: python3 3.7.3-1
ProcVersionSignature: Ubuntu 4.18.0-1024.25~18.04.1-azure 4.18.20
Uname: Linux 4.18.0-1024-azure x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Mon Jul 29 19:44:42
Please follow https://ccid.apdu.fr/#CCID_compliant
I already have the USB device 0a5c:5832 in my list.
https://ccid.apdu.fr/ccid/shouldwork.html#0x0A5C0x5832
Be sure to be using libccid package version 1.4.25 or more.
https://packages.ubuntu.com/search?keywords=libccid
--
You received this bug
The attachment "The workaround for this issue" seems to be a patch. If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned
Note that this bug occurs on all versions of GNOME Software.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1742997
Title:
Newly installed applications are not showing
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/291
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1742997
Title:
Newly installed applications are not
Public bug reported:
Hi,
I am a new user of Ubuntu, just arrived today on this OS and I have
planned to surf a long long time here from now on. Basically I am from
Pakistan and I read many tweets (current affairs) in my language (URDU)
on twitter and I also use my WhatsApp in the Browser so when
I've managed to find a bug that stops apps appearing in the installed
list when they are *reinstalled*.
To reproduce:
1. Open GNOME Software
2. Go to installed tab
3. Click on an installed app
4. Remove this app
5. Install this app
6. Click back button to return to installation page.
The app
*** This bug is a duplicate of bug 1838146 ***
https://bugs.launchpad.net/bugs/1838146
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as
...and here is a smaller log covering only a single attempt to slide the
connection switch to the right (the switch snapped back immediately by
itself)
** Attachment added: "newlog_SingleTry_2019_07_29.txt"
@Daniel Here you go (newlog_2019_07_29.txt). The log covers only the
time while I tried to connect to the headset (took several tries before
the switch switched; there are maybe a dozen mouse actions during that
time).
There are many message like this:
org.gnome.Shell.desktop[1585]: Window
Public bug reported:
On some systems, cryptsetup-based encrypted swap partitions cause
systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so
the rate of occurrence varies from one system to another. Some hardware
will not experience the issue at all, others will only occasionally
icu split up into bug 1838322.
** Changed in: openjdk-8 (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: openjdk-8 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: openjdk-8 (Ubuntu Disco)
Status: New => Fix Released
** No longer affects: icu (Ubuntu)
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pcsc-lite (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
There are mentions of Reiwa in icu in eoan. I'm not sure if this is a
complete fix, since the code appears to have changed somewhat from the
version of icu in Bionic and Disco.
Bionic certainly looks unfixed. Disco doesn't incldue the mentions of
"reiwa" that are present in the eoan code base.
Public bug reported:
[Background]
Many packages are affected by the requirement to support the new era "Reiwa"
(令和）
This is the meta bug to track packages that need fixes; which packages
have already been SRUd to previous releases, how to prioritize the work
needed, and general test cases for
gucharmap split up into bug 1838321
** No longer affects: gucharmap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1828884
Title:
[META] Handling Japanese new era
Public bug reported:
ubuntu freeze again
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13]
I did a quick test with a test package to check if launchpad builders
would be affected by this delay on Eoan and did not notice any
additional delays. Overall build time of the test package was always
below 3 minutes, the lvm2 build-dependency seemed to happen in normal
time and a call to `time
Hi Michael,
looks like we added our comments and files in parallel.
I guess it's okay for now ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1838258
Title:
Unable to
I'm sorry but I have no access to the system any longer, therefore I
cannot the command.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libselinux in Ubuntu.
https://bugs.launchpad.net/bugs/1769301
Title:
resetting
--- Comment From michael.roes...@ibm.com 2019-07-29 11:37 EDT---
(In reply to comment #11)
> Here are more details from my setup...
>
> @Bug reporter, please share your details and logs as well!
>
>
Do you need more logs than the ones I had uploaded earlier? If so, which ones
in
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1838258/+attachment/5279823/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1838258/+attachment/5279824/+files/journalctl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1769301
and then change the status of the bug to 'Confirmed'.
If, due to the
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1838258/+attachment/5279825/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
--- Comment From michael.roes...@ibm.com 2019-07-29 11:24 EDT---
(In reply to comment #6)
> Looks I can re-create this issue.
> Just as a workaround, one may edit /etc/netplan/01-netcfg.yaml
> do the configuration in a persistent way there and do a netplan apply:
> $ sudo netplan apply
Here are more details from my setup...
@Bug reporter, please share your details and logs as well!
** Attachment added: "recreate.txt"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1838258/+attachment/5279822/+files/recreate.txt
--
You received this bug notification because you
--- Comment From michael.roes...@ibm.com 2019-07-29 11:17 EDT---
(In reply to comment #5)
> What's the output of: $ ip a ?
>
> Also matching dmesg / syslog / journal?
root@m3515028:~# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback
--- Comment (attachment only) From michael.roes...@ibm.com 2019-07-29 11:19
EDT---
** Attachment added: "syslog journal dmesg after reproduction"
https://bugs.launchpad.net/bugs/1838258/+attachment/5279821/+files/logs.tar
--
You received this bug notification because you are a
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libselinux in Ubuntu.
https://bugs.launchpad.net/bugs/1769301
Title:
resetting
Looks I can re-create this issue.
Just as a workaround, one may edit /etc/netplan/01-netcfg.yaml
do the configuration in a persistent way there and do a netplan apply:
$ sudo netplan apply --dryrun
$ sudo netplan apply
Please notice that you should have your system always on the latest level -
The verification of the Stable Release Update for apparmor has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
This bug was fixed in the package apparmor - 2.13.2-9ubuntu6.1
---
apparmor (2.13.2-9ubuntu6.1) disco-proposed; urgency=medium
* lp1820068.patch: don't skip read cache when options are set (LP: #1820068)
* reenable ubuntu/parser-conf-no-expr-simplify.patch
-- Jamie Strandboge
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1764087
Title:
Wrongly boots into low graphics mode
so it is, thanks! So I think we can say this original bug is obsolete /
already fixed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1690051
Title:
pulseaudio crashed
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/370689
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
Verified 1.361.4 on Xenial, 1.417.3 on Bionic and 1.431.1 on Disco.
root@x-proposed:~# for i in $(apt-cache show ubuntu-wsl | grep Version: | awk
'{print $2}'); do echo '$' apt-cache show ubuntu-wsl=$i '|' grep dbus ;
apt-cache show ubuntu-wsl=$i | grep dbus; done
$ apt-cache show
I can confirm as well, 237-3ubuntu10.25 fixes the issue for me.
--
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/1833671
Title:
bond interfaces stop working after restart
attached windows recording sample
** Attachment added: "recording under Windows"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1838253/+attachment/5279809/+files/micwindowsGIGABYTE%20X570%20AORUS%20ELITE.m4a
--
You received this bug notification because you are a member of
Public bug reported:
When recording sound under Ubuntu 18.04 there is a whine/beep present.
This is not the case under Windows 10, as such I suspect missing
driver/software bits.
See attachments for audio samples of both cases.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base
** Tags added: eoan
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor quality
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1838208
Title:
Wifi stops responding sporadically on
This sounds like it happened around the same time as Mesa got upgraded
from v18 to v19.
Although it also sounds like a kernel problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/
--
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/1837937
Title:
CRASH
Status
Public bug reported:
Ubuntu 16.04LTS
OS Version： 16.04.5
CUPS Version： 2.1.3
Ghostscript Version： 9.18
ppd updating unexpectedly after printing job finished
We(RICOH printer driver developer) got a bug report from the users of our
printer:
We changed the UI setting(DefaultRICyan,
linux-generic-hwe-18.04 will switch to 5.0 soon.
linux-generic-hwe-18.04-edge can be used to switch to v5.0 kernel right
away.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Thanks for the log file(s). Unfortunately that last one covers several
days.
Could you please record the system log for the short period of time
while reproducing the bug again?
1. In a terminal window run:
journalctl -f > newlog.log
2. Reproduce the bug again.
3. Ctrl-C in the terminal
Thanks for the log file(s). Unfortunately that last one covers several
days.
Could you please record the system log for the short period of time
while reproducing the bug again?
1. In a terminal window run:
journalctl -f > newlog.txt
2. Reproduce the bug again.
3. Ctrl-C in the terminal
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: bluez (Ubuntu)
Status: Incomplete => Invalid
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Invalid
** Summary changed:
- apps use speakers when bluetooth headset is active (REGRESSION)
I rebooted before submitting this bug report using ubuntu-bug, so syslog
is probably the wrong one. I'll attach the previous one (syslog.1) which
I think covers the test demonstrated in the video (and several earlier
attempts).
** Attachment added: "syslog.1"
Public bug reported:
Attempting to slide the "Connection" switch in the gui to connect a
bluetooth device fails initially -- the switch moves but "snaps back" by
itself immediately. Clicking on the switch flashes the "busy"
indicator momentarily, but the switch does not move. After a while,
68 matches
Mail list logo
