[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

2022-11-25 Thread Dmitry Shachnev
** Changed in: linux (Ubuntu) Status: Fix Released => 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Kernel-packages] [Bug 1916070] Re: autopkgtest fails in hirsute on armhf with glibc 2.33

2021-03-30 Thread Dmitry Shachnev
This was fixed by https://launchpad.net/ubuntu/+source/qtwebengine- opensource-src/5.15.2+dfsg-3ubuntu1. And the tests pass since then: http://autopkgtest.ubuntu.com/packages/n/notepadqq/hirsute/armhf. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Package changed:

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

2020-11-10 Thread Dmitry Shachnev
Hi Christian! In comments #11 and #17 there are some patches for this bug. They probably need rebasing though. ** No longer affects: linux (Ubuntu Zesty) ** No longer affects: linux (Ubuntu Eoan) -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

2020-03-11 Thread Dmitry Shachnev
Hi again Juerg and all, I want to mention that upstream Linux developers actually *do* care about ABI stability. For example, one of the commits broke ABI but it was quickly reverted and then fixed in a way that does not change the ABI:

[Kernel-packages] [Bug 1866570] Re: Sync alsa-lib 1.2.2-2.1 (main) from Debian unstable (main)

2020-03-09 Thread Dmitry Shachnev
This bug was fixed in the package alsa-lib - 1.2.2-2.1 Sponsored for Logan Rosen (logan) --- alsa-lib (1.2.2-2.1) unstable; urgency=medium [ Matthias Klose ] * Non-maintainer upload. [ Sebastien Bacher ] * debian/patches/python3.8.diff: - fix the build with python 3.8

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

2019-10-02 Thread Dmitry Shachnev
I think it changes quite rarely: - Once it changed in Linux 4.7, in commit [1] (April 2016), - Then it changed in Linux 5.1, in commit [2] (February 2019). The Debian maintainer has a patch [3] that updates the SONAME version when ABI changes. There has been an attempt [4] to send that patch

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

2019-09-17 Thread Dmitry Shachnev
Debian has package names that follow upstream SONAME, e.g. libcpupower0, libcpupower2. The -dev package is used only for building, the resulting binary packages get dependency on library package. When there is ABI break, upstream changes SONAME, so the library package changes too and all reverse

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

2019-09-16 Thread Dmitry Shachnev
Hi Juerg! This is a step towards what we want, but ideally it would be nice to have an unversioned package (like linux-tools-dev) that would ship some symlinks in /usr/include and /usr/lib, so that we don’t need to pass -I and -L to gcc. -- You received this bug notification because you are a

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

2018-02-16 Thread Dmitry Shachnev
Vlad, thanks for testing! I don’t have much time to work further on the patch (especially when there is no guarantee for it being applied). Maybe you can try to create an updated patch where dh_makeshlibs will be properly called during build? -- You received this bug notification because you are

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

2017-12-16 Thread Dmitry Shachnev
I had some discussion about this on kernel-team mailing list in September, and provided a patch which addresses Juerg Haefliger’s review: https://lists.ubuntu.com/archives/kernel-team/2017-September/086839.html However there has been no action since then :( Attaching the new version of the

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)

2017-01-08 Thread Dmitry Shachnev
Dear Tim or somebody from the kernel team — can you please reconsider my patch, or reply to my proposal in comment #8? -- 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/1215411 Title:

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)

2016-12-19 Thread Dmitry Shachnev
Hi Tim! I understand that the user can have multiple kernels installed. However, I am not sure if supporting multiple versions of a development package makes sense. After all, there can be only one header file matching i.e. #include and only one library file matching -lcpupower. If you really

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)

2016-12-10 Thread Dmitry Shachnev
Added a patch against lp:~ubuntu-kernel/ubuntu/+source/linux/+git/zesty that adds a libcpupower-dev package, compatible with what Debian has. Dear kernel team, please review it. ** Patch added: "0001-UBUNTU-Add-a-new-libcpupower-dev-package-for-compati.patch"

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)

2016-10-17 Thread Dmitry Shachnev
Can we please have a libcpupower-dev package compatible to Debian (https://packages.debian.org/sid/libcpupower-dev)? ** No longer affects: linux (Ubuntu Saucy) ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1529292] Re: Sync intel-gpu-tools 1.13-1 (main) from Debian unstable (main)

2015-12-28 Thread Dmitry Shachnev
This bug was fixed in the package intel-gpu-tools - 1.13-1 Sponsored for Logan Rosen (logan) --- intel-gpu-tools (1.13-1) unstable; urgency=medium * New upstream release. - Drop unneeded build-dep on swig. (Closes: #803522) -- Vincent Cheng Wed, 23 Dec

[Kernel-packages] [Bug 1504072] Re: BUG: unable to handle kernel paging request at ffffebe000000000

2015-10-15 Thread Dmitry Shachnev
*** This bug is a duplicate of bug 1503655 *** https://bugs.launchpad.net/bugs/1503655 ** This bug has been marked a duplicate of bug 1503655 Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107 -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1504072] Re: BUG: unable to handle kernel paging request at ffffebe000000000

2015-10-08 Thread Dmitry Shachnev
This looks like a duplicate of bug 1503655, though I am not sure about that. -- 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/1504072 Title: BUG: unable to handle kernel paging request at

[Kernel-packages] [Bug 1504072] [NEW] BUG: unable to handle kernel paging request at ffffebe000000000

2015-10-08 Thread Dmitry Shachnev
Public bug reported: After upgrading the kernel from 3.19.0-29 to 3.19.0-31, the system is unusable. It boots to the desktop, but immediately after that gets a kerneloops, and neither mouse nor keyboard is working. This is a regression introduced in a Vivid SRU. ProblemType: KernelOops

[Kernel-packages] [Bug 1504072] Re: BUG: unable to handle kernel paging request at ffffebe000000000

2015-10-08 Thread Dmitry Shachnev
** Description changed: - After upgrading the kernel from 3.19.0-29 to 3.19.0-31, the system is + After upgrading the kernel from 3.19.0-30 to 3.19.0-31, the system is unusable. It boots to the desktop, but immediately after that gets a kerneloops, and neither mouse nor keyboard is working.

[Kernel-packages] [Bug 1393878] Re: Freeze of mouse and keyboard after susoend due to i2c-designware

2014-11-18 Thread Dmitry Shachnev
Not a bug in gnome-panel if it also happens with Unity and KDE. ** Package changed: gnome-panel (Ubuntu) = linux (Ubuntu) -- 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/1393878 Title:

[Kernel-packages] [Bug 1310554] Re: Regression: breaks mpc decoding with some players

2014-06-21 Thread Dmitry Shachnev
This bug was fixed in the package libmpc - 2:0.1~r459-4.1 Sponsored for Jackson Doak (noskcaj) --- libmpc (2:0.1~r459-4.1) unstable; urgency=low [ Hideki Yamane ] * Non-maintainer upload. - auto detect aclocal/automake/autoconf version (Closes: #713209) - include

[Kernel-packages] [Bug 1327735] Re: Sync libmpc 2:0.1~r459-4.1 (universe) from Debian unstable (main)

2014-06-21 Thread Dmitry Shachnev
This bug was fixed in the package libmpc - 2:0.1~r459-4.1 Sponsored for Jackson Doak (noskcaj) --- libmpc (2:0.1~r459-4.1) unstable; urgency=low [ Hideki Yamane ] * Non-maintainer upload. - auto detect aclocal/automake/autoconf version (Closes: #713209) - include

[Kernel-packages] [Bug 1327735] Re: Sync libmpc 2:0.1~r459-4.1 (universe) from Debian unstable (main)

2014-06-08 Thread Dmitry Shachnev
syncpackage: Error: Source package libmpc is blacklisted. syncpackage: If this package needs a fakesync, use --fakesync syncpackage: If you think this package shouldn't be blacklisted, please file a bug syncpackage: explaining your reasoning and subscribe ~ubuntu-archive. syncpackage: Blacklist

[Kernel-packages] [Bug 1327735] Re: Sync libmpc 2:0.1~r459-4.1 (universe) from Debian unstable (main)

2014-06-08 Thread Dmitry Shachnev
This package was removed and blacklisted on 2010-03-26, but it exists again since 2010-07-28 (https://launchpad.net/ubuntu/+source/libmpc/2:0.1~r459-1/+publishinghistory). I think it should be removed from blacklist. Subscribing ~ubuntu- archive. -- You received this bug notification because you

[Kernel-packages] [Bug 1327735] Re: Sync libmpc 2:0.1~r459-4.1 (universe) from Debian unstable (main)

2014-06-08 Thread Dmitry Shachnev
ScottK: I believe yes. libmpc (2:0.1~r435-2) experimental; urgency=low * Updating epoch and upload to experimental to give maintainers of packages that depend on libmpc-dev again some more time to port their applications to the new API. -- You received this bug notification because