** Package changed: rhythmbox (Ubuntu) => gtk+3.0 (Ubuntu)
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
You have been subscribed to a public bug:
I report here because but this problem is related to amost any
applicatin in Disco version 19.04 I recently installed, may something
only related to a few users because I surprised not already pointed out
by anyone else.
Attached a screenshoot from where
FUD much?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1841113
Title:
Don't update to 2.13.92 this cycle
Status in fontconfig package in Ubuntu:
Triaged
Bug
** Tags added: radeon
** Summary changed:
- Xorg freeze
+ [radeon] Xorg freeze
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Summary changed:
- gnome-shell crashed with SIGSEGV in g_str_hash() from
g_hash_table_lookup_node() from g_hash_table_lookup() from
console_kit_session_default_init()
+ Various programs crashed with SIGSEGV in g_str_hash() from
g_hash_table_lookup_node() from g_hash_table_lookup() from
** Package changed: wayland (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1841387
You have been subscribed to a public bug:
I do not know what triggered the crash.
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.32.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
** Summary changed:
- some crash rest to a "dash" on left, old system ???
+ Shaky display on GM965 [X3100] (Core 2 Duo L7500)
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
*** This bug is a duplicate of bug 1836979 ***
https://bugs.launchpad.net/bugs/1836979
Are you really sure this is a duplicate of bug 1836979? They don't sound
related.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Package changed: xorg (Ubuntu) => ubuntu
--
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/1841367
Title:
250819
Status in Ubuntu:
Incomplete
Bug description:
rien
What's the wireless card does the system use?
--
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/1840931
Title:
wifi connection keeps being dropped: 18.04 on Lenovo
Please do a test:
When speaker doesn't work, run,
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x6ac8
// check if speaker works now
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0xd
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF
Sorry, it was my fault. Correct #5, it should be "echo 1 >" instead of
"cat 1 >". Anyway you generated the alsa-info.txt with coeff in the #7
and #8.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
This bug can be closed, one could argue that the kernel could handle
this a bit prettier as the -1 options is setting the firmware loading to
auto so a fallback to not loading the firmware would be ok.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Found out it's unrelated to Wayland or GDM, I was using the
"i915.enable_guc=-1" to load the Intel power management firmware, this
causes the DRM initialization to fail if the needed version is missing
and the firmware was updated in 5.3.
Aug 25 23:32:02 xps9380 kernel: [drm] GuC: Failed to fetch
** Project changed: launchpad => wayland (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1841387
Title:
GDM hangs on boot with 5.3rc5 when using wayland
Status
No.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1841006
Title:
gdb reports a segfault in ld-linux.so.3 on armhf
Status in binutils package in Ubuntu:
New
Bug
You have been subscribed to a public bug:
Been testing newer kernels and everything works(5.2.9 works) until 5.3rc
series where it seems there is an issue with Wayland and/or the setup on
Ubuntu is using, it works on Arch Linux.
When booting with 5.3rc5 GDM hangs on launch showing a blank
** Changed in: ufw (Ubuntu)
Status: New => Triaged
** Changed in: ufw (Ubuntu)
Importance: Undecided => Medium
** Changed in: ufw (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Same problem here with Debian 10, Dell Inspiron 13 1370.
Workaround by Florian works for me too.
** Bug watch added: Debian Bug tracker #931304
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931304
** Also affects: bluez (Debian) via
Here is the alsa-info for the case where I booted into windows, shutdown
completely, then boot into Ubuntu. Sound is working
Same permissions issues exist for writing the alsa parameters. I was
able to set dump_coef but not dump_enable
** Attachment added: "Alsa info when sound is working"
Sorry, looks like I did not follow the full instructions. Here is the
file with the proper name.
I am also documenting the steps so that somebody else can follow the
instructions as well.
This is after booting into Windows and then rebooting into Ubuntu
without a Windows shutdown
Stop
I was unable to run the dump_enable command as I was getting permission
denied even when running as sudo su. This is the alsa-info when I booted
into Ubuntu while rebooting from Windows and when there is no sound. I
will do the same while booting from a shutdown state from windows.
** Attachment
Public bug reported:
I have machine with the following nspawn file:
--
[Network]
MACVLAN=laneth0
[Exec]
PrivateUsers=false
--
if I start it with systemctl start systemd-nspawn@name, all works as
expected.
If I start manually with systemd-nspawn -M name -b, I seem to correctly
get a new
Can you perform the following:
$ mkdir /tmp/ufw
$ sudo ufw show raw > /tmp/ufw/raw
$ sudo tar -zcvf /tmp/1833719.tar.gz /tmp/ufw /etc/default/ufw /etc/ufw /lib/ufw
then attach to this bug /tmp/1833719.tar.gz?
** Changed in: ufw (Ubuntu)
Status: Expired => Incomplete
--
You received
** Tags added: version-blocked-ff
** Summary changed:
- Update to 2.9.8
+ Update to 2.9.8 not this cycle
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1797064
Title:
Please collect two alsa-info.txt with dump_coef enabled:
1) boot into windows, shutdown, boot into ubuntu linux, make sure the
speaker works, then sudo su; cat 1 >
/sys/module/snd_hda_codec/parameters/dump_enable; collect an alsa-info
.txt-spk-work by running alsa-info.sh
2) boot into ubuntu
** Tags added: version-blocked-ff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1715931
Title:
Update to exiv2 version 0.27
Status in exiv2 package in Ubuntu:
Triaged
** Summary changed:
- Update to exiv2 version 0.26
+ Update to exiv2 version 0.27
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1715931
Title:
Update to exiv2 version
*** This bug is a duplicate of bug 1715931 ***
https://bugs.launchpad.net/bugs/1715931
** This bug has been marked a duplicate of bug 1715931
Update to exiv2 version 0.27
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: libwebp (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/1351227
Title:
libwebp ftbfs on arm64
Status in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Public bug reported:
rien
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins:
** Description changed:
- Xubuntu 18.04 installed on a new Lenovo IdeaPad 330S; system is up to date (I
run Software Updater pretty much daily).
+ Xubuntu 18.04 installed on a new Lenovo IdeaPad 330S; system is up to date (I
run Software Updater pretty much daily).
lsb_release -rd tells me:
Public bug reported:
Steps to reproduce:
1. Suspend laptop
2. Wake laptop up
3. log in
4. screen goes black
use the command line login to restart lightdm
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic
Ok, so I specified "network-manager" as the package. Don't know if
that's correct, though.
** Package changed: ubuntu => network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
You have been subscribed to a public bug:
Xubuntu 18.04 installed on a new Lenovo IdeaPad 330S; system is up to date (I
run Software Updater pretty much daily).
lsb_release -rd tells me:
Description:Ubuntu 18.04.3 LTS
Release:18.04
I am connected to the internet via a wireless
My version ubuntu server 18.04. Below worked for me:
1. Creating an empty file(/etc/NetworkManager/conf.d/10-globally-
managed-devices.conf)
2. removing the file(10-globally-managed-devices.conf) from /usr/lib
and finally
3. changing Network renderer to NetworkManager in Yaml file.
Yaml file
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libext2fs2:amd64 1.44.1-1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
libext2fs2:amd64:
I move too Ubuntu 19.04 and we are still affected by this bug, into multi users
professional environment we usually just use LTS, but try to solve this issue
without success. ;-(
Try also without success :
===
A workaround for those of us that need a solution now is to place
** Tags added: rls-ee-incoming
** Changed in: accountsservice (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1841079
42 matches
Mail list logo