This bug effects me.
Raspberry Pi 4b 8G 5.1V 5A power supply. This RPi + power supply has worked for
a long time with raspiOS.
put ubuntu 24.04.2 lts image on sd card with rpi-imager.
add 'nomodeset' to cmdline.txt.
Power on.
after a long time, some activity and desktop setup started.
TZ, keyboar
On 4/22/25 09:06, Julian Andres Klode wrote:
> It's plausible to consider this user error and mark the bug as invalid;
> the /boot/grub directory shouldn't disappear (is /boot not mounted for
> some reason?). But also perhaps it should try update-grub as a best
> effort only.
>
> ** Package change
Public bug reported:
When attempt to start a previously working Win 10 VM, a popup with a critical
error appears.
"VirtualBox - Guru Mediation" A critical error has occurred while running the
virtual machine and the machine execution has stopped.
> lsb_release -rd
Description:Ubuntu 22.04 L
On 2/26/24 00:13, Gianfranco Costamagna wrote:
> Which dkms version are you using?
> $ dpkg -l |grep dkms
>
The problem was a mismatch between the gcc used to build the kernel and
the injstalled gcc version.
The kernel was built with gcc-12.
The default Ubuntu 22.04 version is gcc-11.
I use the
On 2/26/24 00:13, Gianfranco Costamagna wrote:
> Which dkms version are you using?
> $ dpkg -l |grep dkms
>
> dpkg -l |grep dkms
ii dkms 2.8.7-2ubuntu2
all Dynamic Kernel Module Support Framework
ii virtualbox-dkms
6.1.50-dfsg-
On 2/23/24 22:53, tomdean wrote:
> Public bug reported:
>
>> uname -a
> Linux aorus 6.5.0-18-generic #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb
> 7 11:40:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
>> lsb_release -a
> LSB Version: core-11.1.0ubuntu4-noarch:se
Public bug reported:
> uname -a
Linux aorus 6.5.0-18-generic #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 7
11:40:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
> lsb_release -a
LSB Version:core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID: Ubuntu
Description:Ubuntu 22.0
** Summary changed:
- when opening some books viewer is hung at 'Loading next section'
+ Calibre when opening some books viewer is hung at 'Loading next section'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Public bug reported:
> uname -a
Linux meerkat 5.8.0-59-generic #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
> lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
> apt-cache policy calibre
calibre:
Installed: 4.99.4+dfsg+really4.12.0-1
Public bug reported:
> uname -a
Linux meerkat 5.8.0-55-generic #62~20.04.1-Ubuntu SMP Wed Jun 2 08:55:04 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
> lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
> sudo apt install virtualbox-qt
eading package lists... Done
Building depen
Public bug reported:
Automatically check for updates = Never
How do I stop this from running?
> lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
> apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: (none)
Candidate: 2.3
Version table:
2.3 500
hwmatch should not be used in x86_64 systems.
set GRUB_GFXPAYLOAD_LINUX=keep in /etc/defaults/grub
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
On 6/4/21 5:29 PM, tomdean wrote:
> Public bug reported:
>
> Grub2 will not boot FreeBSD:
>error:can't find command 'hwmatch'
>
> The file hwmatch.mod is in the i386-pc directory, which is not in the
> proper location for grub to find during boot.
>
&
On 6/4/21 5:29 PM, tomdean wrote:
> Public bug reported:
>
> Grub2 will not boot FreeBSD:
>error:can't find command 'hwmatch'
>
> The file hwmatch.mod is in the i386-pc directory, which is not in the
> proper location for grub to find during boot.
>
&
Public bug reported:
Grub2 will not boot FreeBSD:
error:can't find command 'hwmatch'
The file hwmatch.mod is in the i386-pc directory, which is not in the
proper location for grub to find during boot.
cp -R /usr/lib/grub/i386-pc /boot/grub
fixes this problm
ProblemType: Bug
DistroRelease: Ub
Public bug reported:
> gnome-disks
(gnome-disks:20839): GNOME-Disks-ERROR **: 09:28:42.413: Error getting udisks
client: Error calling StartServiceByName for org.freedesktop.UDisks2: Unit
udisks2.service is masked.
Trace/breakpoint trap (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 20.0
On 5/25/21 1:14 PM, tomdean wrote:
> On 5/24/21 1:50 PM, tomdean wrote:
>> Public bug reported:
>>
>> I installed twm using apt on Ubuntu 20.04.2.
>> At login, I select twm. After entering password, screen blinks and retures
>> to password.
>> This is just
On 5/24/21 1:50 PM, tomdean wrote:
> Public bug reported:
>
> I installed twm using apt on Ubuntu 20.04.2.
> At login, I select twm. After entering password, screen blinks and retures
> to password.
> This is just after May 24 13:35 in syslog.
>
> May 24 13:36:25 mee
Public bug reported:
The search path for avr-cpp does not include /usr/local/include as in
the gcc documents.
# cpp -v
...
#include <...> search starts here:
/usr/lib/gcc/x86_64-linux-gnu/9/include
/usr/local/include
/usr/include/x86_64-linux-gnu
/usr/include
End of search list.
# avr-cpp -v
Public bug reported:
I installed twm using apt on Ubuntu 20.04.2.
At login, I select twm. After entering password, screen blinks and retures to
password.
This is just after May 24 13:35 in syslog.
May 24 13:36:25 meerkat /usr/lib/gdm3/gdm-x-session[114156]: twm:
unable to open fontset "-adobe-h
Public bug reported:
[calBackendLoader] Using Thunderbird's libical backend
console.debug: "Successfully loaded OpenPGP library librnp.so from
/usr/lib/thunderbird/librnp.so"
console.warn: "[l10nregistry] Attempting to synchronously load file\n
resource:///chrome/en-US/locale/en-US/c
This is present on my system
> cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ub
On 2020-11-02 21:15, tomdean wrote:
> Your question #693795 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/693795
>
> tomdean posted a new comment:
> libc6-dev in the title.
>
An old .depend file may have caused the requirement for byteswap-16.h.
Removing
sudo apt-get --reinstall install libc6-dev
sudo cp /mnt/usr/include/x86_64-linux-gnu/bits/byteswap-16.h
/usr/include/x86_64-linux-gnu/bits/
sudo cp /mnt/usr/include/x86_64-linux-gnu/bits/libio.h
/usr/include/x86_64-linux-gnu/bits/
sudo cp /mnt/usr/include/x86_64-linux-gnu/bits/_G_conf
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
~$ uname -a
Linux Fueno 5.3.0-7629-generic #31~1581628854~18.04~2db8a7a~dev-Ubuntu SMP Fri
Feb 14 19:57:43 x86_64 x86_64 x86_64 GNU/Linux
--
Yo
Public bug reported:
Printing is OK for a week, or, so. Then, with no changes, CUPS reports an
error
HP Office Jet Pro 9620 series "connect-to-printer" This lasts for 20 minutes,
or so.
I can ping the printer and connect to it with a browser. After pausing
the printer and resume the printer
On 2020-01-04 02:07, Dmitry Shachnev wrote:
> You reinstalled libqt5help5, but please try also reinstalling
> qttools5-dev.
>
> That is the package that contains the .pc and header files.
>
> /usr/include/x86_64-linux-gnu/qt5/QtHelp/QHelpEngine is present in that
> package. If some other includes
On 2020-01-04 01:22, Dmitry Shachnev wrote:
> Then /usr/lib/x86_64-linux-gnu/pkgconfig/Qt5Help.pc is already present.
> Why did you create it manually?
>
> https://packages.ubuntu.com/bionic/amd64/qttools5-dev/filelist
>
> In your manually created file the include path is wrong. You need to
> rep
On 1/4/20 12:50 AM, Dmitry Shachnev wrote:
> Do you have qttools5-dev package installed?
>
> ** Changed in: qttools-opensource-src (Ubuntu)
> Status: New => Incomplete
>
>
> dpkg -l | grep qttools5-dev
ii qttools5-dev-tools 5.9.5-0ubuntu1 amd64 Qt 5 development tools
Tom Dean
--
Y
Public bug reported:
> lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
> apt-cache policy libqt5help5
libqt5help5:
Installed: 5.9.5-0ubuntu1
Candidate: 5.9.5-0ubuntu1
Version table:
*** 5.9.5-0ubuntu1 500
500 http://us.
The problems appears to be arts of gnome left over from ahanging to TWM.
The following eliminated the problem.
[code]
sudo apt remove --purge gnome-calendar
sudo apt remove --purge libgnome-todo
sudo apt remove --purge gnome-mahjongg gnome-mines gnome-sudoku
sudo apt purge gnome-wea
I have another 18.04.3 installation on this computer, on a WD5000, that
also uses TWM. The 27 second display does not happen. On that system,
I notice a difference in time for the very first execution of eog to the
next. The shared libs seem to have stayed loaded inbetween.
** Changed in: eog (
I have this problem.
Ubuntu 18.04.3
4.15.0-58-generic kernel
X and TWM. Some gnome things are running...
eog image1.jpg takes 27 seconds to open a window.
Sometimes, I get 'Failed to register: Timeout was reached' message and
eog is terminated.
This happens when I have TWM as the desktop. Wit
Still in 18.04 LTS
> uname -a
Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
>
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426216
Title:
pci driver messages - BAR 13: no space for
To manage notifications abo
This happens on my system.
Meerkat> uname -a
Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Meerkat> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Cod
On 8/6/19 9:08 AM, tomdean wrote:
> This does not seem to happen with the 4.15.0-55-generic kernel. I
> allowed simple_ra to run for several hours with the 4.15.0-55-generic
> kernel.
>
Update:
> uname -a
Linux Meerkat 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC
201
This does not seem to happen with the 4.15.0-55-generic kernel. I
allowed simple_ra to run for several hours with the 4.15.0-55-generic
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839171
T
Public bug reported:
> lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
While running simple_ra and doing other things so simple_ra is not
always in totally in the foreground,
Aug 6 08:17:57 Meerkat kernel: [57269.891310] python2[9124]: segfault at 20 ip
7f0834c979e
On 10/30/18 5:25 AM, Marc Deslauriers wrote:
> In Xenial, /usr/share/ghostscript/9.5/iccprofiles was a directory.
> In Bionic, it is a symlink to /usr/share/color/icc/ghostscript.
>
> The Bionic package needs to use dpkg-maintscript-helper to ensure the
> transition is done properly.
>
> I will p
On 10/28/18 9:31 AM, brian_p wrote:
> ls -l/usr/share/ghostscript/
> ls -l /usr/share/ghostscript/
total 8
drwxr-xr-x 4 root root 4096 Oct 28 06:49 9.25
lrwxrwxrwx 1 root root 37 Aug 8 2017 current ->
/etc/alternatives/ghostscript-current
drwxr-xr-x 2 root root 4096 Oct 19 12:44 fonts
Tom D
HP Officejet Pro 8620 fails printing with filter failed message
sudo rmdir /usr/share/ghostscript/9.25/iccprofiles
sudo apt-get install --reinstall libgs9-common
in cups, localhost:631, restart jobs
printed all jobs.
My issue seems to be fixed.
Does something need to be done in the upgrade proces
Public bug reported:
After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails
to print with the status "Filter Failed".
On a 16.04 system printing is OK.
Printer: Network HP-Officejet-Pro-8620
No changes were made other than the do-release-upgrade and 'apt dist-upgrade'.
Pro
Public bug reported:
The upgrade completed and I do not see a problem with using the system.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.27
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion:
On 01/04/18 09:29, Pablo wrote:
> Hi again,
>
> I forgot to comment that this issue also appear in Debian 9 (my other
> PC)...
>
As I posted earlier, this seems to be related to the version of Linux.
I do not have this problem with
Meerkat> uname -a
Linux Meerkat 4.13.9-041309-generic #201710
On 08/07/2017 11:39 PM, Kai-Heng Feng wrote:
> Probably. Although a quick look at the USB stack difference from
> 4.4.0-78.99 to 4.4.0-89.112, I can't find commits related to this issue.
>
> But feel free to reopen the bug if this happens again.
>
> ** Changed in: linux (Ubuntu)
> Status:
On 08/03/2017 10:54 PM, Kai-Heng Feng wrote:
> Okay, I just found a hub with the same VIA chip inside.
> Remote wakeup works when autosuspend is enabled.
>
> Hub like this generally can connect to auxiliary power cord. Does power
> cord connection make any difference?
>
I upgraded the system by
On 08/03/2017 10:54 PM, Kai-Heng Feng wrote:
> Okay, I just found a hub with the same VIA chip inside.
> Remote wakeup works when autosuspend is enabled.
>
> Hub like this generally can connect to auxiliary power cord. Does power
> cord connection make any difference?
>
I normally run the hub wi
On 06/05/2017 08:57 PM, Kai-Heng Feng wrote:
> If you plugged a USB mouse or keyboard to the same port, will it be
> recognized?
>
I plugged a Microsoft USB 2.0 mouse into the externa Plugable USB 3.0
hub and it was recognized.
--
You received this bug notification because you are a member of
On 06/02/2017 12:27 AM, Kai-Heng Feng wrote:
> Sounds like there are two problems here,
> 1. The external drive does not work well in UAS mode (see previous comment)
> 2. The VIA hub has a remote wakeup bug.
>
> uname -a
Linux P9X79 4.12.0-041200rc2-generic #201705212331 SMP Mon May 22
03:32:26
As suggested by kai.heng.feng, I installed the 4.12.0-041200rc2 kernel.
If I connect my WD My Passport drive into an Plugable 7-port, external
USB 3.0 hub, it is not recognized. 'sudo lsusb -v' causes the drive to
be recognized and I can mount it. If I disconnect the drive, wait a few
seconds
ature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: tomdean3698 F pulseaudio
- /dev/snd/controlC0: tomdean3698 F pulse
I installed the '4.22.3' kernel, should be 4.11.3
I marked the bug as confirmed as requested by Joseph Salisbury.
I also tagged the bug as 'kernel-bug-exists-upstream' as requested by
Joseph Salisbury.
** Tags removed: amd64 apport-bug xenial
** Tags added: kernel-bug-exists-upstream
** Changed
On 05/30/2017 08:14 AM, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
This did not start happening after an upgrade.
I do not know of a previous version where this did work.
On 05/26/2017 01:42 AM, Kai-Heng Feng wrote:
> @tomdean
>
> Let's not hijack the original bug.
> Can you file a new bug?
>
> $ ubuntu-bug linux
>
Sorry, typo in the bug number.
I created bug 1693842.
Tom Dean
--
You received this bug notification because you a
On 05/26/2017 01:42 AM, Kai-Heng Feng wrote:
> @tomdean
>
> Let's not hijack the original bug.
> Can you file a new bug?
>
> $ ubuntu-bug linux
>
I created bug 1603842.
Tom Dean
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
ecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tomdean3698 F pulseaudio
/dev/snd/controlC0: tomdean3698 F pulseaudio
Date: Fri May 26 09:05:20 2017
HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a
InstallationDate: Installed on 20
I did a regression on a USB 3.0 problem in 2013. This traced the
problem to a change in the usb code.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151622
Tom Dean
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
On 05/24/2017 09:36 PM, Kai-Heng Feng wrote:
> Create a file, "/etc/modprobe.d/uas-quirk.conf" with this line inside:
> options usb-storage quirks=::u
>
> Replace "" with the storage device's vid:pid in lsusb.
>
I created the file and rebooted with the drive connecte. The reboot
re
On 05/21/2017 09:58 PM, Kai-Heng Feng wrote:
> Well, these are XHCI:
> Good Autosuspend for USB device xHCI Host Controller [usb3]
> Good Autosuspend for USB device xHCI Host Controller [usb4]
> Good Autosuspend for USB device xHCI Host Controller [usb5]
> Good Autosuspend for USB device xHCI Host
I do not see runtime pm for XHCI
Lots for PCI, some for I2c
There are some autosuspend for HCI
Good Autosuspend for unknown USB device 1-1 (8087:0024)
Good Autosuspend for USB device xHCI Host Controller [usb3]
Good Autosuspend for USB device xHCI Host Control
I should have posted the entire list:
> lsusb
Bus 002 Device 006: ID 0cf3:3005 Qualcomm Atheros Communications AR3011
Bluetooth
Bus 002 Device 007: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. I
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
Ubuntu on sda.
P9X79 Motherboard
Plugable 7-port powered USB 3.0 Hub -> USB 3.0 MB Port
Plugable 7-port powered USB 2.0 Hub -> USB 2.0 MB Port
WD My Passport 2T USB 3.0/2.0 Drive
f I plug the WD drive into the USB 3.0 hub power on the computer a
Public bug reported:
/usr/bin/xclock -digital -twentyfour -update 1 -geometry 230x30-1+1
xclock starts displaying time in 24 hour format as requested.
At noon the next day, xclock reverts to displaying time in 12 hour
format.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: x11-apps 7.7+2
status, quitting.
make[2]: *** [doc/interpreter/octave.dvi] Error 1
make[2]: Leaving directory `/home/tomdean/Math/Octave/octave-build'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/tomdean/Math/Octave/octave-build'
make: *** [check] Error 2
--
You receive
On 05/13/16 01:37, tomdean wrote:
Please close this report.
The change to systemd/udev changed the naming for network devices. Many
software packages, such as maple, use the network device name as part of
the licensing process.
The change on the network device name caused these applications
My email address was not available on the 16.04 machine.
Email: tomd...@wavecable.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581374
Title:
Upgrade from 14.04 to 16.04 Changed Network Device
Public bug reported:
The upgrade from 14.04 to 16.04 changed the network device name from
eth0 (14.04) to eno1 (16.04).
This name change broke lots of software. For example, Maple
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.14
ProcVersionSignature:
I upgraded to Ubuntu 14.04 LTS.
The problems and artifacts I saw with 12.04 LTS are not present.
Thank you,
Tom Dean
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1151622
Title:
050d:0237 [ASUS P9
nux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> sudo avrdude -c avrisp2 -p x128a1 -Pusb -v -t
[sudo] password for t
I have Ubuntu 12.04 as a primary desktop. The hardware is a P9X79
motherboard with USB keyboard and USB mouse. I do not use Unity, etc. I
start TWM and use xterm most of the time.
If I boot linux-3.2.0-38-generic (Ubuntu 12.04), and fill the xterm
buffer with lines of text (repeat ls;ls;...;l
On 01/09/14 14:41, Christopher M. Penalver wrote:
> tomdean, thank you for providing the requested information. As Trusty
> has been rebased to the 3.13.x series kernel, could you please test this
> and advise to the results via http://cdimage.ubuntu.com/daily-
> live/current/ ?
&g
On 01/06/14 14:02, Christopher M. Penalver wrote:
> tomdean, thank you for testing the v3.13-rc6 mainline kernel. Just to
> clarify, regarding only the issue mentioned in the Bug Description about
> accessing the avrisp2, with avrdude when plugged into the Belking Hub,
> the pr
On 01/02/14 22:33, Christopher M. Penalver wrote:
Booting
> uname -a
Linux P9X79 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
and repeating the scroll test does not result in a slinky scroll and top
shows Xorg using 15% of one cpu, max.
Something
On 01/02/14 22:33, Christopher M. Penalver wrote:
The looping in the USB driver with the message about failure to assign
address with a USB 3.0 device is not there with the latest kernel.
> uname -a
Linux P9X79 3.13.0-031300rc6-generic #201312291935 SMP Mon Dec 30
00:37:05 UTC 2013 x86_64 x86_
On 01/02/14 22:33, Christopher M. Penalver wrote:
> tomdean, thank you for the URL. I see what happened in why your post was
> largely ignored, as it was because you didn't follow the directions in
> noting everything in the upstream kernel, you did everything in
> downstream. So,
On 01/02/14 21:38, Christopher M. Penalver wrote:
> tomdean, please see
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151622/comments/30
> .
>
http://comments.gmane.org/gmane.linux.usb.general/92215
Is this it?
--
You received this bug notification because you are a memb
On 01/02/14 21:38, Christopher M. Penalver wrote:
> tomdean, please see
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151622/comments/30
> .
>
No, I do not have a direct web link to the post.
--
You received this bug notification because you are a member of Ubuntu
Bu
On 01/02/14 20:17, Launchpad Bug Tracker wrote:
> [Expired for linux (Ubuntu) because there has been no activity for 60
> days.]
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Expired
>
Will this ever be fixed?
--
You received this bug notification because you are a member of U
Here is a copy of the upstream report.
I tested the latest kernel, 3.12.0-031200rc7-generic and the problem is
there. But, not with 3.2.0-38-generic
** Attachment added: "Copy og the Upstream Report"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151622/+attachment/3898898/+files/ups
I removed the USB 3.0 hub and disabled 3.0 support in BIOS.
If I boot any kernel after
> uname -a
Linux P9X79 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
I get slinky scrolling in any xterm. This looks like the system is
heavily loaded. But, top
On 08/11/13 15:41, Greg KH wrote:
I tried linux 3.2.0-40, 3.2.0-5, 3.9.0-7, and, 3.10.5-031005.
The problem started back in 3.2.0-39. Here is a git bisect log
# bad: [ba89d2a7ca8233e29c9fdeabefb7fdbb6775626e] UBUNTU: Ubuntu-3.2.0-39.62
# good: [1420ada1a002d99e49d68d60a72f29ba58376b90] UBUNTU:
On 08/11/13 01:34, tomdean wrote:
I filed an upstream report. I CC'd the Bug 1151622, but, launchpad
refused the CC.
Error message:
The message you sent included commands to modify the bug report,
but you didn't sign the message with an OpenPGP key that is
registered in Launc
On 08/10/13 17:26, Christopher M. Penalver wrote:
> tomdean, the next step would be to perform a Ubuntu kernel commit bisect
> from 3.2.0-38 to 3.2.0-39, in order to identify the offending commit.
> Could you please do this following
> https://wiki.ubuntu.com/Kernel/KernelBisection ?
On 08/10/13 14:00, Christopher M. Penalver wrote:
> tomdean, the next step would be to perform a Ubuntu kernel bisect from
> 3.2.0-38 to 3.2.0-40, in order to identify the offending commit. Could
> you please do this following
> https://wiki.ubuntu.com/Kernel/KernelBisection ?
The
On 08/10/13 13:12, Christopher M. Penalver wrote:
> tomdean, could you please unplug all USB devices from your computer, plug in
> just the hub with nothing further attached in it, and then immediately place
> the following in a terminal and attach the results:
> lsusb -v &
On 08/10/13 01:32, Christopher M. Penalver wrote:
> tomdean, did this problem not occur in a release prior to Precise?
>
I do not know. I do not have prior releases. I did not have the USB
3.0 hub prior to my reporting the problem. I reported this problem the
first time I connected t
** Tags removed: kernel-unable-to-test-upstream-v3.11-rc4
** Tags added: kernel-bug-exists-upstream-v3.11-rc4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1151622
Title:
[ASUS P9X79 PRO] The usb dr
On 08/09/13 16:43, Christopher M. Penalver wrote:
> tomdean, just to clarify, with the mainline kernel you couldn't test for
> the problem you originally reported about because the computer was
> having performance problems, correct?
>
> ** Tags removed: kernel-bug-exis
On 08/09/13 16:43, Christopher M. Penalver wrote:
> tomdean, just to clarify, with the mainline kernel you couldn't test for
> the problem you originally reported about because the computer was
> having performance problems, correct?
>
> ** Tags removed: kernel-bug-exis
I do not want to miss something that may be important. The difference I
see in linux 3.2.0-38 and later kernels is the error happening in a loop
in the later versions.
I do not use the desktop. I boot to the console and then startx. I do
not need the desktop and often run without X.
An addi
On 08/09/13 04:35, Christopher M. Penalver wrote:
> tomdean, could you please confirm this issue exists with the latest
> development release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
> could you please run t
On 08/09/13 04:35, Christopher M. Penalver wrote:
> tomdean, could you please confirm this issue exists with the latest
> development release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
It will be a couple days before
On 08/03/13 22:02, Christopher M. Penalver wrote:
> tomdean, as per
> http://www.asus.com/Motherboards/P9X79_PRO/#support_Download_8 an update
> is available for your BIOS (4104). If you update to this, does it change
> anything?
>
> If not, could you please both specify what hap
On 08/03/13 22:02, Christopher M. Penalver wrote:
> tomdean, as per
> http://www.asus.com/Motherboards/P9X79_PRO/#support_Download_8 an update
> is available for your BIOS (4104). If you update to this, does it change
> anything?
>
OK. It will be a couple days before I can do th
** Tags removed: amd64 apport-bug precise staging
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170428
Title:
USB Driver appears to hang in a loop
To mana
On 04/19/13 08:58, Joseph Salisbury wrote:
> Does this issue go away if you boot into the previous kernel?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.9 kernel[0].
>
> If this bug is fixe
Public bug reported:
After update and the subsequent reboot, the usb driver appears to be
hung in a loop:
> grep "usb 6" /var/log/syslog| tail
Apr 18 10:25:24 P9X79 kernel: [ 1566.320053] usb 6-1: Device not responding to
set address.
Apr 18 10:25:25 P9X79 kernel: [ 1566.523901] usb 6-1: Device
** Tags removed: amd64 apport-bug precise staging
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1151622
Title:
The usb driver appears to fail
To manage not
kernel-bug-exists-upstream
I downloaded
linux-headers-3.9.0-030900rc1-generic_3.9.0-030900rc1.201303060659_amd64.deb
linux-image-3.9.0-030900rc1-generic_3.9.0-030900rc1.201303060659_amd64.deb
linux-image-extra-3.9.0-030900rc1-generic_3.9.0-030900rc1.201303060659_amd64.deb
# sudo dpkg -i *.deb
..
1 - 100 of 171 matches
Mail list logo
