2024.04.1 loaded from usb drive.
** Changed in: subiquity
Status: Expired => Confirmed
** Also affects: 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.
Apologies. Looking for a workaround, thought I found on. was mistaken.
Delete my comment if you can.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589028
Title:
Improper blocksize set by usb-creat
Workaround:
Eject the disk
Remove the disk from the USB slot
Plug it back in
Create your partition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589028
Title:
Improper blocksize set by usb-creato
Retested on 13.10 32 bit updated as of 20-Dec-2013.
This is now working correctly.
After boot or after resume, you can start flightgear and the pedals
work.
This bug can now be closed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notificatio
Retesting on 13.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/38
Title:
[Gigabyte P35-S3G] Saitek Pedals not recognized at boot, work after
unplugging and plugging back in
To manage notifi
This one is closed see Bug #1239912 against 13.10 so take a look there.
for the record, the workaround:
sudo /usr/share/system-config-lvm/system-config-lvm.py;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
the workaround:
sudo /usr/share/system-config-lvm/system-config-lvm.py;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239912
Title:
system-config-lvm fails to start citing missing /etc/init.d/lvm2
** This bug is no longer a duplicate of bug 390421
system-config-lvm fails with invoke-rc.d: unknown initscript,
/etc/init.d/lvm2 not found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239912
T
** Also affects: xdiagnose
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/1005573
Title:
Apport should not present the user with non-actionable information
I tested this with kernel 3.2.0-030200rc2-generic #20151435 SMP
fromfolder v3.2-rc2-oneiric/15-Nov-2011 19:51 in
http://kernel.ubuntu.com/~kernel-ppa/mainline/
The bug is not fixed in the mainline kernel
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exi
** Summary changed:
- Saitek Pedals not recognized at boot
+ Saitek Pedals not recognized at boot, work after unplugging and plugging back
in
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/38
Tit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/38
Title:
Saitek Pedals not recognized at boot, work after unplugging and
plugging back in
To manage notifications about this bug go to:
https://b
Public bug reported:
This report applies to Ubuntu 11.10.
The bug exists under previous versions of linux.
After a boot, Saitek pedals are not recognized.
dmesg contains multiple attempts to read the device:
usb 5-2: device descriptor read/64, error -32
etc.
If you unplug and re-plug the device
This issue is still with us in Ubuntu 11.10
I will file a current bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/565222
Title:
Saitek Pro Pedals not recognized
To manage notifications ab
I Can confirm that this bug also appears in Ubuntu 11.04. I will file a
bug there.
In my case, the symptom appears after a boot.
It can be reproduced at will by unloading and reloading the usb or usbhid
driver.
The current workaround is to unplug the Saitek pedals and plug them back
in.
For s
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746831
Title:
WARNING: at /build/buildd/linux-2.6.38/fs/sysfs/dir.c:455
sysfs_add_one+0x9b/0xd0()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Public bug reported:
This happened when attempting to pair with a bluetooth headset
ProblemType: KernelOops
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-7-generic 2.6.38-7.39
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-
The following case statement in f_u32.c may be the cause:
case 20:
switch (ntohl(key->mask)) {
case 0x:
fprintf(f, "\n match sport %u",
ntohl(key->val) & 0x);
return
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746187
Title:
tc -p option transposes dport and sport output
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
Public bug reported:
Binary package hint: iproute
$ lsb_release -rd
Description:Ubuntu Natty (development branch)
Release:11.04
The filter settings for dport get printed out as sport settings and vice
versa when the -p option is specified for the command.
This issue happens for dpor
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/43865938/lspci.txt
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Alt+SysReq+K is a workaround though.
** Attachment added: "dmidecode.txt"
http://launchpadlibrarian.net/43865894/dmidecode.txt
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because yo
I just nominated this for Lucid because it prevents the beta 1 or beta2
install disks from proceeding beyond the initial screen with the dots.
Kind of ironic, since the purpose of plymouth was to provide a smooth
boot experience.
Anyway, if this is not fixed for the release, Ubuntu is going to hav
23 matches
Mail list logo
