*** This bug is a duplicate of bug 1899233 ***
https://bugs.launchpad.net/bugs/1899233
** This bug has been marked a duplicate of bug 1899233
post login - no apps launched - virtualbox-dkms
6.1.10-dfsg-1~ubuntu1.20.04.1: virtualbox kernel module failed to build
--
You received this bug n
Public bug reported:
When updating docker.io to 19.03.13-0ubuntu3.1, I get the following
errors:
Can't exec "/tmp/docker.io.config.iu4mIv": Permission denied at
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178.
open2: exec of /tmp/docker.io.config.iu4mIv configure 19.03.13-0ubuntu3 fail
I see that too but it is a BIOS issue - the keyboard sometimes is not
initialized properly. Please check if it works for you before grub when
that problem occurs.
This bug is also missing data, please run apport-collect 1910571 to
collect details.
** Changed in: grub2 (Ubuntu)
Status: New
** Package changed: ubuntu => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910455
Title:
Thunar and Nautilus USB drive ejecting takes long time
To manage notifications about thi
** Package changed: ubuntu => firefox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910587
Title:
Software Updater reports possible updates, but shows a blank window
afterwards. No updat
** Package changed: ubuntu => linux-signed-hwe-5.8 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910565
Title:
Ubuntu 20.04 Text Editor displays a black screen, unable to type.
To manage
This bug is due to a double-free in source3/librpc/crypto/gse.c where
gse_ctx->k5ctx is freed twice if gse_context_init fails and the err_out
path is taken.
The beginning of gse_context_init calls talloc_set_destructor to call
gse_context_destructor:
talloc_set_destructor((TALLOC_CTX *)gs
7.01.21 г. 22:11 ч. sudo lyubo : TTY=pts/1 ; PWD=/home/lyubo ;
USER=root ; COMMAND=/usr/bin/systemctl status fwupd-refresh.service
7.01.21 г. 22:13 ч. sudo lyubo : TTY=pts/1 ; PWD=/home/lyubo ;
USER=root ; COMMAND=/usr/bin/systemctl start fwupd-refresh.service
7.01.21 г. 22:13
The first time is with internet enabled, the second with internet
disabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909603
Title:
fwupd-refresh.service: Failed with result 'exit-code'
To man
@mbacarella (and everyone else) I would highly appreciate feedback about
the performance loss in some interesting cases. I plan running general
performance tests, but obviously they won't cover all real-life cases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
To fix the fallout: First, ensure you are running the latest kernel and
all your other packages are up-to-date; Then in "Software & Updates" >
"Additional Drivers" change to the Nouveau driver (which seemed to
uninstall all the Nvidia packages); Finally run `sudo -i ubuntu-drivers
autoinstall` whic
In order to fix this for Focal / 20.04.2 point release:
Groovy is a no-op, because:
1) it has no partman-crypto as stand-alone src pkg anymore.
2) its ubiquity (w/ bundled partman-crypto) doesn't need a
patch as there won't be new ISOs/Desktop install for it.
[thus, partman-crypto: Invalid / u
** Patch added: "lp1898129_focal_partman-crypto.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1898129/+attachment/5450385/+files/lp1898129_focal_partman-crypto.debdiff
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
B
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
Just chiming in to agree with David - please take this issue out of
"Won't Fix". I performed the same steps David says he took with the
same result - Virtualbox is broken through no fault of my own - just
applied a kernel update as I do every time one is found using Software
Updater.
Thanks!
--
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Description changed:
[impact]
a connection session is opened, but the TLS parameters (timeout, ca,
cert and key) are not actually set for the session. This prevents use
of TLS.
[test case]
- TBD
+ create self signed certs
+ -
+ openssl req -x509 -out localhost.crt -keyo
Can somebody with an affected system please try with one of the recently
released 460.xx drivers? There were some brightness regressions that
were resolved in the 460 series that may be related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: firefox (Ubuntu) => update-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910587
Title:
Software Updater reports possible updates, but shows a blank window
aft
** Attachment added: "dmesg1.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909680/+attachment/5450386/+files/dmesg1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909680
Tit
Same here.
tried this:
https://forum.chuwi.com/t/keyboard-not-working-in-linux/14453
and this:
https://askubuntu.com/questions/1269284/keyboard-not-working-after-update-18-04-20-04
No result :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I verified the test case using the package available in bionic-proposed
and I confirm it is working as expected. I set up a 3 nodes cluster on
AWS to test this.
Note: When installing fence-agents also install the Suggested
dependencies, otherwise the 'fence_aws' command will not work.
ubuntu@node
Same problem here. It also affects: 5.8.0-34-generic
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
$ uname -a
Linux vanhalen 5.8.0-34-generic #37~20.04.2-Ubuntu SMP Thu Dec 17 14:53:00 UTC
2020
** Changed in: oem-priority
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888498
Title:
oem-somerville-melisa-meta depends on tlp from universe, without MIR
To mana
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515
Title:
Chainbooting from grub over the network to local shim breaks chain of
trust
I experienced this as well.
Had to revert to previous kernel (5.4.0-59) to get nvidia-grpahics-
drivers-390 installed on my system.
The nouveau drivers were not a viable option, computer kept freezing,
forcing hard resets.
--
You received this bug notification because you are a member of Ubuntu
Forgot to mention, the kernel that had a the problem with nvidia driver
was a 5.8 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910449
Title:
package nvidia-dkms-390 390.138-0ubuntu0.20.04.1
Same for me, no changes.
Thkx for the feedback :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909814
Title:
Keyboard not working
To manage notifications about this bug go to:
https://bugs.launch
Uploaded partman-crypto to focal.
After it makes it to focal-proposed,
updated ubiquity upload will follow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898129
Title:
Cannot configure 'cryptsetup
Public bug reported:
Impossible d'évaluer la mise à niveau
Un problème insoluble est survenu lors du calcul de la mise à niveau.
Si rien de tout cela ne s'applique, signalez ce bogue à l'aide de la
commande « ubuntu-bug ubuntu-release-upgrader-core » dans un terminal.
Si vous souhaitez analyser
This is the error message i got.
It's in french because my installation is in french, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910593
Title:
Unable to upgrade from 18.04 to 20.04
To ma
Public bug reported:
I was installing ubuntu in dual boot with windows and it crashes during
the final part of the installation process. I have a Acer Nitro 5
AN-515-44-RTF with an Nvidia GeForce 1600. I tried the installation in
safe graphics mode, because it didn't let me in the normal mode.
Pr
After a system upgrade last night, the patched version 5.4.0-59 that
works was replaced by an older version of 5.4.0-59 dated Dec 10. So
anyone that installed the patched version will likely find their remote
not working again if they do a system upgrade.
--
You received this bug notification bec
Thanks for the update.
Config files are attached. You will note that the only override we we
for TCP clients is the amount that are allowed to connect as the default
is very low for an ISP DNS server.
However we are relying on the default tcp-timeout values. I will note
that since we removed the
It affects me after yesterday upgrade to 5.8.
Is the release for kernel 5.8 excepted?
uname -r
5.8.0-34-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872950
Title:
Nvidia 340.108 fails t
It affects me after yesterday upgrade to 5.8.
Is the release for kernel 5.8 excepted?
uname -r
5.8.0-34-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872950
Title:
Nvidia 340.108 fails t
** Package changed: ubuntu => kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910566
Title:
Problem with the CH341 driver in Ubuntu 20.04
To manage notifications about this bug go to:
https:/
** Attachment added: "dmesg of freeze without HDDs connected.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909680/+attachment/5450403/+files/dmesg%20of%20freeze%20without%20HDDs%20connected.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Bug watch added: Debian Bug tracker #954600
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954600
** Also affects: graphite-api (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954600
Importance: Unknown
Status: Unknown
--
You received this bug notification be
Used Software&Updates App -> Additional Drivers -> Using NVIDIA binary
driver - version 340.108 from nvidia-340 (proprietary, tested), Apply
Changes.
Error message:
pk-client-error-quark: Error while installing package: installed nvidia-340
package post-installation script subprocess returned err
Public bug reported:
Hello
I cant't installthe nvidia driver 418
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-418-server 418.152.00-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.1
Public bug reported:
I used the "eject" contextual menu on the icon of a blank Bluray-R on
the caja desktop, and I got a message saying that I need to wait for
data to be written on the disc before being able to remove it safely
(same message as when trying to eject an usb stick, when some data
sy
I'm experiencing this on 20.04 after running "dist-upgrade" as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899233
Title:
post login - no apps launched - virtualbox-dkms
6.1.10-dfsg-1~ubun
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: invesalius (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909645
Title:
Crash on startup same kernel, but with 20.04 lts. I had to reverse to
linux kernel 5.4 to boot into system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901024
Title:
Crash on startup using linux 5
Public bug reported:
attempted to install using something else and creating custom partitions for
everything. i'm guessing that by choosing not to create EFI partition but one
for all other cases, even booting and installing through CSM, that that is why
it caused this error? was thrown warning
This bug was fixed in the package tzdata - 2020f-1ubuntu1
---
tzdata (2020f-1ubuntu1) hirsute; urgency=medium
* Merge from Debian unstable (LP: #1909698). Remaining changes:
- Ship ICU timezone data files which are utilized by php and keep them
at 2020d as they have not ye
*** This bug is a duplicate of bug 1899195 ***
https://bugs.launchpad.net/bugs/1899195
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1899195
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage
This bug was fixed in the package u-boot - 2020.10+dfsg-1ubuntu6
---
u-boot (2020.10+dfsg-1ubuntu6) hirsute; urgency=medium
* Add d/p/rpi-8gb-pci.patch for Pi400 and Pi4-8Gb support (LP: #1906552)
* Add d/p/rpi-cm4-sdhci.patch for CM4 eMMC support
* Add d/p/rpi-maxargs.patch for
This bug was fixed in the package lshw - 02.18.85-0.5ubuntu2
---
lshw (02.18.85-0.5ubuntu2) hirsute; urgency=medium
* Add cherry-picked patches for NMVe support (LP: #1826737):
- d/p/lp1826737-code-clean-up.patch
- d/p/lp1826737-implement-NVMe-scanning.patch
- d/p/lp1826
Using "exit 1" to to chainboot breaks if there is no UEFI boot entry.
MAAS currently has two known bugs where this is the case. There may be
more, we need to test all operating systems MAAS supports.
LP:1906379 - Ubuntu is removing the UEFI boot entry during shutdown for CentOS.
LP:1910600 - MAAS
Still a bug in 20.04, evident when installing Linux Mint 20.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997737
Title:
Detroit is not in Canada, 12.04
To manage notifications about this bug go to
** Changed in: apt (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: apt (Ubuntu Focal)
Status: Triaged => Fix Committed
** Changed in: apt (Ubuntu Groovy)
Status: Triaged => Fix Released
** Changed in: apt (Ubuntu Focal)
Status: Fix Committed => Fix R
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu27.12, the problem page at
https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4
contains mor
Here's the Traceback:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 458, in
options = parse_arguments()
File "/usr/share/apport/apport", line 404, in parse_arguments
parser.print_usage()
File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
This is a variation of LP: #1899195 however in this case the executable
path has a space in the name e.g.
/usr/lib/plexmediaserver/Plex Media Server
which ends up being split into multiple arguments:
['/usr/share/apport/apport', '1700', '11', '0', '1', '1700',
'!usr!lib!plexmediaserver!Plex', 'M
** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #398
https://gitlab.gnome.org/GNOME/gedit/-/issues/398
** Also affects: gedit via
https://gitlab.gnome.org/GNOME/gedit/-/issues/398
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
Uname: Linux 5.4.0-59-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.14
AptOrdering:
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-34-generic (not installed)
ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
Uname: Linux 5.4.0-59-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd
Upstreamed fix:
https://salsa.debian.org/debian/genext2fs/-/merge_requests/2
Not landing it in Ubuntu because it fails for other reasons anyway in
Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I have the same issue and was not able fix this by using the repo
version of virtualbox on Ubuntu 20.04.
I found this guide on how to install the latest version of Virtualbox:
https://linuxize.com/post/how-to-install-virtualbox-on-ubuntu-20-04/
I tried it and it worked for me, now I have Virtual
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910604
Title:
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_m
All autopkgtests for the newly accepted openvswitch (2.9.7-0ubuntu0.18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
mininet/2.2.2-2ubuntu1 (i386)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted openvswitch (2.9.7-0ubuntu0.18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
mininet/2.2.2-2ubuntu1 (i386)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted openvswitch (2.9.7-0ubuntu0.18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
mininet/2.2.2-2ubuntu1 (i386)
Please visit the excuses page listed below and investigate the failures,
To add to that, it looks like the way to implement that is
`NotShowIn=LXQt` in lubuntu-default-settings but we've got
https://github.com/lxqt/lxqt/issues/1743 keeping that from working.
** Bug watch added: github.com/lxqt/lxqt/issues #1743
https://github.com/lxqt/lxqt/issues/1743
--
You recei
This bug was fixed in the package tzdata - 2020f-0ubuntu0.20.10
---
tzdata (2020f-0ubuntu0.20.10) groovy; urgency=medium
* New upstream version (LP: #1909698), affecting the following timestamp:
- Volgograd switches to Moscow time on 2020-12-27 at 02:00.
* ICU timezone data fi
The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
after some more commentary from the customer, I'm still not convinced
that this isn't related to the hardware itself, HOWEVER, while doing a
bit more deubgging I noticed that the boot_mode_test.py script opens
files but does not properly close them (expecting python to close them
on exit?)
So whil
** Merge proposal linked:
https://code.launchpad.net/~bladernr/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/395963
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896119
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sssd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647285
Title:
SSL t
While it won't address your UX annoyances, I have filed an issue
upstream proposing an approach to make live search faster for big files:
https://gitlab.gnome.org/GNOME/gedit/-/issues/398
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For context, the update from the customer was that
cat /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-
00e098032b8c
actually works fine UNTIL he runs the cert suite, after which point it
hangs.
So I wonder if not properly closing the file leaves this in a bad state
somehow once the
The patch works. Can it please be applied to the emacs-lisp package ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877185
Title:
maxima-emacs returns LaTeX error
To manage notifications about thi
Hello Michael, or anyone else affected,
Accepted openvswitch into queens-proposed. The package will build now
and be available in the Ubuntu Cloud Archive in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello James, or anyone else affected,
Accepted openvswitch into queens-proposed. The package will build now
and be available in the Ubuntu Cloud Archive in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo ad
This bug was fixed in the package tzdata - 2020f-0ubuntu0.20.04
---
tzdata (2020f-0ubuntu0.20.04) focal; urgency=medium
* New upstream version (LP: #1909698), affecting the following timestamp:
- Volgograd switches to Moscow time on 2020-12-27 at 02:00.
* ICU timezone data fil
Tried to read all.. but I think I have different info.
I originally got the 100%CPU on kube and ended up disabling and not starting
any of that, but the 100% CPU started on another process.. just one, so removed
and rebooted.. and again it's not on gnome-shell.. however found the cpulimit
and se
Public bug reported:
Exactly the same as reported in
#54630
The fresh Ubuntu install I did a few weeks ago now has this exact same issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vlc 3.0.9.2-1
ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
Uname: Linux 5.8.0
as far as I can see in the bluez package source, the midi option is
enabled now, so it *could* be closed...
But even though it's on, I dont get it working, so I cannot confirm for
sure.
Expectation is: when connecting to a device, I get an alsa sequencer
client, but I dont see that happening.
Bu
Public bug reported:
What Happened:
1) Have gnome-shell-extensions-appindicator enabled
2) The only running app using the indicator was charmtimetracker (
https://github.com/KDAB/Charm )
3) At some point usually within 1-2 days of office usage gnome shell crashes
4) Notice "JS ERROR: too much rec
Public bug reported:
Ubuntu 20.04.1 LTS
bcmwl-kernel-source_6.30.223.271
I believe the important part of the
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log is below.
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function
‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl
Hello Richard, it looks like the profile may not have kept up with
changes in the packaging.
The profile has probably been broken ever since:
sssd (2.2.0-1) unstable; urgency=medium
* New upstream release.
* control: Bump policy to 4.4.0.
* control, compat, rules: Bump debhelper to 12.
*
This bug was fixed in the package tzdata - 2020f-0ubuntu0.18.04
---
tzdata (2020f-0ubuntu0.18.04) bionic; urgency=medium
* New upstream version (LP: #1909698), affecting the following timestamp:
- Volgograd switches to Moscow time on 2020-12-27 at 02:00.
-- Brian Murray Wed,
This bug was fixed in the package tzdata - 2020f-0ubuntu0.18.04
---
tzdata (2020f-0ubuntu0.18.04) bionic; urgency=medium
* New upstream version (LP: #1909698), affecting the following timestamp:
- Volgograd switches to Moscow time on 2020-12-27 at 02:00.
-- Brian Murray Wed,
Thanks for the bug report.
Please run:
lspci -kv > lspci.txt
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting files here.
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member o
*** This bug is a duplicate of bug 1910559 ***
https://bugs.launchpad.net/bugs/1910559
** This bug has been marked a duplicate of bug 1910559
GDM3: Black screen with blinking cursor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Not me. I'm using Ubuntu 20.04. Until it's made available by the
software update mechanisms I won't touch it.
But "brightness regressions"? We're talking about basic control. How
does passing regression tests helps this issue? Or did people ignore
regression tests before releasing the 450 series?
*** This bug is a duplicate of bug 1907557 ***
https://bugs.launchpad.net/bugs/1907557
Public bug reported:
Woke up to this bug, didn't know what happened but would like to report
it..
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
P
The closed status is implicit. There are a few different Status values
that Launchpad treats as "closed" so I will set one...
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
After the system comes back to life please immediately run:
journalctl -b0 > journal.txt
and attach the file here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909732
Title:
unable to login to
This bug was fixed in the package tzdata - 2020f-0ubuntu0.16.04
---
tzdata (2020f-0ubuntu0.16.04) xenial; urgency=medium
* New upstream version (LP: #1909698), affecting the following timestamp:
- Volgograd switches to Moscow time on 2020-12-27 at 02:00.
-- Brian Murray Wed,
This bug was fixed in the package tzdata - 2020f-0ubuntu0.16.04
---
tzdata (2020f-0ubuntu0.16.04) xenial; urgency=medium
* New upstream version (LP: #1909698), affecting the following timestamp:
- Volgograd switches to Moscow time on 2020-12-27 at 02:00.
-- Brian Murray Wed,
Public bug reported:
System error
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-418-server 418.152.00-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architec
*** This bug is a duplicate of bug 1870736 ***
https://bugs.launchpad.net/bugs/1870736
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1870736, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1870736 ***
https://bugs.launchpad.net/bugs/1870736
** This bug is no longer a duplicate of bug 1910539
[nvidia] Cannot set scale of screen
** This bug has been marked a duplicate of bug 1870736
[nvidia] Screen scaling 125% gives 200%
--
You received
*** This bug is a duplicate of bug 1907557 ***
https://bugs.launchpad.net/bugs/1907557
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1907557, so is being marked as such.
> Their guess is that the linux notebook is not setting EDID
> configuration correctly and thus not recognized by the ATEM,
> while the cheap LCD screen propably does not care about EDID
> and just plays everything, therefore a wrong EDID information
> would not matter.
EDIDs work the other way ro
401 - 500 of 566 matches
Mail list logo
