@Thayne,
No worries, and thanks for getting back to (not just) me. In fact, this
is not the first Java application with such Snoopy behaviour that I've
heard about.
https://github.com/a2o/snoopy/issues/215 will make sure thread safety
gets enabled by default starting with Snoopy version 2.5.0.
@Thanye, I've checked the stack trace above again, and then inspected the git
history since 2.4.6 has been released in 2016, and only the following commits
have touched the src/datasource/cmdline.c file:
- 4b4ab04 Sun Oct 4 2020 +0200 GH #157: Fix (potentially*) incorrect malloc
size in
@Thayne, can this one be reproduced with the latest Snoopy versions
(2.4.9)? If so, can you provide either a patch that fixes it, or a
method that I can use to reproduce the issue locally?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same behaviour in 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087876
Title:
bond-primary must be set in slave interface
To manage notifications about this bug go to:
I tested with this kernel:
linux-image-4.9.0-040900rc4-generic_4.9.0-040900rc4.201611052031_amd64.deb
No change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610028
Title:
Power usage 50% worse
Thank you for response, will do it tonight and update bug with results.
On 2 November 2016 at 14:13, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> bostjan, to keep this relevant to upstream, one would want check for,
> and test the latest mainline kernel
Hi Joseph,
Sorry for the late response, I did not receive the notification for some
reason.
I did test at the time, with all latest 4.5.x, 4.6.x and 4.7.x kernels,
no change.
It would make sense to test with 4.8, or even better, wait for 4.9 and
test it with that?
** Changed in: linux (Ubuntu)
:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bostjan3629 F pulseaudio
/dev/snd/controlC1: bostjan3629 F pulseaudio
Date: Fri Aug 5 02:29:33 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a1169bd1-3502-4168-a9f9-639255a224c0
InstallationDate: Installed on 2016-08-04 (0
By updating mba6x_bl module this issue went away.
I am unable to replicate it on 4.4.x as there are build issues (initial
is with stack protection gcc flag which does not yet exists in trusty,
then something about signing module).
Feel free to close this, as it gets resolved with module update.
/controlC1: bostjan2559 F pulseaudio
/dev/snd/controlC0: bostjan2559 F pulseaudio
CurrentDesktop: Unity
Date: Sun Nov 22 22:16:04 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-18 (553 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Rel
Additional info: the buttons themselves work as expected, I can see the
brightness bar adjusting up/down, just brightness itself does not change
and stays at 100%.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, doing this fixes the issue:
sudo rmmod mba6x_bl
sudo modprobe mba6x_bl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518767
Title:
Macbook Air 6.2 brightness buttons stopped working after
I am also experiencing this one, it is annoying (if I put it mildly).
I have few other ubuntu installations (fresh ones, not upgrades from
pre-14.04 versions) and they do not exhibit this behaviour.
Will compare filesystems tonight and report if I discover which
difference is/was relevant.
b.
13 matches
Mail list logo
