Upstream fix proposed in: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2974
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7069
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7069
** Also affects: gnome-shell via
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2031447
Title:
Xorg crashed with SIGBUS in
** Tags added: mantic
** Summary changed:
- Bluetooth LE not working after upgrade from 22.04 to 23.10
+ [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status:
** Changed in: libfprint (Ubuntu Lunar)
Assignee: (unassigned) => Andy Chi (andch)
** Changed in: libfprint (Ubuntu Lunar)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
I can see Xorg crashing in XorgLogOld.txt but the lack of debug symbols
makes the stack trace wildly inaccurate so please:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files
You are trying to build an upstream release tarball, this is not
supported. You can have many other non distro supplied packages
installed. How can anyone tell, thus unsupported.
When reporting bugs on Ubuntu, be sure to specify the version you are
working on. Be verbose but concise.
--
You
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2034619, so it is being marked as such. Please
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
The panel and dock also look too pixelated in that screenshot. Seems
like the same bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2037461
Title:
Broken scaling on app labels
Oh sorry, I missed the "legacy" part. I'll try and reproduce it this
week.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2036440
Title:
Choosing "Try Ubuntu" on daily-legacy
That's cool, but please also consider contributing a permanent fix to
mutter so we don't need extensions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1778983
Title:
Resume from
Hello sirs,
I discovered my specific problem was because actually the video card was
not initialized at a hardware level in motherboard.
So what happened was that I had Display plugged into Intel motherboard
onboard video output.
Linux started and video card was kinda not initialized, so then
Hello sirs,
Sorry for being so noob. I see comment by janitor says something like:
"in package version 1:0.9.6.2~0.22.04.2 this is fixed."
However I have package version
maurirope@ubuntuserver:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common: date.
Installed:
I found this https://github.com/thesofproject/linux/issues/4055 can
anyone confirm if this also fixes issues with razer bldes?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2009071
Blade 18 same issue
No exactly sure if this is related, but supposedly fix for samsung
notebooks using same card -
https://github.com/thesofproject/linux/issues/4055
** Bug watch added: github.com/thesofproject/linux/issues #4055
https://github.com/thesofproject/linux/issues/4055
--
You
Hi Phil
What do you mean?
"Note: You are trying to build out of distro upstream packages that are
not supported by Debian. This is not supported."
It works on one instance with Debian? But it doesn't work on all
--
You received this bug notification because you are a member of Desktop
You state distro as Debian 11 (bullseye), so you need to be making bug
reports on the Debian bug tracker.
https://www.debian.org/Bugs/
Note: You are trying to build out of distro upstream packages that are
not supported by Debian. This is not supported.
** Changed in: poppler (Ubuntu)
This did not seem to fix the issue entirely see bug 2037894 for details.
** Changed in: ubuntu-drivers-common (Ubuntu Lunar)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in
Public bug reported:
Have installed poppler on several systems, but experience issues in some
cases.
All the dependencies should be installed!
Distro: Debian Bullseye 11
# apt-get install libopenjp2-7-dev libfreetype6-dev libfontconfig1-dev
libjpeg-dev libtiff5-dev
# cd /var/bin && wget
Public bug reported:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0:
Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0:
Firmware loaded in 1706498 usecs
Also fixed in the currently daily, on both Pi 4 and 5. The recent of
release of mutter is likely to have been the fix in this case (according
to @vanvugt).
** Changed in: firefox (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
Thanks a lot, @jkavery, such a relief after **years**(!!!) of messed up
windows after resume!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1778983
Title:
Resume from suspend on
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu flavour releases are only supported for three years, so in this
case until April, 2023.
Do
Public bug reported:
Description:Ubuntu 23.04
Release:23.04
Cinnamon 23.04
Default VM with virt-manager on 22.04 LTS
Xorg crashes randomly and i need to login again.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
I'm setting the status of this bug to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely ma
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
I'm setting the status of this bug to
Further to comment #15 I'll close this as not a Firefox issue.
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1882309
Upstream issue was closed sometime ago (see comment #7).
Also closing this issue as no activity since bug report was raised.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
If this issue is still current in a supported release of Ubuntu then
please open a new bug report
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
I'm setting the status of this bug to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still
A lone and somewhat anonymous user speaking on behalf of an anonymous
company is unlikely to change current Ubuntu/Canonical policy regarding
the use of the Firefox snap in the more recent releases of Ubuntu and
its various flavours.
Apparently this change was requested sometime ago by the
Concerning 1a86:7523, the udev rules file in ubuntu indeed seems to be
missing the manufacturer filter:
debian/brltty.udev.rules says:
ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm",
GOTO="brltty_usb_run"
while it should be:
ENV{PRODUCT}=="1a86/7523/*", ATTRS{idVendor}=="1a40",
Ah, I was looking in /etc/udev. But it was in /lib/udev:
This is the offending rule that selects my generic device:
# Device: 1A86:7523
# Baum [NLS eReader Zoomax (20 cells)]
ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm",
GOTO="brltty_usb_run"
When looking at
Not sure what is fixed with 6.4-4ubuntu3.
I removed/purged brltty, rebooted (just to make sure) and checked the
/dev/ttyUSB0 availability:
[ 89.311770] usb 3-3: new full-speed USB device number 4 using xhci_hcd
[ 89.529433] usb 3-3: New USB device found, idVendor=1a86, idProduct=7523,
Public bug reported:
Totem black screen playing an webm video. Video is payed ok by mpv.
corrado@corrado-n02-mm-0923:~/Videos$ ffprobe -loglevel error -show_streams
-show_format DSCF0001.webm
[STREAM]
index=0
codec_name=vp9
codec_long_name=Google VP9
profile=Profile 1
codec_type=video
30 sept 2023: I had the same kind of crash on a second laptop (OS:
Kubuntu 22.04, GPU Geforce RTX 3060) when using Firefox 108.0.1 (just
browsing a website, not youtube nor video).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in
39 matches
Mail list logo
