Status in xorg package in Ubuntu:
New
Bug description:
Dell Precision 3660
I upgraded BIOS to 2.11.1 which also upgraded some other things.
When I login into Xubuntu I get a frozen gray screen
jim@jim:~/Scripts$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu
Public bug reported:
Dell Precision 3660
I upgraded BIOS to 2.11.1 which also upgraded some other things.
When I login into Xubuntu I get a frozen gray screen
jim@jim:~/Scripts$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
jim@jim:~/Scripts
> Does it still happen on Ubuntu 22.04 (and 23.04)?
22.04 deprecates engines, so this ticket is not relevant beyond Focal.
> Can you reproduce it without the engine?
Nope, you have to use the TPM engine.
To replicate, you need to generate a key pair in the TPM. Persist the
private key into
Public bug reported:
The look utility has more or less stopped working, i.e. it finds results
for some words but not others.
Example: look answ, among many others, returns nothing while a grep of
/usr/share/dict/words returns matches.
All the links to /usr/share/dict/words appear to be correct.
Public bug reported:
I'm using:
bsci@ip-10-132-42-225:~/test$ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
bsci@ip-10-132-42-225:~/test$ apt-cache policy openssl
openssl:
Installed: 1.1.1f-1ubuntu2.10
Candidate: 1.1.1f-1ubuntu2.10
Version table:
***
Public bug reported:
Downloaded and installed Turboprint driver for Canon iP90 but balked at
the high ($55 USD) price. The 30 day free trial ended and I found that
the iP90 printer would operate after installing the iP110 driver (with
the iP90-Cups or the iP90-Gutenprint drivers, it would only
Public bug reported:
The following always returns size of Letter regardless of what the
default is set to at localhost:631. This is the case for multiple
printers and printer manufacturers.
cups_size_t size;
int count = cupsGetDestMediaDefault(CUPS_HTTP_DEFAULT, m_dest, m_info, 0,
);
Ubuntu
** Also affects: debconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1634508
Title:
Clients cannot connect when
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Jim Denny (bluedanser)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1773859
Title:
Upgra
This bug affects me, too, on an amd64 system after an in-place do-
release-upgrade upgrade from 18.04 LTS yesterday.
I have no interactions with an OpenWRT box, though.
My config is currently a WiFi connection away from home, with an
automatic OpenVPN tunnel to my router at home, using split DNS
m is.
How can I fix these permission issues as a workaround while you
investigate this bug.
Thanks.
Jim!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion:
Just tried upgrading my Xubuntu 19.10 desktop to 20.04 and I'm now
getting the same staircase effect. Video card is an AMD Radeon RX 5700
XT which is connected with a DisplayPort -> DVI-D cable to an ancient LG
W2252TQ monitor with a resolution of, yes, 1680x1050. It is the only
monitor connected.
Public bug reported:
Failed during do-release-upgrade from 18.04.4 to 20.04.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cron 3.0pl1-136ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
In trying to recreate the issue this afternoon, it looks as though
installs based on all of the updated / most recent packages are
succeeding again (i.e., this may no longer be an issue).
In our dpkg logs, we noticed that an update came through today for libc-
bin (2.27-3ubuntu1), and wonder if
We are doing additional testing here. Please sit tight / do not research
further until we check into things further on our end.
Thanks again for your help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in
Before I continue - I want to say thanks for your response to this
report. I appreciate your effort and help.
As for the issue, when I say, "If I only install the latest packages" I
mean a fully up-to-date system at the time of install, including sssd
version 1.16.1-1ubuntu1.4. As part of my
... I tried this following Leonidas' (leosilvab) request to "Could you
downgrade to the previous version and check if it happens there too? And
so re upgrade and re-test?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
If I only install the latest packages (without the earlier versions of
these packages being installed previously) (i.e., if I do a clean
install of the most current packages when deploying a new host), it does
not work.
If I downgrade the packages to the prior versions, and then upgrade the
After allowing the packages to be upgraded to their newer versions, the
problem does _not_ persist. We see expected / desired results.
We only get a good outcome after the packages have been upgraded,
though. When the packages are installed as the initial versions ... that
is when we consistently
I will try updating the packages to their current-released versions and
see if the problem persists. We ran into this issue across several 18.04
deployments yesterday, though. It prevented commands like `id -u
username` from working (at least that is how we initially noticed a
problem).
I'll
We are using SSSD version 1.16.1-1ubuntu1.4 on Ubuntu 18.04.3. The
package itself is from the standard Ubuntu repos.
$ dpkg -s sssd
Package: sssd
Status: install ok installed
Priority: extra
Section: metapackages
Installed-Size: 32
Maintainer: Ubuntu Developers
Architecture: amd64
Multi-Arch:
When downgrading to the prior package, we do not see this problem.
We've taken the following steps as a work-around:
- apt-get -y --allow-downgrades install libsasl2-2=2.1.26.dfsg1-14build1
- apt-get -y --allow-downgrades install
libsasl2-modules-db=2.1.26.dfsg1-14build1
- apt-get -y
Public bug reported:
We are seeing the following in the journal after upgrading to these sets
of packages:
libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1
amd64
libsasl2-modules/bionic-updates,bionic-security
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64
Bug also affects me:
VGA compatible controller: NVIDIA Corporation GF106GL [Quadro 2000] (rev a1)
I was running dual monitors.
After reboot second monitor is not recognized.
Primary monitor displays as 'Default'. Only one resolution setting is available
I have Driver nvidia-driver-390
This happened to me when I upgraded from 16.04 LTS to 18.04 LTS, I
noticed error dialog boxes during the install but unsure if they are
related.
The /etc/resolv.conf contained:
# Generated by NetworkManager
search lan
nameserver 127.0.0.53
I compared it to a fresh install of 18.04 and this
I found this thread via Google, trying to fix the Bluetooth pairing of
my Bose QC35 (version 1) running Ubuntu 16.0.4.6 on a ThinkPad X230.
Whilst trying out a few things I managed to solve my problem by
temporarily disabling my VPN. Might have been a random coincidence but I
wanted to leave this
Looks like the same issue I'm having on Thinkpad X1 Carbon 7th Gen
running Ubuntu 19.04.
Debug output here:
http://alsa-project.org/db/?f=5c09dfb7b0fc0ff5ad32c0576893316f5613d3a1
As well as the Mic not being detected, and therefore not available for
use in any applications, there is an issue
Public bug reported:
I just cant figure it out.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.6
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Tue
I see this error in 18.04. The error recommends I try running a command
$ InstrumentationBrowser
(InstrumentationBrowser:24156): GdkPixbuf-WARNING **: 15:24:47.916:
Cannot open pixbuf loader module file '/usr/lib64/gdk-
pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
This likely
Public bug reported:
Description:Ubuntu 18.04.1 LTS
Release:18.04
network-manager:
Installed: 1.10.6-2ubuntu1.1
Candidate: 1.10.6-2ubuntu1.1
Version table:
*** 1.10.6-2ubuntu1.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500
I'm still on 18.04, but this problem remains for me, as well.
Grub with noresume doesn't work
RESUME=none doesn't work
RESUME=/dev/mapper/ubuntu-root doesn't work
RESUME=/dev/mapper/ubuntu-swap doesn't work
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I've added a similar comment / request on this related launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
Seems okay now, after typing exit and following the commands to run the
(fsck.ext4 /dev/mapper... something) command that it had listed and
following the prompt to fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Yes can’t boot into system after updating this morning.
Initramfs
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in
Public bug reported:
none
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu21.4
ProcVersionSignature: Ubuntu 3.13.0-160.210-generic 3.13.11-ckt39
Uname: Linux 3.13.0-160-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
Date: Tue Oct 2 09:36:51
** Changed in: lightdm (Ubuntu)
Status: Fix Committed => 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/1228079
Title:
Login issue: Lightdm + LDAP +
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jim2793 F pulseaudio
/dev/snd/controlC0: jim2793 F pulseaudio
Date: Wed Dec 13 00:03:34 2017
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more
Same issue here on Ubuntu 16.04 as descried.
Nvidia Driver 384.90-0ubuntu0.16
4.4.0-98-generic
system up to date
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1542782
Public bug reported:
Error occurred while upgrading Ubuntu 16.04 to 17.10. Other errors
occurred during the process. System appears to be working normally
after upgrade.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu
Public bug reported:
Simple scan driver install failed
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libperl5.26 5.26.0-8ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date:
Isak: yeah same here, that usually has to do with bluez still querying
for other devices in the background and sucking up all of the channel
bandwidth. It really needs someone to investigate if we can get bluez to
not consume so much bandwidth, or make the query period more context
sensitive such
apt-get upgrade reported that gdb was up to date. However, removing and
re-installing gdb with apt-get got it working again.
The gdb packaging? The upgrade procedure?
I have a copy of the systems with bad gdb instances if anyone would like
to take this on.
But for now, I'm out of the woods...
Yes I've experienced the same kind of jitter. The volume level is pretty
decent for me, but not the streaming performance. I basically need to be
doing nothing else on my laptop for it to stream without jittering.
--
You received this bug notification because you are a member of Ubuntu
Touch
After logging in, my actual tests move several gigabytes of http traffic
- downloads of incompressible data in files ranging from 16KB to 16MB -
complete without incident.
I've been resorting to establishing an ssh control channel while the
test laptops are in short range, then taking them to the
Public bug reported:
This is a weird one. I use a small fleet of laptops to do professional
network testing, and I wrote some tools that use SSH with pubkey auth to
run simultaneous tests.
The problem is, if the wifi connection isn't superb, the auth times out
more often than not. For example,
> So I think this is something that you will want to fix in your image
> mastering scripts.
I agree and am fine with this being marked INVALID.
However, is juliank's note about the implementation of After= a concern
w.r.t. how LP#1693361 was resovled?
--
You received this bug notification
Hmmm. I confirm what you see.
I think this problem is arising because we have Packer run (due to LP#1693361):
systemctl disable apt-daily.service
systemctl disable apt-daily.timer
when building the AMI.
I guess if apt-daily.service is disabled the Before is not transitive
from
Confirm on this bug with hardware:
HP Z230, Intel Raid bios, Ubuntu 16.04.2.
--
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/1587142
Title:
Shutdown hangs in md kworker
"Applications can no longer access your [gmail address]. Choose Online
Accounts from the user menu to reinstate access to this account."
This bug is still present in 17.04 with Gnome. I don't think it was an
issue until I entered the information for my Google account in Online
Accounts. Now, the
** This bug is no longer a duplicate of bug 1639776
name resolution (dnsmasq) fails to send queries out after suspend/resume
reconnects the interface
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
We don't need this anymore, so switched to won't fix.
** Changed in: mediaplayer-app (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: mediaplayer-app
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I also have this issue. Running "alsactl restore" will allow sound to
come through the headphones without rebooting, but this is suboptimal. I
have attached my alsa-info output.
** Attachment added: "alsa-info.txt.vU4MuqgaEu"
Hi, Daniel,
Appears to be fixed entirely now. I was running Ubuntu 12.04 when I
first encountered the bug, and if memory serves it was fixed at least a
year or two ago. I'm currently running 16.04.
Thanks for responding.
--
You received this bug notification because you are a member of
** Package changed: powerman (Ubuntu) => pm-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1680750
Title:
pm-hibernate does nothing at all
Status in
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Michał Sawicz (saviq)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1577641
Title:
Unity8
** Summary changed:
- The bluetooth headset can not control the media playback
+ The bluetooth headset cannot control media playback
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
Failure on upgrade.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu Jan 26 23:57:33 2017
** Changed in: canonical-devices-system-image
Assignee: John McAleely (john.mcaleely) => Jim Hodapp (jhodapp)
--
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/1398
in: canonical-devices-system-image
Assignee: John McAleely (john.mcaleely) => Jim Hodapp (jhodapp)
--
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/1620636
Title:
Fa
@Robin: yeah after a reboot or after simply turning the headphones on
and off again, pairing doesn't work. I need to use the Bose Connect app
on my phone to delete the remembered pairing, delete it from Ubuntu, and
add a new pairing from the app and pair from Ubuntu. Only then does it
work.
--
@Will: thanks for confirming that. I removed media-hub from the list of
affected packages.
** No longer affects: media-hub (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
@Will: Are you sure media-hub is running in this session and actually
being utilized? Check in ~/.cache/upstart/media-hub.log (this log may be
located elsewhere in Unity8 session on the desktop, I'm not entirely
sure).
--
You received this bug notification because you are a member of Ubuntu
Reply back here if anything like this comes up again and we can discuss
re-opening this bug.
** Changed in: media-hub (Ubuntu)
Status: Incomplete => Invalid
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Invalid
** Changed in: qtmultimedia-opensource-src (Ubuntu)
@Robin: Yeah I've been able to get mine working as well. Were you trying
with Ubuntu desktop or on Ubuntu Touch? The choppiness seems to be bluez
doing other device scans. So on Touch, if you make sure that system
settings is in the background, it should remain nearly chop-free. On the
desktop, it
Replaced the Radeon with a Geforce 710 eliminating a Cirago DisplayPort to
HDMI adapter and the problem went away.
On Fri, Oct 21, 2016 at 12:09 PM, Jim Tarvid <tar...@ls.net> wrote:
> Public bug reported:
>
> This defect is not apparent on two other Ubuntu 16.04 machines. The
>
@Andrea, Anupam, Robie: That's interesting indeed and might explain why
I've never been able to reproduce this myself. I would always have been
actively engaged with the phone when trying to reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@Andrea: media-hub manages the playback state of nearly all playback
sessions on Ubuntu Touch. It utilizes pulseaudio for the sound server.
Any sounds coming from the web browser or web apps do not use media-hub.
Ringtone and notification sounds all go through media-hub for playback.
--
You
I can confirm that the aspect ratio is incorrect, both for the inline
video scope playback and in mediaplayer-app. It seems to be stretch
vertically.
** Also affects: qtvideo-node (Ubuntu)
Importance: Undecided
Status: New
** Project changed: mediaplayer-app => media-hub
** Project
Btw, I confirmed this on turbo running image #r219.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtvideo-node in Ubuntu.
https://bugs.launchpad.net/bugs/1634261
Title:
Wrong aspect ratio for video playback
Status in
Public bug reported:
sudo aptitude upgrade
...
Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) over (1.0.1ubuntu2.14) ...
Errors were encountered while processing:
/var/cache/apt/archives/libnss3_2%3a3.23-0ubuntu0.14.04.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A
Will get to landing the QtMultimedia patch sometime soon.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1630399
Title:
[Phone] Please enable opus
This will need to see if it's reproducible for anyone else in order to
begin to determine what package this should be properly filed under.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
@Ben: ok thanks for checking on that. So the issue is not with media-hub
then since qtubuntu-media is required for the Unity8 apps to utilize
media-hub. Without qtubuntu-media installed, the apps will use the
default gstreamer-based plugin in QtMultimedia that should utilize the
pulsesink in
I am also still affected by this bug. I build small Ubuntu-based
routers, and the ones running Xenial are very likely to fail to get new
leases after the connection drops from the ISP, or if they're booted
while the connection to the ISP / the ISP's edge device is down.
I'm having to resort to
@Ben: can you please check if qtubuntu-media is installed on your
system?
** Changed in: media-hub (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Public bug reported:
This defect is not apparent on two other Ubuntu 16.04 machines. The
upgrade to 16.10 did not change the symptoms.
lsb_release -rd
Description:Ubuntu 16.10
Release:16.10
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
This bug is easy to fix. For example, it will be caused by a section
like this:
zh-cn
zh-sg
The correct syntax would be
zh-cn
zh-sg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@pat: have added this to the backlog of things to investigate. Will see
if it's possible to reliably reproduce this issue and identify the root
cause.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
@Pat: I was looking into this a bit more the other day, reading the
attached logs. This no longer seems like a media-hub issue and instead
seems more like an issue at one of the higher software layers. If you
look at the time in the media-hub logs where Anupam has stated it
happened to him, you'll
** Description changed:
I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41
from installed from yakkety archive), nor using Ubuntu Touch rc-proposed
build for Turbo #174. I'm trying to pair through the
Anupam: your last 3 comments have been the start of some useful
information. Thanks for observing more closely and providing the logs
along with time reference to look at the logs. Very helpful, thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Let's keep the autopilot stuff out of main.
Here's an MR from renato that adds some build tests:
https://code.launchpad.net/~renatofilho/mediaplayer-app/add-
unittest/+merge/306784
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@Anupam: sorry to hear that you're still experiencing this issue. It's
been a difficult one to pin down indeed. I've yet to reproduce the same
symptoms that you're experiencing. That being said, if you can continue
to try and notice much more precise times that it occurs and document
those here,
Thanks Saviq, I don't have this device so I've not seen it personally.
But that's very good info to have.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1617975
Title:
I need an opinion from the Unity8 team on whether they think this might
be an issue with Unity8 or perhaps something more specific to
mediaplayer-app. I've not been able to reproduce this on any other
device other than frieza.
--
You received this bug notification because you are a member of
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8
Public bug reported:
I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41
from installed from yakkety archive), nor using Ubuntu Touch rc-proposed
build for Turbo #174. I'm trying to pair through the normal
@Pat: that doesn't look right. For a normal case, you should only see
one Engine: playing uri: ...
Normal output should look like this:
[II 2016-09-01 12:58:26.995539] [engine.cpp:73@on_playbin_state_changed] State
changed on playbin: READY
[II 2016-09-01 12:58:26.995731]
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
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/1612367
Title:
[Touch] Incoming call gets
You'll want to try again with OTA-13 once it's released. My hunch is
that it will greatly help in reducing this issue as various system
components will now be able to reconnect to media-hub-server after a
crash.
--
You received this bug notification because you are a member of Ubuntu
Touch
Added qtmultimedia to the affected list to capture future effort to more
permanently fix this bug. Recovery after a media-hub-server crash really
belongs in qtmultimedia so that every supported client is able to
continue playback even after a media-hub-server crash.
** Changed in:
@Alfonso: well it is *a* cause but not necessarily all causes. I knew
that this was reproducible if you killed media-hub-server or it crashed
on its own and I did take care of several cases of unhandled exceptions
that would cause media-hub-server to crash. Having said that, ahayzen is
working on
@Anupam: with OTA-12 you already have the fix for bug #1596329. The
other one will come with OTA-13. Until we know what the cause is though,
which many people have been trying to identify, it'll be very difficult
to make sure that it's fixed. I appreciate your patience as we try and
figure this
@Michal: which device are you using?
--
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/1544477
Title:
No sound notification for new SMS (Ubuntu Touch)
Status in
@Michal: can you reproduce it reliably? What were you doing when you
noticed it wasn't working? Are Telegram notifications working for you
right now? How about alarms in the clock app? Can you play music from
the music-app?
--
You received this bug notification because you are a member of Ubuntu
Marked this bug as incomplete. If anybody sees this issue with OTA-12
and can reliably reproduce the issue, we'll reopen this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
It's possible that a fix that I landed in OTA-12 that took care of a
nasty thread deadlock issue took care of this issue, or at least once
trigger of it.
** Changed in: canonical-devices-system-image
Status: In Progress => Incomplete
** Changed in: indicator-sound (Ubuntu)
Status:
@Alfonso, @Pat: that's the issue I mentioned yesterday. Sounds like
something that might be a hole in QA testing that we should bring up
with that team.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Changed in: ofono (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: dialer-app (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
1 - 100 of 488 matches
Mail list logo
