[Bug 2007194] Re: gnome-screenshot sometimes hangs leaving a transparent white square over the screen
To repro: make sure you select the Video (not Photo) option. Then click the (now-red-inner-circled) Record button. The white selection/area pane will remain, with the rest of the screen dimmed, until you stop the recording. How do you stop it? Look for a small control, with a white-on-red black square to the right of a counting-up timer for the video, and click that little square. So it's not so much a "bug" as a surprising, if not almost-hidden (especially for those of us with kinda-largish monitors), behavior. (This took me almost 10 minutes to figure out!!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007194 Title: gnome-screenshot sometimes hangs leaving a transparent white square over the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/2007194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019247] Re: perf should be compiled with libtraceevent
This still appears to be an issue. Events are listed in `perf list` but not available for use by `perf record` e.g. $ sudo /usr/lib/linux-tools/6.2.0-39-generic/perf record -e syscalls:sys_enter_fsync -ag event syntax error: 'syscalls:sys_enter_fsync' \___ unsupported tracepoint libtraceevent is necessary for tracepoint support Run 'perf list' for a list of valid events Usage: perf record [] [] or: perf record [] -- [] -e, --eventevent selector. use 'perf list' to list available events ➜ test git:(UPM-29742) ✗ /usr/lib/linux-tools/6.2.0-39-generic/perf version perf version 6.2.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2019247 Title: perf should be compiled with libtraceevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056578] Re: Tor Browser - keyboard not functioning
torbrowser-launcher: Installed: 0.3.7-1 Candidate: 0.3.7-1 Version table: *** 0.3.7-1 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status ** Description changed: I have installed tor browser v13.0.11 on 24.04 (noble). The keyboard does not operate, when typing no characters are appearing. I have tried to enter a search and also type in a URL but this is not working. + + I am using default Ubuntu GNOME with wayland. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: torbrowser-launcher 0.3.7-1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 16:01:36 2024 InstallationDate: Installed on 2024-03-08 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: torbrowser-launcher UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I have installed tor browser v13.0.11 on 24.04 (noble). The keyboard does not operate, when typing no characters are appearing. I have tried to enter a search and also type in a URL but this is not working. - I am using default Ubuntu GNOME with wayland. + I am using default Ubuntu desktop with wayland. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: torbrowser-launcher 0.3.7-1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 16:01:36 2024 InstallationDate: Installed on 2024-03-08 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: torbrowser-launcher 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/2056578 Title: Tor Browser - keyboard not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2056578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056578] [NEW] Tor Browser - keyboard not functioning
Public bug reported: I have installed tor browser v13.0.11 on 24.04 (noble). The keyboard does not operate, when typing no characters are appearing. I have tried to enter a search and also type in a URL but this is not working. I am using default Ubuntu desktop with wayland. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: torbrowser-launcher 0.3.7-1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 16:01:36 2024 InstallationDate: Installed on 2024-03-08 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: torbrowser-launcher UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: torbrowser-launcher (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056578 Title: Tor Browser - keyboard not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2056578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023322]
(In reply to Michael Catanzaro from comment #62) > Hi Craig and Thomas (and Emil if you're still around): if you're still > encountering problems with NVIDIA graphics, please report new a bug and > leave a comment here linking to the new bug. My problem was on legacy nvidia driver, and newer versions wouldn't even start. But I now know a workaround (GSK_RENDERER=cairo) and don't expect there will be a fix for my old driver anyway. https://gitlab.gnome.org/GNOME/gtk/-/issues/5858 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2023322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@BloodyIron, please see: https://github.com/christgau/wsdd I suggest you install as it is a significantly better work-around than constantly killing the daemon. It is intended to be released in the next Debian (bookworm) release as a package, I do not know if Ubuntu will also be including it in their next release. Whether Nautilus will use it or not, I could not answer to that - I have long since switched to using Thunar without any issues. With regards to "If restarting it 'fixers' it, then why on earth does it break in the first place?" I suggest you see one of the replies here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/307 and further reading here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #307 https://gitlab.gnome.org/GNOME/gvfs/-/issues/307 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (1881780). https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [ubuntu-us-mi] Package Updates on Ubuntu
* Justin Macauley (macauley.justi...@gmail.com) wrote: > Hi there, > > Python 3.11 has just released. I did a apt package manager update on my > distro 20.10 and nothing was updated on my distro to the current release of > the Python Programming Laungage. How long does it typically take for a new > apt package update to be updated on Ubuntu typically after a new release of > software? Thanks. Hi Justin, Generally speaking there aren't updates for the Python versions that ship with an Ubuntu release. That said if you want to update to Python 3.11 you should check out the "Dead Snakes" PPA: https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa Note that these are built for the LTS releases so I'm not sure if they'll install on 20.10 (which isn't an LTS release and is end-of-life). You'll likely want to upgrade to a later LTS like 22.04. Hope this helps! -- Craig Maloney (cr...@decafbad.net) http://decafbad.net -- ubuntu-us-mi mailing list ubuntu-us-mi@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-mi
[Bug 1970912] [NEW] python3-pyaudio fails with: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
Public bug reported: I recently upgraded my system from 21.10 to 22.04 and a previous working python program stopped working. It uses the python3-pyaudio package, and its initialisation fails like this: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats A bit of searching came up with this stack overflow answer: https://stackoverflow.com/a/70358664/164234 > Unfortunately, a breaking change was introduced in Python 3.10 (see bpo-40943 > and PEP-0353), and thus PyAudio needs updated. > > I've submitted a fix upstream, but as the project has not been updated since > 2017, I'm not quite sure how quick it will get reviewed. > > In the meantime, you are free to build my fork from source and use that :) The fix looks quite simple: https://git.skeh.site/skeh/pyaudio/commit/2ee560056ec889ea7cd3ce1801b796b0939dd540 So might be something that you could carry as a fix. ** Affects: python-pyaudio (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/1970912 Title: python3-pyaudio fails with: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pyaudio/+bug/1970912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969945] [NEW] Update background preference for 22.04 (jammy)
Public bug reported: The vanilla-gnome-default-settings package does not revert the Ubuntu background/screensaver images to gnome behavior in 22.04. vanilla-gnome-default-settings contains the file /usr/share/glib-2.0/schemas/20_vanilla-gnome-default- settings.gschema.override for reinstating most gnome default settings. The keys org.gnome.desktop.background.picture-uri and org.gnome.desktop.screensaver.picture-uri currently point to the file /usr/share/backgrounds/gnome/adwaita-timed.xml, which was removed from the gnome-backgrounds package in 22.04. The removal appears to be related to a change in the way Gnome 42 handles background images in the context of light/dark theme preferences. gnome-control-center seems to be in a halfway migrated state between Gnome 41 and 42, so I'm not completely sure I understand what the right fix here should be... Simply updating the keys to point to (what appears to be the new equivalent file?) /usr/share/gnome-background- properties/adwaita.xml doesn't change anything. I think a minimal (short term?) fix is to set [org.gnome.desktop.background] picture-uri='file:///usr/share/backgrounds/gnome/adwaita-l.jpg' picture-uri-dark='file:///usr/share/backgrounds/gnome/adwaita-d.jpg' There is not an equivalent 'dark' version of the key for the screensaver portion, though... There are also some new 'primary-color', 'secondary- color' keys which should probably be considered (their upstream gnome values appear to be '#023c88' and '#5789ca' respectively). ** Affects: ubuntu-gnome-default-settings (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/1969945 Title: Update background preference for 22.04 (jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1969945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968165] Re: Epiphany snap and App Armor permissions spamming my log files
Thank you for moving this to the right place. I wasn't sure what my options were. The link on https://snapcraft.io/epiphany needs changing as well so that the folks with the unfortunate name collision don't get blessed with irrelevant bug reports. :) Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968165 Title: Epiphany snap and App Armor permissions spamming my log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1968165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968165] Re: Epiphany snap and App Armor permissions spamming my log files
Grrr. Apparently this is the wrong epiphany package. Thanks Ubuntu Snap Store for directing me to the wrong location. Please close this bug. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968165 Title: Epiphany snap and App Armor permissions spamming my log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany/+bug/1968165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968165] [NEW] Epiphany snap and App Armor permissions spamming my log files
Public bug reported: It looks like there's an issue with the epiphany snap and apparmor under Ubuntu 18.04 (unsure if this is also in other releases) When I start up / use Epiphany my log messages get spammed with the following messages: [ 1659.277503] audit: type=1400 audit(1649334320.692:78): apparmor="DENIED" operation="capable" profile="/snap/core/12834/usr/lib/snapd/snap-confine" pid=4689 comm="snap-confine" capability=4 capname="fsetid" [ 1662.336508] audit: type=1326 audit(1649334323.748:79): auid=1000 uid=1000 gid=1000 ses=3 pid=4689 comm="epiphany" exe="/snap/epiphany/111/usr/bin/epiphany" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f059617576d code=0x5 [ 1662.863666] audit: type=1326 audit(1649334324.276:80): auid=1000 uid=1000 gid=1000 ses=3 pid=4780 comm="WebKitNetworkPr" exe="/snap/epiphany/111/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitNetworkProcess" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f0cb5bbb76d code=0x5 [ 1663.586197] audit: type=1326 audit(1649334325.000:81): auid=1000 uid=1000 gid=1000 ses=3 pid=4689 comm="pool-epiphany" exe="/snap/epiphany/111/usr/bin/epiphany" sig=0 arch=c03e syscall=93 compat=0 ip=0x7f059616c3cb code=0x5 [ 1664.964308] audit: type=1326 audit(1649334326.376:82): auid=1000 uid=1000 gid=1000 ses=3 pid=4798 comm="WebKitWebProces" exe="/snap/epiphany/111/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess" sig=0 arch=c03e syscall=314 compat=0 ip=0x7ff3239a876d code=0x5 [ 1667.863229] audit: type=1400 audit(1649334329.277:83): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1667.863538] audit: type=1400 audit(1649334329.277:84): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/sys/fs/cgroup/memory/memory.usage_in_bytes" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1672.864491] audit: type=1400 audit(1649334334.277:85): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1677.867686] audit: type=1400 audit(1649334339.281:86): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1682.870926] audit: type=1400 audit(1649334344.285:87): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1687.874001] audit: type=1400 audit(1649334349.289:88): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1692.877044] audit: type=1400 audit(1649334354.293:89): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1697.880054] audit: type=1400 audit(1649334359.293:90): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1702.883208] audit: type=1400 audit(1649334364.297:91): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1707.886283] audit: type=1400 audit(1649334369.301:92): apparmor="DENIED" operation="open" profile="snap.epiphany.epiphany" name="/proc/zoneinfo" pid=4689 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 I searched online for a fix but to no avail. Is there a way to get these messages to stop, or perhaps a way to allow epiphany access to whatever it needs to access so my log messages may live in peace? Thank you! ** Affects: epiphany (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968165 Title: Epiphany snap and App Armor permissions spamming my log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany/+bug/1968165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967614] [NEW] Dropbox on Ubuntu 22.04 beta not logging in
Public bug reported: Ubuntu 22.04 beta, the dropbox icon in the top system bar is just stuck on 'Starting'. Signing in loads the web page, it allows me to enter a username and password, but then nothing happens after. ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: - Ubuntu 22.04 beta, the top icon is just stuck on 'Starting'. Signing in - loads the web page, it allows me to enter a username and password, but - then nothing happens after. + Ubuntu 22.04 beta, the dropbox icon in the top system bar is just stuck + on 'Starting'. Signing in loads the web page, it allows me to enter a + username and password, but then nothing happens after. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967614 Title: Dropbox on Ubuntu 22.04 beta not logging in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964622] Re: MariaDB limits to 1000 parameters
I suspect this might be related to `in_predicate_conversion_threshold`?
While I have fixed this elsewhere by using
foreach (array_chunk($ids, 900) as $chunk_ids) {
}
I've also been able to use the following as a temporary work around:
SET in_predicate_conversion_threshold=2000;
I assume this config variable is used to protect against something, so
I'm hesitant to apply it globally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964622
Title:
MariaDB limits to 1000 parameters
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1964622/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964622] [NEW] MariaDB limits to 1000 parameters
Public bug reported:
With the recent release of MariaDB `1:10.3.34-0ubuntu0.20.04.1`, or
maybe php7.4-mysql `7.4.3-4ubuntu2.9`, something changed so the number
of parameters used with `IN()` is now being limited to 1000.
I believe the number of parameters used to only be limited by the
`max_allowed_packet` value, where I was able to specify 3,000+ integers.
This is not noted in the MariaDB documentation, but is in MySQL:
https://mariadb.com/kb/en/in/
https://dev.mysql.com/doc/refman/8.0/en/comparison-operators.html#operator_in
The `$statement->errno` returns the integer 2014, and
`$statement->error` does include "Commands out of sync; you can't run
this command now", which matches later versions of MariaDB, so I think
part of this change has been back-ported somehow (cannot see in either
patch, but I can't understand all that has changed).
For a test script, using PHP (so I can easily use parameters)... I can
do 2 x `IN()` with 999 parameters each, but as soon as there are 1000
parameters in either or both, it fails.
prepare('SELECT id FROM my_table WHERE id IN (' . $params .
') AND id IN (' . $params . ')');
$statement->bind_param($types, ...$values);
$statement->execute();
$result = $statement->get_result();
var_dump($db->error);
var_dump($statement->error);
var_dump($statement->errno);
var_dump($result);
while ($row = mysqli_fetch_assoc($result)) {
print_r($row);
}
?>
Running this without parameters is fine, same with the `mysql` cli:
SELECT id FROM my_table WHERE id IN (
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
);
** Affects: mariadb-10.3 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- MariaDB limits to 1000 parameters, but no error
+ MariaDB limits to 1000 parameters
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964622
Title:
MariaDB limits to 1000 parameters
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1964622/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962043] Re: libwacom9 : depends on : libwacom-common
https://i.imgur.com/khRelQJ.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962043 Title: libwacom9 : depends on : libwacom-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1962043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960080] Re: libgcc_s.so.1 must be installed for pthread_exit to work
*** This bug is a duplicate of bug 1958594 *** https://bugs.launchpad.net/bugs/1958594 ** This bug has been marked a duplicate of bug 1958594 Boot error: libgcc_s.so.1 must be installed for pthread_exit to work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960080 Title: libgcc_s.so.1 must be installed for pthread_exit to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1960080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960080] [NEW] libgcc_s.so.1 must be installed for pthread_exit to work
Public bug reported: I'm unable to decrypt my root partition at boot using the cryptsetup- initramfs package currently in jammy (2:2.4.2-1ubuntu4). I get the askpass prompt, but after entering the password, decryption fails with the error message: libgcc_s.so.1 must be installed for pthread_exit to work and I'm prompted to retry. This library indeed seems to be missing from the initrd file: lsinitramfs /boot/initrd.img-5.15.0-18-generic | grep libgcc Compared with an identically configured image running impish: lsinitramfs /boot/initrd.img-5.13.0-28-generic | grep libgcc usr/lib/x86_64-linux-gnu/libgcc_s.so.1 I noticed the following line in the jammy changelog: * cryptsetup-initramfs now requires initramfs-tools 0.137 or later and no longer copies libgcc_s.so.1 to the initrd since recent initramfs-tools take care of it. And found the following lines in the impish version of /usr/share/initramfs-tools/hooks/cryptroot: # libargon2 uses pthread_cancel for so in $(ldconfig -p | sed -nr 's/^\s*libgcc_s\.so.*=>\s*//p'); do copy_exec "$so" done Which are not in the jammy version. Adding an explicit copy_exec line for this library and rebuilding the initrd file fixes the problem. I'm not exactly sure which binary in the cryptsetup initrd inclusion requires this library (it doesn't appear to be the askpass nor cryptsetup binaries), but whatever it is doesn't seem to be properly declaring its dependency for inclusion. I also don't completely understand the changelog message that implies inclusion of this library is now the responsibility of initramfs- tools... ** Affects: cryptsetup (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/1960080 Title: libgcc_s.so.1 must be installed for pthread_exit to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1960080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908800] Re: Wireless card crashes daily on my XPS 13 9380
I updated the firmware for this card from the 00157 to the 00288 version of firmware: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 and it seems to have fixed it but still I get: ath10k_pci :3a:00.0: failed to install key for vdev 0 peer MY_AP_MAC_ADDRESS: -110 in my journal and on dmesg. but things seem to not disconnect for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908800 Title: Wireless card crashes daily on my XPS 13 9380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1908800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908800] Re: Wireless card crashes daily on my XPS 13 9380
** Attachment added: "lspci output" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1908800/+attachment/5547183/+files/ath10k-qca6174-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/1908800 Title: Wireless card crashes daily on my XPS 13 9380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1908800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908800] Re: Wireless card crashes daily on my XPS 13 9380
I am on 21.04 (Linux XPS-13-9360 5.11.0-41-generic #45-Ubuntu SMP Fri Nov 5 11:37:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) and this is an issue for me. I have to re-connect to my AP to get connected again. My wireless card is: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) See attached lspci and journalctl output. ** Attachment added: "journalctl output" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1908800/+attachment/5547182/+files/ath10k-qca6174-journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908800 Title: Wireless card crashes daily on my XPS 13 9380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1908800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951279] Re: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds
I have the same issue. It's preventing me from doing some fairly important things, without an obvious workaround at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951279 Title: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
I upgraded my PC from 21.04 to 21.10. I found that WebGL doesn't work in the snap firefox that 21.10 installed. I uninstalled the snap firefox and installed the deb firefox via apt. That fixed the WebGL issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947257] Re: Partial profile loss on upgrade from 21.04 to 21.10
I upgraded from 21.04 to 21.10. Other (non-sudo) users of the computer reported that their Firefox profiles were lost. I uninstalled the snap firefox, and installed deb firefox via apt. Their profiles "came back". I guess the snap firefox looks for profiles in a different location, and the profiles aren't transferred from the old deb-firefox location to the snap-firefox-expected location. It looks as though this transition to snap firefox has been done badly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947257 Title: Partial profile loss on upgrade from 21.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875756] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled
I've never had this in Ubuntu 21.04 Hirsute. But after upgrading to Ubuntu 21.10 Impish, I had it boot up without WiFi. In 21.04 Hirsute, here is an example good boot from /var/log/syslog: Oct 21 15:03:08 nary kernel: [2.596955] ath10k_pci :02:00.0: enabling device ( -> 0002) Oct 21 15:03:08 nary kernel: [2.599059] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Oct 21 15:03:08 nary kernel: [2.880904] ath10k_pci :02:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901 Oct 21 15:03:08 nary kernel: [2.880913] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Oct 21 15:03:08 nary kernel: [2.881690] ath10k_pci :02:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877 Oct 21 15:03:08 nary kernel: [2.945483] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 8aedfa4a Oct 21 15:03:08 nary kernel: [3.131331] ath10k_pci :02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Oct 21 15:03:09 nary kernel: [3.222767] ath10k_pci :02:00.0 wlp2s0: renamed from wlan0 Oct 21 15:03:09 nary NetworkManager[673]: [1634788989.1422] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:1d.6/:02:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci) In 21.10 Impish, here is a bad boot: Oct 22 07:49:16 nary kernel: [2.444721] ath10k_pci :02:00.0: enabling device ( -> 0002) Oct 22 07:49:16 nary kernel: [2.447680] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Oct 22 07:49:16 nary kernel: [2.740342] ath10k_pci :02:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901 Oct 22 07:49:16 nary kernel: [2.740348] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Oct 22 07:49:16 nary kernel: [2.741071] ath10k_pci :02:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877 Oct 22 07:49:16 nary kernel: [2.804728] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 8aedfa4a Oct 22 07:49:21 nary kernel: [7.967436] ath10k_pci :02:00.0: wmi service ready event not received Oct 22 07:49:21 nary kernel: [8.047727] ath10k_pci :02:00.0: could not init core (-110) Oct 22 07:49:21 nary kernel: [8.047774] ath10k_pci :02:00.0: could not probe fw (-110) But, I rebooted it, and WiFi came back after the boot. It remains to be seen how often this issue appears in Ubuntu 21.10 Impish. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875756 Title: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
What does it take to get bugs fixed in LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945854] [NEW] package python3-lib2to3 3.8.10-0ubuntu1~20.04 failed to install/upgrade: installed python3-lib2to3 package post-installation script subprocess returned error exit status 2
Public bug reported: I have previously installed python3 using miniconda, and wonder if somehow that could conflict with this upgrade? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-lib2to3 3.8.10-0ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: ncurses-term:amd64: Install openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 2 11:47:42 2021 Dependencies: DpkgHistoryLog: Start-Date: 2021-10-02 11:47:37 Commandline: apt-get install openssh-server Requested-By: craig (1000) Install: openssh-sftp-server:amd64 (1:8.2p1-4ubuntu0.3, automatic), ncurses-term:amd64 (6.2-0ubuntu2, automatic), openssh-server:amd64 (1:8.2p1-4ubuntu0.3), ssh-import-id:amd64 (5.10-0ubuntu1, automatic) DuplicateSignature: package:python3-lib2to3:3.8.10-0ubuntu1~20.04 Setting up python3-lib2to3 (3.8.10-0ubuntu1~20.04) ... /usr/bin/python3.9: can't open file '/usr/lib/python3.9/py_compile.py': [Errno 2] No such file or directory dpkg: error processing package python3-lib2to3 (--configure): installed python3-lib2to3 package post-installation script subprocess returned error exit status 2 ErrorMessage: installed python3-lib2to3 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-06-23 (465 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-stdlib-extensions Title: package python3-lib2to3 3.8.10-0ubuntu1~20.04 failed to install/upgrade: installed python3-lib2to3 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-stdlib-extensions (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945854 Title: package python3-lib2to3 3.8.10-0ubuntu1~20.04 failed to install/upgrade: installed python3-lib2to3 package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1945854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942606] [NEW] Got crash report on startup
Public bug reported: Crash report popped up on startup. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: elpa-magit 2.99.0.git0957.ge8c7bd03-1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Sep 3 10:55:52 2021 ErrorMessage: installed elpa-magit package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-09-02 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: magit Title: package elpa-magit 2.99.0.git0957.ge8c7bd03-1 failed to install/upgrade: installed elpa-magit package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: magit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942606 Title: Got crash report on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magit/+bug/1942606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927159] [NEW] 21.04 Multi-Monitor Desktop Click & Drag Issues
Public bug reported: Hello, I've got two displays set up in "Join Displays" mode, where screen 1 is above screen 2 When both monitors are enabled, the "Click and Drag" area on the desktop (and only the desktop!) is wrong. However, when one monitor is disabled, click & drag behaves properly. When I depress the mouse on the bottom screen, the point I click on to start the 'square of selection' is correct, but the bottom left automatically starts 1000~ pixels (or more) below where I click. Strangely, on the top monitor, the behaviour is different and the right 'x' coordinate is moved to the right about 700~ pixels E.g in the picture below (top monitor), I clicked on the top right of the edge of the volcano, but it automatically added another selection point to the right of it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 4 16:51:44 2021 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-11 (1028 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-05-04 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Screenshot of behaviour" https://bugs.launchpad.net/bugs/1927159/+attachment/5494789/+files/Screenshot%20from%202021-05-04%2014-24-58.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927159 Title: 21.04 Multi-Monitor Desktop Click & Drag Issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[ubuntu-us-mi] Ubuntu 21.04 (Hirsute Hippo) Release Party
Hi all, We'll be having the Ubuntu 21.04 (Hirsute Hippo) Release Party at Virtual Penguicon this year. The event will be held from 7pm-9pm on Friday, April 23rd. More details here: https://loco.ubuntu.com/events/ubuntu-us-mi/4113-ubuntu-2104-hirsute-hippo-release-party/ You will need to register with Penguicon for the link to the online discussion. Registration is $10 and helps Penguicon to defray the expenses of not having a convention for one year. (If you need a scholarship to defray the expenses please contact Penguicon Registration. They'll be more than happy to help out.) Plus you'll get access to one of the most exciting online conventions this year covering a broad range of topics. Hope to see you there! -- Craig Maloney (cr...@decafbad.net) http://decafbad.net -- ubuntu-us-mi mailing list ubuntu-us-mi@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-mi
[Bug 1920632] Re: use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works
I'm seeing this issue in groovy with kernel 5.8.0.48.53. Has the fix regressed in the later kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920632 Title: use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1920632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922500] [NEW] kmines timer doesnt stop when game complete, doesnt allow saving high scores
Public bug reported: To replicate, you must successfully complete a puzzle. When complete, in bionic version (and as expected) it tells you you're done and offers to save your score in top 10.In focal version, nothing happens when you succesfully complete puzzle. Timer doesnt stop, doesn't report game over, doesnt allow you to save high score, etc. ** Affects: kmines (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/1922500 Title: kmines timer doesnt stop when game complete, doesnt allow saving high scores To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmines/+bug/1922500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917816] Re: Firefox not loading gifv, gifs
Installed VLC, problem is gone. This has been confirmed on multiple systems. Something about the way FireFox is handling media. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917816 Title: Firefox not loading gifv, gifs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921599] Re: PHP 7.4 segfaults on addserver
This appears to be fixed in Ubuntu 20.10 (Groovy Gorilla): php- gearman_2.0.6+1.1.2-8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921599 Title: PHP 7.4 segfaults on addserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-gearman/+bug/1921599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921599] [NEW] PHP 7.4 segfaults on addserver
Public bug reported:
root@server:/var/www/html# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
root@server:/var/www/html# apt-cache policy php-gearman
php-gearman:
Installed: (none)
Candidate: 2.0.6+1.1.2-7build1
Version table:
2.0.6+1.1.2-7build1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
It says uninstalled since I installed it and then got the error. So I
uninstalled it and compiled the master branch and that fixes the issue.
root@server:/var/www/html# php -v
PHP 7.4.3 (cli) (built: Oct 6 2020 15:47:56) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.3, Copyright (c), by Zend Technologies
Running test php file gets a segfault:
root@server:/var/www/html# php -f test.php
PHP Fatal error: Uncaught GearmanException: Failed to set exception option in
/var/www/html/test.php:3
Stack trace:
#0 /var/www/html/test.php(3): GearmanClient->addServer()
#1 {main}
thrown in /var/www/html/test.php on line 3
Segmentation fault (core dumped)
It appears the issue is fixed in the latest version of the gearman
extension (https://github.com/php/pecl-networking-gearman).
Unfortunately this was fixed after the 2.0.6 release.
https://github.com/php/pecl-networking-
gearman/commit/afd2ed880c67455fbf28097dfde7bd3e368c183e
** Affects: php-gearman (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- # lsb_release -rd
+ root@server:/var/www/html# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
- # apt-cache policy php-gearman
+ root@server:/var/www/html# apt-cache policy php-gearman
php-gearman:
- Installed: (none)
- Candidate: 2.0.6+1.1.2-7build1
- Version table:
- 2.0.6+1.1.2-7build1 500
- 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: (none)
+ Candidate: 2.0.6+1.1.2-7build1
+ Version table:
+ 2.0.6+1.1.2-7build1 500
+ 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
+ 100 /var/lib/dpkg/status
It says uninstalled since I installed it and then got the error. So I
uninstalled it and compiled the master branch and that fixes the issue.
Running test php file gets a segfault:
- root@hv101:/var/www/html# php -f test.php
+ root@server:/var/www/html# php -f test.php
PHP Fatal error: Uncaught GearmanException: Failed to set exception option
in /var/www/html/test.php:3
Stack trace:
#0 /var/www/html/test.php(3): GearmanClient->addServer()
#1 {main}
- thrown in /var/www/html/test.php on line 3
+ thrown in /var/www/html/test.php on line 3
Segmentation fault (core dumped)
It appears the issue is fixed in the latest version of the gearman
extension (https://github.com/php/pecl-networking-gearman).
Unfortunately this was fixed after the 2.0.6 release.
https://github.com/php/pecl-networking-
gearman/commit/afd2ed880c67455fbf28097dfde7bd3e368c183e
** Description changed:
root@server:/var/www/html# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
root@server:/var/www/html# apt-cache policy php-gearman
php-gearman:
Installed: (none)
Candidate: 2.0.6+1.1.2-7build1
Version table:
2.0.6+1.1.2-7build1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
It says uninstalled since I installed it and then got the error. So I
uninstalled it and compiled the master branch and that fixes the issue.
+ root@server:/home/aiso# php -v
+ PHP 7.4.3 (cli) (built: Oct 6 2020 15:47:56) ( NTS )
+ Copyright (c) The PHP Group
+ Zend Engine v3.4.0, Copyright (c) Zend Technologies
+ with Zend OPcache v7.4.3, Copyright (c), by Zend Technologies
+
Running test php file gets a segfault:
root@server:/var/www/html# php -f test.php
PHP Fatal error: Uncaught GearmanException: Failed to set exception option
in /var/www/html/test.php:3
Stack trace:
#0 /var/www/html/test.php(3): GearmanClient->addServer()
#1 {main}
thrown in /var/www/html/test.php on line 3
Segmentation fault (core dumped)
It appears the issue is fixed in the latest version of the gearman
extension (https://github.com/php/pecl-networking-gearman).
Unfortunately this was fixed after the 2.0.6 release.
https://github.com/php/pecl-networking-
gearman/commit/afd2ed880c67455fbf28097dfde7bd3e368c183e
** Description changed:
root@server:/var/www/html# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
root@server:/var/www/html# apt-cache policy php-gearman
php-gearman:
Installed: (none)
Candidate: 2.0.6+1.1.2-7build1
Version table:
2.0.6+1.1.2-7build1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
It says
[Bug 530797] Re: Please support theming the VLC systray icon
8 Years later, I think this has regressed? I have tried vlc-panel.png in both icon theme and in hicolor and pixmaps, it is not being used in VLC 3.0.8 Is vlc-panel the correct filename? I haven't been able to find where it's documented, hence why posting on 8 year old bug tracker... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/530797 Title: Please support theming the VLC systray icon To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/530797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917816] Re: Firefox not loading gifv, gifs
Downloaded the ubuntu-20.04.2.0-desktop-amd64.iso image and installed a virtual machine, updated it with apt update && apt dist-upgrade. Rebooted, tried firefox again and saw the same problem. Disabled most of the security and privacy restrictions in the firefox settings, same problem. # apt info firefox ... Version: 86.0+build3-0ubuntu0.20.04.1 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917816 Title: Firefox not loading gifv, gifs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917816] [NEW] Firefox not loading gifv, gifs
Public bug reported: Firefox 86.0-3, fresh installation of Ubuntu 20.04 with no additional repositories added other than for Google Chrome, no third-party drivers, etc. Full dist-upgrade run, rebooted and otherwise working fine. A version of firefox was pulled down using 'snap install firefox' and it did not have the same issues. Some gifs work, but no gifv so far. Not sure of the pattern. Example gifv from imgur.com: https://i.imgur.com/xFVwISe.gifv I've disabled all restrictions in the privacy and security settings. I've also started in safe-mode so no extensions. No reports of this issue on other operating systems or on https://bugzilla.mozilla.org No huge impact to me personally, but maybe something to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 86.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 16:40:12 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-03-03 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=86.0/20210222142601 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502LW.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502LW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502LW.309:bd09/01/2020:br5.17:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGZephyrusM15GU502LW_GU502LW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502LW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus M15 dmi.product.name: ROG Zephyrus M15 GU502LW_GU502LW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917816 Title: Firefox not loading gifv, gifs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912077] Re: xfce4 screensaver does not enable on Saver Timout
If I kill -15 the xfce4-screensaver process and restart it, the screensaver will work ok but when I close lid and open again during future session, screensaver will not work but is still running.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912077 Title: xfce4 screensaver does not enable on Saver Timout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1912077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947664] Re: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1)
Thanks much @~s-chriscollins! For me that setting in virtualbox was it. When I started reading this thread and see similar issues since 2012 I wasnt very optimistic... but 7 years later you provide a solution! I don't understand if it's a problem in virtualbox or problem with dkpg, but this is great. I was using hwe in ubuntu 18 based VM and every friggen time I use it there seems to be a kerel update, and waiting an hour each time was ridiculous, thank you so much for posting this, back to a a couple minutes for updates like it should be. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947664 Title: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1) To manage notifications about this bug go to: https://bugs.launchpad.net/dpkg/+bug/947664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912077] [NEW] xfce4 screensaver does not enable on Saver Timout
Public bug reported: xfce4-screensaver started not enabling after the 'Saver Timeout' would be past. At some point I removed light-locker as per one of comments in https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1875025 as I have having password unlock issues. To give some background - I did an upgrade from 16.04 to 18.xx and then to 20.04 LTS. Ever since then I believe xfce4-screensaver hasn't behaved properly. My laptop will be idle and it sometimes works (xfce4-screensaver sometimes enables and sometimes not). I still cannot find when it works and when it doesn't. I sometimes have to shutdown xfce4-screensaver and restart it. When I do this and to try and debug this I have been running: 'xfce4-screensaver --no-daemon --debug 2>&1| tee xfce4-screensaver.debug'. Attached is that file from the last couple of days. My xfce4-screensaver options are: SCREENSAVER tab: - Enables Screensaver: ON - Activate screensaver when computer is idle: ON - Regard the computer as idle: 2min - Inhibit screensaver for fullscreen applications: ON LOCK SCREEN tab: - Enable Lock Screen: OFF ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfce4-screensaver 0.1.10-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jan 16 15:06:25 2021 ExecutablePath: /usr/bin/xfce4-screensaver InstallationDate: Installed on 2017-04-07 (1380 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) SourcePackage: xfce4-screensaver UpgradeStatus: Upgraded to focal on 2020-08-10 (159 days ago) ** Affects: xfce4-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal xfce4-screensaver ** Attachment added: "xfce4-screensaver debug output" https://bugs.launchpad.net/bugs/1912077/+attachment/5453808/+files/xfce4-screensaver.debug ** Description changed: xfce4-screensaver started not enabling after the 'Saver Timeout' would be past. At some point I removed light-locker as per one of comments in https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1875025 as I have having password unlock issues. + + To give some background - I did an upgrade from 16.04 to 18.xx and then + to 20.04 LTS. Ever since then I believe xfce4-screensaver hasn't behaved properly. My laptop will be idle and it sometimes works (xfce4-screensaver sometimes enables and sometimes not). I still cannot find when it works and when it doesn't. I sometimes have to shutdown xfce4-screensaver and restart it. When I do this and to try and debug this I have been running: 'xfce4-screensaver --no-daemon --debug 2>&1| tee xfce4-screensaver.debug'. Attached is that file from the last couple of days. My xfce4-screensaver options are: SCREENSAVER tab: - Enables Screensaver: ON - Activate screensaver when computer is idle: ON - Regard the computer as idle: 2min - Inhibit screensaver for fullscreen applications: ON LOCK SCREEN tab: - Enable Lock Screen: OFF ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfce4-screensaver 0.1.10-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jan 16 15:06:25 2021 ExecutablePath: /usr/bin/xfce4-screensaver InstallationDate: Installed on 2017-04-07 (1380 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) SourcePackage: xfce4-screensaver UpgradeStatus: Upgraded to focal on 2020-08-10 (159 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912077 Title: xfce4 screensaver does not enable on Saver Timout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1912077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824023] Re: Kernel issue causes wifi interface failure
@dn I'm having same issues with ubuntu 20.04.1 LTS and getting same 'pcieport' errors. Have you upgraded from 18.04 to something newer since your comment back in 2019? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824023 Title: Kernel issue causes wifi interface failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1824023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906857] Re: XPS 9310 Developer Edition not booting when connected to WD19TB dock
*** This bug is a duplicate of bug 1902469 *** https://bugs.launchpad.net/bugs/1902469 Marking this as duplicate of https://bugs.launchpad.net/ubuntu/+source /linux-oem-5.6/+bug/1902469 as the fix seen there resolved the issue I was having. ** This bug has been marked a duplicate of bug 1902469 drm/i915/dp_mst - System would hang during the boot up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906857 Title: XPS 9310 Developer Edition not booting when connected to WD19TB dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1906857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906857] Re: XPS 9310 Developer Edition not booting when connected to WD19TB dock
Setting target to plymouth based on description here: https://wiki.ubuntu.com/Bugs/FindRightPackage#During_boot ** Tags added: dell ** Tags added: dock ** Package changed: ubuntu => plymouth (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906857 Title: XPS 9310 Developer Edition not booting when connected to WD19TB dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1906857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906857] [NEW] XPS 9310 Developer Edition not booting when connected to WD19TB dock
Public bug reported: With a XPS 9310 Developer Edition laptop (using pre-installed Ubuntu 20.04 from Dell with all updates, including LVFS updates for laptop and dock) is powered off and connected to the WD19TB docking station, it will not boot when I power it on. When I press the power button (on the laptop or dock) the screen on the laptop becomes active, shows a dell logo, but just stays stuck that way indefinitely. If I press and hold the power button for 10+ seconds the computer can be forcefully shut down. When I start it up again after forcing it down I then see the Dell logo, but the computer continues where the next screen I see is a GRUB boot menu. From there I can choose "Ubuntu" and the computer boots normally with no problems. Another way to make everything work is before booting the computer, unplug the Thunderbolt cable from the laptop. Then it boots up normally and I can connect the Thunderbolt cable again and things work normally from there. I am seeking a solution so I can leave the laptop connected to the docking station and have it boot up normally on the first attempt (no forced shutdowns or having disconnect/reconnect things). Some details: OS: Ubuntu 20.04 factory installed from Dell with all updates as of this date. Kernel: 5.6.0-1034-oem Laptop: XPS 9310 Developer Edition Dock: WD19TB ** Affects: ubuntu Importance: Undecided Status: New ** Tags: dell dock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906857 Title: XPS 9310 Developer Edition not booting when connected to WD19TB dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906158] Re: Mouse and Keyboard input stalling/pausing/freezing after there is no mouse or keyboard activity for a few seconds.
I'm out of my element here and don't know what I'm doing. I do know that the updates release today resolved the problem I was having so I'll make the changes that seem right to me. Hopefully it won't leave too big a mess for someone else to clean up. ** Changed in: ubuntu Status: New => Fix Released ** Changed in: ubuntu Assignee: (unassigned) => Craig Christie (curmudgeoncraig) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906158 Title: Mouse and Keyboard input stalling/pausing/freezing after there is no mouse or keyboard activity for a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906158] [NEW] Mouse and Keyboard input stalling/pausing/freezing after there is no mouse or keyboard activity for a few seconds.
Public bug reported: I'm having a problem in Ubuntu Hirsute Hippo (development branch) VERSION_ID="21.04" with the Pre-Release updates (hirsute-proposed) turned on. Since the updates that came out about 11/20/2020 that included some updates to compression stuff (I'm not saying those caused the problem), I have problems with the Mouse and Keyboard input stalling/pausing/freezing after there is no mouse or keyboard activity for a few seconds. Sometimes keystrokes will be lost, other times they are buffered and catch up. I've been putting in the available updates several times a day since the problem started, but nothing seems to help. I've also tried changing the video drivers back and forth between proprietary x.orXserver and Nvidia metapackage, but there's no change to the problem. Also if there's a video playing while the problem occurs the video is not affected, only the inputs. In researching fixes I thought there was a reference to turning off a feature that hides the mouse pointer when it's inactive, but I haven't been able to find that again. It does seem to coincide with the problem. NAME="Ubuntu" VERSION="21.04 (Hirsute Hippo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Hirsute Hippo (development branch)" VERSION_ID="21.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=hirsute UBUNTU_CODENAME=hirsute ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: I'm having a problem in Ubuntu Hirsute Hippo (development branch) VERSION_ID="21.04" with the Pre-Release updates (hirsute-proposed) - turned on. The regular bug reporting systems says it's only for the - regular release software, is there somewhere I can at least report the - problem. It's not causing a crash so I doubt there's any automatic - reporting going on. Just let me know where to go to report it. I'll - describe the problem here, but I realize that I'll probably need to do - it again in the proper location. + turned on. Since the updates that came out about 11/20/2020 that included some updates to compression stuff (I'm not saying those caused the problem), I have problems with the Mouse and Keyboard input stalling/pausing/freezing after there is no mouse or keyboard activity for a few seconds. Sometimes keystrokes will be lost, other times they are buffered and catch up. I've been putting in the available updates several times a day since the problem started, but nothing seems to help. I've also tried changing the video drivers back and forth between proprietary x.orXserver and Nvidia metapackage, but there's no change to the problem. Also if there's a video playing while the problem occurs the video is not affected, only the inputs. In researching fixes I thought there was a reference to turning off a feature that hides the mouse pointer when it's inactive, but I haven't been able to find that again. It does seem to coincide with the problem. NAME="Ubuntu" VERSION="21.04 (Hirsute Hippo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Hirsute Hippo (development branch)" VERSION_ID="21.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=hirsute UBUNTU_CODENAME=hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906158 Title: Mouse and Keyboard input stalling/pausing/freezing after there is no mouse or keyboard activity for a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
My apologies for sidetracking this far trying to explain differences between discovery and browsing but there seems to be a lot of mixing the 2 as one. The fact that you have "discovered" a server you wish to "browse" is irrelivant for this bug (afaik you shouldn't have been able to discover it as there are currently no working mechanisms to do so in LTS versions judging from the open bug reports). If however you are experiencing a crash whilst attempting to browse a share of the discovered host, that is relevant and is to do with the way SMB protocol versions themselves are being handled. WRT the rest of the discussion: SMBv1 leveraged NetBios to do discovery, (as did WINS which was a fallback discovery method). With SMBv1 removed/disabled, all of the NetBios discovery is also removed/disabled. Therefore, a discovery protocol is needed. Enter WSD. SMBv2 and SMBv3 use WSD to discover hosts on the network, (incidentally WSD was designed for SMBv2 during the development of Vista to remove the dependancy on NetBios). If you know the address of a host serving SMBv2 or SMBv3 already (via WSD, any other discovery protocol, off by heart), you can just do an SMB request against that address: smbclient --list=<> --user=Anonymous -N >The discoverability and connectivity works when the process is terminated and >restarted. Clearly this is achievable. > Yes, netbios was used previously, but clearly after killing the process I can > reach them without SMB v1, just not after the first boot. This is still probably nothing more than a cached entry, start-up check of previously known hosts, or initial broadcast. Some of which may or may not be unintentional from a security perspective, so as @seb128 said, file another bug report against them if you so wish. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
In the very same article you linked: https://docs.microsoft.com/en-us /windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by- default-in-windows With SMBv1 being removed, Network Browser (which depended on SMBv1) was removed, all of which relied on NetBios being used for discovery. (Hence, NetBios is dead, long live NetBios). Microsoft's replacement for NetBios discovery is *drumroll please*: WSD. I'm completely speculating here but: Your initial start up effect is probably gvfsd-smbd doing something like a Browser Tree scan of last known hosts. This actively goes to the host asking about available protocols, shares etc. This is NOT discovery. You could argue "well if it already knew about it, how does it lose it?" and that is a fair question, to which the answer might well be "Don't want to do an expensive back n forth poll, would rather use a discovery protocol", and now we are back to the discussion of needing a discovery protocol: WSD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Not to put too fine a point on it, but actually that is exactly what this requires. Microsoft phased out the SMBv1 protocol, (NetBios is dead, long live NetBios), in favour of their new protocol: Web Services Dynamic Discovery (WSD). There has been a lot of discussion and work as to exactly HOW WSD should be implemented for SAMBA and gvfs and what to do in future if Microsoft do another flip of the switch. Granted this has taken a lot of time, but as previously mentioned, all of this discussion and development is dependent on people gratuitously handing over their free time. If you want up to date support and to demand for things to be done, might I politely suggest you fork out for a Red Hat enterprise subscription. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903883] Re: XPS 13 9310 Tiger Lake Unable to boot 20.10 after intel-microcode update 3.20201110.0ubuntu0.20.10.1
I've installed a prior intel-microcode version (3.20191115.1ubuntu3) and can verify that all is back to normal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903883 Title: XPS 13 9310 Tiger Lake Unable to boot 20.10 after intel-microcode update 3.20201110.0ubuntu0.20.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1903883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903883] Re: XPS 13 9310 Tiger Lake Unable to boot 20.10 after intel-microcode update 3.20201110.0ubuntu0.20.10.1
I am having this same issue. Here's a photo (attached) of my screen when booting. Machine is exact same model as described in original bug report here. I am on kernel 5.6.0-1033-oem though, which was installed at the same time as intel-microcode:amd64 3.20201110.0ubuntu0.20.04.1. ** Attachment added: "1.jpg" https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1903883/+attachment/5433593/+files/1.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903883 Title: XPS 13 9310 Tiger Lake Unable to boot 20.10 after intel-microcode update 3.20201110.0ubuntu0.20.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1903883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902430] [NEW] package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Public bug reported: I just reinstalled Ubuntu 20.10 on RPi 4 (4GB) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: ca-certificates 20201027ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 AptOrdering: ca-certificates:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: skip Date: Sun Nov 1 07:18:27 2020 DuplicateSignature: package:ca-certificates:20201027ubuntu0.20.10.1 Setting up ca-certificates (20201027ubuntu0.20.10.1) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package ca-certificates (--configure): installed ca-certificates package post-installation script subprocess returned error exit status 1 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20201022 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: ca-certificates Title: package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902430 Title: package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1902430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896110] Re: Ubuntu Dock has no icons when logged in with USB storage plugged in
boot log with no USB storage attached ** Attachment removed: "boot log with no USB storage attached" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+attachment/5413033/+files/withno-bsb.log ** Attachment added: "boot log with no USB storage attached" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+attachment/5413035/+files/withno-usb.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Ubuntu Dock has no icons when logged in with USB storage plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896110] Re: Ubuntu Dock has no icons when logged in with USB storage plugged in
boot log with no USB storage attached ** Attachment added: "withno-bsb.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+attachment/5413033/+files/withno-bsb.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Ubuntu Dock has no icons when logged in with USB storage plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896110] Re: Ubuntu Dock has no icons when logged in with USB storage plugged in
Output of 'journalctl -b 0' attached both with USB storage attached on boot and without. ** Attachment added: "boot log with USB straoge attached" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+attachment/5413032/+files/with-usb.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Ubuntu Dock has no icons when logged in with USB storage plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896110] Re: Ubuntu Dock has no icons when logged in with USB storage plugged in
This is issues is reproducible. Update If I open a terminal screen (CTRL + ALT + T) and then go full screen (F11) for at least 5 seconds then go back to default size (F11) then the Ubuntu Dock is redrawn and is shown as expected. USB storage is 4 GB FAT formatted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Ubuntu Dock has no icons when logged in with USB storage plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896110] Re: Favorites side bar empty when login in with USB pluged in
Update - If I lock the screen and then unlock it - the Side bar comes back and works as normal. Screenshot attached ** Attachment added: "Screen shot of problem" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1896110/+attachment/5411879/+files/Broken.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Favorites side bar empty when login in with USB pluged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1896110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896110] [NEW] Favorites side bar empty when login in with USB pluged in
Public bug reported: If I connect a USB key to the computer then login the Favorites side bar is empty and the Application launcher does not work. The mouse and keyboard still work Removing the USB key does not resolve the issue Removing the USB key and then logging out and back in again resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 07:32:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140] NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 730] [1462:3380] InstallationDate: Installed on 2020-05-28 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 10TXCTO1WW ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: M22KT42A dmi.board.name: 3140 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258133898759 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM22KT42A:bd12/23/2019:svnLENOVO:pn10TXCTO1WW:pvrV530S-07ICB:rvnLENOVO:rn3140:rvrSDK0J40700WIN3258133898759:cvnLENOVO:ct3:cvrNone: dmi.product.family: V530S-07ICB dmi.product.name: 10TXCTO1WW dmi.product.sku: LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB dmi.product.version: V530S-07ICB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Favorites side bar empty when login in with USB pluged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1896110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893781] Re: xfce4-screensaver shows desktop and no login screen when waking from suspend
I have similar behaviour. When I close lid, it suspends normally. When I open the lid, I see a glimpse (0.5s to 1.0s duration) of my desktop but login screen shows up. But the only difference is I get the login screen show up. I assume the glimpse of the desktop is also a bug but I couldn't find it through the search. This bug could be related to 1875025: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1875025/comments/24 as I've turned off the 'Enable Lock Screen' on the screensaver preferences in the meantime until 1875025 is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893781 Title: xfce4-screensaver shows desktop and no login screen when waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1893781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892712] Re: Printing garbage to Brother HL-L2375DW printer
Bug #1832646 sounds similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892712 Title: Printing garbage to Brother HL-L2375DW printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892712] [NEW] Printing garbage to Brother HL-L2375DW printer
Public bug reported: Starting a few weeks ago, sometimes trying to print ends up printing pages and pages of garbage/junk/mojibake. It's not all the time. Printer drivers are somewhat mysterious, because if I delete them, they automatically reappear. Often a program will list two printer drivers for the one printer, and one of them prints okay while the other prints garbage, and it's not at all obvious which is which. This affects two Ubuntu PCs, one a desktop running Ubuntu 20.04.1, the other a laptop running Lubuntu 20.04.1. The printer is on the network. I guess the computers find it via Zeroconf. The problem seems to be Ubuntu, rather than the printer, because printing from a Windows PC works fine. And, for months, printing from Ubuntu also worked fine. I also noticed earlier, several months back, that double-sided printing was misbehaving, always flipping on the short edge rather than the long edge, no matter which was selected. Short edge is the setting I usually don't want -- the other side is effectively upside down. I have also noticed that selecting 2 or more copies doesn't print multiple copies, but just one copy. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: printer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892712 Title: Printing garbage to Brother HL-L2375DW printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875025] Re: Cannot enter password to unlock session
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875025 Title: Cannot enter password to unlock session To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-screensaver/+bug/1875025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875025] Re: Cannot enter password to unlock session
I upgraded from Xubuntu 16.04->18.04 and then 18.04->20.04.1 I get this same behavior when laptop lid is closed and re-opened for new session. I've temporarily disabled 'Enable Lock Screen' under the Screensaver Preferences screen as a work around for now. See attached snippet from my journal log (removing irrelevant entries).. I do not have xscreensaver installed but light-locker binary is present. ** Attachment added: "journal log output" https://bugs.launchpad.net/xfce4-screensaver/+bug/1875025/+attachment/5401218/+files/launchpad-1875025.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875025 Title: Cannot enter password to unlock session To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-screensaver/+bug/1875025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Seeing this in 20.04.1 with lightdm 1.30.0. see output attached. ** Attachment added: "output from journalctl using unit=lightdm" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1404172/+attachment/5400542/+files/lightdm.bug-1404172 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404172 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888385] Re: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic)
I experience the identical problem, but with TP-LINK TL-WN722N (Atheros) WiFi USB stick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888385 Title: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I will have to read up on this, and I am in a situation where I have to rely on this as my only computer for a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I already tried that, it V4.1.5 worked with both Ubuntu 18.04 and 20.04. I put in an earlier comment about this. On Wed, Jul 8, 2020 at 10:40 AM Kai-Heng Feng <1882...@bugs.launchpad.net> wrote: > Can you please test kernel v4.15, which is used by 18.04: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1882442 > > Title: > Upgrade from 18.04 to 20.04 deactivates internal monitor in display > manager > > Status in linux package in Ubuntu: > Incomplete > Status in linux package in Fedora: > Unknown > > Bug description: > output of lsb_release -rd: > Description: Ubuntu 20.04 LTS > Release: 20.04 > > I recently upgraded from 18.04 to 20.04 and was using MATE. When the > upgrade was run my external > HDMI monitor was plugged in, after the update, when I reboot, the > internal monitor shows the beginning of the boot process (I deactivated > 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor > and the internal monitor goes dark. I can also get the tty consoles on the > external monitor but not on the internal monitor. > > In MATE it was a real problem because the panel is apparently still on > the invisible part of the desktop; I used a tty to install gnome, then > I could get the display settings by right-clicking on the desktop, and > setting the monitors to mirror, so I can reach applications, etc. > > Computer is a Dell Inspiron 3275 AIO with touch screen and Intel > on-board video, I think. > I had no problems with Ubuntu 18.04 with MATE. > > The problem seems to be similar to this bug: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 > but sort of the reverse, in that the internal monitor is the problem. > > Thank you for your help. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-33-generic 5.4.0-33.37 > ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 > Uname: Linux 5.4.0-33-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC2: david 2012 F pulseaudio >/dev/snd/controlC1: david 2012 F pulseaudio >/dev/snd/controlC0: david 2012 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 7 11:43:37 2020 > HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 > InstallationDate: Installed on 2020-03-07 (91 days ago) > InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release > amd64 (20160719) > MachineType: Dell Inc. Inspiron 3275 AIO > ProcFB: 0 amdgpudrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic > root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro > RelatedPackageVersions: >linux-restricted-modules-5.4.0-33-generic N/A >linux-backports-modules-5.4.0-33-generic N/A >linux-firmware1.187 > SourcePackage: linux > UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) > dmi.bios.date: 03/15/2019 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.7.0 > dmi.board.name: 04NJ6P > dmi.board.vendor: Dell Inc. > dmi.board.version: A02 > dmi.chassis.type: 13 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: 00 > dmi.modalias: > dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: > dmi.product.family: Inspiron > dmi.product.name: Inspiron 3275 AIO > dmi.product.sku: 0855 > dmi.product.version: 1.7.0 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
Yes, it worked on 18.04. The problem came with the upgrade to 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
The above did not work. I edited grub to remove the amdgpu.dc=0 from the command line, ran update-grub and rebooted. Essentially the same behavior as before. I did notice some 'Tell Plymouth to write out...(something) in the boot messages, but otherwise very similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I got the files for the kernel and did this (many warnings, one error): (base) david:new-kernel$ sudo dpkg -i *.deb Selecting previously unselected package linux-headers-5.8.0-050800. (Reading database ... 454198 files and directories currently installed.) Preparing to unpack linux-headers-5.8.0-050800_5.8.0-050800.202007052030_all.deb ... Unpacking linux-headers-5.8.0-050800 (5.8.0-050800.202007052030) ... Preparing to unpack linux-headers-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ... Unpacking linux-headers-5.8.0-050800-generic (5.8.0-050800.202007052030) over (5.8.0-050800.202007052030) ... Preparing to unpack linux-image-unsigned-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ... Unpacking linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) over (5.8.0-050800.202007052030) ... Selecting previously unselected package linux-modules-5.8.0-050800-generic. Preparing to unpack linux-modules-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ... Unpacking linux-modules-5.8.0-050800-generic (5.8.0-050800.202007052030) ... Setting up linux-headers-5.8.0-050800 (5.8.0-050800.202007052030) ... Setting up linux-headers-5.8.0-050800-generic (5.8.0-050800.202007052030) ... Setting up linux-modules-5.8.0-050800-generic (5.8.0-050800.202007052030) ... Setting up linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) ... Processing triggers for linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.8.0-050800-generic modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory W: Possible missing firmware /lib/firmware/amdgpu/navi12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.8.0-050800-generic Found initrd image: /boot/initrd.img-5.8.0-050800-generic Found linux image: /boot/vmlinuz-5.4.0-40-generic Found initrd image: /boot/initrd.img-5.4.0-40-generic Found linux image: /boot/vmlinuz-5.4.0-39-generic Found initrd image: /boot/initrd.img-5.4.0-39-generic Found linux image: /boot/vmlinuz-4.15.0-101-generic Found initrd image: /boot/initrd.img-4.15.0-101-generic Adding boot menu entry for UEFI Firmware Settings done I will edit grub.cfg and try this. Just saving here before I do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I found a similar Fedora bug report, it is a kernel issue, and there is a workaround. See: https://bugzilla.redhat.com/show_bug.cgi?id=1594488 Need to add 'amdgpu.dc=0' to the kernel command line in grub.cfg: GRUB_CMDLINE_LINUX="amdgpu.dc=0" then run grub-update reboot after booting to a version 5 kernel, video on both monitors works, and a check of the proc cmdline shows: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro amdgpu.dc=0 ** Bug watch added: Red Hat Bugzilla #1594488 https://bugzilla.redhat.com/show_bug.cgi?id=1594488 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1594488 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/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829625] Re: Vagrant box startup timeout due to no serial port
This issue bit me yesterday. The fix provided in for the Vagrantfile in comment 5 worked. This is incredibly frustrating to realize, though I think the issue is more with the vagrant folks not having the serial port. Is there a way to coordinate to fix this? I'll also note that generic/ubuntu2004 doesn't seem to have this issue, so perhaps making the Vagrant images not require the serial port would be an approach? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829625 Title: Vagrant box startup timeout due to no serial port To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1829625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
PARTIAL FIX: downgrade the kernel. I can confirm that everything seems to return to normal if you use GRUB2 to select Linux 4.15.0-101-generic as the kernel. I edited /etc/default/grub to - give a boot menu with a reasonable timeout - use the last selected kernel as default ** Description changed: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 - I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external - HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. + I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external + HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not on the internal monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. - The problem seems to be similar to this bug: + The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: david 2012 F pulseaudio - /dev/snd/controlC1: david 2012 F pulseaudio - /dev/snd/controlC0: david 2012 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: david 2012 F pulseaudio + /dev/snd/controlC1: david 2012 F pulseaudio + /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: - linux-restricted-modules-5.4.0-33-generic N/A - linux-backports-modules-5.4.0-33-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-33-generic N/A + linux-backports-modules-5.4.0-33-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
This seems to be a kernel issue: when I switched back to kernel 4.15 in GRUB2, the problems seems to go away. Checking on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I left the machine on a while, and the internal monitor came on while I was gone for about an hour. ??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
If the external HDMI is plugged in at power-on, a login window will show up on the HDMI, and then I can choose gnome or gnome classic for the session, log in, then right-click on the desktop, set the displays to mirror, and get to the main panels or activities menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
If I shutdown and unplug the external HDMI monitor, then power on, the internal display only shows the initial UEFI message, the screen appears grey, then it goes dark. If I then plug in the HDMI (not changing the power state) I can get a tty with ctrl-alt-f1, login, and run startx. MATE then appears, but only the non-panel part of the display. Also the monitor arrangement is flipped, but I think that is a minor MATE problem I noticed in 18.04 after a cli startx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] [NEW] Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
Public bug reported: output of lsb_release -rd: Description:Ubuntu 20.04 LTS Release:20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I also went in the dconf editor and changed some settings for laptop lid behavior to 'nothing", since the display settings show the internal monitor as a laptop monitor. No effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878955] [NEW] resolved dhclient-enter-hook complains about an empty file
Public bug reported: When starting/using `dhclient`, it will often return an error such as: cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter- hooks.d/resolved" Because the $oldstate file can be empty, or different, it should use `cmp --quiet` This happens when "/run/systemd/resolved.conf.d/isc- dhcp-v*-$interface.conf" files do not exist, or when the content changes. This is very loosely related to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183 ** Affects: systemd (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/1878955 Title: resolved dhclient-enter-hook complains about an empty file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1878955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874953] [NEW] package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
Public bug reported: Issue occurred on upgrade from 19.10 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 21:33:08 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2011-06-18 (3233 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375 mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282 ** Affects: smartmontools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874953 Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1874953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec
One does not simply close a bug report about a Radeon driver because Christopher went out and got an Nvidia card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707695 Title: radeon :03:00.0: ring 0 stalled for more than 1msec To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1707695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec
One does not simply close a bug report about a Radeon driver because Christopher went out and got an Nvidia card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707695 Title: radeon :03:00.0: ring 0 stalled for more than 1msec To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1707695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
I'm having this problem -- printing duplex on short edge instead of long edg -- with a Brother HL-L2375DW. I'm running Ubuntu 19.10. It was working in Ubuntu 19.04. But, I thought it had also been printing correctly previously in 19.10, until it stopped working more recently. But I'm not 100% sure when it stopped working, since I don't print duplex very often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859327] [NEW] xfce4-screenshooter copy to clipboard doesn't work
Public bug reported: Prior to upgrading to eoan (from disco 19.04) xfce4-screenshooter worked perfectly. However when I use it now, it seems to fail to copy the image to the clipboard. You can reproduce this easily by doing this to take a full screen screenshot to the clipboard. xcfe4-screenshooter -f -c Now open GIMP and press SHIFT-CTRL-V to paste the clipboard into a new image. GIMP reports "There is no image data in the clipboard to paste". clipman also reports "The clipboard is empty". I usesd to be able to paste screenshots to - gimp - libreoffice writer - chrome but none of these work any more. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy xfce4-screenshooter xfce4-screenshooter: Installed: 1.9.6-1 Candidate: 1.9.6-1 Version table: *** 1.9.6-1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: xfce4-screenshooter (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/1859327 Title: xfce4-screenshooter copy to clipboard doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screenshooter/+bug/1859327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824168] Re: classic opengl application on 19.04 fail to find gl drivers
(Commenting here instead of a new issue since the symptoms/error messages seem close) In case it matters, the CMake snap (specifically the cmake-gui app) also reports the same error message on startup. It is also a classic snap, but in this case the app does appear to run successfully. Can't comment on whether performance is affected or if it might lead to artefacts in some cases. Seen on an Ubuntu 18.04 VM under Parallels on a macOS host. Also same error message appears on a CentOS 7 VM under Parallels on the same macOS host. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824168 Title: classic opengl application on 19.04 fail to find gl drivers To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1824168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04
For me, this bug just started happening when I did a software update yesterday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825544 Title: Switch User menu item gone after upgrade to Ubuntu 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830638] [NEW] Keyboard Autorepeat Broken For All Keys and All Applications
Public bug reported: Holding down any key fails to provide the configured X11 autorepeat behavior. Autorepeat completely fails, or starts after a long delay (longer than the configured delay), only repeats one or a couple characters, pauses, then repeats one or a couple more characters, then pauses, etc. This happens for all keys in all applications. If the psensor window state is 'Show' (including both Minimized state and not-Minimized state) Close'ing the psensor window, without quitting the psensor application (by clicking the window manager's 'x' icon in psensor's window frame) immediately restores expected autorepeat behavior. psensor 1.1.3 Linux 4.15.0-50-generic #54~16.04.1-Ubuntu SMP Wed May 8 15:55:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Affects: psensor (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/1830638 Title: Keyboard Autorepeat Broken For All Keys and All Applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1830638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
today I started to follow the steps here: https://wiki.ubuntu.com/DebuggingKernelSuspend I found this in the dmesg after replicating the problem with pm_trace [0.950964] Magic number: 0:66:1001 [0.950965] hash matches drivers/base/power/main.c:1012 Is there more going on here perhaps than a video driver? Not sure what else to do with this information. ** Attachment added: "dmesg_post_boot-Mac-removed.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+attachment/5263125/+files/dmesg_post_boot-Mac-removed.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
if by chance this is an Acer UEFI bug is there somewhere else I could report it? either in launchpad or upstream? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
tested the kernel from here today with the same result: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc4/ generic amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[ubuntu-us-mi] Ubuntu 19.04 Release Party
Hi all, It's that time of year again: time to celebrate a new release of Ubuntu! We'll be meeting at Penguicon 2019 this year on Friday, May 3rd at 7:30pm. http://loco.ubuntu.com/events/ubuntu-us-mi/3882-ubuntu-1904-release-party-at-penguicon/ Hope to see you there! -- -- Craig Maloney (cr...@decafbad.net) http://decafbad.net -- ubuntu-us-mi mailing list ubuntu-us-mi@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-mi
[Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
Reported here: https://bugs.freedesktop.org/show_bug.cgi?id=110117 ** Bug watch added: freedesktop.org Bugzilla #110117 https://bugs.freedesktop.org/show_bug.cgi?id=110117 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
ok produced this with the correct steps this time ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+attachment/5246717/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
here is the output of 'journalctl -b -1 -k' ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+attachment/5246309/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
today tried another new kernel with the same result, still the screen produces garbage after resuming from suspend. This was the kernel used: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.2/ should i report this upstream to bugzilla? should mention i also switched from Kubuntu 18.10 to Ubuntu 18.10.. uname -a 5.0.2-050002-generic #201903131832 SMP Wed Mar 13 22:35:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
I get this bug on Ubuntu 18.10 with the kernel upgraded to 5.0.2 from the ubuntu repository. My machine is an Acer Predator Helios 500 Ryzen. acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763648] Re: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04
I would just like to add I wish it worked too, for an older system with an older video card and crt monitor. The neavau driver is causing the mouse pointer to intermittently disappear when changing resolutions and a solution (for older ubuntu) was to switch to nvidia drivers. There may be a good reason why not to fix and provide it for Ubuntu 18, but no explanation provided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763648 Title: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1763648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
took the following steps:
Went to
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
Downloaded the master branch which was uploaded 5 days ago by Josh Boyer
Backup my current firmware: sudo cp -r /lib/firmware /lib/firmware-$(uname -r)
tar -xvzf linux-firmware-master.tar.gz
CD into the resulting directory
sudo make install
mkdir -p /lib/firmware
sudo cp -r * /lib/firmware
sudo find /lib/firmware \( -name 'WHENCE' -or -name 'LICENSE.*' -or
-name 'LICENCE.*' \) -exec rm -- {} \;
Rebooted and tried to suspend. Still have the same result as above.
Let me know if I did any of this incorrectly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813820
Title:
Waking from Suspend causes screen to appear with grey static (like a
TV with no signal)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
