Public bug reported:
Kate fails to update CTAGS index with the following error:
[CTags Error] Failed to run. Error: execvp: No such file or directory
There is an upstream bug report and a fix:
https://bugs.kde.org/show_bug.cgi?id=475521
https://invent.kde.org/utilities/kate/-/commit/5ea1d5df75685
I just checked and it seems like apparmor might be the cause:
```
Oct 20 20:10:08 vmsan plasmashell[3367]: LaunchProcess: failed to execvp:
Oct 20 20:10:08 vmsan plasmashell[3367]: /usr/lib/qt6/libexec/QtWebEngineProcess
Oct 20 20:10:08 vmsan kernel: audit: type=1400 audit(1729480208.652:174):
app
@vorlon
Currently when installing using Calamares (Kubuntu, Lubuntu etc) and probably
Ubiquity (Mate etc), manual partitioning allows arbitrary number of luks
volumes including one them being /home.
Configurations with /home on luks which is not the first one, are "unbootable".
Configurations wi
While I agree that moving systemd-cryptsetup to 'recommended' (or even
'depends') is the solution, it doesn't solve the issue with installs
using LiveCDs.
Install ISOs must be updated to make systems with separate encrypted
/home bootable and systems with 2+ encrypted volumes usable.
Which projec
** Also affects: qt6-webengine (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Plasma shell crashes with plasmoids using WebView.
More technical details at https://github.com/Martchus/syncthingtray/issues/287
- In addition to plasmoid mentioned in issue above,
Public bug reported:
Plasma shell crashes with plasmoids using WebView.
More technical details at https://github.com/Martchus/syncthingtray/issues/287
In addition to plasmoid mentioned in the issue above, the bug is easily
reproducible with built-in Web Browser plasmoid on clean install.
** Affe
I can confirm.
Not mounting luks volumes is not the only issue.
Among the issues are: very long boo times, inability to login using
graphical login managers and random hangs all over the place. Systems
with /home on separate encrypted location are completely broken even
with fresh installs.
The i
This originally a Debian bug but affects Ubuntu users using KDE Plasma 6.
Some apps/widgets use qdbus and fail since qdbus is not accessible.
Currently qdbus-qt6 installs the binary at /usr/lib/qt6/bin/qdbus which is not
in PATH.
The package must install a symlink/alternative in location defined
** Summary changed:
- On Kubuntu 24.10 can no longer use qdbus commands
+ On Kubuntu 24.10 qdbus command is not in PATH
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084278
Title:
On Kubuntu 24.10
Original bug reporter here.
After ~60 hours of testing I am confident the bug is resolved in 6.8.0-48.
With earlier Kernels 'intel_iommu=igfx_off' workaround still works as
expected.
I'll address reports of people still having issues.
There are 3 possibilities:
1. The user failed to apply proper
Thanks everyone.
From my point of view, the issue is resolved and since there were no complains
regarding upgrading to 24.04.1, so I guess we can mark Noble as "Fix Released".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Hello @tjaalton
Thank you for the fix!
Unfortunately I won't be able to test on anything but Noble.
TBH, I don't think we should worry about Jammy since it was working even with
older Kernels/Firmwares.
Noble is still fixed ;-)
--
You received this bug notification because you are a member of
After installing linux-firmware 20240318.git3b128b60-0ubuntu2.2 i can
confirm that now the driver loads the correct versions of firmware/ddc
and everything works as expected.
Since identical (manually installed) firmware binaries worked perfectly
for weeks, I am confident the new package will have
I've updated to kubuntu-desktop_1.451.1 on two systems with zero issues.
System A:
---
Already switched to libayatana-appindicator3-1.
Install went transparently.
System B:
---
Had the default libappindicator3-1 with indicator-multiload depending on it.
Upgrade went as follows:
```
apt dist-upgr
@acelankao
The patched kernel (without any parameters) seems to be working without any
issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with Intel i915 (Gen9 G
After 10 days of zero issues, I am convinced that the problem is with
linux-firmware and not kernel.
I've changed affected package accordingly.
** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@racb
AFAIK libayatana-appindicator is a "Non-Unity-Specific" fork of
libappindicator.
At some point (I believe during 20.04) libappindicator was abandoned and
libayatana-appindicator was marked as a replacement.
While they were mostly compatible, at some point software packages (eg.
Spotify) st
@mapengyu
Thanks you for the advice.
I "installed" the latest firmware/ddc images from the linux-firware git and
they are very different from the ones in
linux-firmware-20240318.git3b128b60-0ubuntu2.1. Uncompressed binary diff is
~1KBytes for .sfi and 1 Byte for ddc.
The firmware works and dev
Update:
Thanks to @jeff250 it seems like we narrowed the issue to kernel config changes
between 6.6 and 6.8 in Ubuntu kernels.
Unfortunately, proper fix is still not available but we have a working
workaround (intel_iommu=igfx_off).
More details can be found at upstream bug report:
https://gitla
@mapengyu
Unfortunately the fix didn't work.
Just now, after 11 days of uptime and ~25 suspend-resume cycles, bluetooth
(btintel) didn't wake up after suspend.
I am attaching kernel log of failed suspend-resume with the error msg:
```
Jul 29 14:11:44 hostanme kernel: Bluetooth: hci0: Reading Int
@jeff250
Thank you for doing your research into the issue but I am confused by
your results.
Are you claiming that removing mentioned Ubuntu specific commit resolves
the issue?
What about the fact that the issue also affect upstream/mainline
kernels?
Are you trying to say that the issue is just
@mapengyu
Thanks!
I'll continue my test and report back in a few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073047
Title:
Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stop
I've been testing kernel from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073047/comments/7 for 6
days now.
I'd continue testing for longer but without kernel headers for DKMS I am
missing functionality I need.
So far zero issues, Bluetooth works across many suspend/resume cycles.
Asi
@mapengyu
Installed the test kernel.
dmesg looks identical to -38.
Will report back asap.
I didn't notice that before but both -38 and the test kernel having issues
initializing intelbt:
```
[ 23.139943] kernel: usbcore: registered new interface driver btusb
[ 23.165732] kernel: Bluetooth: hc
@mapengyu
I was running -36 for 16 days without any issues.
I tried to use -38 in June (before -36 was published) and experienced
the same issue with Bluetooth right away. I ignored it at the time
assuming it was a one time glitch.
But now when I tried -38 again (after it was officially publishe
@mapengyu
linux-firmware 20240318.git3b128b60-0ubuntu2.1
linux 6.8.0-38.38
Attaching kernel log since last boot until btintel stops working.
** Attachment added: "Kernel log since boot until btintel fail"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073047/+attachment/5797380/+file
Reloading the driver:
```
modprobe -r btusb
modprobe -r btintel
modprobe btintel
modprobe btusb
```
fixes the issue (temporally):
```
Bluetooth: hci0: Reading Intel version command failed (-110)
usbcore: deregistering interface driver btusb
usbcore: registered new interface driver btusb
Bluetooth:
Public bug reported:
After upgrading to Linux 6.8.0-38, Bluetooth adapter (USB part of the
Intel AX200) stops working after a few suspend/resume cycles. WiFi (PCIe
part) continues to work as expected.
Kernel log shows:
Bluetooth: hci0: Reading Intel version command failed (-110)
instead of the us
@bandali
I believe this bug report on bugzilla is related:
https://bugzilla.mozilla.org/show_bug.cgi?id=1862159
** Bug watch added: Mozilla Bugzilla #1862159
https://bugzilla.mozilla.org/show_bug.cgi?id=1862159
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Confirming the fix on Noble with ubuntu-pro-client (32.3.1~24.04)
P.S.
Added mention of the fix on upstream issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067810
Title:
Apparmor denial on /v
@acelankao
Reported upstream:
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11504
** Bug watch added: gitlab.freedesktop.org/drm/i915/kernel/-/issues #11504
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11504
--
You received this bug notification because you are a member
To fix the issue, I was forced to switch to KDE Plasma (on the same system).
KDE Plasma had no issues with Firefox on both 23.10 and 24.04.
I opened a bug with Mate and there is already a bug report on bugzilla.
Unfortunately, no solution was provided so for now Mate + Firefox is not a
practical
@acelankao
Last mainline version I tried was 6.8.7 and at the time it was as bad as on
6.8.0-11.
Unfortunately, on my hardware, bisecting/testing this bug would take
unreasonable amount of time and risk running bleeding edge kernel since
even with 6.8.0-35 it happens only once in 1 to 3 days.
I
I've been testing kernel 6.8.0-38 (from proposed) and while it's not
fixing the problem completely, at least on my hardware it is
significantly better.
The flickering happened only once in 3 days and it was very brief (~1s)
and I didn't have to do anything for it to stop. Previously I had to
move
People suggest adding "i915.enable_dc=0 intel_idle.max_cstate=2" to the cmdline
but for my hardware "intel_idle.max_cstate=4" is sufficient.
I believe higher max_cstate will result in lower power consumption and
enable_dc is not needed.
--
You received this bug notification because you are a me
@vartee
This bug is Intel i915 specific.
I am afraid you are experiencing AMDGPU related issue and should look
for related open bug or open one by your self.
P.S.
I remember having similar flickering issues with AMDGPU and adding
"amdgpu.dcdebugmask=0x10" helped. Note, it was completely differe
Proper fix might come in future releases of Linux kernel.
For now adding "intel_idle.max_cstate=4" to the kernel command line should work
at expense of a minor power consumption.
See
https://wiki.ubuntu.com/Kernel/KernelBootParameters#Permanently_Add_a_Kernel_Boot_Parameter
for instructions.
-
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
** This bug has been marked a duplicate of bug 2062951
Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Summary changed:
- Random flickering with i915 on Linux 6.8
+ Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
Random fl
In addition, if the sound does work (on intel-hda Sunrise Point-LP HD
Audio) it stutters badly and under heavy load sound quits working
completely.
To fix 'alsa force-reload' or reboot are required.
Blacklisting snd_soc_avs seems to work for now and time will tell since
the issue usually appears
** Summary changed:
- No sound after upgrade to 24.04
+ No sound, stutters and clicks after upgrade to 24.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063150
Title:
No sound, stutters and clic
Public bug reported:
Some indicators like Dropbox etc can't show submenus out of the box.
The issue seems to be incorrect dependency.
Kubuntu-Meta still depends on libappindicator3-1 while nowadays it is
common to link against libayatana-appindicator3-1 hence the issue.
Not sure how to do the tr
Update:
Still happens on Kubuntu 24.04 with Linux 6.8.0-32 (6.8.4).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with i915 on Linux 6.8
To manage notifications abo
** Tags added: kernel-bug regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with i915 on Linux 6.8
To manage notifications about this bug go to:
http
Update:
I did some preliminary testing and it seems like adding
"intel_idle.max_cstate=4" to cmdline resolves the issue but probably at the
power efficiency cost.
I also tried "i915.enable_psr=0" but it didn't help just made the
flickering a slightly different.
--
You received this bug notific
Public bug reported:
After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy
flickering at random.
It happens after a moderate to heavy on screen activity like window switching,
scrolling etc.
It never happens when playing video or when there is no interaction using
keyboar
@wxl
People on #kubuntu-dev decided to skip zram for now since they wanted for issue
to be recognized as "release critical " for that change.
You can see more details at the end of
https://irclogs.ubuntu.com/2024/04/18/%23kubuntu-devel.html
--
You received this bug notification because you are
@wxl
I am not sure if the Kernel change is the sole reason, but I first encountered
the issue when Kernel switched from 6.6 to 6.8.
Maybe it was just a tipping point when memory consumption became too
high for 2GB systems and later for 2.5GB.
Also I am not sure when zram-config was removed from
** Description changed:
Since around introduction of Kernel 6.8 to Daily builds, installation of
Kubuntu / Ubuntu / Ubuntu-Mate builds randomly hangs(mostly), crashes or
fails on systems with less than 3GB of RAM.
When the system hangs, VM indicates heavy CPU and CDROM usage. My bet is
@guiverc
Thank you for pointing deficiencies in my reporting.
I've added additional context.
Unfortunately, I probably won't be able to provide apport reporting
since (1) Most of the times the system hard locks. (2) Since I've seen
it fail dozens of times, in order to save time I either increase
** Description changed:
- Install randomly crashes/fails/hangs on systems with 3GB or less
- When the system doesn't hang, I can see kernel OOM killing random processes
like calamares, cryptsetup etc.
+ Since around introduction of Kernel 6.8 to Daily builds, installation of
+ Kubuntu / Ubuntu /
** Summary changed:
- Install randomly crashes/fails/hangs on systems with 3GB or less
+ Ubuntu 24.04 daily builds - Install randomly crashes/fails/hangs on systems
with 3GB or less
** Summary changed:
- Ubuntu 24.04 daily builds - Install randomly crashes/fails/hangs on systems
with 3GB or le
** Summary changed:
- Install randomely crashes/fails/hangs on systems with 3GB or less
+ Install randomly crashes/fails/hangs on systems with 3GB or less
** Description changed:
- Install randomely crashes/fails/hangs on systems with 3GB or less
+ Install randomly crashes/fails/hangs on systems
Public bug reported:
Install randomely crashes/fails/hangs on systems with 3GB or less
When the system doesn't hang, I can see kernel OOM killing random processes
like calamares, cryptsetup etc.
I had ~75% success of installing Kubuntu 24.04 daily on VMs with less then 3GB
and almost 0% on 2GB
Update:
I tried switching to BGRT theme and it fixed the issue.
Both start and shutdown splashe screen display correctly and encryption input
prompt displays correct locale.
Trying any other non-text splash screen results in full or partial
(shutdown only) activation of kubuntu-logo which breaks
Public bug reported:
On Kubuntu 24.04 daily (up to 24.04.2)
kubuntu/modules/after_bootloader_context.conf claims to fail to remove
installation .desktop file:
2024-04-11 - 23:38:46 [6]: Starting job "Performing contextual processes'
job…" ( 32 / 41 )
2024-04-11 - 23:38:46 [6]: .. Running
Public bug reported:
After fresh install of Kubuntu 24.04 daily, plymouth luks input prompt fails to
display current locale.
It displays 'no' instead 'en' and I couldn't find a way to switch to alternate
locale.
Also after changing plymouth theme, it applies only to the shutdown
sequence. The b
Seems like the bug is back.
It pops up occasionally (one error line every ~2 hours) on Linux 6.5.0-14,
6.6.0-14 and 6.8.0-20.
Appears on both Jammy: Xorg (Mate) and Mantic: Xorg/Wayland (Mate/KDE).
Default kernel cmdline.
On Xorg the graphics is fine, but on Wayland it can a bit "flickery" at tim
Update:
Since release of 6.8.0-20.20 real machine (XPS13) seems to be working fine.
VMs are still hanging.
Short testing showed that the issue is caused by RAM starvation.
Booting LiveCD or Desktop should consume ~1.2GB but under 6.8, it starts with
~2GB usage and keeps going up.
Maybe it is rela
I can confirm the issue on 23.10 with no printers configured
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2021956
Title:
crash cups-proxyd
To manage notifications about this bug go to:
https://bug
** Package changed: linux (Ubuntu) => hwe-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049991
Title:
zswap is not working with Linux Kernel 6.5.x
To manage notifications about this bug go to
I did not have the chance to see the logs but I can confirm that 6.8.0-11 is
extremely unstable.
It randomly but surely hangs under load.
It usually hangs at the beginning of default Ubuntu 24.04 ISO install on both
KVM and Virtual box.
On real H/W (Dell XPS13) it hangs under load (nothing in th
Still exists as of build 20240311 and workaround from
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2054795/comments/4
works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054795
Title:
Nearing 2nd LTS release after the bug was reported and still no solution
or even acknowledgement of how serious the problem is.
To make it worse, in main desktop image they completely removed
encryption option from manual disk partitioning screen.
--
You received this bug notification because yo
Also, two versions of libfalcosecurity0-0.14.1-3ubuntu1 and
libfalcosecurity0t64-0.14.1-5ubuntu1 are available in archive and sysdig
pulls the older version by default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
csysdig in Noble (0.35.0+repack-1build2) refuses to start with the following
error:
```
filesystem error: directory iterator cannot open directory: No such file or
directory [./chisels/].
```
strace confirms that csysdig looking for chisels/ in current directory
instead of
@oibaf
ZRAM driver now supports multi-threading automatically so if all you are
interested in is multi-threading , you can use official version.
For those who want additional features like /tmp and performance
optimizations feel free to use my version of zram-config (
https://git.launchpad.net/~e
I use a different workaround, which seems to fix additional indicators besides
dropbox.
In file /usr/share/xsessions/gnome-flashback-metacity.desktop, I add
"Ubuntu;Unity" to the variable "DesktopNames".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Just wanted to share my observations.
At least on my machine, "failed resumes" are appearing in series after
initial BSOD (black screen of death), which usually occurs after a long
suspend.
After some experimentation, I've found that full/proper shut-down and
boot-up cycle (in addition to the for
The bug also affects Xenial with Linux HWE (4.15.0.24.46).
No issues with Linux HWE (4.13.0.45.64).
** Also affects: linux-meta-hwe (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-meta-hwe (Ubuntu Bionic)
--
You received this bug notification because you are a m
** Tags added: xenial
** Tags added: linux-hwe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757445
Title:
Suspend does not always resume
To manage notifications about this bug go to:
https://bug
Compatibility issue with GDM on Ubuntu 18.04 was fixed in zram-config
version 0.7
Updated code and packages can be found at:
https://git.launchpad.net/~eugenesan/+git/zram-config
https://code.launchpad.net/~eugenesan/+recipe/zram-config-ppa
--
You received this bug notification because you are a
Compatibility issue with GDM on Ubuntu 18.04 was fixed in zram-config
version 0.7
Updated code and packages can be found at:
https://git.launchpad.net/~eugenesan/+git/zram-config
https://code.launchpad.net/~eugenesan/+recipe/zram-config-ppa
** Changed in: zram-config (Ubuntu)
Status: Fix
** Changed in: zram-config (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761740
Title:
[PATCH] zram-config.service should start earlier - add "After=loc
Hello Brian,
I am running Bionic where the bug is fixed (gnome-applets - 3.26.0-3).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729728
Title:
window picker is broken in 3.26
To manage notificat
Public bug reported:
WindowPicker seems to be broken in 3.26.
It just crashes upon applet addition on fresh 17.10.
** Affects: gnome-applets (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Tags added: lts
** Summary changed:
- Please update microcode to version 20170511 on all supported platforms
+ intel-microcode should be updated, version 20170511 fixes severe errata on
6th and 7th generation platforms
** Summary changed:
- intel-microcode should be updated, version 2017051
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out after suspend disconnects the interface
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
I have merged in another bug(s) and updated the name of the bug to be a
bit more "user friendly".
** Summary changed:
- dnsmasq fails to send queries out after suspend disconnects the interface
+ name resolution (dnsmasq) fails to send queries out after suspend/resume
reconnects the interface
-
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
Confirming the bug in Xenial.
** Tags removed: amd64
** Tags added: xenial
** Description changed:
After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
suspend DNS resolution stops working.
+
+ * Also affect Xenial (Unity/GnomeFlashback)since Network-Manager stack
+ was upgr
Public bug reported:
Wirelsss/WiFi adapter BCM4350 (brcmfmac) fails after sleep on Dell XPS
9350.
Symptom:
WiFi fails to reconnect and no networks are visible.
Kernel reports: "brcmf_fil_cmd_data: bus is down. we have nothing to do."
Workaround:
$ rmmod brcmfmac
$ modprobe brcmfmac
The driver w
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1670038/+attachment/4831480/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670038
Title:
Public bug reported:
A firmware for embedded bluetooth adapter on Broadcom 4350 is missing.
Chip is provided as part of DW1820A/DW1830A on Dell XPS 2016 13/15 and probably
other machines.
More info at: https://wiki.archlinux.org/index.php/Dell_XPS_13_(2016)#Bluetooth
Device IDs:
* 0a5c:6412
* BC
Confirming #136.
Environment (on 2 machines):
Machine: XPS 13 9350 FHD Display
Distro: Ubuntu 16.04
Kernel: 4.4.0-24-generic
Bluetooth: off and on
Firmware: 1.3.3 and 1.4.3
DE: Unity and GnomeFlashback
Power: On battery and on AC
Screen: eDP (Built-In) or/and DP1 (External TB3/USBC->HDMI)
--
You
** Description changed:
- The fixes in 38.7, which was released on the 14th of March 2016 [0], six
- of which are deemed critical [1].
+ Despite Thunderbird being updated on 38.x branch (original bug was
+ probably filed before recent updates to the package), there is at least
+ one significant se
*** This bug is a duplicate of bug 1575731 ***
https://bugs.launchpad.net/bugs/1575731
** This bug has been marked a duplicate of bug 1575731
Thunderbird package is out of date
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
*** This bug is a duplicate of bug 1575731 ***
https://bugs.launchpad.net/bugs/1575731
** This bug has been marked a duplicate of bug 1575731
Thunderbird package is out of date
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
*** This bug is a duplicate of bug 1575731 ***
https://bugs.launchpad.net/bugs/1575731
** This bug has been marked a duplicate of bug 1575731
Thunderbird package is out of date
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Also affects: indicator-bluetooth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554878
Title:
fix up usage of XDG_CURRENT_DESKTOP
To manage
@romano-giannetti and anyone who followed the instructions referenced in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554613/comments/125,
There was a typo in instructions, please read bug description for details and
fix.
** Description changed:
*** Temporary workaround ***
Instal
** Description changed:
*** Temporary workaround ***
Install Kernel from the following location:
- http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/
OR
Perform the following:
- $ apt-add-repository "deb
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety mai
** Description changed:
*** Temporary workaround ***
Install Kernel from the following location:
- http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/
- OR (if you brave enough)
-
- Invoke: apt-add-repository "deb
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety
1 - 100 of 492 matches
Mail list logo
