@Seth, Indeed it is fixed. Thanks guys!
** Changed in: linux-5.4 (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1861462
Title:
Awesome!... Thanks Daniel.
On Wed, May 9, 2018 at 6:01 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Now available for testing:
>
> https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
>
> Only cosmic is expected to get 5.49 but the above PPA also provides it
> for bionic if you
As much as I love to have this fixed in the final release, I understand
Daniel's hesitation. The point is to try and keep things as stable as
possible prior to releasing. Good news it is fixed and it is just a
matter of time before it is released.
--
You received this bug notification because
The following patches were added to the 5.48 version in Fedora and they
did fix the problem. Perhaps worth you adding them as well. Please see
https://koji.fedoraproject.org/koji/buildinfo?buildID=1040106 and the
bug https://bugzilla.redhat.com/show_bug.cgi?id=1534857
** Attachment added:
Problem seems resolved with bluez 5.48.2 as outlined in this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1534857#c30
** Bug watch added: Red Hat Bugzilla #1534857
https://bugzilla.redhat.com/show_bug.cgi?id=1534857
--
You received this bug notification because you are a member of Kernel
Public bug reported:
Steps to repro:
* Cold boot the laptop
* Pair it with bluetooth headset
* Listen to music
* Turn off the headset or turn off the bluetooth on the laptop
* Play music, sound comes out of the laptop speakers
* Turn on the headset back on or the bluetooth on the laptop
*
link textThe soln to this is to turn the nouveau driver modesettings and
leave things up to the Intel board.
To do that, you need to edit the /etc/default/grub and add
nouveau.modeset=0 to the GRUB_CMDLINE_LINUX
so it looks like this: GRUB_CMDLINE_LINUX="nouveau.modeset=0"
Once done, just run
The fix is easy enough. here is what you need to do.
== Booting a live image
* Enter the boot prompts by presseing Esc
* Edit the boot prompt and append nouveau.modeset=0 to the linux boot command
line
== Once installed, you need to do the following:
* Log into the system, assuming it work, if
Just tested 4.15-rc8 and it boots but the system isn't stable. Gets
lockups and screen flicker.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1718936
Title:
Can't boot Artful 17.10
Hopefully future kernel releases don't need the nouveau.modeset=0
option. But until then, 17.10 is rock solid (been full time on it for
the past 3+ weeks) without issues. Kudos to the Ubuntu and Canonical
teams for doing such a great job.
On Fri, Oct 20, 2017 at 7:15 AM, Hagen Kuehn
I agree with Kai-Heng. 17.04 is getting old and given all the good
work that went into the 17.10 release, I recommend you switch to it
Hagen.
BTW, in 17.10, there is a problem on the XPS 15
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718936) booting
from live CD and general use. You
I have done some more testing and here are my findings:
* 4.12.14 works like a charm with nothing extra added to the command boot option
* 4.13.16 doens't boot and operate normally without nouveau.modeset=0 . The
same go for 4.14-rc4
With nouveau.modeset=0, I can use the kernels that ship with
I tried it and it is the same problem as all the previous kernels I tested
(including the latest 4.13 available in Artful)
On Thursday, September 28, 2017, Kai-Heng Feng
wrote:
> Please try drm-tip kernel [1].
>
> [1]
I tried it and it is the same problem as all the previous kernels I tested
(including the latest 4.13 available in Artful)
On Thursday, September 28, 2017, Kai-Heng Feng
wrote:
> Please try drm-tip kernel [1].
>
> [1]
This bug shouldn't be fixed-released. Nothing got fixed. The live image
doesn't boot without the nouveau modeset kernel boot option. It
shouldn't be fixed until the live image boots without any tinkering.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
You received
I just tested the "blacklist=nouveau modprobe.blacklist=nouveau" and the
"nouveau.modeset=0" separately and both of them the machine booted off
the USB stick. I had a live image running 4.12 kernel so I will test
today's images (with 4.13 kernel) and report back.
Here is my dmidecode just in
I did that with yesterday's Ubuntu 17.10 live image and it did boot.
Q: Does that mean the acceleration is done by the Intel board instead?
On Tue, Sep 26, 2017 at 8:56 AM, Hlini Melsteð Jóngeirsson
wrote:
> I just tried adding "blacklist=nouveau
I just tried today's image and I it isn't booting still. Like Joseph, I
tried
On Mon, Sep 25, 2017 at 11:18 AM, Joseph Salisbury
wrote:
> Can you see if this issue also happens with the latest daily image? It can
> be downloaded from:
> Desktop:
>
I removed the "splash ---" from the boot command option and still didn't
boot up. I got more error messages so please attached photon.
** Attachment added: "DSC_0309.JPG"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718936/+attachment/4955249/+files/DSC_0309.JPG
--
You received
Here is a photo of the errors I get when I boot off the live CD. This is
the live CD from Sep 21, 2017
** Attachment added: "DSC_0308.JPG"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718936/+attachment/4955150/+files/DSC_0308.JPG
--
You received this bug notification because you
Public bug reported:
I usually test Ubuntu beta releases. With Artful, I haven't been able to
boot the image on my XPS 15 (9560) Dell laptop because the boot process
stops half way.
The boot proceeds properly if I pass the "nomodeset" kernel boot option
but that won't work because there is no
I just checked the the 17.10 live images on my XPS 15 (9560) and the
kernel still doesn't boot without using "nomodeset" kernel boot arg.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Have you guys tried uninstalling the Intel Xorg driver so you default
to kernel mode settings. That solved a lot of flicker issues for me.
$ sudo dpkg --purge install xserver-xorg-video-intel
On Tue, May 30, 2017 at 12:02 PM, Brad Buran <1554...@bugs.launchpad.net> wrote:
> Same here. It
Guys, there is an entry on the Chromium site talking about xorg modesetting
vs intel xorg driver. By installing modesetting module and getting rid of
the intel driver, the flicker was gone completely on Ubuntu 16.04.
https://bugs.chromium.org/p/chromium/issues/detail?id=606152#c73
On Thu, Oct 6,
Yikes. In your case it isn't the browser for sure. I read somewhere that
the adaptive brightness control might be a culprit but don't count on that
being true unless confirmed.
On Thu, Oct 6, 2016 at 11:38 AM, Thiago Martins
wrote:
> Anmar,
>
> I am 100% sure that it
Chrome flickers... but FF doesn't for me. Are you sure it isn't the
browser.
On Thu, Jul 7, 2016 at 7:58 PM, Thiago Martins
wrote:
> I'm on 4.4.0-28-generic (Xenial), problem still here.
>
> A good website to test it, is TradingView:
>
>
I have tested the following kernels:
4.6.0 - Works on resume without any problems. Zero failure rate
4.6.1 - Doesn't boot to lightdm. Erro with udev. Ignore it for now
4.6.2 - Boots but resume is the same problem. When I resume the laptop, the
machine restarts. Could be i915. Not sure.
--
You
BTW, the kernels I have tested in comment #6 are all for the Ubuntu
mainline kernel team PPA.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1572723
Title:
Dell XPS 9350 Reboots upon
I just booted windows and re-applied the new BIOS (1.3.3) and the new
Thunderbolt Firmware so I am all caught up on the BIOS and firmware
settings on the board.
I also nuked all the HD and re-installed Ubuntu from scratch. I just
retested it and the crash still happens when you close the lid or
BTW, I did install i3 and tried it, to eliminate Compiz and the same
problem continues to happens so I am guessing it is the kernel and not
Compiz causing the problem (This issue happened but turned out to be
compiz last time I filed a similar report)
--
You received this bug notification
Public bug reported:
Make sure your machine is up to date (has the 4.4.0-21) kernel and close
the lid on the laptop. When you open the lid, the machine reboots. This
didn't happen with the 4.4.0-18 kernel)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic
Turned out to be a lightdm issue and an update fixed it. Therefore, this
bug is invalid.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Either select suspend from the menu or close the lid. Upon re-opening
the lid or pressing power to wake the laptop up, the system will reboot
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-16-generic 4.4.0-16.32
ProcVersionSignature: Ubuntu
I assume you have updated the entire distro to the latest set of
packages?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1552304
Title:
screen flicker on Dell XPS 13 9350 after kernel
I discovered that if you have tlp installed and running, you will get
screen flicker. If you disable it, or remove it, the flicker goes away.
Seems something to do with the power management and skylake.
--
You received this bug notification because you are a member of Kernel
Packages, which is
This issue no longer occurs ... not sure if it is compiz specific or not
any kore as I switched to Ubuntu Gnome.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1554330
Title:
Reboot
1.2.3
01/08/2016
On Tue, Mar 8, 2016 at 8:12 PM, Christopher M. Penalver
<christopher.m.penal...@gmail.com> wrote:
> Anmar Oueja, please provide the output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
>
My BIOS is version 1.2.3 and the flicker continues to happen even with
the -11 latest kernel update. I just tested Ubuntu Gnome and the
flicker is gone. Interestingly , if you boot standard Ubuntu, with
unity, and spt-get install gnome-shell-session, then log out and log
back in the Gnome shell,
Public bug reported:
If you close the lid or choose suspend from the system menu then resume,
the system reboots. This didn't happen in the previous release of the
kernel. This is a Dell XPS 13 9350 (Skylake) with latest firmware 1.2.3
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package:
I also found another problem. Resume for a long sleep doesn't turn the
LCD back on . Will continue to test using the Linux xps
4.4.4-040404-generic #201603031931 SMP Fri Mar 4 00:34:16 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux and report back
--
You received this bug notification because you are
Just tested the Linux xps 4.4.4-040404-generic #201603031931 SMP Fri Mar 4
00:34:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
and flicker is gone.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Linux xps 4.4.0-8-generic #23-Ubuntu doesn't exhibit this bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1552304
Title:
screen flicker on Dell XPS 13 9350 after kernel upgrade
I tried 4.5 kernel from the Canonical team PPA and it is still
flickering but to a lesser degreee. BTW, the flickering goes away when I
am on a video conference call such as google hangouts.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
I upgraded to this version of the linux kernel (Linux xps
4.4.0-9-generic #24-Ubuntu SMP Mon Feb 29 19:33:19 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux) and the screen now flickers ramdomly. flicker
every few seconds for a fraction of the second. Not related to
application
I also confirm that problem continue to exists for Ubuntu 14.04 using th
standard Linux X1 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:45:01
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux kernel.
The way around it is to go the console, adjust the brightness to desired
level, then go back to X.
I just tested it on my Thinkpad X1 (haswell) and the fix works.
However, there is a side effect. Connecting and Disconnecting the
Power resets the brightness to maximum. Not sure how to go about
working around this.
anmar
On 26 February 2014 23:14, madbiologist 1098...@bugs.launchpad.net wrote:
I have been busy. I will test with the latest 3.14-rc3 of greater.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1221790
Title:
8086:0166 [ThinkPad X1 Carbon] Screen brightness is
On 13.10, the brightness works fine but the stepping is screwed up. In
other words, you don't get to access all of the brightness levels the
LCD offers. Instead, you get half the number of steps. It isn't a show
stopper by any stretch so go ahead and get your X1 carbon. It is the
best machine out
I am now booting 14.04 dev images and the problem persists.
On 18 December 2013 07:09, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Anmar Oueja, thank you for providing the requested information. Could
you please confirm this issue exists with the latest development release
I did upgrade the BIOS a few weeks ago when I was running 13.10.
Unfortunately, this didn't change anything. I am now running 14.04
with the latest apt-get and the results are the same.
What happened?
Upon cold boot or restart, the screen brightness is set to maximum
even if my setting wasn't.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1221790
Title:
Screen brightness is maximum upon fresh boot
Status in
I just confirmed that the problem continue to exist using Linux X1
3.11.0-8-generic #15-Ubuntu kernel. The 13.10 system is updated as of
2013.09.21.
On 20 September 2013 18:40, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
Given the number of bugs that the Kernel Team receives during
I installed Ubuntu 13.10 running 3.11 kernel and I noticed the stepping
is still there. The following fixed the stepping:
sudo sh -c 'echo -n 0
/sys/module/video/parameters/brightness_switch_enabled'
Seems that the driver and the GNOME settings daemon, or some other user
space tool, is
Public bug reported:
Problem: When I press the laptop screen brighteness, each step yield an
event that is displayed on the OSD but the screen brightness doesn't
change until the third press. Same happens for decreasing or increasing
the brightness.
Exepcted behaviour: Each press of the
I filed a new bug to capture the issue with the screwed up brightness
stepping (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221795)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
BTW, this command line option (acpi_backlight=vendor) fixes the
problem so I am now not sure if this is a bug or not.
On 6 September 2013 13:00, Anmar Oueja anmar.ou...@linaro.org wrote:
I will check 3.10 and earlier 3.11 RCs to see if I can narrow it down.
On 6 September 2013 11:47, Joseph
This didn't used to happen. I believe it started with the 3.11 kernel
since there is new code in that area. I will try installing 3.10 and
some early 3.11 RCs and see where I land. I know where to get the
earlier kernel packages (kernel team PPA) but how do I interrupt the
boot process to tell
57 matches
Mail list logo