[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
Turns out "pcie_aspm=off" effectively disables AER because Linux doesn't
request AER control when it doesn't advertise ASPM support (see
ACPI_PCIE_REQ_SUPPORT). That explains why "pcie_aspm=off" would avoid
the error reporting.
This report was from a v3.11-based kernel. v3.11 is from Mon Sep 2
13:46:10 2013, so it should contain
https://git.kernel.org/linus/dce87b960cf4 ("netxen: mask correctable
error"), which should mask all Correctable Errors for this device (see
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/qlogic/netxen/netxen_nic_main.c?id=v3.11#n1420),
so I don't know why this flood happened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279699
Title:
AER: Corrected error received: id=00e4 / PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279699/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 671979] Re: Repeated (spurious?) pcieport errors in logs (PCIe Bus Error)
Also, if you do see this issue, some have reported that "pcie_aspm=off" avoids the errors. If that's the case for you, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6 and help me investigate it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/671979 Title: Repeated (spurious?) pcieport errors in logs (PCIe Bus Error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/671979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
Generally we should not see reproducible PCIe Correctable Errors in significant numbers. Some have reported that "pcie_aspm=off" avoids the errors. If that's the case for you, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6 and help me investigate it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279699 Title: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726159] Re: PCIe BUS Error causing really slow laptop performance
We should not need to use "pci=noaer". Generally we should not see reproducible PCIe Correctable Errors in significant numbers. Some have reported that "pcie_aspm=off" avoids the errors. If that's the case for you, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6 and help me investigate it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726159 Title: PCIe BUS Error causing really slow laptop performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2033693] Re: Kernel bug lead to unresponsive system
Is this reproducible? Is it related to suspend/resume? Even if the kernel hang is not reproducible, I'm interested in the PCIe Corrected Errors. Some have reported that "pcie_aspm=off" avoids the errors. If that's the case for you, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6 and help me investigate it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2033693 Title: Kernel bug lead to unresponsive system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852420] Re: /var/log/syslog and /var/log/kern.log reports millions of nvme errors
We should not need to use "pci=noaer". Generally we should not see reproducible PCIe Correctable Errors in significant numbers. Some have reported that "pcie_aspm=off" avoids the errors. If that's the case for you, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6 and help me investigate it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852420 Title: /var/log/syslog and /var/log/kern.log reports millions of nvme errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859429] Re: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
We should not need to use "pci=noaer". Generally we should not see reproducible PCIe Correctable Errors in significant numbers. Some have reported that "pcie_aspm=off" avoids the errors. If that's the case for you, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6 and help me investigate it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859429 Title: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
There are a couple mentions of "pcie_aspm=off" making a difference here. If that's the case, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6 and help me look at this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798880] Re: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
If this is still reproducible, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798880 Title: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
Thank you! "pci=noaer" definitely sweeps this dust under the carpet, and it would be much better to avoid that. Narcis (comment #157) reported that "pcie_aspm=off" is a workaround and is much more specific than "pci=noaer". If we can collect complete dmesg and "sudo lspci -vv" output when booting with and without "pcie_aspm=off", there might be a clue about something we're doing wrong with ASPM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888523] Re: PCIe Bus Error device 8086:a298 spam
Sometimes the "pcie_aspm=off" kernel parameter hides this problem. I would really like to fix the underlying problem so the parameter isn't needed. If anybody sees this problem and is willing to help fix it, please open a bug report at https://bugzilla.kernel.org/, product Drivers/PCI, mention the hardware platform, and attach: - complete dmesg log (I assume this will include some Correctable Errors) - output of "sudo lspci -vv" If booting with the "pcie_aspm=off" kernel parameter makes a difference, please also attach similar dmesg and lspci output for this boot. This seems similar to https://bugzilla.kernel.org/show_bug.cgi?id=215027, which we originally thought was related to Intel VMD and/or the Samsung NVMe device you have, but I now suspect we might have an ASPM configuration problem. ** Bug watch added: Linux Kernel Bug Tracker #215027 https://bugzilla.kernel.org/show_bug.cgi?id=215027 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888523 Title: PCIe Bus Error device 8086:a298 spam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043665] Re: Hundreds of errors per second: kernel: pcieport 0000:00:1c.3: PCIe Bus Error
The "pcie_aspm=off" kernel parameter hides a problem. I would really like to fix the underlying problem so the parameter isn't needed. If anybody sees this problem and is willing to help fix it, please open a bug report at https://bugzilla.kernel.org/, product Drivers/PCI, mention the hardware platform, and attach: - complete dmesg log (I assume this will include some Correctable Errors) - output of "sudo lspci -vv" If booting with the "pcie_aspm=off" kernel parameter makes a difference, please also attach similar dmesg and lspci output for this boot. This seems similar to https://bugzilla.kernel.org/show_bug.cgi?id=215027, which we originally thought was related to Intel VMD and/or the Samsung NVMe device you have, but I now suspect we might have an ASPM configuration problem. ** Bug watch added: Linux Kernel Bug Tracker #215027 https://bugzilla.kernel.org/show_bug.cgi?id=215027 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043665 Title: Hundreds of errors per second: kernel: pcieport :00:1c.3: PCIe Bus Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015670] Re: [r8169] Kernel loop PCIe Bus Error on RTL810xE
The "pcie_aspm=off" kernel parameter hides a problem. I would really like to fix the underlying problem so the parameter isn't needed. If anybody is willing to help fix it, please open a bug report at https://bugzilla.kernel.org/, product Drivers/PCI, mention the hardware platform, and attach: - complete dmesg log (I assume this will include some Correctable Errors) - output of "sudo lspci -vv" If booting with the "pcie_aspm=off" kernel parameter makes a difference, please also attach similar dmesg and lspci output for this boot. This seems similar to https://bugzilla.kernel.org/show_bug.cgi?id=215027, which we originally thought was related to Intel VMD and/or the Samsung NVMe device you have, but I now suspect we might have an ASPM configuration problem. ** Bug watch added: Linux Kernel Bug Tracker #215027 https://bugzilla.kernel.org/show_bug.cgi?id=215027 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015670 Title: [r8169] Kernel loop PCIe Bus Error on RTL810xE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
Should be fixed by https://git.kernel.org/linus/d341838d776a, which will appear in v5.19-rc1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973359] [NEW] on_ac_power says false, but real answer is true
Public bug reported:
On a Dell 7000 Micro (Intel 12700T), plugged into mains power,
on_ac_power reports false.
As the micro computer is plugged into mains power, I had expected it
instead to report true.
/sys/class/power_supply$ ls
ucsi-source-psy-USBC000:001
/sys/class/power_supply/ucsi-source-psy-USBC000:001$ cat type
USB
/sys/class/power_supply/ucsi-source-psy-USBC000:001$ cat online
0
The initial logic in /usr/bin/on_ac_power goes:
if [ -d /sys/class/power_supply/ ]; then
for FN in /sys/class/power_supply/*; do
if test -d "${FN}" && test -r "${FN}/type"; then
type="$(cat "${FN}/type")"
case "${type}" in
Mains|USB*|BrickID|Wireless)
if [ -r "${FN}/online" ]; then
online="$(cat "${FN}/online")"
[ "$online" = 1 ] && exit 0
[ "$online" = 0 ] && OFF_LINE_P=yes
fi;;
esac
fi
done
[ "${OFF_LINE_P}" = "yes" ] && exit 1
fi
Due the adapter being of type USB and the online status being 0,
OFF_LINE_P is set to "yes" and the script exits with status code 1.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: powermgmt-base 1.36
Uname: Linux 5.17.0-051700-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
Date: Fri May 13 11:50:59 2022
Dependencies:
InstallationDate: Installed on 2022-04-22 (21 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220421)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: powermgmt-base
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: powermgmt-base (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy uec-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973359
Title:
on_ac_power says false, but real answer is true
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1973359/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970637] Re: ffmpeg depends on libmfx-gen1.2 on Alder Lake for Intel QSV support
** Description changed: On Intel 12th gen CPUs (Alder Lake), ffmpeg requires package libmfx- gen1.2 to use QSV hardware decoding/encoding, but it's not marked as a dependency and therefore not installed with ffmpeg. - As stated on https://github.com/Intel-Media-SDK/MediaSDK#media-sdk-support-matrix, ADL-S, ADL-P and future Intel CPUs are not supported by libmfxhw64.so.1. When h264_qsv is used as a decoder or encoder, without libmfx-gen1.2 installed, ffmpeg exists with error: + As stated on https://github.com/Intel-Media-SDK/MediaSDK#media-sdk-support-matrix, ADL-S, ADL-P and future Intel CPUs are not supported by libmfxhw64.so.1. When h264_qsv is used as a decoder or encoder, without libmfx-gen1.2 installed, ffmpeg exits with error: Error initializing an internal MFX session: unsupported (-3) This is because the libmfx.so.1 dispatcher wants to dispatch to libmfx- gen.so.1.2 for the Intel Quick Sync Video support, but can't due to the missing shared library. When libmfx-gen1.2 is installed, the dispatcher succeeds and the QSV usage occurs. It seems to me that libmfx-gen1.2 should be marked as a dependency (possibly as a dependency of libavutil56, of which ffmpeg depends) to ensure QSV hardware can be used on Alder Lake architectures, and beyond, without users figuring this out themselves. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ffmpeg 7:4.4.1-3ubuntu5 Uname: Linux 5.17.0-051700-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 27 16:08:12 2022 InstallationDate: Installed on 2022-04-22 (5 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: ffmpeg UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970637 Title: ffmpeg depends on libmfx-gen1.2 on Alder Lake for Intel QSV support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970637] [NEW] ffmpeg depends on libmfx-gen1.2 on Alder Lake for Intel QSV support
Public bug reported: On Intel 12th gen CPUs (Alder Lake), ffmpeg requires package libmfx- gen1.2 to use QSV hardware decoding/encoding, but it's not marked as a dependency and therefore not installed with ffmpeg. As stated on https://github.com/Intel-Media-SDK/MediaSDK#media-sdk-support-matrix, ADL-S, ADL-P and future Intel CPUs are not supported by libmfxhw64.so.1. When h264_qsv is used as a decoder or encoder, without libmfx-gen1.2 installed, ffmpeg exists with error: Error initializing an internal MFX session: unsupported (-3) This is because the libmfx.so.1 dispatcher wants to dispatch to libmfx- gen.so.1.2 for the Intel Quick Sync Video support, but can't due to the missing shared library. When libmfx-gen1.2 is installed, the dispatcher succeeds and the QSV usage occurs. It seems to me that libmfx-gen1.2 should be marked as a dependency (possibly as a dependency of libavutil56, of which ffmpeg depends) to ensure QSV hardware can be used on Alder Lake architectures, and beyond, without users figuring this out themselves. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ffmpeg 7:4.4.1-3ubuntu5 Uname: Linux 5.17.0-051700-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 27 16:08:12 2022 InstallationDate: Installed on 2022-04-22 (5 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ffmpeg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ffmpeg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970637 Title: ffmpeg depends on libmfx-gen1.2 on Alder Lake for Intel QSV support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944752] Re: AER PCIe Bus Error for Asus X541UVK
The "ACPI region does not cover" errors are not related to the AER PCIe bus error. Neither is the nouveau MMIO read fault (that looks like a null pointer problem). Naveen Naidu is looking at the AER problem, so I hope we'll have a patch that makes "pci=noaer" unnecessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944752 Title: AER PCIe Bus Error for Asus X541UVK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901187] Re: Keyboard layout switch problem
I'm on Ubuntu 20.04.3 LTS, gnome 3.36.8. I have the same or a related problem. See also here: https://askubuntu.com/questions/448183/keyboard-map-is-changed-randomly (the dconf fix didn't work). Basically, when a new device is connected, the keyboard map seems to be reset, e.g. a USB webcam. The issue also occurs when a bluetooth device connects. Does anybody have any ideas what I could do here? Many thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901187 Title: Keyboard layout switch problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173]
Riccardo, would you mind booting with just "pci=noaer" to see if that works around the problem? Your photo at https://i.imgur.com/PPZ49lL.jpg suggests that it might. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5
Chime in on this email thread if interested: https://lore.kernel.org/r/20200723201403.GA1450503@bjorn-Precision-5520 There are instructions at the bottom of that page about how to reply to the thread. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
Yes, I think that kernel is fine. You can leave the i8042.nopnp=1 in your kernel command line parameters. Otherwise it looks right. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad doesn't work at all on ACER Spin 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
1) Sorry, I don't have a PPA or similar kernel image for you to try.
2) I expected that Windows would move 00:1f.5 BAR 0 to be inside the
windows reported by the PCI0 _CRS, but the AIDA64 report shows
otherwise:
B00 D1F F05: Intel Ice Point-LP PCH - SPI (Flash) Controller
Offset 000: 86 80 A4 34 06 04 00 00 30 00 80 0C 00 00 00 00
Offset 010: 00 00 01 FE 00 00 00 00 00 00 00 00 00 00 00 00
BAR 0 is at offset 0x10, and it still contains the value BIOS put there
(0xfe01).
I don't know why Linux couldn't find space for 00:1f.5 BAR 0. Tracing
the resource assignment code with 'dyndbg="file drivers/pci/* +p"' and
possibly some new trace messages might give a clue.
When Linux fails to assign space, it tries to revert to the BIOS
assignment ("BAR 0: trying firmware assignment [mem
0xfe01-0xfe010fff]"). Apparently we declined to use that BIOS
assignment because it "conflicts with Reserved [mem
0xfc80-0xfe7f]". Perhaps Linux should ignore that conflict.
That "Reserved [mem 0xfc80-0xfe7f]" comes from the E820 map, and
the Linux handling of that map is somewhat haphazard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad doesn't work at all on ACER Spin 5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
It looks like a BIOS bug to me. But Windows does work, and Linux should, too. It looks like there's plenty of available space for 00:1f.5 BAR 0. Can you try a current version of Linux, e.g., v5.8-rc1 with the command line argument 'dyndbg="file drivers/pci/* +p"'? There were some significant resource assignment changes in v5.5. AIDA64 (https://www.aida64.com/) has a free trial version that should show the PCI address map under Windows. I assume it probably moved 00:1f.5 BAR 0 to somewhere inside the PCI host bridge window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad doesn't work at all on ACER Spin 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
This looks like a BIOS defect. BIOS programmed BAR 0 to [mem 0xfe01-0xfe010fff], but according to the PCI0 _CRS method, that area is not routed to the PCI bus: ACPI: PCI Root Bridge [PCI0] (domain [bus 00-fe]) pci_bus :00: root bus resource [mem 0x000a-0x000b window] pci_bus :00: root bus resource [mem 0x3f80-0xbfff window] pci :00:1f.5: [8086:34a4] type 00 class 0x0c8000 pci :00:1f.5: reg 0x10: [mem 0xfe01-0xfe010fff] pci :00:1f.5: can't claim BAR 0 [mem 0xfe01-0xfe010fff]: no compatible bridge window pci :00:1f.5: BAR 0: no space for [mem size 0x1000] pci :00:1f.5: BAR 0: trying firmware assignment [mem 0xfe01-0xfe010fff] pci :00:1f.5: BAR 0: [mem 0xfe01-0xfe010fff] conflicts with Reserved [mem 0xfc80-0xfe7f] pci :00:1f.5: BAR 0: failed to assign [mem size 0x1000] Can you check to see whether a BIOS update is available? Can you please attach the contents of /proc/iomem (I think you have to save the contents as root in order to see the values). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad doesn't work at all on ACER Spin 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Re: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on
I'm not using Mint. I started with Ubuntu 18.04 in June 2018, installed the "cinnamon" package, and recently updated to 20.04. I don't know if this is a regression because I didn't start using this configuration until after moving to 20.04. Pretty sure cinnamon came from the ubuntu repo; my only apt sources change is for chrome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Re: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on
I'm sure it's not a Linux kernel bug. I don't have any idea *where* the bug is, and https://wiki.ubuntu.com/Bugs/FindRightPackage suggested "linux" as a safe bet. Sorry, I didn't realize Cinnamon wasn't supported by Ubuntu. I will either live with the behavior or switch to the supported Ubuntu desktop. Feel free to close as "not our bug" or whatever is appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379885/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379884/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379886/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379890/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379891/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379896/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379889/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379894/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379888/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379895/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379887/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379897/+files/WifiSyslog.txt ** 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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379882/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379883/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379893/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379892/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Re: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on
apport information ** Tags added: apport-collected focal ** Description changed: Dell 5520 laptop -> Dell Thunderbolt dock -> HDMI -> external monitor. Running 20.04, i915 driver. Laptop lid closed, using external monitor only. When external monitor turns off (after sleep-display-ac), keyboard/mouse activity should turn it back on, but do not. Opening and closing the laptop lid does turn the external monitor back on. Laptop is not suspended; I can ssh in from another machine. Happy to collect any additional information. To reproduce: - On Dell 5520 laptop connected to Dell Thunderbolt dock connected to external monitor via HDMI - Close laptop lid - Use external monitor, external keyboard, external mouse - Leave system idle for "sleep-display-ac" time - System puts external monitor in power-save mode - Move mouse, type on keyboard - No response, external monitor remains in power-save mode - Open laptop lid - External monitor turns on - Close laptop lid - External monitor remains on, I'm able to work as usual + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: bjorn 1993 F pulseaudio + /dev/snd/controlC1: bjorn 1993 F pulseaudio + /dev/snd/controlC0: bjorn 1993 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=UUID=39f2962e-3115-438f-a447-03558db08edb + InstallationDate: Installed on 2018-06-08 (725 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: Dell Inc. Precision 5520 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-31-generic N/A + linux-backports-modules-5.4.0-31-generic N/A + linux-firmware1.187 + Tags: focal + Uname: Linux 5.4.0-31-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-29 (34 days ago) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/17/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.18.0 + dmi.board.name: 0R6JFH + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.asset.tag: 1203147 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Precision + dmi.product.name: Precision 5520 + dmi.product.sku: 07BF + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1881644/+attachment/5379881/+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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] Re: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on
** Summary changed: - 20.04 i915 laptop external monitor turns off when inactive, must open lid to turn it on + 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on ** Package changed: 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/1881644 Title: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881644] [NEW] 20.04 i915 laptop external monitor turns off when inactive, must open lid to turn it on
Public bug reported: Dell 5520 laptop -> Dell Thunderbolt dock -> HDMI -> external monitor. Running 20.04, i915 driver. Laptop lid closed, using external monitor only. When external monitor turns off (after sleep-display-ac), keyboard/mouse activity should turn it back on, but do not. Opening and closing the laptop lid does turn the external monitor back on. Laptop is not suspended; I can ssh in from another machine. Happy to collect any additional information. To reproduce: - On Dell 5520 laptop connected to Dell Thunderbolt dock connected to external monitor via HDMI - Close laptop lid - Use external monitor, external keyboard, external mouse - Leave system idle for "sleep-display-ac" time - System puts external monitor in power-save mode - Move mouse, type on keyboard - No response, external monitor remains in power-save mode - Open laptop lid - External monitor turns on - Close laptop lid - External monitor remains on, I'm able to work as usual ** 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.net/bugs/1881644 Title: 20.04 i915 laptop external monitor turns off when inactive, must open lid to turn it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1881644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931368] Re: PCI/internal sound card seems to be detected, but is not available
This issue should be resolved by https://git.kernel.org/linus/1dace0116d0b, which appeared in v4.2. If the kernel contains that commit, the "pci=use_crs" boot parameter should not be needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931368 Title: PCI/internal sound card seems to be detected, but is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/931368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855938] Re: [nvidia] Screen freezes and only mouse moves
I'm experiencing the same issue. Similarly, around 3 times a week on Ubuntu 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855938 Title: [nvidia] Screen freezes and only mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864561] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
Hello all, any updates or thoughts on this? Many thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864561 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1864561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864561] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
Hello all, any updates or thoughts on this? Many thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864561 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1864561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864562] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
*** This bug is a duplicate of bug 1864561 *** https://bugs.launchpad.net/bugs/1864561 Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864562 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1864562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864562] [NEW] For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
Public bug reported: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! ** Affects: gtk+3.0 (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/1864562 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1864562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864561] [NEW] For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
Public bug reported: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! ** Affects: ibus (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/1864561 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1864561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763006] Re: arm-none-eabi-gdb missed in ubuntu 18.04
gdb-multiarch seemed like it should work. I use openocd 0.10.0 but when I attempt a connection to it reports of my SAMD09D14A (on an Adafruit Seesaw) "warning: Architecture rejected target-supplied description ... Truncated register 16 in remote 'g' packetInfo : dropped 'gdb' connection" This very helpful post provided the solution and got me here to see what was up: https://acassis.wordpress.com/2018/12/27/adding-arm-none-eabi-gdb-to-ubuntu-18-04/ gdb-arm-none-eabi works perfectly! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763006 Title: arm-none-eabi-gdb missed in ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkconfig/+bug/1763006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785434] Re: VLC under Wayland causes system freezes in fullscreen mode
Me three. Intel Iris pro 5200. Xorg is fine. Wayland crashes on full screen. Ubuntu 18.04.1. VLC 3.0.3. Wayland 2:1.19.6-1ubuntu4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785434 Title: VLC under Wayland causes system freezes in fullscreen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1785434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu
John, can you also include a little more detail about what the failure looks like to a user? Does this result in AER errors being logged? When we come up with a patch that works, I'd like to include a hint about what user-visible problems it fixes in the changelog. I see from the initial report that it "causes the card to not function", but I'd like to know if there are messages from AER or the driver that are connected to this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571798 Title: Broadwell ECRC Support missing in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu
Please try the attached patch. It makes it so that if the device does
not support ECRC generation or checking, we don't enable those features.
Currently (without this patch), we *do* enable ECRC generation and
checking if _HPX allows, i.e., if the platform can support ECRC.
The ACPI dump confirms my theory from comment #65 that the system
supplies an _HPX method with PCI_ERR_CAP_ECRC_GENE and
PCI_ERR_CAP_ECRC_CHKE set (see disassembly below).
Apparently the Intel Quick Assist card is at 85:00.0 ("Intel Corporation
DH895XCC Series QAT"). Here's the path leading to it:
pci :80:02.0: [8086:6f04] # Xeon D PCI Express Root Port 2
pci :80:02.0: PCI bridge to [bus 83-86]
pci :83:00.0: [10b5:8724] # PLX 8724 Upstream Port
pci :83:00.0: PCI bridge to [bus 84-86]
pci :84:00.0: [10b5:8724] # PLX 8724 Downstream Port
pci :84:00.0: PCI bridge to [bus 85]
pci :85:00.0: [8086:0435] # DH895XCC Series QAT
Here are the ECRC settings along the path:
80:02.0: AERCap: GenCap+ CGenEn+ ChkCap+ ChkEn+
83:00.0: AERCap: GenCap+ CGenEn+ ChkCap+ ChkEn+
84:00.0: AERCap: GenCap+ CGenEn+ ChkCap+ ChkEn+
85:00.0: AERCap: GenCap- CGenEn+ ChkCap- ChkEn+
This looks suspect because 85:00.0 claims that it does not support ECRC
Generation ("GenCap-") or ECRC Checking ("ChkCap-"), yet we set the
Enable bits for both features. The workaround in the initial report
turns off ECRC checking in 80:02.0. I suspect that turning off ECRC
generation and checking in 85:00.0, e.g., "setpci -s85:00.0 118.w=0"
would also be a workaround. This patch should be the equivalent of this
setpci command.
Here's the _HPX disassembly from dsdt.dsl (extracted from comment #66):
Device (PCI0)
...
Method (_HPX, 0, NotSerialized) // _HPX: Hot Plug Parameter
Extensions
{
Store ("_HPX", Debug)
Name (SSDH, Package (0x01)
{
Package (0x12)
{
0x02,
0x01,
0xFC000FCF, // Uncorrectable Mask AND
0x03A18000, // Uncorrectable Mask OR
0xFC000FCF, // Uncorrectable Severity AND
0x004E7030, // Uncorrectable Severity OR
0x0E3E, // Correctable Mask AND
0xF1C1, // Correctable Mask OR
0xFEBF, // AER AND
0x0140, // AER OR
0xFFF1, // Device Control AND
0x0E, // Device Control OR
0x, // Link Control AND
0x00, // Link Control OR
0xC010, // Secondary Uncorrectable Severity AND
0x1BC0, // Secondary Uncorrectable Severity OR
0xC010, // Secondary Uncorrectable Mask AND
0x242F // Secondary Uncorrectable Mask OR
}
})
Store (SSDH, Debug)
Return (SSDH)
}
** Attachment added: "test patch to leave ECRC disabled when unsupported"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+attachment/4841199/+files/hpx-ecrc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571798
Title:
Broadwell ECRC Support missing in Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363313] Re: mpt2sas not loaded with LSISAS2008 card in trusty 14.04.1
https://bugzilla.kernel.org/show_bug.cgi?id=92351#c1 reports the problem occurs with LSI FW 18. https://bugzilla.kernel.org/show_bug.cgi?id=92351#c8 reports the problem does NOT occur with LSI FW 19. So upgrading the adapter firmware to version 19 may be a fix. There is a patch at https://bugzilla.kernel.org/show_bug.cgi?id=92351#c7, but it has not been tested and has not been merged upstream. This fix would be a possible workaround for systems with LSI FW 18. My understanding is that it would not be necessary with LSI FW 19. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363313 Title: mpt2sas not loaded with LSISAS2008 card in trusty 14.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1363313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
>From the Linux kernel point of view, changing the BIOS option is not a good fix, and "pci=realloc=off" is just a workaround and not a real fix either. Linux should be able to work even without that, or at least give meaningful error messages. The original problem appears to be that: - BIOS allocated space for the normal PCI BARs 0, 2 and 4, but not for the SR-IOV VF BARs, - Linux tried to allocate space for the SR-IOV BARs, but failed, and - Linux removed even the space allocated for the normal PCI BARs Here's the initial state Linux found: pci :22:00.0: [8086:10fb] type 00 class 0x02 pci :22:00.0: reg 0x10: [mem 0xe940-0xe947 64bit] # BAR 0 pci :22:00.0: reg 0x18: [io 0xdcc0-0xdcdf]# BAR 2 pci :22:00.0: reg 0x20: [mem 0xe95f8000-0xe95fbfff 64bit] # BAR 4 pci :22:00.0: reg 0x30: [mem 0xe950-0xe957 pref] # ROM BAR pci :22:00.0: reg 0x184: [mem 0x-0x3fff 64bit] # SR-IOV BAR pci :22:00.0: reg 0x190: [mem 0x-0x3fff 64bit] # SR-IOV BAR After trying to move things around to provide space for the SR-IOV BARs: pci :22:00.0: BAR 0: can't assign mem (size 0x8) # BAR 0 pci :22:00.0: BAR 4: can't assign mem (size 0x4000)# BAR 4 pci :22:00.0: BAR 7: can't assign mem (size 0x10) # SR-IOV BAR pci :22:00.0: BAR 10: can't assign mem (size 0x10) # SR-IOV BAR This may have been fixed by changes in the resource assignment code. I don't remember similar recent problem reports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363313] Re: mpt2sas not loaded with LSISAS2008 card in trusty 14.04.1
** Bug watch added: Linux Kernel Bug Tracker #92351 http://bugzilla.kernel.org/show_bug.cgi?id=92351 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=92351 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363313 Title: mpt2sas not loaded with LSISAS2008 card in trusty 14.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1363313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627496] Re: radeon broken with kernel 4.6.0+
There's a test patch at https://bugzilla.kernel.org/show_bug.cgi?id=175391 Any test reports would be welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627496 Title: radeon broken with kernel 4.6.0+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
Related problem report: https://bugzilla.kernel.org/show_bug.cgi?id=109691 Brief analysis of AER issue: http://lkml.kernel.org/r/20151229155822.GA17321@localhost I did say in that analysis that I was going to work on fixing this, but I haven't had time. It would be great if somebody would jump in and help out. ** Bug watch added: Linux Kernel Bug Tracker #109691 http://bugzilla.kernel.org/show_bug.cgi?id=109691 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu
The register in question is the Advanced Error Capabilities and Control register, at offset 0x18 in the Advanced Error Reporting capability, which starts at 0x148 in the config space of device 80:02.0. In the pre-boot value of 0x00a0, the following bits are set (per PCIe spec r3.0, sec 7.10.7, these bits are read-only): PCI_ERR_CAP_ECRC_GENC 0x0020 /* ECRC Generation Capable */ PCI_ERR_CAP_ECRC_CHKC 0x0080 /* ECRC Check Capable */ In the value of 0x01e0 after Linux boots, the following additional bits are set: PCI_ERR_CAP_ECRC_GENE 0x0040 /* ECRC Generation Enable */ PCI_ERR_CAP_ECRC_CHKE 0x0100 /* ECRC Check Enable */ Linux is setting these bits in program_hpp_type2() because there is apparently an ACPI _HPX method that applies to this device, and it returns a PCI Express setting record (ACPI spec 5.0, sec 6.2.8.3) with an "Advanced Error Capabilities and Control Register OR Mask" that has PCI_ERR_CAP_ECRC_GENE and PCI_ERR_CAP_ECRC_CHKE set. Can you collect an ACPI dump to confirm that this is the case? As I mentioned in the 1302fcf0d03e changelog, it's not completely clear from the spec (ACPI 5.0, sec 6.2.8) when to apply these _HPX settings. It says OSPM should use them to "configure devices not configured by the platform firmware during initial system boot." The question is how OSPM can tell whether a device has been configured by platform firmware. Since I don't know how to tell if a device has been configured by platform firmware, I chose to apply the _HPX settings to *all* devices. Any BIOS folks want to suggest a way to tell whether firmware has configured a device? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571798 Title: Broadwell ECRC Support missing in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588428] Re: PCI bus error on startup while booting into login screen (Kubuntu 16.04)
This looks related to https://bugzilla.kernel.org/show_bug.cgi?id=111601 Is "pci=noaer" (without using "pci=nomsi") sufficient to allow the system to boot? If you boot with "pci=noaer", does it still take a long time to boot? If so, can you collect a dmesg log with timestamps so we can see where the time is? ** Bug watch added: Linux Kernel Bug Tracker #111601 http://bugzilla.kernel.org/show_bug.cgi?id=111601 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588428 Title: PCI bus error on startup while booting into login screen (Kubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386490] Re: HP ProLiant m400 nic doesn't work after trusty
The git link in comment #17 is stale because it references a branch name, which is often re-used. I think http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?h=9a6d7298b0833614c411f774c46514efb1bd5651 is a permanent link to the same thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386490 Title: HP ProLiant m400 nic doesn't work after trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1386490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033299] Re: Ubuntu 12.04 - no sound with VT8237A/VT8251
In comment #40, I mistakenly said we reassign 80:01.0 to an address that is under PCI0, not PCI1. I had misread the address 0xfd as 0xfd00, but it is actually 0xfd__, which is just after the [mem 0x8000-0xfc] range from amd_bus.c, and is not in any of the apertures of either PCI host bridge. I also mis-typed the boot option in comment #41. The workaround should be pci=use_crs (not pcie=use_crs). I'm planning to merge this patch, which should fix the problem: http://lkml.kernel.org/r/20150616165543.9306.88230.stgit@bhelgaas- glaptop2.roam.corp.google.com If all goes well, this will appear in v4.2-rc1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033299 Title: Ubuntu 12.04 - no sound with VT8237A/VT8251 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1033299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931368] Re: PCI/internal sound card seems to be detected, but is not available
Anybody seeing this problem on a Foxconn K8M890-8237A system, please test this patch. With it, sound should work without having to boot with pci=use_crs. If you test it, please attach the complete dmesg log here. Thanks! ** This bug is no longer a duplicate of bug 662299 Soundcard not detected (workaround: add pci=use_crs to GRUB) ** Attachment added: quirk to turn on pci=use_crs on Foxconn K8M890-8237A https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/931368/+attachment/4415764/+files/x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931368 Title: PCI/internal sound card seems to be detected, but is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/931368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664785] Re: VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) had sound in 10.04, not 10.10
*** This bug is a duplicate of bug 662299 *** https://bugs.launchpad.net/bugs/662299 Bug #662299 includes several problems with similar symptoms and the same workaround (booting with pci=use_crs). Booting with pci=use_crs may be a workaround for this bug as well. If it is, please attach a complete dmesg log here so we can make the kernel work even without the pci=use_crs option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/664785 Title: VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) had sound in 10.04, not 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/664785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931912] Re: [Dell Latitude E6510] PCI/internal sound card not detected, unless pci=use_crs is specified
Manuel, does this problem still occur? I can't see what the problem is in your dmesg logs. Your logs contain 'PCI: Using host bridge windows from ACPI; if necessary, use pci=nocrs and report a bug', booting with pci=use_crs shouldn't make a difference on your machine. If this is still a problem, can you attach the complete dmesg logs both with and without pci=use_crs? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931912 Title: [Dell Latitude E6510] PCI/internal sound card not detected, unless pci=use_crs is specified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/931912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662299] Re: Soundcard not detected (workaround: add pci=use_crs to GRUB)
pci=use_crs is a workaround but not a fix. If anybody who has this problem can attach a complete dmesg log, we should be able to fix the kernel so it works without having to boot with pci=use_crs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662299 Title: Soundcard not detected (workaround: add pci=use_crs to GRUB) To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/662299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682185] Re: Soundcard not detected - VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
*** This bug is a duplicate of bug 662299 *** https://bugs.launchpad.net/bugs/662299 Bug #662299 includes several problems with similar symptoms and the same workaround (booting with pci=use_crs). Booting with pci=use_crs may be a workaround for this bug as well. If it is, please attach a complete dmesg log here so we can make the kernel work even without the pci=use_crs option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682185 Title: Soundcard not detected - VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/682185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664785] Re: VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) had sound in 10.04, not 10.10
*** This bug is a duplicate of bug 662299 *** https://bugs.launchpad.net/bugs/662299 valkyr's report was on an ASUSTeK M2V-MX SE. That problem should be fixed by this commit, which appeared upstream in v3.1: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=29cf7a30f8a0 I can't tell what systems the other reporters have, so it's possible we need similar whitelist entries for them. If so, please attach the dmesg log here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/664785 Title: VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) had sound in 10.04, not 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/664785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682185] Re: Soundcard not detected - VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
*** This bug is a duplicate of bug 662299 *** https://bugs.launchpad.net/bugs/662299 Stormhierta 's Micro-Star MS-7253 system, this should be fixed by these commits, which appeared upstream in v3.3: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=841137170961 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a97f4f5e524b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682185 Title: Soundcard not detected - VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/682185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 892414] Re: [P53G, VIA VT1708B 8-Ch, Green Line Out, Rear] No sound at all
Hi JoseLuisTriana, 1) pci=use_crs shouldn't make a difference on your system because we enable pci=use_crs automatically on systems with BIOS date of 2008 or newer, and yours is 02/21/2008 2) Re comment #4, the kernel should be able to configure devices even if the BIOS didn't set it up correctly. 3) I don't know anything about the spurious responses or audio quality issues, sorry. I just wanted to remove pci=use_crs from the equation so it doesn't confuse things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892414 Title: [P53G, VIA VT1708B 8-Ch, Green Line Out, Rear] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/892414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940200] Re: No sound (card not recognized)
*** This bug is a duplicate of bug 1033299 *** https://bugs.launchpad.net/bugs/1033299 ** This bug has been marked a duplicate of bug 1033299 Ubuntu 12.04 - no sound with VT8237A/VT8251 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940200 Title: No sound (card not recognized) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/940200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662299] Re: Soundcard not detected (workaround: add pci=use_crs to GRUB)
For Micro-Star MS-7253 systems, this should be fixed by: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=841137170961 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a97f4f5e524b which appeared upstream in v3.3. This should fix the problem seen by Dimitar, Matt, and Carlos, so they shouldn't need pci=use_crs any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662299 Title: Soundcard not detected (workaround: add pci=use_crs to GRUB) To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/662299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931368] Re: PCI/internal sound card seems to be detected, but is not available
*** This bug is a duplicate of bug 662299 *** https://bugs.launchpad.net/bugs/662299 ** This bug has been marked a duplicate of bug 662299 Soundcard not detected (workaround: add pci=use_crs to GRUB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931368 Title: PCI/internal sound card seems to be detected, but is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/931368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555645] Re: 0 [VT82xx ]: HDA-Intel - HDA VIA VT82xx HDA VIA VT82xx at 0xbfffc000 irq 17
Eran, can you confirm whether (1) this is still a problem, and (2) whether pci=use_crs makes a difference? Based on your dmesg log, I don't see what it would change, but I might have missed something. If pci=use_crs does make a difference, can you attach complete dmesg logs with and without it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/555645 Title: 0 [VT82xx ]: HDA-Intel - HDA VIA VT82xx HDA VIA VT82xx at 0xbfffc000 irq 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/555645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555645] Re: 0 [VT82xx ]: HDA-Intel - HDA VIA VT82xx HDA VIA VT82xx at 0xbfffc000 irq 17
I think this should be fixed by these commits: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=841137170961 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a97f4f5e524b Both appeared upstream in v3.3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/555645 Title: 0 [VT82xx ]: HDA-Intel - HDA VIA VT82xx HDA VIA VT82xx at 0xbfffc000 irq 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/555645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839208] Re: PCI/internal sound card not detected: Soundblaster Audigy SE
Hi timmy, pci=use_crs shouldn't make any difference on your system, because it was already automatically enabled even without pci=use_crs. If you still have an issue with sound or xgifb, please attach a complete dmesg log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839208 Title: PCI/internal sound card not detected: Soundblaster Audigy SE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/839208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033299] Re: Ubuntu 12.04 - no sound with VT8237A/VT8251
FichdlMaa, you said in comment #12 that pcie=use_crs didn't make a difference. Can you attach a complete dmesg log with pci=use_crs? I think it should make some difference (it should change the address assigned to the 80:01.0 sound device), but that may not be enough to fix the whole problem. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033299 Title: Ubuntu 12.04 - no sound with VT8237A/VT8251 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1033299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
How come this is listed as bug fix released, when bug is still affecting systems? Not resolved, STILL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091465] Re: debian-installer fails to detect lsi 2208-based raid card in precise, quantal, raring
This might be related to https://bugzilla.kernel.org/show_bug.cgi?id=63661 That issue was bisected to 3c076351c402 (PCI: Rework ASPM disable code), which appeared upstream in v3.3-rc1. That commit was backported to Ubuntu-3.2.0-22.35: http://kernel.ubuntu.com/git/ubuntu/ubuntu- precise.git/commit/?id=2dcce0a318fc. I'm told that 3c076351c402 has *not* been backported to RHEL6.3, and I expect the same is true for CentOS6.3, which might explain why the problem doesn't occur on CentOS6.3. For this Ubuntu issue, pci=conf1 is a workaround, but for 63661, pci=conf1 didn't help (http://www.spinics.net/lists/linux- scsi/msg76194.html), so it may be that this issue on Ubuntu is different. But 63661 is the same hardware (Intel S2600 motherboard, MegaRAID SAS 2208), so it seems likely these issues are the same. One reporter there found that turning off Fast Boot in the BIOS settings is a workaround. My theory is that megaraid_sas depends on something done by the option ROM, and that enabling Fast Boot in the BIOS (which is apparently the default) causes the BIOS to skip executing the option ROM. Further, I speculate that prior to 3c076351c402 (PCI: Rework ASPM disable code), the Linux PCI core did something that made things work. If anybody still cares about this issue, please look at https://bugzilla.kernel.org/show_bug.cgi?id=63661 and we can try to debug it further. ** Bug watch added: Linux Kernel Bug Tracker #63661 http://bugzilla.kernel.org/show_bug.cgi?id=63661 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091465 Title: debian-installer fails to detect lsi 2208-based raid card in precise, quantal, raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1091465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430059] Re: Many options in various menus appear greyed out, inaccessible
I have the same problem on a fresh install on ubuntu vivid on an dell xps 13 (9343). Removing the ~/.lxy directories brings some items in the menus back, but it does not solve the problem. The majority are still greyed out (eg. copy, paste, insert citation, math...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430059 Title: Many options in various menus appear greyed out, inaccessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1430059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335367] Re: \_SB_.PCI0:_OSC invalid UUID
Thanks for the bug report, Cristian. There's definitely something wrong here. There are several similar reports of invalid UUID, and I just don't believe they're all caused by BIOS bugs: https://bugzilla.kernel.org/show_bug.cgi?id=17792 (your report) https://bugzilla.kernel.org/show_bug.cgi?id=34192 https://bugzilla.kernel.org/show_bug.cgi?id=35532 https://bugzilla.kernel.org/show_bug.cgi?id=36932 https://bugzilla.kernel.org/show_bug.cgi?id=42604 https://bugzilla.kernel.org/show_bug.cgi?id=43229 https://bugzilla.kernel.org/show_bug.cgi?id=54951 https://bugzilla.kernel.org/show_bug.cgi?id=54981 (includes analysis that might be useful) https://bugzilla.kernel.org/show_bug.cgi?id=59311 https://bugzilla.kernel.org/show_bug.cgi?id=70891 https://bugzilla.kernel.org/show_bug.cgi?id=73241 (SDHCI) https://bugzilla.kernel.org/show_bug.cgi?id=87491 https://bugzilla.kernel.org/show_bug.cgi?id=90351 https://bugzilla.kernel.org/show_bug.cgi?id=93561 (SDHCI) If these all really are BIOS bugs, I think we should figure out a better way of handling them. In https://bugzilla.kernel.org/show_bug.cgi?id=93561, Maarten found that we complained about an invalid _OSC UUID when CONFIG_HOTPLUG_PCI_ACPI was not set, but _OSC worked when CONFIG_HOTPLUG_PCI_ACPI=y. We're still trying to figure out how that could make a difference. Can you tell whether CONFIG_HOTPLUG_PCI_ACPI has any effect on the _OSC UUID error you're seeing? I attached a patch at https://bugzilla.kernel.org/show_bug.cgi?id=93561#c12 to try to debug a little further. It would be interesting if you could try it out, too. I guess you should post results either here or in a new kernel.org bugzilla, because 93561 is really not about the UUID error; it's about an SDHCI problem. ** Bug watch added: Linux Kernel Bug Tracker #17792 http://bugzilla.kernel.org/show_bug.cgi?id=17792 ** Bug watch added: Linux Kernel Bug Tracker #34192 http://bugzilla.kernel.org/show_bug.cgi?id=34192 ** Bug watch added: Linux Kernel Bug Tracker #35532 http://bugzilla.kernel.org/show_bug.cgi?id=35532 ** Bug watch added: Linux Kernel Bug Tracker #36932 http://bugzilla.kernel.org/show_bug.cgi?id=36932 ** Bug watch added: Linux Kernel Bug Tracker #42604 http://bugzilla.kernel.org/show_bug.cgi?id=42604 ** Bug watch added: Linux Kernel Bug Tracker #43229 http://bugzilla.kernel.org/show_bug.cgi?id=43229 ** Bug watch added: Linux Kernel Bug Tracker #54951 http://bugzilla.kernel.org/show_bug.cgi?id=54951 ** Bug watch added: Linux Kernel Bug Tracker #54981 http://bugzilla.kernel.org/show_bug.cgi?id=54981 ** Bug watch added: Linux Kernel Bug Tracker #59311 http://bugzilla.kernel.org/show_bug.cgi?id=59311 ** Bug watch added: Linux Kernel Bug Tracker #70891 http://bugzilla.kernel.org/show_bug.cgi?id=70891 ** Bug watch added: Linux Kernel Bug Tracker #73241 http://bugzilla.kernel.org/show_bug.cgi?id=73241 ** Bug watch added: Linux Kernel Bug Tracker #87491 http://bugzilla.kernel.org/show_bug.cgi?id=87491 ** Bug watch added: Linux Kernel Bug Tracker #90351 http://bugzilla.kernel.org/show_bug.cgi?id=90351 ** Bug watch added: Linux Kernel Bug Tracker #93561 http://bugzilla.kernel.org/show_bug.cgi?id=93561 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335367 Title: \_SB_.PCI0:_OSC invalid UUID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033299] Re: Ubuntu 12.04 - no sound with VT8237A/VT8251
I see two problems in the initial report from FichdlMaa: 1) Linux ignores ACPI _CRS information and consequently assigns addresses to the 80:01.0 device that may not work. 2) The page fault: BUG: unable to handle kernel paging request at c9378000 Booting with pci=use_crs should work around the first problem. This is only a workaround, not a real fix because we don't expect users to have to use that option. If pci=use_crs makes a difference, and if it still fixes a problem in the current upstream kernel (v4.0-rcX), please open a bug report at http://bugzilla.kernel.org (in drivers/pci category), attaching a complete dmesg log, and we can add a quirk to turn on that option automatically. I don't have a theory about the page fault problem. Details about the _CRS problem: bus: 00 index 2 [mem 0x8000-0xfc] The range above is from amd_bus.c. Note that it covers the mem windows for both PCI0 and PCI1 below. PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug ACPI: PCI Root Bridge [PCI0] (domain [bus 00-7f]) pci_root PNP0A08:00: host bridge window [mem 0x8000-0xbfef] (ignored) pci_root PNP0A08:00: host bridge window [mem 0xc000-0xdfff] (ignored) pci_root PNP0A08:00: host bridge window [mem 0xf000-0xfebf] (ignored) ACPI: PCI Root Bridge [PCI1] (domain [bus 80-ff]) pci_root PNP0A08:01: host bridge window [mem 0x000a-0x000b] (ignored) pci_root PNP0A08:01: host bridge window [mem 0xbff0-0xbfff] (ignored) pci :80:01.0: [1106:3288] type 0 class 0x000403 pci :80:01.0: reg 10: [mem 0xbfffc000-0xbfff 64bit] The initial configuration from BIOS (above) looks correct. The 80:01.0 BAR 0 is inside the PCI1 host bridge window reported by ACPI _CRS. pci :80:01.0: address space collision: [mem 0xbfffc000-0xbfff 64bit] conflicts with PCI Bus #00 [mem 0x8000-0xfc] pci :80:01.0: BAR 0: assigned [mem 0xfd-0xfd3fff 64bit] But we're ignoring _CRS and using the information from amd_bus.c, so we think there's a conflict with the PCI0 window. We reassign 80:01.0 to an address that is under PCI0, not PCI1. If the ACPI _CRS description is correct, this means MMIO accesses intended for 80:01.0 will never reach the device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033299 Title: Ubuntu 12.04 - no sound with VT8237A/VT8251 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1033299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301708] Re: PCI/internal sound card not detected[ 20.936039] hda-intel 0000:04:01.0: no codecs initialized
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1033299 is a different problem from what robusta is reporting here. In 1033299, pci=use_crs should work around at least part of the problem, but I don't think it will make a difference here. Here, we have this: pci :00:13.0: PCI bridge to [bus 04-06] pci :00:13.0: bridge window [mem 0xdf80-0xdfaf] pci :00:13.0: bridge window [mem 0xdf60-0xdf7f 64bit pref] pci :04:01.0: [1106:3288] type 00 class 0x040300 pci :04:01.0: reg 0x10: [mem 0xdfafc000-0xdfaf] 04:01.0 is the audio device, and its resources look fine from a PCI core point of view. I don't see a PCI problem here, so I'd suspect a driver issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301708 Title: PCI/internal sound card not detected[ 20.936039] hda-intel :04:01.0: no codecs initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1301708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-be] ubuntu-be Digest, Vol 104, Issue 3
Hi Merlijn, I know a few people who work at the government IT departments and I will forward your email so they can contact you about this... Kind regards Met vriendelijke groeten, Bjorn Robijns Verstuurd vanaf mijn iPhone Op 10-jan.-2015 om 13:00 heeft ubuntu-be-requ...@lists.ubuntu.com het volgende geschreven: Send ubuntu-be mailing list submissions to ubuntu-be@lists.ubuntu.com To subscribe or unsubscribe via the World Wide Web, visit https://lists.ubuntu.com/mailman/listinfo/ubuntu-be or, via email, send a message with subject or body 'help' to ubuntu-be-requ...@lists.ubuntu.com You can reach the person managing the list at ubuntu-be-ow...@lists.ubuntu.com When replying, please edit your Subject line so it is more specific than Re: Contents of ubuntu-be digest... Today's Topics: 1. Belgian eID installation on Ubuntu 14.04 (Merlijn Sebrechts) -- Message: 1 Date: Sat, 10 Jan 2015 12:27:21 +0100 From: Merlijn Sebrechts merlijn.sebrec...@gmail.com To: Ubuntu Belgium ubuntu-be@lists.ubuntu.com Subject: [Ubuntu-be] Belgian eID installation on Ubuntu 14.04 Message-ID: CANiiDBFj5M8Qm6gp9-mXK1SPnsYpRC5Ly3v1exc3GMdQ3OKm=a...@mail.gmail.com Content-Type: text/plain; charset=utf-8 Hi I figured out the steps to get my eID working on Ubuntu 14.04. I made an Askubuntu question about it and answered it myself: http://askubuntu.com/questions/571850/how-to-setup-belgian-eid-ubuntu-14-04/ I found three problems, maybe someone can help me with that? 1) The official documentation is really terrible. The worst page is this one: http://eid.belgium.be/nl/je_eid_gebruiken/de_eid-middleware_installeren/linux/. Does anybody have contacts at the eID department? I would like to propose a few changes to that page to make it more clear, but I don't know who to contact. 2) The official documentation on how to configure Google Chrome is outdated, and I think this configuration should/could be included in the middleware installer for Linux... Chrome also needs to be restarted while your card reader is connected for it to work. 3) I can't get the Google Chrome configuration to work on Ubuntu 14.04 32bit. https://code.google.com/p/eid-mw/wiki/ChromeLinux -- next part -- An HTML attachment was scrubbed... URL: https://lists.ubuntu.com/archives/ubuntu-be/attachments/20150110/e9c8784b/attachment-0001.html -- -- ubuntu-be mailing list ubuntu-be@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-be End of ubuntu-be Digest, Vol 104, Issue 3 * -- ubuntu-be mailing list / mailto:ubuntu-be@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-be
Re: [Bug 985645] Re: Remmina crashed under connection via RDP
Hi I do not have this bug in my current system. Ubuntu 14.04 LTS (X64), so it must have been fixed :) Med Venlig Hilsen Bjørn Ryborg Gammel Skolevej 8, Tandslet, DK-6470 Sydals Tlf: +45 3694 9898 - E-mail: bjorn.ryb...@gmail.com 2014-12-15 9:03 GMT+01:00 Christopher M. Penalver christopher.m.penal...@gmail.com: Bjorn Ryborg, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: sudo nano /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Please do not attach your crash report manually to this report and reopen it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: remmina (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/985645 Title: Remmina crashed under connection via RDP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/985645/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985645 Title: Remmina crashed under connection via RDP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/985645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385388] Re: iommu dmar pci passthrough regression
Reported upstream as https://bugzilla.kernel.org/show_bug.cgi?id=86951 ** Bug watch added: Linux Kernel Bug Tracker #86951 http://bugzilla.kernel.org/show_bug.cgi?id=86951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385388 Title: iommu dmar pci passthrough regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1385388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445062] Re: pci BAR 3: messages on boot
This is not a duplicate of bug 438335. This bug is caused by something wrong with the BARs of 00:0b.0: pci :00:0b.0: BAR 1: error updating (0x001001 != 0x01) pci :00:0b.0: BAR 4: error updating (0x4004 != 0x36850264) pci :00:0b.0: BAR 4: error updating (high 0x00 != 0x20) pci :00:0b.0: BAR 3: error updating (0x001401 != 0x09) This report is from a very old kernel, and the dmesg log doesn't contain quite enough information to tell exactly what's wrong. If this is still a problem, and somebody can collect a dmesg log from a current kernel, I'll take a look at it. ** This bug is no longer a duplicate of bug 438335 Boot messages show before xsplash kicks in -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/445062 Title: pci BAR 3: messages on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/445062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091263] Re: Cannot install Ubuntu Server on Intel Raid System
https://bugzilla.kernel.org/show_bug.cgi?id=63661 claims to be the same as this bug and that the problem is caused by pci: Rework ASPM disable code from commit 3c076351c4027a56d5005a39a0b518a4ba393ce2. I'm not 100% sure that's the case, because comment #8 reports that pci=conf1 is a workaround, and I don't know how that would be related to ASPM. I would like to see complete dmesg logs and lspci -vvxxx output both with and without pci=conf1 to explore that issue. Obviously a user should not have to specify a parameter like that to get things to work. ** Bug watch added: Linux Kernel Bug Tracker #63661 http://bugzilla.kernel.org/show_bug.cgi?id=63661 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091263 Title: Cannot install Ubuntu Server on Intel Raid System To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1091263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307044] Re: Unity looses mouse click handler when using enabling USB headset
I am having the same issue with a Plantronics, Inc. Savi 7xx USB headset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307044 Title: Unity looses mouse click handler when using enabling USB headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1307044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316920] [NEW] The screen isn't turning off when the login screen is shown
Public bug reported: Just as the screen is fading the login screen pops up and the fading immediately stops and the screen goes back to full brightness. Even though the Brightness Lock settings are set to Turn screen off when inactive for 5 minutes the screen does not turn off after this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 6 19:48:41 2014 DistUpgraded: 2014-04-23 21:23:35,278 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304-updates, 304.117, 3.13.0-24-generic, x86_64: installed nvidia-304-updates, 304.117, 3.2.0-60-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.2.0-60-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1311] InstallationDate: Installed on 2012-04-26 (740 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) LightdmGreeterLog: Error writing X authority: Error writing to file: No space left on device LightdmGreeterLogOld: Error writing X authority: Error writing to file: No space left on device MachineType: System76, Inc. Wildebeest Performance ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-24 (12 days ago) dmi.bios.date: 12/27/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0146.2011.1227.1631 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-211 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1227.1631:bd12/27/2011:svnSystem76,Inc.:pnWildebeestPerformance:pvrwilb2:rvnIntelCorporation:rnDH67BL:rvrAAG10189-211:cvn:ct3:cvr: dmi.product.name: Wildebeest Performance dmi.product.version: wilb2 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Apr 26 19:25:31 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPS2 to USB KEYBOARD, id 8 inputPS2 to USB KEYBOARD, id 9 inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 10 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316920 Title: The screen isn't turning off when the login screen is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
Oops, I screwed up. Please try this patch. ** Attachment added: Revert EISA changes https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+attachment/3951225/+files/eisa-revert -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178131] Re: 14e4:16bc [Acer Aspire One 756] SD card slot doesn't work
StefanF, I took care of attaching these to the upstream report (https://bugzilla.kernel.org/show_bug.cgi?id=59311). Thanks a lot for collecting them. I apologize that I haven't had time to make progress on this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178131 Title: 14e4:16bc [Acer Aspire One 756] SD card slot doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1178131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255025] Re: filemanager connect to server crashes when using sftp
... and terminal dump... However though I managed to connect nautilus still crashed. The gdb dump gives you the whole overview. ** Attachment added: terminal2.txt https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1255025/+attachment/3921925/+files/terminal2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255025 Title: filemanager connect to server crashes when using sftp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1255025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255025] Re: filemanager connect to server crashes when using sftp
(...more brainpower available today...) I've added the ppa and installed with sudo apt-get update; sudo apt-get upgrade -y --force-yes I get the warning that libnautilus-extension1a nautilus-dbg nautilus- data nautilus are not authenticated, but it installs under the --force-y ** Attachment added: gdb-nautilus.txt https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1255025/+attachment/3921924/+files/gdb-nautilus.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255025 Title: filemanager connect to server crashes when using sftp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1255025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1255025] Re: filemanager connect to server crashes when using sftp
can you send an IRC stackexchange invitation to my launchpad email? Then I can show you more... On 3 December 2013 10:34, Sebastien Bacher seb...@ubuntu.com wrote: could you describe what happens exactly? the new stacktrace seems like a bookmark related error which is different -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1255025 Title: filemanager connect to server crashes when using sftp Status in “nautilus” package in Ubuntu: Incomplete Bug description: Connect to server from file manager by entering sftp://sftp.example.com results repeatedly in crash of filemanager on 13.10 frsh install in virtual box and on asusEEE No harddisk faults detected. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Tue Nov 26 09:19:37 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'840x550+182+189' InstallationDate: Installed on 2013-10-20 (36 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1255025/+subscriptions -- Bjorn Madsen *Researcher Complex Systems Research* Ph.: (+44) 0 7792 030 720 bjorn.mad...@operationsresearchgroup.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255025 Title: filemanager connect to server crashes when using sftp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1255025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1255025] Re: filemanager connect to server crashes when using sftp
Hi Sebastien, Sorry for being in the blanks, but does that change propagate through ubuntu updates automatically or do I need to do anything at my end? On 2 December 2013 10:04, Sebastien Bacher seb...@ubuntu.com wrote: it seems like it should be fixed with that commit https://git.gnome.org/browse/nautilus/commit/?id=c2a5e05231ea0743ef89e666c37a0a77534b9573 Could you try if that's the case? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1255025 Title: filemanager connect to server crashes when using sftp Status in “nautilus” package in Ubuntu: Incomplete Bug description: Connect to server from file manager by entering sftp://sftp.example.com results repeatedly in crash of filemanager on 13.10 frsh install in virtual box and on asusEEE No harddisk faults detected. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Tue Nov 26 09:19:37 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'840x550+182+189' InstallationDate: Installed on 2013-10-20 (36 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1255025/+subscriptions -- Bjorn Madsen *Researcher Complex Systems Research* Ph.: (+44) 0 7792 030 720 bjorn.mad...@operationsresearchgroup.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255025 Title: filemanager connect to server crashes when using sftp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1255025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
