It's fixed in ubuntu 23.10, thanks to kernel 6.5 I guess.
--
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/2024680
Title:
Dell XPS 9730 no sound, I have tried the 22.04
I have the same issue after a recent kernel update. Not sure if the
cause is the same, but after about 5 hours looking to the issue, the
mostly likely cause seems well explained on this bug comment:
https://bugzilla.kernel.org/show_bug.cgi?id=208061#c5
In my case.
Distro v: 20.04.6 LTS
Kernel v:
I am experiencing this problem too. using VNC (tigervnc-standalone-server).
I read the entire thread. I tried damn near all of the workarounds. None worked.
The symptom is that I can't start Firefox in my xfce4 session .
madbrain@u22041:~/Desktop$ firefox
/system.slice/vncserver.service is not a
Public bug reported:
There is a missing dependency that makes using GTK/GDK from Python a bit
brittle.
GTK/GDK uses cairo for drawing, so having GTK/GDK means that cairo is
available and can be used.
However, having the Python bindings for GTK/GDK currently doesn't
guarantee that the Python
@lotuspsychje: I have the same problems as the ones you mention in
lp:1949183.
** Description changed:
There is a problem with Cheese on 22.04 beta (image shows up scrambled
- even though it works as expected when I visit www.webcamtests.com).
+ even though it works as expected when I visit
Cheese issue filed in upstream project:
https://gitlab.gnome.org/GNOME/cheese/-/issues/139
** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #139
https://gitlab.gnome.org/GNOME/cheese/-/issues/139
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Attachment added: "Screenshot from 2022-04-13 16-31-40.png"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1968855/+attachment/5580362/+files/Screenshot%20from%202022-04-13%2016-31-40.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
There is a problem with Cheese on 22.04 beta (image shows up scrambled
even though it works as expected when I visit www.webcamtests.com).
I tried to report the problem using `ubuntu-bug cheese`.
I am asked if the problem is with Cheese, or with the image shown in
Cheese. I
I can confirm crash on latest 20.04 is still there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1871959
Title:
Xorg crashed with SIGABRT in _iris_batch_flush from
Hello,
Thanks for your answers. I did a full update/upgrade and install latest
displaylink driver. I'll let you know if crash still here.
"X server crash in iris driver" subject is still open, no news since 8
months. Any way to know if it's still in progress or if it's on pause? I
just try to
Hello,
You spoke about a fixed in your comment on 2021-06-22
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/comments/30
. Is that to say that no fix will be part of Ubuntu next LTS version
22.04?
I see your link on mesa. No reponse since 8 months. In your comment on
2021-03-05 you
Hello Daniel,
So far I still have the issue on Ubuntu 20.04 LTS. Can you tell me if
the patch will be in next 22.04 LTS ? Or maybe there's a way to patch
20.04?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa
if patching the PulseAudio default.pa works, then the initial issue was
probably a problem with alsa-ucm-conf not being updated in your distros.
There's no reason to use asound.state these days, it's a much better
idea to use UCM. my 2 cents.
--
You received this bug notification because you are
Well, maybe or not but I don't understand how to install the patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1871959
Title:
Xorg crashed with SIGABRT in
Hello,
Any news on when it will be solved ? No update solved it on my ubuntu
with officials updates.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1871959
Title:
@Sebastien Sorry for the late reply.
I recall that the workaround consisted in adding a random delay to the
apt-daily task, so that it would not happen *right* at startup.
How exactly this was done, unfortunately, I did write it down :-/ but I
think it was adding or creating the file
Hi,
Last message seems to indicate that a fix is found, good news! Anything
to do to get the fix?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1871959
Title:
Hello,
I sent a mail to DisplayLink, here is their answer...
"
Thank you for bringing it to our attention but based on the log files and
errors over there the best way would be to discuss it with Xorg engineers as
the majority of problems comes from the OS itself and not from our driver here.
"
Hi, thanks,
can't I just do a sudo apt purge linux-generic-hwe-20.04 ?
For now, i'll keep the choice to boot on kernel 5.8 or 5.4. About the
subject you opened on
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 it seems to have
some news. That's very technical, can you put here
Hello,
This is why you have no report from kernel 5.8+ :
"The supported kernel version range is from 4.15 to 5.5, minimum supported Xorg
version is 1.16 and minimum supported Mutter (Wayland) is 3.32."
https://support.displaylink.com/knowledgebase/articles/684649
Some people seems to have
Hello,
Well I tried... and have some troubles :). After reboot, displaylink didn't
work anymore. I tried to uninstall but when I try to reinstall, here what I
get :
ERROR (dkms apport): binary package for evdi: 1.7.0 not found
Error! Bad return status for module build on kernel:
Hi,
I created an account on mesa forum. I don't really know what to tell,
and which file send them. Can you help me and tell me what to say and
send?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
*** This bug is a duplicate of bug 1871959 ***
https://bugs.launchpad.net/bugs/1871959
Hi,
Ok thanks. In bug 1871959 you ask to report to mesa, what's "mesa"? I
don't think I have installed myself this. If it cause the bug, is it
possible to remove it?
Thanks,
--
You received this bug
Well if I couldn't use ubuntu bug, I could use that, hope it'll help :
apport-cli -c /var/crash/_usr_lib_xorg_Xorg.1000.crash
It then create this bug entry :
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915375
--
You received this bug notification because you are a member of
Oh I forgot, Yes, i have installed dbgsym :
$ dpkg -l| grep dbgsym
ii libgl1-mesa-dri-dbgsym:amd64 20.2.6-0ubuntu0.20.04.1 amd64 debug symbols for
libgl1-mesa-dri
ii xserver-xorg-core-dbgsym 2:1.20.9-2ubuntu1.2~20.04.1 amd64 debug symbols for
xserver-xorg-core
--
You received this bug
Hi,
Ok, if there's nothing here about xorg crash, how may I provide you more
information about that :
ppaquin@PORTABLE-PPAQUIN:/var/crash$ ls -alrt
.
-rw-r- 1 username whoopsie 17322105 févr. 10 14:15
_usr_lib_xorg_Xorg.1000.crash
It seems I have some informations on my system
Hi, one more crash for me, you'll find iris_dri error at 14:15:47 time
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1907142/+attachment/5462347/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Same problem with 20.04.
I believe this is related to this issue:
https://bbs.archlinux.org/viewtopic.php?id=255817 .
FTR, as `apt-daily.service` is running on startup, this was also
increasing my boot-time significantly (although I found a workaround for
this particular problem). Just to
Public bug reported:
follow up for https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1914573
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
I had the same problem.
- Since this bug only appeared by me by consulting the proprieties of the file
with Nautilus, and did not occur with linux mint 20 and Nemo, I reported it as
bug 1890958 in Nautilus.
- Since updates beginning of the year 2021 I can no longer reproduce it. It
seems to be
Hi Salima,
this bug has been identified as happening only for people who were
upgrading from a previous version of Ubuntu (that came with a previous
version of Pulseaudio). Daniel Van Vugt found a workaround (check
comments 18 and 19 above), and a fix has been made by the Pulseaudio
developers
Another correction. For the one workaround, switching to discrete
graphics in the BIOS only seemed to get past the initial gnome login.
But resuming from DPMS off/suspend, the same error loop happens even
when hybrid graphics is disabled in the BIOS.
Even worse, seems hardware acceleration ends
Apologies, continuing the comment above (mistakenly posted when adding
the log attachment). Let me retry.
Failure loop observed:
- Failed to blit shared framebuffer: EGL failed to allocate resources for the
requested operation.
- Failed to set CRTC mode 3840x2160: No such file or directory
To
Here's the script I run to workaround the intital failure of gnome to
use the external display after unlocking or resuming from DPMS
suspend/off.
** Attachment added: "fix-hdmi-uhd.sh"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh
--
Hi, thanks to everyone, especially Daniel for unpacking this issue.
I have had a very similar issue, where gnome shell fails to run my
external 4K/UHD display at 60HZ and I see the following failure loop
triggered in `journalctl -b -p warning _COMM=gnome-shell`:
May 02 20:39:38 JNBA434499PLL
@Daniel:
I've tried the workaround I've described in bug 1866194 comment 7, but
it doesn't work on this device.
As Rex mentioned, it's probably a known limitation... for the time
being, I'll use the HDMI audio output and plug my headphones to my
external screen (that works fine).
--
You
** Tags added: ce-qa-concern champagne
** Tags added: ubuntu-certified
--
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/1871329
Title:
No "Select Audio Device" panel
** Attachment added: "pactl_list_headphones.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348500/+files/pactl_list_headphones.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Attachment added: "pactl_info_internal_speakers.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348499/+files/pactl_info_internal_speakers.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "pactl_list_internal_speakers.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348501/+files/pactl_list_internal_speakers.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "pactl_info_headphones.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348498/+files/pactl_info_headphones.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Summary
===
Internal speakers work as expected, but when plugging headphones through
the 3.5mm jack, the "Select Audio Device" panel doesn't show up (it
normally shows up to allow user to select what kind of device has been
plugged in, be it headphones, microphone or
Installed bluez 5.50 -> same result.
Installed linux 5.3 -> same result.
Tried a combination of all the linux/bluez possibilites -> same result.
Until now, I was only looking at the output of btmon (so basically, low
level BT commands).
Then, while I was doing one of the tests above, I tailed
Please find attached my dmesg. I don't see anything related to
bluetoothd.
The same issue happens with two other BT devices (2 earphones from the
same brand, TaoTronics), so I'm pretty confident it's not a BT device
issue. Plus, as I mention, it works well with the same hardware (laptop
and BT
** Attachment added: "5.3.0-18-btmon-speaker.log"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869857/+attachment/5343689/+files/5.3.0-18-btmon-speaker.log
** Description changed:
Laptop: Dell Inspiron 7370
CID: 201704-25503
Ubuntu version: 20.04 daily
Linux kernel:
Public bug reported:
Laptop: Dell Inspiron 7370
CID: 201704-25503
Ubuntu version: 20.04 daily
Linux kernel: 5.4.0-18-generic
Bluez: 5.53-0ubuntu2
Summary
===
BT earphones/speaker cannot be connected either using GNOME control
center, either using bluetoothctl. I've tried with previous
I filed an issue upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832
** Bug watch added: PulseAudio #832
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Description changed:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503
Steps to reproduce:
- 1. Go to Bluetooth settings panel
- 2. Pair a BT device
- 3. Make sure it's marked as Connected, and go to the
** Summary changed:
- [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options
but the sound keeps being emitted from the internal laptop speaker
+ [Dell Inspiron 7370] shows up in the sound output options but the sound keeps
being emitted from the internal laptop speaker
--
*** This bug is a duplicate of bug 1850766 ***
https://bugs.launchpad.net/bugs/1850766
Daniel,
this bug is not a duplicate of lp:1850766. In lp:1850766, selecting the
output device back and forth is an enough workaround to make it work.
Here, doing so doesn't do anything, and the only
** Description changed:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503
Steps to reproduce:
1. Go to Bluetooth settings panel
2. Pair a BT device
3. Make sure it's marked as Connected, and go to the
Thanks a lot for the input, Ken!
You were right, it is not related to BT, but to the sound devices being
added and removed.
I happend to have a Zoom microphone that can be connected as USB and
creates a new audio interface (both input and output). Here are my new
tests and findings:
1. Plug the
** Tags added: ce-qa-concern rls-ff-incoming
--
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/1866194
Title:
After connecting a Bluetooth headset or speaker, it shows up
** Attachment added: "btmon_bt_speaker.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333852/+files/btmon_bt_speaker.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
** Attachment added: "pactl_list_after_bt_speaker_connected.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333856/+files/pactl_list_after_bt_speaker_connected.log
** Description changed:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic
** Attachment added: "btmon_pair_headset.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333853/+files/btmon_pair_headset.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio
** Attachment added: "pactl_list_after_bt_headset_paired_and_connected.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333854/+files/pactl_list_after_bt_headset_paired_and_connected.log
--
You received this bug notification because you are a member of
Public bug reported:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503
Steps to reproduce:
1. Go to Bluetooth settings panel
2. Pair a BT device
3. Make sure it's marked as Connected, and go to the Sound settings
4.
Sorry forgot that I commented out the updates and security repositories
in /etc/apt/sources.list . You can probably hold the python3-apt package
to get the same effect.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
sudo mv /etc/apt/sources.list.distUpgrade /etc/apt/sources.list
sudo apt update
sudo apt install python3-apt=1.8.4
sudo do-release-upgrade
That gets it going for Lubuntu 19.04 to 19.10 upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
if you can recompile a kernel, using Mark Brown's for-next should have
have all the latest changes from Google for Cyan.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Attachment added:
"pactl_list_before_switching_output_device_back_and_forth.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306132/+files/pactl_list_before_switching_output_device_back_and_forth.log
--
You received this bug notification because you are
I ran the following steps:
1. Power laptop on with bluetooth turned off
2. Turn BT on in gnome settings and set my BT headphones in pairing mode
3. Pair the headphones.
4. In Sound settings, it looks like the selected device is the BT headphones,
but if I play something it outputs on the laptop
** Attachment added:
"pactl_list_after_switching_output_device_back_and_forth.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306133/+files/pactl_list_after_switching_output_device_back_and_forth.log
--
You received this bug notification because you are a
Public bug reported:
Ubuntu 19.10 (using -proposed pocket)
Kernel 5.3.0-21-generic #22
pulseaudio 1:13.0-1ubuntu1
bluez 5.50-0ubuntu4
Device: Dell Inspiron 7370
Step to reproduce
=
1. Pair a bluetooth headset with the laptop
2. Go to sound settings
-> in "Output device", the
Sorry (again) for the late reply.
I just got an opportunity to install a fresh ubuntu 19.04, so I thought
I would give a try to the patch... But on this fresh install, I do not
have the problem... (without even enabling proposed packaged).
I don't even understand *why* the x11-bell module is
Sorry for the late answer.
In my case, the sound was the correct one, but it was played twice at
the same time, causing some unpleasant saturation.
Furthermore, if I changed the sound in the Gnome control panel, than I
would have two different sounds playing at the same time (the newly
configure
@Daniel
4/5. I collected the attached drminfo.txt while at login screen.
While in tty4, I noticed that the computer would freeze for more or less
long periods of time because of some nouveau-related kernel messages
that were printed on the screen. I managed to type the command you
mentioned
1/2/3. I made a fresh install.
On the first boot, device was blocked at the "Ubuntu" logo with the dots
blinking white and orange forever. Pressing Esc wouldn't do anything
(it's supposed to show the boot process) and pressing NumLock on the
numpad wouldn't light the NumLock LED (it's my to-go
To see a sample of dmesg when nouveau is activated, please refer to
lp:1822026
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1822047
Title:
After install, cannot boot into
Public bug reported:
System: Disco (19.04 beta)
Hardware: Dell Precision 7530
After installing the system, it cannot start unless manually adding
`nomodeset` in the kernel command line at boot time.
Steps to reproduce:
1. Install disco 19.04 beta on the device. Leave all the options at default
** Tags added: ce-qa-concern
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1821882
Title:
Screen is very dark and brightness cannot be adjusted
Status in xorg package in
I tried the same while blacklisting nouveau driver in grub:
$ cat /proc/cmdline
BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet
splash modprobe.blacklist=nouveau ---
This time, I have "acpi_video0" in /sys/class/backlight, but the result
is the same. The screen is
Public bug reported:
Device: Dell Precision 7530
In the BIOS, the Switchable Graphics option is deactived, which means only the
nVidia GPU is used.
When booting 19.04 beta live USB, the screen becomes very dark and
brightness cannot be adjusted. (The same issue happens with 18.04.2)
There is
It's a shot in the dark, but in my case, pulse sound server (atop of
alsa) seems to have gotten into a mess with an upgrade between 16.04 and
18.04. Post login, removing old / session start user config fixed my
dodgy channel mappings (but not quite the same as crackling, etc):
pulseaudio --kill \
Wish there was a "needs more info" tag or a way to tag bug reports like
this. There's no context as to exactly what the problem is despite the
alsa-info script output being supplied.
It's unfair to maintainers to expect them to fish out the problem.
"Sound bug ubuntu 18.04" is way too generic.
See
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774904/comments/4.
gnome-control-center should rather add libcanberra-pulse to depends
rather than just recommends.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hi, in my case, I think it was simply a missing package dependency.
Installing the libcanberra-pulse package fixed it for me.
gnome-control should probably add libcanberra-pulse to a proper
dependency rather than just recommends since it's likely common that
people would want to test speakers and
A fix [1] in LXC was pushed recently and actually allows systemd daemon-
reexec without the cap sys_admin in a container.
We tested that it totally solved the issue for us.
Would it possible to move this bug report to the LXC project? And to ask for a
backport of such fix to Xenial LXC?
Thanks!
** Changed in: hud (Ubuntu)
Assignee: (unassigned) => pierre (pierrefischer)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1165420
Title:
Unable to access indicat
I can confirm that this is fixed in (at least) 18.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1452193
Title:
Backends can't look at FINAL_CONTENT_TYPE to determine
Same issue here on T570 running Manjaro, this is the only bug report talking
about the problem which seems not related to Ubuntu but to alsa. All sliders
are up in alsamixer, sound is around half-volume compared to the Windows
install. ALSA Driver Version: k4.14.67-1-MANJARO.
these did not
: Linux 4.4.0-131-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pierre 1521 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Aug 1 18:28:12 2018
InstallationDate: Installed on 2016-10-12 (658 days ago
I have the same problem of power drains even when prime-select is on
intel. I know for sure that the nvidia GPU is running because the
external HDMI port is working and shouldn't since it's wired to the GPU.
sudo sh -c 'echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control'
sudo sh -c
Ok I troubleshot this problem.
Apparently, it came from the package `connman`, an Intel utility to
manage wlan and bluetooth that I installed wrongly since it's intended
for embedded systems.
Removing it solved all my problems.
** Package changed: bluez (Ubuntu) => connman (Ubuntu)
** Changed
Yes it looks like the same bug (at least for the GUI part), and it's a
Thinkpad as well.
--
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/1762603
Title:
bluetooth keeps
Same bug on Ubuntu 18.04 / Thinkpad P51.
--
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/1738838
Title:
Bluetooth icon shows "Off" and the only option given below it is
Also I have tried with blueman instead, with and without acpi-calls-
dkms, tp-smapi-dkms, tlp installed, the issue remains.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
I mean reboots.
So, on boot, the airplane mode is turned on by default (for an unknwon
reason).
The rfkill output is attached above. I have to trigger several `sudo
rfkill unblock all` to actually have them unlocked (in command line).
But then, the GUI still shows the bluetooth switch as OFF.
Public bug reported:
the bluetooth worked well right after install. After a few reboots, it's
impossible to keep it on and to connect devices.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux
Sorry. Mistyped. Read initramfs SETS UP wrong ..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1752528
Title:
initramfs swretu up wrong swap partition for
Public bug reported:
I have a low end laptop on which using zram to improve memory (2GB only)
is critical.
When I have zram-config installed and running, every kernel update tells
initramfs to try to resume from /dev/zram0 (which it can't it's
compressed virtual memory!)
At next reboot,
with the kernel release which
began to manage Intel graphic cards.
I remember, without warranty, having feared the worse at that moment,
_before_. Since, perhaps with Unity a crazy process is remaining on
awakening.
Pierre Wilch
Le 16/02/2018 à 01:20, Christopher M. Penalver a écrit :
> Pie
, Christopher M. Penalver a écrit :
> Pierre Wilch:
>
> 1)
>> "So long I remember, this bug appeared before september 2017. No problem in
>> year 2016."
> What version of Ubuntu were you using in 2016 when this was not reproducible?
>
> 2) To further root cause
A new xorg version has been installed yesterday 14.02.2018.
I could make a video of the problem on my screen before that installation, and
have joined it.
The bug as posted is still active with the new version.
It is not easy to reproduce. Sometimes it comes often, sometimes not.
Open and close
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1739322/+attachment/5050655/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1739322/+attachment/5050643/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1739322/+attachment/5050649/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1739322/+attachment/5050647/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1739322/+attachment/5050652/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
1 - 100 of 183 matches
Mail list logo
