(In reply to dreamsyntax from comment #884)
> Related:
> https://bugzilla.suse.com/show_bug.cgi?id=1223462
> https://github.com/torvalds/linux/commit/
> 39815cdfc8d46ce2c72cbf2aa3d991c4bfb0024f
>
> Now with Kernel 6.9.0 the issue should be fixed for devices with Cirrus.
>
> Unfortunately for me
(In reply to Markus from comment #881)
> I tested this script on my Lenovo Legion S7 16IAH7 with a fresh installation
> of Fedora Linux 40 with Kernel 6.8.8-300.fc40.x86_64. After installing
> i2c-tools the script return a lot of "Error: Write failed" errors. Pipewire
> version is:
> Compiled with
In my case, there seems to be an issue with pipewire using too many file
descriptors:
systemctl status --user pipewire
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset:
enabled)
Active: active (running) since Fri
Created attachment 306213
kernel-mute.log
(In reply to Tintin from comment #874)
> # . tas2781-2dev-on.sh 2
Sorry if this is a bit long, but trying to include info to help debug
the issue.
Well, it has finally happened again... It seems like the script hasn't
really helped... But I'll have to
(In reply to Tintin from comment #869)
> kindly run
> #i2cdetect -r 2
> and run following command during no sound issue
> dmesg -c > kernel-mute.log
Forgot to get the dmesg even though I did look at the dmesg output
(*facepalm*). There are no messages related to this in dmesg when this
occurs.
To confirm... You want my dmesg output when there's no issue, but you
want me to clear it after reading it?
On 4/22/24 03:23, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> Tintin (shenghao-d...@ti.com) changed:
>
> What|Removed
Unfortunately, my sound finally did fail again... But the symptoms seem
different. Audacious just hangs for a while before ultimately giving up
(and it stops hanging and stops trying to play).
But this is a new type of failure so perhaps this patch did make a bit of a
difference?
On 4/16/24 16:54, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #859 from Gergo K (so...@irl.hu) ---
> What else came to mind, the driver currently writes the calibration data to
> one
> of the wrong registers of tas2781, which can also
I had some time this morning to try and repeat the issue.. I couldn't do
it. So until I can find a way to repeat it, it's not worth testing other
kernel releases.
I will try Gergo's command once it happens again and report back.
--
You received this bug notification because you are a member of
I can try 6.7.9 and 6.7.12.
What you described vaguely sounds like the stuff I'm doing when it
breaks on me so I'll try that too!
I might have some time to do this tomorrow night.
I've wondered if this is a firmware issue as well. Here are my md5sums
for my files:
(In reply to dreamsyntax from comment #853)
> Hi, just confirming that on:
> Lenovo Legion Pro 7i (Gen 8 / 2023) the no sound issue has regressed again
> on 6.8.5.
>
> Last working version without any issues is 6.7.9 - which is odd considering
> the original post lists this as not a regression?
>
Songine,
Can you provide more info about your specific model? You should be able
to get that from running "lshw".
For the top of my output, I get:
version: Legion 7 16ITHg6
On 6/4/22 17:46, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment
Great!
Some probably silly questions:
1) Do both speakers work? Do you get left channel sound out of the left
speaker and right channel sound out of the right speaker?
2) After resuming from suspend/hibernate, does your sound still work?
3) What if you insert headphones and remove them? Does
Did you test this yourself?
On 6/3/22 00:11, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> Songine (donglingluoy...@gmail.com) changed:
>
> What|Removed |Added
>
Looking at your alsa-info, you don't have the CLS0100 amplifier chips,
which is what those modules would enable support for. Your laptop is not
supported by those modules and likely aren't supported at all.
(In reply to cris223 from comment #620)
>
> Hi everyone, with a thanks of your support!
>
Appears that these kernels are including these drivers. You might have
to figure out how to build your own kernel while enabling the necessary
kernel options yourself after all.
On 5/24/22 01:46, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> ---
It seems the path to endian.h may have changed from
/usr/include/sys/endian.h to /usr/include/endian.h.
In the failing file(s), try changing it from:
#include
To:
#include
On 5/24/22 05:37, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment
Your error message shows you're 5.13, which definitely doesn't have
support.
On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #614 from she...@liang.at (she...@liang.at) ---
> The first two modprobe commands returned
> `
>
There's no patch for your laptop yet.
Assuming your sound bar is initialized through verbs (I suspect it is),
you'll need to find the verb sequence yourself:
https://github.com/thiagotei/linux-realtek-alc287/tree/cameron
Once there's a working verb sequence, a patch can be created.
On 5/23/22
I would try try 5.17. 5.18 only came out yesterday, and therefore
doesn't even have any point releases so chances are reasonably high
you'll run into bugs.
Additionally, I don't have the ACHg6. It's possible you'll need to
specify which modules to load. In the likely event that 5.17 doesn't
work,
Seems like this is the best way to do it (but if someone knows of a better way
for Ubuntu, let us know):
https://sleeplessbeastie.eu/2021/11/01/how-to-install-mainline-linux-kernel-on-ubuntu-based-distribution/
Seems this gets you a tool that allows you to manage and install
mainline kernels.
According to your alsa-info, you have the already supported 16ACHg6
which is supported in the latest versions of the kernel.
There should be a repo you can add on your system to be able to pull the
latest mainline kernels. I don't have it handy at the moment as I've
been building/installing
Created attachment 300990
attachment-14829-0.html
From your alsa-info (thanks!), I see that your subsystem id is 0x3822
compared to the 0x1813 of the 15IMHG05.
In the root of the linux source folder/directory, open the file:
sound/pci/hda/patch_realtek.c
Find this line:
SND_PCI_QUIRK(0x17aa,
Looking at the model number, there's a chance it's compatible with the
verbs of the 15IMHG05, or another model from around that time.
Do you know how to build and run your own kernel?
Also, please provide a URL to your alsa-info.
On 5/15/2022 12:12 PM, bugzilla-dae...@kernel.org wrote:
>
The issue appears to be that the Nvidia kernel module is failing to
build and therefore you do not have working Nvidia support with this
kernel. I'm not sure how you configured your kernel so I suspect you
have one OR both of the following issues:
1. Nvidia's drivers do not yet support 5.18-rc1.
Sounds like https://github.com/ibus/ibus/pull/2394 might fix the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965673
Title:
Object 0x... of type IBusText has been finalized while it was
So I can confirm that copying /usr/share/pipewire/media-session.conf to
/etc/pipewire/media-session.d/media-session.conf and deleting these lines fixes
the issue:
$ diff /etc/pipewire/media-session.d/media-session.conf
/usr/share/pipewire/media-session.d/media-session.conf
94a95,116
>
Probably the models of laptop each need their own set of verbs.
On 2/14/22 05:34, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #552 from Jürg Lempen (i...@jlempen.com) ---
> Hi all,
>
> Good news for Lenovo Yoga Duet 7 13IML05 owners!
>
>
Lucas,
Do the CS35L5* chips require firmware to operate? It seems the
CS35L41/2's do not.
And out of curiosity, does the CLSA0101 have the CS35L51?
On 2/7/22 00:36, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #549 from Lucas Tanure
> My laptop has ALC287/ALC3306 + 2 CS35L53 (denoted as CLSA0102 in the DSDT)
Just curious, how do you know it's a CS35L53?
My laptop has a CLSA0101 and these patches don't work for me either.
Lucas has informed me that this will be supported at some point. I've no
idea what current the status is.
Also, I have to fully power off the laptop before booting again or else
the devices won't come back (rebooting alone doesn't work).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766825
Title:
Attached more logs here. File contains dmesg for wifi crash, PCI device
list and USB device list. Search for === to find section separators.
** Attachment added: "dmesg, lspci, lsusb"
https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+attachment/5206472/+files/combined.txt
--
You
I am also experiencing that both bluetooth and wifi are missing after
setting mem_sleep to deep. My laptop also refuses to actually stay
asleep in s2idle, I can see the screen come back on after I close the
lid.
Ubuntu 18.04
Kernel 4.15.0-36-generic
XPS 9370
** Attachment added: "Firmware
I'm not seeing a -proposed kernel for linux-generic-hwe-16.04 or linux-
generic-hwe-16.04-edge, but would be happy to test one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Confirmed that the updated perf binary doesn't crash with the cgroups
argument.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769027
Title:
perf record crash: refcount_inc assertion failed
To
(setting to confirmed because this error isn't in the kernel logs)
** Description changed:
+ On linux-hwe-tools-4.13.0-39 in xenial:
+
Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion
failure:
refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed.
Whoops, just checked the latest xenial systemd source package and
mistakenly thought I saw the patch had already been pulled. Please pull
this.
** Changed in: systemd (Ubuntu)
Status: Fix Released => New
** Description changed:
- Please backport this patch to 16.04, which should improve
** Tags added: patch patch-accepted-upstream
** Changed in: systemd (Ubuntu)
Status: New => 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/1659676
Title:
backport timesyncd
Confirmed I didn't get the error with your perf binary. However, I found
another bug and patch. I'll open another bug and tag you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767204
Title:
perf
Public bug reported:
Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion
failure:
refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed.
Confirmed fixed by patching my linux-tools package with this upstream
commit (on top of the commit in bug #1767204):
Confirmed that applying this patch makes my perf command not crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767204
Title:
perf record crash due to swapped xyarray function signatures
To
Public bug reported:
Crash happens on 16.04 with kernel 4.13.0-39.
Please backport this upstream patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/patch/?id=3d8bba9535ac6e79453c769dd0c8ea852a51ad60
** Affects: linux-hwe (Ubuntu)
Importance: Undecided
Public bug reported:
I'm trying to get a gtx1050 card working in linux. I've installed the
latest nvidia drivers (375.39) and my main issue is that the card does
not seem to be recognized by the system. Secondary issue is the nvidia
drivers aren't showing up in Software & Updates.
lspci -nn |
Public bug reported:
performed apt-get updated followed by apt-get autoremove
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: humanity-icon-theme 0.6.10
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Bump. This matters again because 4.10 is out now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484376
Title:
purge-old-kernels doesn't work when minor kernel version numbers add a
digit
To
LGTM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668724
Title:
fails to mount cgroupfs inside containers running on 16.04
To manage notifications about this bug go to:
I'm happy to provide a patch, but if the root cause of my issue is in lxc
it may be easier to patch that than worrying about backwards compatibility
for cgroups on older distro releases.
On Mar 3, 2017 20:11, "Serge Hallyn" <1668...@bugs.launchpad.net> wrote:
> This bug incidentally also affects
Hm, I found a bug in my last version of this patch. Freshly booted machines
which had not mounted the cgroupfs had all the hierarchies as 0, causing all
cgroups to get mounted onto a single directory. I can work around this by
detecting this scenario.
However, I wonder if I am actually seeing a
Edit: re: the systemd hierarchy, it's actually not mentioned in
/proc/cgroups, it's /proc/self/cgroups
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668724
Title:
fails to mount cgroupfs inside
Also, is there a reason the name=systemd cgroup controller gets mounted
at /sys/fs/cgroup/systemd instead of /sys/fs/cgroup/name=systemd in
newer versions of cgroups-mount? It means my applications have to
special-case stripping off the name= when they try to work with cgroups
based upon
Patch for 1.1.5
** Patch added: "cgroup-lite_1.1.5.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828588/+files/cgroup-lite_1.1.5.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch for 1.12
** Patch added: "cgroup-lite_1.12.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828590/+files/cgroup-lite_1.12.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Whoops, didn't notice I changed that part in my local copy. Should have
been more careful with my patch.
** Patch removed: "cgroup-lite_1.1.5.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828546/+files/cgroup-lite_1.1.5.patch
** Patch removed:
It looks like there were fixes in the latest version of cgroup-lite that
would still be applicable/useful for earlier ubuntu releases, but I
tried to minimize the diffs to have the functionality that I need. Let
me know if you need a patch for trusty as well.
--
You received this bug
Patch for 1.12
** Patch added: "cgroup-lite_1.12.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828547/+files/cgroup-lite_1.12.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch for cgroup-lite 1.1.5
** Patch added: "cgroup-lite_1.1.5.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828546/+files/cgroup-lite_1.1.5.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
and have noticed that the cgroups-mount script for mounting the cgroups
inside the containers has stopped working. This is because systemd now
comounts multiple controllers on a single hierarchy, which
Public bug reported:
Please backport this patch to 16.04, which should improve reliability of
timesyncd updates to the RTC:
https://github.com/systemd/systemd/commit/5f36e3d30375cf04292bbc1bf3f4d7512cf80139
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
Error report while updating
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-libopencl1-340 340.96-0ubuntu3.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic i686
.tmp.unity_support_test.0:
ApportVersion:
@jarnos: I don't think this is related to byobu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484376
Title:
purge-old-kernels doesn't work when minor kernel version numbers add a
digit
To
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591311/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591310/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591312/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591304/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591303/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591308/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591306/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591307/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591309/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
Title:
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591298/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
tVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: cam2962 F pulseaudio
+ /dev/snd/controlC0: cam2962 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=d2
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591299/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
Title:
BUG:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591301/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591305/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591302/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553400
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1553400/+attachment/4591300/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Filesystem IO has started hanging when trying to access certain
directories. Relevant kernel oops below:
[12779.747913] BUG: unable to handle kernel NULL pointer dereference at
(null)
[12779.747961] IP: []
locked_inode_to_wb_and_lock_list+0x22/0xd0
[12779.748004]
Nathan: How many interfaces or IP's are you bringing up? That error
message makes it sound like there could be a lot of contention on the
lock. Could you also get the output of `pstree | grep -B3 lockfile`
while a VM is coming up? (You'll need to attach to a free virtual
terminal using the kvm
Nathan: How many interfaces or IP's are you bringing up? That error
message makes it sound like there could be a lot of contention on the
lock. Could you also get the output of `pstree | grep -B3 lockfile`
while a VM is coming up? (You'll need to attach to a free virtual
terminal using the kvm
Hi,
I'm using Inkscape 0.91 r13725 on Xubuntu 15.10, and it looks to be the same
problem for me.
I have to close 6 windows before pasting...
I don't know how to help.
** Attachment added: "Error messages"
I can confirm I've been running this in production and have not seen any
further issues.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
I can confirm I've been running this in production and have not seen any
further issues.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Test procedure:
In 3.16.0-57-generic:
$ sudo dd if=/dev/zero of=/lower/f1 bs=4096 count=55
55+0 records in
55+0 records out
225280 bytes (2.3 GB) copied, 4.00938 s, 562 MB/s
$ sudo mount -t overlayfs overlayfs -olowerdir=/lower,upperdir=/upper
/mnt/overlayfs
$ sudo chmod 666
** Description changed:
- We're seeing a race between if-up.d/ntpdate and the ntp startup script.
+ [Impact]
+ * Hardware clocks are not stepped at boot, which can prevent NTP from ever
+ syncing the clock.
+ Incorrect clocks can cause serious issues in distributed systems.
- 1)
** Description changed:
- We're seeing a race between if-up.d/ntpdate and the ntp startup script.
+ [Impact]
+ * Hardware clocks are not stepped at boot, which can prevent NTP from ever
+ syncing the clock.
+ Incorrect clocks can cause serious issues in distributed systems.
- 1)
** Also affects: linux-lts-vivid (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/1523000
Title:
writing files larger than 2GB to overlayfs fails
Public bug reported:
There's simply a missing flag, which was fixed here:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=0480334
The patch claims it requires kernel 3.18+, but the overlayfs code in
ubuntu's 3.16 kernel is already backported from later kernel
It works with 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/1518016
Title:
[SRU] Nova kilo requires concurrency 1.8.2 or better
To manage notifications about this bug go to:
It works with me, thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1518016
Title:
[SRU] Nova kilo requires concurrency 1.8.2 or better
To manage notifications about this bug go
In case it wasn't clear, my patch is supposed to be for the
debian/ntpdate.if-up file. Also, I think the priority of this bug should
be higher, it was assigned 'low' when there was no clear problem caused
by the race. Systems booting with uncorrectable clock skew can be a
serious problem.
--
You
In case it wasn't clear, my patch is supposed to be for the
debian/ntpdate.if-up file. Also, I think the priority of this bug should
be higher, it was assigned 'low' when there was no clear problem caused
by the race. Systems booting with uncorrectable clock skew can be a
serious problem.
--
You
I think a common cause for this issue could be stuck buttons. I was
seeing a similar symptom today where the left button on my usb mouse
attached to my closed laptop wasn't working. Opening the lid and tapping
the mouse buttons by my touchpad fixed the issue.
--
You received this bug
It can be dangerous to step the clock while applications are running
(see the fallout from the last couple of leap seconds). Stepping only
needs to be done at boot. It makes more sense to just have separate init
scripts for both ntpdate and ntp and to order them correctly. Adding
ntpdate to the
The fix for 246203 was wrong: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/karmic/ntp/karmic/revision/23
The issue is that the ntp init script is started inside the ntpdate ifup
script BEFORE the lock file is unlocked. That init script then blocks
because the lock is taken. The correct
The fix for 246203 was wrong: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/karmic/ntp/karmic/revision/23
The issue is that the ntp init script is started inside the ntpdate ifup
script BEFORE the lock file is unlocked. That init script then blocks
because the lock is taken. The correct
It can be dangerous to step the clock while applications are running
(see the fallout from the last couple of leap seconds). Stepping only
needs to be done at boot. It makes more sense to just have separate init
scripts for both ntpdate and ntp and to order them correctly. Adding
ntpdate to the
Public bug reported:
Ex: Have 3 kernels installed, [ 3.2.1, 3.2.2, 3.16.1 ]. Or [4.5.1,
4.8.1, 4.11.1]. Be booted into one of the older kernels. Run purge-old-
kernels. You'll be left without the newest kernel. You would run into
this if, for instance, you install a new kernel and run the script
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484376
Title:
purge-old-kernels doesn't work when minor kernel version numbers add a
digit
To manage notifications about this
I think adding the sorting function should do it.
** Attachment added: patch
https://bugs.launchpad.net/ubuntu/+source/bikeshed/+bug/1484376/+attachment/4443957/+files/patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Christopher,
It has been reported here :
http://marc.info/?l=linux-wirelessm=143420832618489w=2
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459367
Title:
10ec:b723 Realtek RTL8723BE
1 - 100 of 188 matches
Mail list logo
