** Also affects: bluez (Ubuntu Artful)
Importance: Low
Status: New
** Tags removed: sts-sponsor-chiluk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf
I'm now on the 4.11.0-10-generic kernel, and have not seen this failure
again. However, I'll leave it up to the kernel team to see if they want to
pursue this further. You can install this kernel on Xenial by
installing linux-generic-hwe-16.04-edge.
More information is available
Sponsored artful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned in bluetooth.conf and README
To manage notifications about this bug go to:
For those of you that really want Trusty fixed, please be aware, that
the preferred way to resolve this kind of issue is to upgrade the EFI
Firmware on your machine.
Also I just checked the source code for initramfs-tools, Yingying Zhao
(yingying-zhao) was wrong in
Public bug reported:
Unable to resize window after snapped to half screen. You can see the
arrow, tempting you to just try and resize the window at the edge, but
it's just toying with you.
More info https://bugzilla.gnome.org/show_bug.cgi?id=645153
This used to work in z+Unity ;(.
** Description changed:
- haproxy is releasing a feature that provides for seamless reloads for
- 1.8.
+ Reloading haproxy causes TCP resets for active connections. This can be
+ a serious issue for clouds that rely on haproxy for load balancing, and
+ as a result are restarting it frequently.
Added configuration and testing results to top page. Upload commencing
shortly.
** Description changed:
Reloading haproxy causes TCP resets for active connections. This can be
a serious issue for clouds that rely on haproxy for load balancing, and
as a result are restarting it
** Changed in: haproxy (Ubuntu)
Status: Triaged => 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/1712925
Title:
FFE: HAproxy dropping connections (RST) during config reload /
** Description changed:
haproxy is releasing a feature that provides for seamless reloads for
1.8.
Full related blog post is here.
https://www.haproxy.com/blog/truly-seamless-reloads-with-haproxy-no-more-hacks/
I have attempted a backport of the feature, and attached it. The
to be cleaned up, needs dep-3 tags, and needs to be tested.
** Affects: haproxy (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Attachment added: "artful.patch"
https://bugs.launchpad.net/bugs/1712925/+attachment/4938252/+files/artful.patc
I have created a ppa with this current patch to assist with testing.
https://launchpad.net/~chiluk/+archive/ubuntu/lp1712925
This patchset is still in the early stages, so use/test this with
extreme caution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Another thing just occurred to me. We probably want the kinks in this
worked out in the 17.10 development and release cycle, as 18.04 will
hopefully get haproxy 1.8 which will include these changes officially.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The original intention was to get it into 17.10, but I didn't have
enough time yesterday to get it tested and cleaned up. I really think
we should consider this for FFE, as it is a bug fix. That being said it
also is an interface change, and will probably require changes to the
systemd unit
According to the bios changelog
https://downloadmirror.intel.com/26841/eng/SY_0061_ReleaseNotes.pdf
0061 of your bios should already include the microcode that is also
available in the intel-microcode package. As such, on boot I'd expect a
no-op when checking for newer microcode version. We
@yarko, Please start by gathering the information @hmh requested. Those
include:
1. output of /proc/cpuinfo
2. /var/log/kern.log
Please provide both of these with both the working and newest microcode.
Also please reverify bluetooth in both cases, as we need to make sure
that the issue wasn't
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications about this bug go to:
udevadm info -e as requested.
** Attachment added: "udevadminfo"
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+attachment/5010640/+files/udevadminfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I reviewed your patch, and it appears as if it only turns off receive
checksumming. The internets are saying that transmit needs to be turned off
as well. Have you checked to see if transmit is affected as well?
I will try to do some transmit tests. I'll also "test" your kernel when I
get a
I am not using ipv6.
On Tue, Nov 14, 2017 at 9:10 AM, Mario Limonciello
wrote:
> @Dave:
>
> I was glancing at r8152 driver and notice that it has some special
> handling for ipv6. Is this issue reproducing only in ipv6 for you?
>
I also just went through the process of reproducing this while watching
the kern.log. Absolutely 0 messages came out. If you find some verbose
debugging you want me to turn on let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
There is no way to tell if you even have the intel-microcode package
installed which should have the newest microcode. Please apt install
intel-microcode and update this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
gnome has moved to gitlab. Corresponding bug is now
https://gitlab.gnome.org/GNOME/gnome-calculator/issues/59
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680438
Title:
gnome-calculator comes
@katamo
4.14.xx is not a supported Ubuntu kernel. I'm not sure where you pulled that
kernel from, but it is not supportable.
At this point all Supported Ubuntu kernels and mainline 4.15+ have this
fix.
@EVERYONE ELSE
If you think you are hitting this issue and are running the latest supported
I'm sorry I've been unable to test this from my end. Have you been able
to make any progress on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729674
Title:
TB16 dock ethernet corrupts data
** Also affects: intel-microcode (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: intel-microcode (Ubuntu Bionic)
Importance: Critical
Status: Triaged
** Also affects: intel-microcode (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also
That patch note makes it sound like there will be a hardware/firmware
fix that will hopefully resolve this. If so it is very unlikely that
upstream will accept your patch, as the proper fix will really be to
upgrade your firmware. A more preferable patch will be to log a big bad
warning if you
Those changes test as good.
@Kai-Heng Feng. In the future you should consider setting LOCALVERSION
or using a PPA and setting a +lp1729674 to version string in the
changelog. With what you did it's hard to distinguish between your test
package and an official package.
See
I should also mention that this should probably be pushed to linux-
stable as well as mainline as this is a silent data corruption bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729674
Title:
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724557
Title:
gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
To manage notifications about this bug go
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729674
Title:
@kmously I see that you marked this fix as Fix Committed in Artful, but
I do not see it in the master-next branch of artful. I'm moving this
back to In progress in artful as this does not appear to have been
pushed to master-next for artful yet. Feel free to push it back to Fix
Committed when
@pandasauce ... Fix committed means it's in the git archive, but has
completed testing nor been integrated into the archives yet.
Also please refrain from repeating things we already know in the thread
or otherwise +1'ing or me-tooing. It just wastes developers time that
could be spent actually
Hasn't completed testing or been integrated into the archives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729674
Title:
TB16 dock ethernet corrupts data with hw checksum silently failing
To
Looks like this has been released with 4.15.0-9.10 which is available in
bionic.
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Kai-Heng Feng (kaihengfeng)
Status: In Progress
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Released
**
Ran same tests against 4.13.0-38 on artful.
Just curious, this only seems to be applied to hwe and hwe-edge kernels
for xenial. Is that a change in policy?
Even though I haven't attempted it, it appears as if this should be
pretty straightforward apply on the 4.4 kernel stream.
--
You
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729674
Title:
TB16 dock ethernet corrupts data with hw checksum
Closing Won't fix as this version has end of lifed and has likely been
resolved.
** Changed in: xfsprogs (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Closing Won't fix as this version has end of lifed and has likely been
resolved. Please reopen if this is still an issue.
** Changed in: xfsprogs (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing Won't fix as this version has end of lifed.
** Changed in: xfsprogs (Ubuntu)
Status: New => Incomplete
** Changed in: xfsprogs (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing Won't fix as this version has end of lifed and has likely been
resolved. Please reopen if this is still an issue.
** Changed in: xfsprogs (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing Won't fix as this version has end of lifed and has likely been
resolved. Please reopen if this is still an issue.
** Changed in: xfsprogs (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing Won't fix as this version has end of lifed and has likely been
resolved. Please reopen if this is still an issue.
** Changed in: xfsprogs (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing Won't fix as this version has end of lifed and has likely been
resolved. Please reopen if this is still an issue.
** Changed in: xfsprogs (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing Won't fix as this version has end of lifed and has likely been
resolved. Please reopen if this is still an issue.
** Changed in: xfsprogs (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing Won't fix as this version has end of lifed and has likely been
resolved. Please reopen if this is still an issue.
** Changed in: xfsprogs (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing Won't fix as this version has end of lifed and has likely been
resolved. Please reopen if this is still an issue.
** Changed in: xfsprogs (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
xfs_quota appears to be working as expected, but it seems you would like
to change it's behavior. Ubuntu would prefer not diverge from the
upstream xfsprogs project. Please bring up this issue with xfs project
directly at http://xfs.org/index.php/Main_Page
If they agree to change the behavior
I'm marking this won't fix pending a response from @Kaoet and a behavior
change from upstream xfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727285
Title:
xfs_quota always exit with 0
To
Same thing in bionic
# journalctl -u systemd-hostnamed
-- Logs begin at Wed 2018-02-28 16:43:47 UTC, end at Wed 2018-02-28 16:44:28
UTC. --
Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Failed to reset
devices.list: Operation not permitted
Feb 28 16:44:03 bionic systemd[1]:
Verified kind of still exists with ubuntu 17.10 amd64 (daily) (20180227)
# journalctl -u systemd-hostnamed.service
-- Logs begin at Wed 2018-02-28 16:38:35 UTC, end at Wed 2018-02-28 16:39:16
UTC. --
Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Failed to reset
devices.list:
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Low
** Also affects: pulseaudio (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: pulseaudio (Ubuntu
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754294
Title:
After last updated libcurl3 on libcurl4, some apps are removed.
To manage notifications about this bug go to:
ed; assignee=None;
> Launchpad-Bug-Tags: indeed verification-done-artful
> verification-done-xenial
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: ballengerm benjamin-redhat-bugs chiluk
&
I have tested bionic and cosmic myself, but I'd like to hear from a user
or two. I have experienced the low-volume issue, but that appears to be
correctable by launching alsamixer. All in all it's a better experience
than before imho.
--
You received this bug notification because you are a
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: pulseaudio (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: pulseaudio (Ubuntu Disco)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm pretty sure you need to adjust the "chat mix" knob on your headset
as the audio will now be playing through a separate audio device on the
headset. Basically previously it was using the mono "chat"/mono output
on the headphones. Now with the ppa it's primarily using the
"game"/stereo output.
I uploaded these changes for bionic and cosmic. Just waiting on sru
approval now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No
I uploaded the changes to disco this morning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
mono playback
To
I uploaded test packages for cosmic and disco to my ppa today. If
someone with the headset could test either of those as well that would
be awesome. I should be getting a headset here soon to test with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
+ [Impact]
+
+ * User is only able to get mono audio from steelseries headsets because
+ they provide both a stereo and mono output. PA selects the mono output
+ by default.
+
+ * This should be backported to stable releases because this fix is
+isolated to code
Looking at pulseaudio upstream, it looks like 12.2 has
15386a710c1500f70085a6312fb4d84be4d254c9 and
c7fe78c9f73ded2c3428666722ec9c1af4b82812
but not
83675b3745c64bd738400eae44eb4daa195ed88a
fe6a9a8f59932f29cc77eac2a7e2c6bd07c8c7d0
3454c19f3c277d5d0099f17e7ebf5d2005afa4b0
Bionic will needs all
Basically what I did was backport all the required Arctis stuff that
seemed to be required in order to get my lucid sound headphones working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Can someone on this bug please test the packages from
https://launchpad.net/~chiluk/+archive/ubuntu/lp1758736
on Bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio -
Yah @jparedes you should probably open a different bug. You are running
into something different.
I've also verified that this is now fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813663
@Kaj Printz Madsen
I know you opened this a long time ago, but is there any chance you
could test the ppa for me?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio -
I'm going to close out this bug, as I have not experienced this since
moving to 18.04.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812527
Title:
[bionic][regression] gnome-shell crashes with SIGSEGV in
meta_window_actor_is_destroyed(self=NULL) called from
Enabling this plugin is the easiest way to work around this issue in bionic.
https://extensions.gnome.org/extension/1328/disable-workspace-switch-animation/
That being said what is the status of a real fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839589
Title:
pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL:
Hey thanks for the fix, I've been on vacation, and didn't have a chance
to look at this further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839589
Title:
pulseaudio FTBFS on eoan 12.2-2ubuntu4
We (Indeed) were recently hit by mawk posix non-compliance as well. For
all the reasons stated above, I would also like to see mawk replaced
with gawk in main. I'd also like to see the mawk dependencies in the
ubuntu-meta packages replaced with gawk. For that reason I'm opening a
separate
Public bug reported:
pulseaudio fails to build from source on Eoan
I was attempting to put together a patchset for LP#1839580, but it
appears as if the packages are currently failing to build from source.
Not sure how they built the first time around.
Here's my ppa's buildlog, for a source
Upstream merge request.
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/143
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839580
Title:
LucidSound LS31 only outputs mono sound
Public bug reported:
LucidSound LS31 only outputs mono sound.
The usb vendor:prod = 2f12:0109.
The fix is incoming.
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: In Progress
** Changed in: pulseaudio (Ubuntu)
Status: New
I got my act together and sponsored this bug today. Now you just need
SRU approval.
@mruffell, welcome to the party.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838555
Title:
nvme-cli 1.5 in
@oddbjornk @cristofaro
Launchpad is not a forum. Each bug is meant to solve one problem. One
of you need to create a new bug for the new problem. You are welcome to
reference or link this issue in that new bug though so whoever triages
it has a reference.
--
You received this bug
Public bug reported:
With 5.3.0-12-generic on bionic virtualbox-dkms fails to build the
kernel driver. Excerpt of build failure below. Full text attached.
This is the second time I've been bitten by this dkms failing to build
on kernel upgrades. It really feels like the -dkms packages
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521734
Title:
virtualbox-dkms: virtualbox kernel module failed to build
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371494
Title:
VirtualBox crashed with SIGSEGV
To manage notifications
This is similar to
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1844805
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
virtualbox, virtualbox-dkms, virtualbox-qt fail
@slashd ,
Reading through the patch, it's exactly as @mruffell says it is. It's
sequestered into a code path that only exists for micron drives. A code
path which previously did not exist. This satisfies the intro, and the
first three bullet points of Other_safe_cases. This patch is upstream
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847786
Title:
Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels
To manage notifications about this bug go to:
Public bug reported:
It looks like the hwe kernels need the linux-firmware revved again.
update-initramfs: Generating /boot/initrd.img-5.3.0-12-generic
W: Possible missing firmware /lib/firmware/i915/icl_guc_32.0.3.bin for module
i915
W: Possible missing firmware
** Changed in: mysql-5.7 (Ubuntu)
Importance: Undecided => High
** Also affects: mysql-5.7 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Tags added: regression-release
** Changed in: mysql-5.7 (Ubuntu Bionic)
Milestone: None => bionic-updates
** Changed in: mysql-5.7
Targeting for bionic, but I haven't checked the other releases.
I will say it's odd that there's a
libssl-dev
and
libssl-doc
but not a
libssl
only a libssl1.0 and a libssl1.1.
I'm sure there's reasons, and I'm not privy to them.
--
You received this bug notification because you are a member
** Also affects: linux-5.4 (Ubuntu Focal)
Importance: Medium
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861521
Title:
[FOCAL][REGRESSION] Intel Gen 9 brightness
** Summary changed:
- [FOCAL][REGRESSION] HP EliteBook 840 G5 screen brightness cannot be controlled
+ [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also am hitting this. This looks to be a gen 9 graphics problem, as
sforshee with gen 10 graphics appears unaffected.
I'm on a Dell Inspiron 5540 with an i9-9880H
$ glxinfo | grep Device
Device: Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) (0x3e9b)
@tyhicks reported on
** Package changed: linux-signed-5.4 (Ubuntu) => linux-5.4 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861521
Title:
[FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
To
Also I should have mentioned that 5.3.0-24-generic as a workaround also
fixed it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861521
Title:
[FOCAL][REGRESSION] Intel Gen 9 brightness
This is seems to be wider than simply Lenovo machines as my Dell
Precision 5540 is hitting this as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851749
Title:
Frequently getting thermal
Public bug reported:
gnome-shell becomes unresponsive after about 1 day. I'm able to interact
with the window that had focus when the problem appears (in this case it
was Chrome), but I'm unable to select or otherwise interact with other
windows, the shell, dock, or indicators.
The logs are
Get memtest into debian, and it will get pulled in to Ubuntu ...
eventually. The reason it hasn't been updated is that Ubuntu does not
wish to fork memtest from Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The activities panel is showing up on the wrong display. Selecting the
"primary display" as 3 in the display settings puts the top bar on
display 3 , but the activities bar on screen 2. Screenshot attached
Similarly, selecting
primary display = 2 then activities bar ends
Unfortunately Ubuntu is not a rolling release. If there are specific
issues that you'd like patched please link to the specific patches so
they can be discussed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like the linked ticket has been closed as fixed released. I'm
closing this ticket as a result. If there is still an issue please re-
open.
** Changed in: freeipa (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm moving this to won't fix in 18.04 as it doesn't follow the Ubuntu
ethos of bug/security-fix only after release.
Also it looks like 4.9.8-1 is being worked on for jammy.
** Changed in: freeipa (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968588
Title:
Cannot create or add VPN in connection editor
To manage notifications about this bug go to:
Workaround available here
https://askubuntu.com/questions/1403896/cant-add-cisco-compatible-vpn-vpnc-on-network-manager-ubuntu-22-04/1404609#1404609
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
901 - 1000 of 1000 matches
Mail list logo