Public bug reported:
When running Oculus Rift compatible software, the HMD rotation seen by
software drifts by a few degrees per second, even when the HMD is not
moving at all (ie, it's sitting perfectly still on the desk).
This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24
I forgot to mention this, but the way OpenHMD switches modes is by using
the hidapi library, which has two versions for libusb and hidraw. You
just link against the one you want. So the code is doing the exact same
thing in each case, and the HID version of it doesn't work. That's why I
think it
This isn't a BIOS issue, it's been reproduced across multiple different
hardwares including by the oculus developers themselves, and is a
regression in the stable release. It's either a bug in the oculus driver
code, or it's a bug in the kernel.
** Changed in: linux (Ubuntu)
Status:
There is a much easier workaround. Just copy the files with terminal, or
another file manager that isn't Nautilus. As such, I don't believe this
is a fault with bluez or even gvfs, but with Nautilus or some other
Gnome component.
The really easy way to do it with Terminal:
cd to the destination
Today my workaround didn't work. This suggests the problem is in gvfsd
or obex-data-server.
** Also affects: obex-data-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gvfs (Ubuntu)
Subsribed additional packages to try to get some eyes on this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1284308
Title:
Bogus another operation in progress error. Can't copy files
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172995/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172996/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1284308
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172993/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172997/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1284308
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172994/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2013-12-22 (228 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
InterestingModules: btusb rfcomm bnep bluetooth
MachineType: ASUS All Series
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172998/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4173001/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4173000/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4173002/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1284308
apport information
** Attachment added: getfacl.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4173004/+files/getfacl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4173003/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
That didn't really attach anything useful, oh well. Here's the log
snippet from ~/.cache/upstart/dbus/ showing the error happening:
** (zeitgeist-fts:2146): WARNING **: Unable to get info on
application://nautilus-autostart.desktop
** Message: transfer of Image010.jpg to
*** This bug is a duplicate of bug 1353021 ***
https://bugs.launchpad.net/bugs/1353021
** This bug has been marked a duplicate of bug 1353021
USB HIDRAW Feature Report Implementation for HID devices not working
correctly in Ubuntu 14.04
--
You received this bug notification because you
Still broken in 14.04
--
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/1073089
Title:
ubuntu kernel does not support gadgetfs
Status in linux package in Ubuntu:
Triaged
Bug
This is a regression since 14.04. Out of date bios is irrelevant. Please
provide a citation for your claims of "buggy" and "insecure."
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
None of the links you provided support your claim that my BIOS is
insecure or buggy. Have you tried actually reading the stuff you copy
and paste every day?
I would further point out that the last update for this system was
released in 2010, at least four years before this bug was introduced.
On
The last working kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/
The first broken kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/
Probably related:
http://lkml.iu.edu/hypermail/linux/kernel/1410.1/02561.html
--
You received this bug notification
While messing around with this I noticed that the system does actually
unsuspend on recent kernels after exactly five minutes. After
unsuspending the system clock is five minutes slow, to the second. There
are no useful messages in dmesg, syslog or journalctl.
** Summary changed:
- close laptop
** 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/1575250
Title:
close laptop lid = complete system freeze
Status in
Since it looks like I am expected to fix this myself, why don't you just
mark it triaged and assign it to me?
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alistair Buxton (a-j-buxton)
--
You re
I'm working on the bisect now. I already ruled out the suspected commit
- the first bisect step blew right past it. Each build takes about 2.5
hours on an i7-3770 and there's another 10 to go, so I should find the
answer in about about four days or so.
--
You received this bug notification
Sure, just give me access to a build server where I can build the
kernels for bisection.
** 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.
I completed the bisection and googling the resulting commit ID revealed
that this bug has already been reported upstream.
** Bug watch added: Linux Kernel Bug Tracker #107151
http://bugzilla.kernel.org/show_bug.cgi?id=107151
** Also affects: linux via
If one actually reads the release notes (as I did yesterday) one will
notice that there are no references to security fixes and the only two
changes listed are described as a workaround and a fix for Windows XP
respectively.
Regardless, I have now obtained a copy of Windows and updated to the
4.7-rc2 does not work. The regression is somewhere between 3.9 and 4.0.
--
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/1575250
Title:
close laptop lid = complete system freeze
Status
Public bug reported:
When running 14.04 my CPU fan speed increases relative to the CPU
temperature, which keeps the temperature fairly constant.
When running 15.04 or 15.10 the CPU fan speed is locked to the minimum
until the temperature reaches 81 degrees, then it switches to maximum
until the
This is probably fixed by:
https://github.com/torvalds/linux/commit/7fc595f4c02636eadaeeecfe7bbc45b57c173004
--
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/1564901
Title:
xpad rumble
For reference/impact assessment here's the steam thread where I found
the patch:
https://steamcommunity.com/app/233130/discussions/0/611702631210587760/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yes, it works fine with that kernel.
--
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/1564901
Title:
xpad rumble causes full system hang
Status in linux package in Ubuntu:
Confirmed
Public bug reported:
To reproduce:
1. Have a wired xbox controller.
2. Modify the SDL2 testrumble.c so it runs forever. (attached)
3. Build and run it.
4. Kill it with sigkill from another terminal.
Expected result: The program should stop running.
Actual result: Entire computer freezes.
Public bug reported:
Wifi works correctly after cold boot.
After warm boot the wifi hardware is detected correctly but cannot see
any access points.
This bug report was generated after a warm boot, ie while the bug is
happening.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package:
Public bug reported:
To reproduce:
1. Close laptop lid.
2. Wait a couple of minutes.
3. Open laptop lid.
Result: the screen remains powered off and the system will not respond
in any way. Pressing keys does nothing. Pressing the power button does
nothing. There is no disk activity but the power
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
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/1574018
Title:
Atheros
** Tags added: kernel-bug-exists-upstream
** 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/1575250
Title:
close
Yes, I do, eg with Saints Row 3, the controller starts vibrating
immediately and never stops.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1564901
Title:
xpad rumble causes
Still broken in 16.04. gadgetfs has been replaced by functionfs, which
is also available in the standard kernel packages, but still does not
work because it too relies on dummy_hcd on x86 platforms.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Still broken in 18.04
--
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/1073089
Title:
ubuntu kernel does not support gadgetfs
Status in linux package in Ubuntu:
Triaged
Bug
The same messages are logged on the live image boot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1754836
Title:
Failed to activate service
Status in bluez package in Ubuntu:
New
** Attachment added: "log running blueman-applet manually"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5077985/+files/blueman-applet-manual.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
No, we are talking about the errors in xsession-errors.txt:
ERROR:dbus.proxies:Introspect error on org.bluez:/:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ERROR:dbus.proxies:Introspect
** Summary changed:
- Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed:
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez':
timed out (service_start_timeout=25000ms)
+ ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
There is more stuff in syslog too. It looks like pulseaudio is trying
and failing to start blueman.
** Attachment added: "cat syslog | grep -E '(pulseaudio|blueman)'"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5077997/+files/syslog.txt
--
You received this bug
*** This bug is a duplicate of bug 1749546 ***
https://bugs.launchpad.net/bugs/1749546
The Bluez timeout errors still show up in ~/.xsession-errors at least on
hardware without Bluetooth. However, it seems to be harmless.
--
You received this bug notification because you are a member of
Some more: touching the system cache files doesn't make it work.
Binary diff on the cache files before and after running fc-cache shows
this:
63 c7 c3 5a 00 00 00 00 47 72 ce 15 00 00 00 00
63 c7 c3 5a 00 00 00 00 00 00 00 00 00 00 00 00
Before, at offset 0x38, the "bad" cache files have
As far as the original bug with delayed login goes... it seems that the
Bluetooth stuff is a red herring.
Since it only happens on first login, I deleted the contents of ~ and
relogged. The delay came back, so I bisected the files until I arrived
at the single file which needs to be deleted in
seems related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1754836
Title:
Xubuntu: ERROR:dbus.proxies:Introspect error on
Another piece of the puzzle: if you run:
sudo fc-cache -fv
this will rebuild the system font cache in /var/cache/fontconfig
If you then delete the user's cache in ~/.cache/fontconfig and re-log,
there is no delay... and the user's font cache will NOT be rebuilt.
After a delayed login,
One final thing: this does not affect Ubuntu desktop after install. But
it does affect the Ubuntu live image, which takes an extra minute or so
to boot. It seems that the Ubuntu desktop installer rebuilds the system
font cache during install.
--
You received this bug notification because you are
On the current daily ISO this now hangs for 50 seconds instead of 75,
and the blueman/bluetooth messages are completely gone from xsession-
errors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Since this only happens on first login, I ran a diff on the full home
directory before/after login:
https://paste.ubuntu.com/p/SJ2nNx7WfP/
I don't see anything obvious in there. The pulse cookie and a blueman
settings file (empty) were created. The rest seems to be Thunar/desktop
defaults and
I tried to log in over ssh and run top so I could watch which processes
were running but this caused the delay to disappear.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1754836
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283952/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283947/+files/CRDA.txt
--
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/1841040
apport information
** Tags added: apport-collected
** Description changed:
Whenever the computer is rebooted there is a roughly 50% chance that the
r8169 ethernet cannot negotiate a link. There is no relevant information
in dmesg except for the "link down" message. The work around is to
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283954/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283948/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283949/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283951/+files/Lsusb.txt
--
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/1841040
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283959/+files/WifiSyslog.txt
** Description changed:
Whenever the computer is rebooted there is a roughly 50% chance that the
r8169 ethernet cannot negotiate a link. There is no
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283957/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283950/+files/Lspci.txt
--
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/1841040
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283956/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283958/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283955/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1841040/+attachment/5283953/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Whenever the computer is rebooted there is a roughly 50% chance that the
r8169 ethernet cannot negotiate a link. There is no relevant information
in dmesg except for the "link down" message. The work around is to just
keep rebooting the computer until it eventually works;
I am not able to test that kernel as it is not signed.
--
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/1841040
Title:
r8169 ethernet sometimes doesn't work after cold boot/boot
Status
(and by cold boots I mean very cold - like the computer has been
switched off for several hours.)
--
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/1841040
Title:
r8169 ethernet sometimes
I am working on this but it is slow as the bug is difficult to
reproduce. It seems to happen more often after cold boots.
--
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/1841040
Title:
I have managed to reproduce this as far back as 2f34c1231bfc9f which is
somewhere between 4.11 and 4.12rc1. I have been unable to reproduce it
with 4.11, but this may just be due to bad luck. I will continue testing
tomorrow.
--
You received this bug notification because you are a member of
It is perhaps worth mentioning that there are only two patches to r8169
in this time frame:
commit 1bcf165ac6556dc55a596d524b8187d1ba7a8c7d
Author: Zhu Yanjun
Date: Sun Mar 12 05:02:54 2017 -0400
r8169: replace init_timer with setup_timer
Replace init_timer with setup_timer to
Reloading the module does clear the error for me.
I have never seen the problem where the link comes up but it won't
receive packets.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I disabled secure boot and I was able to reproduce the problem with
mainline on the first attempt.
--
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/1841040
Title:
r8169 ethernet sometimes
Why -rc? The last working kernel I know of is from the 4.4 series.
--
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/1841040
Title:
r8169 ethernet sometimes doesn't work after cold
Seems like you may be right. I could not reproduce it with
1bcf165ac6556d after about 10 attempts. This isn't conclusive
unfortunately. I will continue with a regular bisect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I finally completed the bisection. An extremely large number of kernels
failed to build. This is the result:
# only skipped commits left to test
# possible first bad commit: [4d6ca227c768b50b05cf183974b40abe444e9d0c] Merge
branch 'for-4.12/asus' into for-linus
# possible first bad commit:
It is a r8168 card. The problem continues to happen with the dkms module
however.
--
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/1841040
Title:
r8169 ethernet sometimes doesn't work
I can no longer reproduce this in 22.04.
--
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/1841040
Title:
r8169 ethernet sometimes doesn't work after cold boot/boot
Status in linux
Public bug reported:
To reproduce:
1. Install Ubuntu
2. Switch to Nvidia driver
3. Wait
The default for Ubuntu is to install updates automatically in the
background. Eventually an updated Nvidia driver will be installed, and
then all graphics acceleration stops working for any new programs
86 matches
Mail list logo
