** Also affects: ubiquity (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.net/bugs/1509633
Title:
Failed Ubuntu 15.10 installation on UEFI system if
** Also affects: dell-sputnik
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/1500387
Title:
System boots to a black screen and the customer has to close
Chris: I'm well aware of the newer BIOS versions. I work at Dell on
Project Sputnik. The issue is that the I2S audio mode is not well
supported. There is now a quirk in the Linux kernel that sets the ACPI
_REV reported to the firmware to 5 only if on certain systems needing to
be quirked. (Setting
Is there a sponsor for trusty or vivid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415880
Title:
14e4:4365 bcmwl-kernel source: fix for null pointer crash
To manage notifications about this
Yes, please go ahead with removing dell-dup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491140
Title:
Please remove dell-dup from the archive
To manage notifications about this bug go to:
** Also affects: dell-sputnik
Importance: Undecided
Status: New
** Changed in: dell-sputnik
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415880
Title:
Uh, you realize that Debian doesn't have biosdevname, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455871
Title:
biosdevname isn't giving interface names as expected
To manage
** Package changed: efibootmgr (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393575
Title:
efibootmgr gives an Oops
To manage notifications about this bug go to:
rEFInd isn't even part of Ubuntu. From what you describe, efibootmgr is
functioning just fine. You likely need to file a bug against rEFInd
instead.
** Changed in: efibootmgr (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Matthew Garrett developed a patch to make Linux's ASPM support match
reality. Please backport this to Ubuntu's 3.13, 3.16 and 3.19 kernels.
This should offer power savings and would match Windows behavior.
Please see the submission at https://lkml.org/lkml/2015/4/7/781.
**
Public bug reported:
Matthew Garrett developed a patch to make Linux's ASPM support match
reality. Please backport this to Ubuntu's 3.13, 3.16 and 3.19 kernels.
This should offer power savings and would match Windows behavior.
Please see the submission at https://lkml.org/lkml/2015/4/7/781.
**
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441335
Title:
PCI: Don't clear ASPM bits when the FADT declares it's unsupported
Also verified that that works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431857
Title:
dbus crash in ubuntu 14.04
To manage notifications about this bug go to:
Public bug reported:
The system is a Dell Precision M3800 Developer Edition, i.e. it has
Ubuntu 14.04 factory installed. If I upgrade the kernel and Xorg to the
Utopic HWE versions, the touchscreen doesn't work. *However*, if I
suspend and resume, the touchscreen starts working again.
I noticed
Awesome, I see that installing the HWE Xorg also removes gnome-control-
center. (and downgrades the nvidia driver from 340 to 331).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430622
Title:
** Summary changed:
- [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped
working in Ubuntu 15.10
+ [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped
working in Ubuntu 15.04
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Volume hotkeys were working and now they're not. A coworker has another
2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated in a week,
and the hotkeys function, so it seems like the bug came up sometime in
the past week.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Public bug reported:
Note that I am forcing the audio into HDA mode. (It has two modes: HDA
and I2S.) In HDA mode, audio out works. The mic is known with a previous
version of ALSA (Sept 3 2014 snapshot).
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
Thanks Robert. See the attached log. This seems to be relevant from
there:
[+0.45s] DEBUG: main-window.vala:185: Screen is 3840x2160 pixels
[+0.45s] DEBUG: main-window.vala:193: Monitor 0 is 3840x2160 pixels at 0,0
[+0.45s] DEBUG: main-window.vala:185: Screen is 1920x1080 pixels
[+0.45s] DEBUG:
Andon: Nope, same thing with those commits.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413446
Title:
Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04
To manage
Public bug reported:
Tap-to-click does not work unless I tap several times really fast (which
is really hard to do), which also causes the cursor to move. This is a
poor user experience.
Relatedly, sometimes when using two-finger scrolling, the touchpad will
get stuck such that I can let go and
Building with the ASoC for-next branch[1], I get what's possibly slightly
improved results:
$ dmesg -t | egrep (audio|snd|INT3438)
dmar: ACPI device INT3438:00 under DMAR at fed91000 as 00:13.0
snd_hda_intel :00:03.0: enabling device ( - 0002)
sst-acpi INT3438:00: DesignWare DMA
Public bug reported:
(This is a public bug report for LP1402828.)
This system has a dual-mode audio with an HDA and an I2S interface.
Which shows up depends on the reported _OSI from the last cold boot.
Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
report an _OSI of Windows
** Attachment removed: ProcCpuinfo.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446/+attachment/4303432/+files/ProcCpuinfo.txt
** Attachment removed: IwConfig.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446/+attachment/4303430/+files/IwConfig.txt
**
** Also affects: dell-sputnik
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/1315770
Title:
[Dell Precision M3800, Realtek ALC668, Black Headphone Out,
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366841
Title:
[Dell XPS 11] Card reader RTS5249 doesn't work
is still necessary. The patches for LP 723994 do not fix
this bug.
** Changed in: linux (Ubuntu Trusty)
Assignee: Daniel Jared Dominguez (jared-dominguez) = (unassigned)
** Changed in: linux (Ubuntu Utopic)
Assignee: Daniel Jared Dominguez (jared-dominguez) = (unassigned)
--
You received
That's just a workaround that manually forces MSI to be disabled. If you look
at the lspci output in that other bug report, you see that MSI is also disabled
for the card reader in that system:
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5249
(rev 01)
[snip]
Public bug reported:
This patch has been submitted upstream and is queued up for inclusion in
mfd-next:
https://git.kernel.org/cgit/linux/kernel/git/lee/mfd.git/commit/?h=for-
mfd-nextid=eb61b3276e099d937fcdae2c67aec4766bba2dc3
Please include this patch in Trusty and Utopic.
** Affects: linux
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366841
Title:
mfd: rtsx_pcr: Fix MSI enable error handling
To manage
Bernard,
We still haven't been able to reproduce the bug, but if you have time,
please see if the following patches applied to your kernel help:
[PATCH net v5 1/4] tg3: Limit minimum tx queue wakeup threshold
http://marc.info/?l=linux-netdevm=140934527707734w=2
[PATCH net v5 2/4] tg3: Fix
It was suggested to me that this may be relevant:
https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=4d8fdc95c60e90d84c8257a0067ff4b1729a3757
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks. I'm building with this patch now and will upload to Debian. I'll
need to also have it SRU'ed.
** Changed in: ledmon (Ubuntu)
Status: New = In Progress
** Changed in: ledmon (Ubuntu)
Assignee: (unassigned) = Daniel Jared Dominguez (jared-dominguez)
** Also affects: dell
** Changed in: biosdevname (Ubuntu)
Status: New = Opinion
** Changed in: systemd (Ubuntu)
Status: New = Opinion
** Changed in: udev (Ubuntu)
Status: New = Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is fixed in Utopic.
** Changed in: efibootmgr (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311917
Title:
not built for arm64
To manage
I need more information on whether this bug still exists on Ubuntu
12.04. Based on comment #5, it doesn't exist on any other currently
supported Ubuntu releases.
** Changed in: efibootmgr (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a
** Changed in: mactel-support
Status: Confirmed = Fix Released
** Changed in: efibootmgr (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/248699
** Changed in: efibootmgr (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/bugs/948568
Title:
System does not boot
To manage notifications about this bug go to:
** Changed in: efibootmgr (Ubuntu)
Status: Confirmed = Invalid
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Invalid
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Please report upstream.
** Changed in: efibootmgr (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058751
Title:
The -b switch for modifying a variable
** Changed in: efibootmgr (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/bugs/1314759
Title:
Issues with dual-booting Windows 8 and Ubuntu 14.04 on a Sony Vaio
Bernard,
I've some quick suggestions from my colleague Narendra here at Dell to
pass on. First try disabling TSO. If that doesn't work, disable both GSO
and TSO. ethtool can be used to disable both GSO and TSO.
Also, I can't see what firmware version you have on the NIC. Can you
verify that it's
Whoops, even if you hadn't updated the firmware, I gave you the wrong
link anyway.
I did see that the bug is fixed if you disable SG. I'm trying to isolate
the cause, and my colleague gave those suggestions. The goal is to fix
the bug, not leave you permanently without offloading capabilities.
Could you do two different tests?
1) Re-enable only Smart Connect. Does the issue persist?
2) With Smart Connect enabled, can you check if the intel-smartconnect
module is loaded? In your apport report, it looks like it gets loaded...
The kernel should output Disabling Intel Smart Connect if the
Tested on an XPS 15.
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255297
Title:
XPS 15 SD Card Reader Support
I tested on an L322X with _F_HD display and A09 BIOS in UEFI mode.
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/ubuntu--vg-root ro
splash quiet i915.disable_pch_pwm=0 vt.handoff=7
If I use i915.disable_pch_pwm=0 with the legacy OPROM enabled, I have to run
echo
Public bug reported:
The latest linux-firmware in saucy is missing firmware for ath10k chips
even though the ath10k drivers exist in saucy. This is likely because
the ath10k firmware is not available in the upstream linux-firmware git
repository. http://wireless.kernel.org/en/users/Drivers/ath10k
** Also affects: firmware-nonfree (Debian)
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/1232990
Title:
firmware for ath10k missing
To manage
** Bug watch added: Debian Bug tracker #724970
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724970
** Changed in: firmware-nonfree (Debian)
Importance: Undecided = Unknown
** Changed in: firmware-nonfree (Debian)
Status: New = Unknown
** Changed in: firmware-nonfree (Debian)
Yes, I did a full reinstall and tested all four cases as in my last
comment. When I did the UEFI install, I booted the Ubuntu 13.04 Desktop
installer in UEFI mode since I was trying not to make my life too
difficult. :) I forgot to mention, but the firmware version was A09 as
well. I did not
Nikki: Oh, actually, which version of Ubuntu are you installing? I ask
because I've not seen any issues on Ubuntu 12.04...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169376
Title:
XPS13
I tested with these kernels in both UEFI and BIOS (CSM) mode:
linux-image-3.8.0-27-generic (raring)
linux-image-3.8.0-29-generic (raring-proposed)
In all four cases, the backlight buttons do not work correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Addie: Did you do a reinstall or just switch to EFI mode and update the
bootloader? If the Former, please confirm what the difference in
packages and package versions is between your previous install and your
current install.
--
You received this bug notification because you are a member of
Michael: Before switching to an unsupported kernel, please use first try
the linux-image-generic-lts-raring kernel. Since you're using an old
BIOS version, please update that as well. Also, if you bought the XPS 13
Developer Edition, note that you are entitled to help from Dell
ProSupport. (I am
Public bug reported:
Precise's udev package doesn't detect that the Dell Latitude 6430U or
3330 need keyboard force release synthesis. This causes undesirable
behavior on these two systems. Quantal and upstream udev have an updated
rule to handle the 6430U. Neither have such a rule to handle the
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1193147
Title:
[keymap] Touchpad key broken on Dell Latitude 6430U and 3330
To manage notifications about this bug go to:
Public bug reported:
Running 3.8.0-19.30 or 3.8.0-20.31 (and likely some earlier versions), no
carrier is detected by the OS on eth0 (e1000e driver) on my Latitude E6420. 'ip
link' shows:
2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state
DOWN mode DEFAULT qlen 1000
Yes, Ubuntu 12.04 does not have this issue.
Actually, I see that 3.9-rc5 was released yesterday, and it contains this
change:
Revert drm/i915: write backlight harder
http://permalink.gmane.org/gmane.linux.kernel.commits.head/372554
Right now, someone else is using the L322X I was testing with,
Public bug reported:
On both versions of the XPS 13 (L322X and L321X) running Ubuntu Raring with the
latest 3.8 kernel, letting the screen turn off and then back on causes the
backlight to go to maximum brightness and become not adjustable. This behavior
is not seen with suspend/resume or at
apport information
** Tags added: apport-collected raring
** Description changed:
- On both versions of the XPS 13 (L322X and L321X) running Ubuntu Raring
- with the latest 3.8 kernel, letting the screen turn off and then back on
- causes the backlight to go to maximum brightness and become not
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606969/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606970/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606971/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606972/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606973/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606974/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606975/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606976/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606977/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606978/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606979/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606980/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1162026/+attachment/3606981/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
I've tested with the latest upstream kernel.
test@test-Dell-System-XPS-L322X:~$ uname -a
Linux test-Dell-System-XPS-L322X 3.9.0-030900rc4-generic #201303232035 SMP Sun
Mar 24 00:36:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-bug-exists-upstream
--
You received this bug
** Description changed:
- On both versions of the XPS 13 (L322X and L321X) running Ubuntu Raring with
the latest 3.8 kernel, letting the screen turn off and then back on causes the
backlight to go to maximum brightness and become not adjustable. This behavior
is not seen with suspend/resume or
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jared 1925 F pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=293cdf82-ef61-45de-8ab3-5113c6788a9b
InstallationDate: Installed on 2013-03-01 (7
apport information
** Attachment added: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564140/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564141/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564142/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
Cypress
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564146/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564147/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564144/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564148/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564143/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564151/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564153/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564155/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564149/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564154/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564150/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1048258/+attachment/3564152/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
I've tested on a second system and found the same behavior.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048258
Title:
Cypress
This fix does not appear to be in the 3.8 kernel for Raring. I see the same
kernel messages:
[ 326.372692] psmouse serio1: Trackpad at isa0060/serio1/input0 lost sync at
byte 1
[ 326.374291] psmouse serio1: Trackpad at isa0060/serio1/input0 - driver
resynced.
The kernel I am running is
** Changed in: linux (Ubuntu)
Status: Fix Committed = New
** Changed in: linux (Ubuntu)
Assignee: Kyle Fazzari (kyle.f) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
0.5 is in git: http://linux.dell.com/cgi-
bin/gitweb/gitweb.cgi?p=biosdevname.git;a=summary
I'm not sure why there isn't a tarball for it at
http://linux.dell.com/files/biosdevname/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Colin: Here's a screenshot.
** Attachment added: IMAG0309.jpg
https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/1065281/+attachment/3499057/+files/IMAG0309.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Colin: I've subscribed Matt to this bug and will email him requesting
that he incorporate that in a new upstream release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065281
Title:
Installer
Jordan Hargrave now owns efibootmgr. I've asked him about incorporating
this patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065281
Title:
Installer crashed when trying to partition 4k/4k
For the language bindings, at minimum please include those for C, C++
and Python. Other components that are built from this source that are
needed are (using the rpm names since openwsman includes a spec.in)
libwsman1, libwsman-devel, libwsman_clientpp1, libwsman_clientpp-devel,
and
I've encountered the same problem. I installed Ubuntu 12.10 without any
network access from a USB stick created with usb-creator-gtk -n. I
also notice that there are no linux-signed* packages on the live CD
install media, although grub2-signed (actually grub-efi-amd64-signed)
and shim-signed are
1 - 100 of 153 matches
Mail list logo
