I just ran into this too from `apport-collect -p chromium-browser`. I
wonder if it has anything to do with a modified /etc/chromium-
browser/default file?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Is there anything I can do to move this along?
I'm fairly certain it's a kernel or driver issue since zesty since I'm
currently running 16.04 on live USB and all three monitors work just
fine. I've tried using the 4.8 kernel from yakkety, but I couldn't get
it to boot, I'm assuming it was
lspci and lshw show 2 GPUs. The builtin one, and the actual card, but
xrandr only lists one provider.
$ xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3
associated providers: 0 name:KAVERI @ pci::00:01.0
Might be a
Public bug reported:
I'm not 100% sure this is the right package to file the bug against, but
since upgrading to zesty the two monitors on my second GPU are no longer
detected once I reach the greeter screen at login time. However, both of
them display information during boot.
Let me know how I
** Attachment added: "lshw output"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/4881175/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Some more information:
- If I switch my primary display adapter in BIOS to the onboard GPU, I can get
all three monitors and two cards working, but the framerate on the monitors
attached to the PEG GPU is so low that it's almost unusable.
- If I set the PEG GPU as primary display adapter, all
I'm beginning to think this is a driver issue. I have a builtin "Kaveri"
amd gpu, and pci Radeon HD 4850. I usually have the 4850 as my primary
card/monitor setup. However, since upgrading to Ubuntu 17.04, once
lightdm is started, only the monitor on the Kaveri works.
I dropped to VT1, and ran `X
I ran into this running a `do-release-upgrade -d` on a xenial machine at
$work. The upgrade failed partway through leaving the system in a
partial upgrade state afaict; lsb-release -a reports 18.04, but the apt
sources are still xenial.
--
You received this bug notification because you are a
I filmed my computer boot up to better show what happens. The right
monitor is on the integrated video card (the R7), and doesn't show
anything initially. The center and left monitor turn on and mirror each
other during boot, and show grub and most of the kernel and systemd
messages, then at some
** Attachment added: "dmesg log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235234/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
I've come across this again after upgrading to 18.10
$ xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3
associated providers: 0 name:KAVERI @ pci::00:01.0
$ sudo lspci -nn | grep
Added gpu-manager log
It says "Unsupported discrete card vendor: 1002",
Does this mean my discrete card is no longer supported?
** Attachment added: "gpu-manager.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235683/+files/gpu-manager.log
--
You received
** Attachment added: "xorg log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235697/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Also affects: switcheroo-control (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
** Changed in: lightdm
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
After going on the #radeon channel on Freenode, we narrowed the problem
down to the switcheroo-control package. We started by hand making an
xorg.conf file and disabling gpu-manager, but still had issues. Looking
at the dmesg log, we saw that the discrete gpu is enabled at first, then
disabled
15 matches
Mail list logo
