Customer installed U18.04 Dell OEM and that works as expected. We can
drop the severity. I installed the Base Dell OEM image to confirm the
issue. When I first booted the issue was not there. Then when I loaded
the updates/upgrades and rebooted the segfaults came back. I have
nothing else inst
Any updates on this bug? Is there anything else I need to provide you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820323
Title:
amdgpu-pro xorg crash
To manage notifications about this bug go
https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Is
there a solution or workaround for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820323
Title:
amdgpu-pro xorg crash
To ma
The uninstall and reinstall of amdgpu-pro has not worked for me. I have
also tried to purge amdgpu-core and amdgpu-dmks which I was told by
others got around this issue. I have not been successful thus far. Any
other suggestions and or logs needed to help me find a suitable
workaround until this
Is there any updates on this bug? Anything you need me to collect?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821264
Title:
gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04
Any updates on this bug? What is needed from the customer or Dell to
isolate this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821264
Title:
gnome-software from xps 13 9365 with Dell-oem running
I loaded the default debug symbols and I see Reading symbols from gnome-
software... (no debugging symbols found)...done. I then tried to load
all and still I receive no debug symbols. It is not that I didn't load
them, it is I have no idea what the debug symbol for gnome-software is.
Can you con
I googled and found you could get more information with running the
gnome-software --verbose. Attaching that file in case it helps. There
was no gnome-software-dbg or gnome-software-dbgsym to install and or
download, I checked.
--
You received this bug notification because you are a member of U
** Attachment added: "command run with verbose"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+attachment/5252581/+files/gnome-verbose.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Backtrace is not working since there are no debug symbols example
attached
** Attachment added: "backtrace no debug symbol"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+attachment/5252582/+files/gdb-gnome.txt
--
You received this bug notification because you are a m
dmesg -T | grep seg
[Wed Apr 3 14:52:31 2019] pool[18867]: segfault at ffb8 ip
7f8bf01e1b97 sp 7f8bca5b0938 error 5 in
libappstream-glib.so.8.0.6[7f8bf01c5000+42000]
[Wed Apr 3 14:57:24 2019] pool[25609]: segfault at ffb8 ip
7fa7ef7d3b97 sp 7fa7ccae3938
backtrace
** Attachment added: "backtrace"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+attachment/5252584/+files/gdb-gnome2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
backtrace
** Attachment added: "backtrace"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+attachment/5252585/+files/gdb-gnome2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I ran backtrace with --verbose so hopefully that helps as well attaching
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821264
Title:
gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.
backtrace
** Attachment added: "backtrace"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+attachment/5252583/+files/gdb-gnome2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Valgrind output
** Attachment added: "valgrind"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+attachment/5252595/+files/valgrind.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
apport logs
** Attachment added: "previous apport"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+attachment/5252624/+files/apport.log.3.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
This is on Precision 3620, Precision 5820, Precision 7820 - systems with
AMD bundled for OEM fail to properly boot after update/upgrade. I
believe this is related to this issue:
https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory
Since our image contains the amd
Public bug reported:
installing Dell Oem.
Running update/upgrade
sudo -s
sudo apt-get update && sudo apt-get upgrade -y
Then running gnome-software results in the GUI loading but after 10
seconds it crashes and you see a segfault.
I tried information in +Bug/1798236 but U16 does not have a later
attaching now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821264
Title:
gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04
segfaults
To manage notifications about this bug go t
Is this related too https://bugs.launchpad.net/ubuntu/+source/gnome-
software/+bug/1781996
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821264
Title:
gnome-software from xps 13 9365 with Dell-oem
** Attachment added: "backtrace"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+attachment/5248638/+files/gdb-gnome.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821264
Dell OEM image with updated kernel has the qca\qca6174 fix. I reloaded
the dell image and have not been able to reproduce this issue with LE BT
mouses. I will let it run and confirm. So it looks like the issue is
just with the generic image not dell image. non-oem.
--
You received this bug no
To add to this the following URL suggests the support and drivers should be
bundled:
https://certification.ubuntu.com/hardware/201803-26164/
The Dell OEM image does not house the drivers, nor does the Canonical
image. Is this expected? Should there be documentation on how to get
this working wi
Does this cert indicate only Realtek is certified?
The lsusb output is:
Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass
The information Nick previously provided was how they got around the
issue using the Kali opensource drivers. Would you like us to follow
https://pcsclite.alioth.debian.org/ccid.html#support to get you that
information.
--
You received this bug notification because you are a member of Ubuntu
Bug
Following https://help.ubuntu.com/community/CommonAccessCard
Does not work to get the smartcard reader working.
pcsc_scan returns
'Waiting for first reader'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
The link is not working. Skip that. I have the following commands in case it
helps:
*-usb
description: Mass storage device
product: DataTraveler 3.0
vendor: Kingston
physical id: 1
bus info: usb@2:1
logical name: scsi0
version: 0.01
seria
I am asking our colleague Juan to respond but yes these are 2 bugs that
are duplicate of each other. Let Juan know what you need from us to
take this further?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
1813208 is a duplicate of this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812446
Title:
Bluetooth mouse stops responding after 24-48 hours of connectivity
To manage notifications about thi
Daniel, my name is Jill and I have the customer's capture so I have to
run the apport-collect from the customer's system. Juan is our back
line engineer that opened the case with you so we could have Canonical
and Dell collaborate. If this is not correct. How can I get you the
data?
--
You rec
Public bug reported:
Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso
Bluetooth mouse tested with HP X4b BT Last mouse stops responding
after long extended deep sleep (24-48 hours).
Bluetooth settings window which initially reported Bluetooth as
connected now shows disconnected. Pushing
*** This bug is a duplicate of bug 1814925 ***
https://bugs.launchpad.net/bugs/1814925
running ubuntu-bug bluez; I received a new bug id 1814925. These bugs
are all related.
** This bug has been marked a duplicate of bug 1814925
Bluetooth mouse stops responding after extended deep sleep
*** This bug is a duplicate of bug 1814925 ***
https://bugs.launchpad.net/bugs/1814925
running ubuntu-bug bluez; I received a new bug id 1814925. These bugs
are all related.
** This bug has been marked a duplicate of bug 1814925
Bluetooth mouse stops responding after extended deep sleep
** Description changed:
Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso
- Bluetotth mouse tested with HP X4b BT Last mouse stops responding
+ Bluetooth mouse tested with HP X4b BT Last mouse stops responding
after long extended deep sleep (24-48 hours).
Bluetooth settings wi
More detailed information on this issue is below:
The customer has Ubuntu OEM through Dell. The laptop goes into deep sleep over
night and they can no longer use their BT devices. You click on bt via GUI and
try to toggle on and it looks like it is doing something and goes right back to
off.
I am told by internal engineering the Qualcom fix below is being tested
for this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=2ddd8f0f33972a96f34722de6165ed88a6231f9d
Can you get me more information about this and when it is being
released?
--
Y
37 matches
Mail list logo
