[Bug 1893635] [NEW] three monitor setup hangs
Public bug reported: I have a Ubuntu 20.04 setup with three almost identical monitors (1920x1080) connected to a Radeon RX5500XT 8GB. All works fine as long as I don't turn one of the monitors off and back on. Whenever that happens, all other monitors briefly go blank and then turn back on, as if they are being detected again, and all what I see then is three black screens, with a mouse cursor that still can be moved across all screens. From that moment on, nothing can be done anymore, and I have to hit the reset button of the desktop PC. The monitors have VGA, HDMI and DVI ports. I tried connected them to the RX5500XT (which has 3xDP+1xHDMI ports), using all possible different combinations of cables. (DVItoHDMI, DVItoDP, HDMItoHDMI, HDMItoDP). The problem persists in any case. Whenever I start the system with only two monitors connected, there is no problem. If I switch off one of the monitors and back on, I see the other go blank for a second or two, it turns back on, and the canvas is properly filled with menu and background without any issue. Obviously there is also no problem with only one monitor connected. I experienced this problem with the standard Ubuntu 20.04 amdgpu driver. So, I tried to install the most recent driver from AMD's website, and that driver has the same issue. I tried both gdm3 and lightdm. Same problem. ** Affects: xserver-xorg-video-amdgpu (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/1893635 Title: three monitor setup hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1893635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748889] Re: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files
Exploit is already available at https://www.exploit- db.com/exploits/44022/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748889 Title: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748889] Re: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748889/+attachment/5053595/+files/JournalErrors.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748889/+attachment/5053597/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748889/+attachment/5053596/+files/ProcCpuinfoMinimal.txt ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6871 ** Tags removed: amd64 ** Tags added: multiarch ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748889/+attachment/5053594/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748889 Title: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748889] [NEW] [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files
*** This bug is a security vulnerability *** Public security bug reported: CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6871 LibreOffice through 6.0.1 allows remote attackers to read arbitrary files via =WEBSERVICE calls in a document, which use the COM.MICROSOFT.WEBSERVICE function. Current version 1:5.1.2-0ubuntu1 in Ubuntu 16.04.3 is confirmed to be affected ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial2 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Feb 12 14:19:03 2018 InstallationDate: Installed on 2016-04-22 (661 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748889 Title: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471230] Re: ping got confused about IP-adress after host unreachable
*** This bug is a duplicate of bug 1405232 *** https://bugs.launchpad.net/bugs/1405232 ** This bug has been marked a duplicate of bug 1405232 ping reports wrong IP responding under certain conditions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471230 Title: ping got confused about IP-adress after host unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1471230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471230] Re: ping got confused about IP-adress after host unreachable
I was about to enter a new bug report, but came across yours Ketil. Have same issue. The reported source address from the ping reply is wrong when an intermediary router sent an icmp-host-unreachable, after which the destination host becomes reachable and starts replying. In that case the reported source address is that from the intermediary router (or the originating host itself) that sent the icmp-host- unreachable, and not of the destination host that sent the icmp-echo- reply, as it should be. v@p8p67:~$ ping -n 172.31.168.107 PING 172.31.168.107 (172.31.168.107) 56(84) bytes of data. >From 172.31.168.161 icmp_seq=1 Destination Host Unreachable >From 172.31.168.161 icmp_seq=2 Destination Host Unreachable >From 172.31.168.161 icmp_seq=3 Destination Host Unreachable 64 bytes from 172.31.168.161: icmp_seq=4 ttl=64 time=7.46 ms 64 bytes from 172.31.168.161: icmp_seq=5 ttl=64 time=3.26 ms 64 bytes from 172.31.168.161: icmp_seq=6 ttl=64 time=3.41 ms ... Obviously the last three lines should start with 64 bytes from 172.31.168.107... and not .161. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471230 Title: ping got confused about IP-adress after host unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1471230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299747] Re: Cannot create PGP key in Ubuntu 14.04
The problem is caused by very long period when random key generator collects random bytes. You can find gpg ... --gen-key process still runs. This operation could take up to few minutes, so users won't wait. When I was investigating this I have restored a snapshot of my VM each time before the key is generated. IMO this issue is related to the interface. We need to have some information that the process of the key creation isn't finished. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299747 Title: Cannot create PGP key in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1299747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071209] Re: memtest86 test #7 fails (random pattern error)
Other people are experiencing the same problem. http://forum.canardpc.com/threads/72840-Ubuntu-12.10-build-Memtest-v4.20 -fails-on-Sandy-Bridge http://ubuntuforums.org/showthread.php?p=12318981#post12318981 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071209 Title: memtest86 test #7 fails (random pattern error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692727] Re: amd64 libnss-sss package should include 32bit library for 3rd party application compatibility
Bug still persists in Ubuntu 12.04.1 LTS Unable to install libnss-sss:i386 libnss-sss:i386 : Depends: perl:i386 but it is not going to be installed Recommends: sssd:i386 but it is not going to be installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692727 Title: amd64 libnss-sss package should include 32bit library for 3rd party application compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/692727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003845] [NEW] Invisible symbols in sssd upstart config causes sssd to not start if /bin/sh is a link to /bin/bash
Public bug reported:
This problem appeared when I changed /bin/sh link to /bin/bash. Somehow
dash tolerates this bug described below.
When trying to start sssd I've got:
root@ubuntu-precise:~# start sssd
start: Job failed to start
The only trace in syslog was:
May 24 11:11:59 ubuntu-precise kernel: [66576.880595] init: sssd pre-start
process (9782) terminated with status 2
I've took a look on /etc/init/sssd.conf and everything looks ok, but after some
play I make it to start, and this is the difference to the original:
root@ubuntu-precise:/etc/init# diff sssd.conf sssd.conf.orig
19c19
test -f /etc/sssd/sssd.conf || { stop; exit 0; }
---
test -f /etc/sssd/sssd.conf || { stop; exit 0; }
This looks bizzare for me, so I tried that:
root@ubuntu-precise:/etc/init# cat -A sssd.conf|grep test
^Itest -f /etc/sssd/sssd.conf || { stop; exit 0; }$
root@ubuntu-precise:/etc/init# cat -A sssd.conf.orig|grep test
^Itest -f /etc/sssd/sssd.conf ||M-BM- { stop; exit 0; }$
root@ubuntu-precise:/etc/init#
I have no idea what does M-BM- stand for, but I'm sure this is not how
it should be.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: sssd 1.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Thu May 24 11:02:44 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: sssd
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.init.sssd.conf: 2012-05-24T10:54:11.246378
** Affects: sssd (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003845
Title:
Invisible symbols in sssd upstart config causes sssd to not start if
/bin/sh is a link to /bin/bash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1003845/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003845] Re: Invisible symbols in sssd upstart config causes sssd to not start if /bin/sh is a link to /bin/bash
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003845 Title: Invisible symbols in sssd upstart config causes sssd to not start if /bin/sh is a link to /bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1003845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003845] Re: Invisible symbols in sssd upstart config causes sssd to not start if /bin/sh is a link to /bin/bash
** Description changed:
This problem appeared when I changed /bin/sh link to /bin/bash. Somehow
dash tolerates this bug described below.
When trying to start sssd I've got:
+ [code]
root@ubuntu-precise:~# start sssd
start: Job failed to start
+ [/code]
The only trace in syslog was:
+ [code]
May 24 11:11:59 ubuntu-precise kernel: [66576.880595] init: sssd pre-start
process (9782) terminated with status 2
+ [/code]
I've took a look on /etc/init/sssd.conf and everything looks ok, but after
some play I make it to start, and this is the difference to the original:
- root@ubuntu-precise:/etc/init# diff sssd.conf sssd.conf.orig
+ [code]
+ root@ubuntu-precise:/etc/init# diff sssd.conf sssd.conf.orig
19c19
test -f /etc/sssd/sssd.conf || { stop; exit 0; }
---
test -f /etc/sssd/sssd.conf || { stop; exit 0; }
+ [/code]
This looks bizzare for me, so I tried that:
+ [code]
root@ubuntu-precise:/etc/init# cat -A sssd.conf|grep test
^Itest -f /etc/sssd/sssd.conf || { stop; exit 0; }$
root@ubuntu-precise:/etc/init# cat -A sssd.conf.orig|grep test
^Itest -f /etc/sssd/sssd.conf ||M-BM- { stop; exit 0; }$
- root@ubuntu-precise:/etc/init#
+ root@ubuntu-precise:/etc/init#
+ [/code]
I have no idea what does M-BM- stand for, but I'm sure this is not how
it should be.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: sssd 1.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Thu May 24 11:02:44 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
ProcEnviron:
- SHELL=/bin/bash
- TERM=xterm
- PATH=(custom, no user)
- LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ TERM=xterm
+ PATH=(custom, no user)
+ LANG=en_US.UTF-8
SourcePackage: sssd
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.init.sssd.conf: 2012-05-24T10:54:11.246378
** Description changed:
This problem appeared when I changed /bin/sh link to /bin/bash. Somehow
dash tolerates this bug described below.
When trying to start sssd I've got:
- [code]
+
root@ubuntu-precise:~# start sssd
start: Job failed to start
- [/code]
+
The only trace in syslog was:
- [code]
- May 24 11:11:59 ubuntu-precise kernel: [66576.880595] init: sssd pre-start
process (9782) terminated with status 2
- [/code]
+
+ May 24 11:11:59 ubuntu-precise kernel: [66576.880595] init: sssd pre-
+ start process (9782) terminated with status 2
+
I've took a look on /etc/init/sssd.conf and everything looks ok, but after
some play I make it to start, and this is the difference to the original:
- [code]
+
root@ubuntu-precise:/etc/init# diff sssd.conf sssd.conf.orig
19c19
test -f /etc/sssd/sssd.conf || { stop; exit 0; }
---
test -f /etc/sssd/sssd.conf || { stop; exit 0; }
- [/code]
+
This looks bizzare for me, so I tried that:
- [code]
+
root@ubuntu-precise:/etc/init# cat -A sssd.conf|grep test
^Itest -f /etc/sssd/sssd.conf || { stop; exit 0; }$
root@ubuntu-precise:/etc/init# cat -A sssd.conf.orig|grep test
^Itest -f /etc/sssd/sssd.conf ||M-BM- { stop; exit 0; }$
root@ubuntu-precise:/etc/init#
- [/code]
- I have no idea what does M-BM- stand for, but I'm sure this is not how
- it should be.
+
+ I have no idea what does M-BM- stand for, but I'm sure this is not how it
should be.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: sssd 1.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Thu May 24 11:02:44 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: sssd
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.init.sssd.conf: 2012-05-24T10:54:11.246378
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003845
Title:
Invisible symbols in sssd upstart config causes sssd to not start if
/bin/sh is a link to /bin/bash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1003845/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003845] Re: Invisible symbols in sssd upstart config causes sssd to not start if /bin/sh is a link to /bin/bash
Attaching the original sssd.conf from /etc/init/ ** Attachment added: sssd.conf.orig https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1003845/+attachment/3160741/+files/sssd.conf.orig -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003845 Title: Invisible symbols in sssd upstart config causes sssd to not start if /bin/sh is a link to /bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1003845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996960] [NEW] package grub-pc 1.98-1ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126
Public bug reported: - localuser@ubuntu-ald:~$ lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 localuser@ubuntu-ald:~$ apt-cache policy grub-pc grub-pc: Installed: 1.98-1ubuntu13 Candidate: 1.98-1ubuntu13 - I've tried to update a pretty old 10.04 installation to the most fresh. Upgrade of grub-pc package was unsuccessful. After reboot I've tried one more time: -- localuser@ubuntu-ald:~$ sudo apt-get install grub-pc Reading package lists... Done Building dependency tree Reading state information... Done grub-pc is already the newest version. grub-pc set to manually installed. The following packages were automatically installed and are no longer required: linux-headers-2.6.32-33-generic linux-headers-2.6.32-21 linux-headers-2.6.32-33 linux-headers-2.6.32-21-generic Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up grub-pc (1.98-1ubuntu13) ... /var/lib/dpkg/info/grub-pc.config: line 48: .: /etc/default/grub: cannot execute binary file dpkg: error processing grub-pc (--configure): subprocess installed post-installation script returned error exit status 126 Errors were encountered while processing: grub-pc E: Sub-process /usr/bin/dpkg returned an error code (1) localuser@ubuntu-ald:~$ sudo dpkg-reconfigure grub Package `grub' is not installed and no info is available. Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. /usr/sbin/dpkg-reconfigure: grub is not installed localuser@ubuntu-ald:~$ - ProblemType: Package DistroRelease: Ubuntu 10.04 Package: grub-pc 1.98-1ubuntu13 ProcVersionSignature: Ubuntu 2.6.32-41.88-generic 2.6.32.59+drm33.24 Uname: Linux 2.6.32-41-generic i686 Architecture: i386 Date: Wed May 9 09:19:43 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 126 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) SourcePackage: grub2 Title: package grub-pc 1.98-1ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996960 Title: package grub-pc 1.98-1ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/996960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996960] Re: package grub-pc 1.98-1ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996960 Title: package grub-pc 1.98-1ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/996960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
