I already have the workaround in bug 994921 and have for a long time. My
system has generated and reported crashes as recently as February 28.
There's no crash for this in /var/crash.
There's no crash for this on errors.ubuntu.com.
For some reason, when this crash occurs it's not generating a cr
Public bug reported:
gnome-shell has crashed twice on me today.
Unfortunately there's nothing in /var/crash.
There's nothing in the journalctl log prior to the crash that explains
it.
I've attached a log of everything between when the crash happened and
when I logged back in (though I suspect m
Public bug reported:
With all current focal updates from proposed, the sound indicator in my
top bar has disappeared.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: indicator-sound 12.10.2+18.10.20180612-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
Uname: Linux 5.4.0-17
** Attachment added: "What I see after boot is finished"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865911/+attachment/5333110/+files/boot_finished.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
(I honestly don't know what the right package to file this against is so
I'm starting with "linux" and hoping that people can help it get to the
right place if that's not it.)
I have the proposed repository enabled and all current packages from
proposed installed.
The screen
** Attachment added: "Boot screen after I hit ESC"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865911/+attachment/5333109/+files/boot_screen_2.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
There is still something wrong here.
The site in question has fixed the issue in response to my query, and
SSL Labs now gives it an A grade:
https://www.ssllabs.com/ssltest/analyze.html?d=www.toodledo.com
According to SSL Labs, it supports these two ciphers for TLS 1.2:
TLS_ECDHE_RSA_WITH_AES_2
Fair enough, I will contact the web site maintainer. However, regarding
this:
>You can override this via command-line, a system config file, or a local
>config file + environment variable pointing to it.
>
>On Ubuntu 20.04 LTS:
>
>man SSL_CTX_get_security_level.3ssl
1) I searched high, low, and
Aha! `curl -v --ciphers 'DEFAULT:@SECLEVEL=1' https://www.toodledo.com/`
works but `curl -v --ciphers 'DEFAULT:@SECLEVEL=2'
https://www.toodledo.com/` fails.
According to
https://www.openssl.org/docs/man1.1.0/man3/SSL_CTX_get_security_level.html,
the default security level for the library is 1 if
I may be misunderstanding something, but as far as I can tell this is
not a cipher mismatch problem.
According to
https://www.ssllabs.com/ssltest/analyze.html?d=www.toodledo.com, the
site supports TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. According to
"openssl ciphers", openssl supports ECDHE-RSA-AES
Public bug reported:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'i
Example output:
jik@jik-x1:~$ curl -v https://www.toodledo.com/
* Trying 146.20.52.175:443...
* TCP_NODELAY set
* Connected to www.toodledo.com (146.20.52.175) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/
It was a private email exchange between me and the DisplayLink folks.
Basically, I emailed them and told them them their package wasn't
working on 20.04 and asked them to fix it and they emailed back and said
they're working on it.
--
You received this bug notification because you are a member of
I added `options snd-hda-intel dmic_detect=0` to modprobe, and now
_output_, i.e., my speakers, work, but still no input device is being
detected, or at least the sound control panel isn't showing any
available input devices.
I see this in dmesg:
[ 11.075563] input: HDA Intel PCH Mic as
/device
You say that the library and kernel module in Ubuntu are older than the
ones from DisplayLink.com. Can you explain why the current versions of
the module and library aren't being shipped in Focal?
I'm afraid I can't test any further in 19.10 since I've already upgraded
both of my laptops to 20.04.
FYI, just to confirm that this isn't something specific to my Focal
install, I tested it with a Focal Live CD (thumb drive) and reproduced
the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18619
Public bug reported:
My ThinkPad X1 Carbon 7th Gen running 20.04 hangs every time I put it to
sleep. It doesn't finish going to sleep, i.e., the LEDs stay on, and all
I can do is hard power-cycle it by holding down the power button.
/var/log/syslog extract showing that after "PM: suspend entry (d
My ThinkPad firmware is up-to-date, and the BIOS is set to Linux mode,
though just for kick I tested with Windows sleep mode and that didn't
help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861938
OK, so additional data...
19.10 also doesn't hang when I use the kernel module and library that
ship with Ubuntu, so apparently the problem which prompted me to report
this bug is limited to when using the kernel module and library that are
installed by the installer on DisplayLink.com.
I'm not s
Public bug reported:
`apt-get update` and the nightly `apticron --cron` job are reporting:
"The AppStream system cache was updated, but some components were
ignored. Refer to the verbose log for more information."
This is pretty much meaningless to most people who have no idea what
AppStream is
So, um, this has been broken since Bionic and still not fixed, despite
the fact that ubuntu-bug is the only supported way for reporting bugs?
This seems highly sub-optimal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Is this going to get done for Focal? It would be a shame to ship an LTS
release without remote desktop support for Wayland. Aren't we at the
point now where Wayland is supposed to people's first choice?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Sorry, I meant 19.10 in my last comment, not 19.04.
When I use the evdi module and library shipped with Ubuntu in 20.04,
then DisplayLink works in Xorg, but it's very glitchy, with cursor
artifacts showing up constantly all over the place on all screens, both
DisplayLink and non-DisplayLink.
--
Learning more about this as I go:
* I'm no longer convinced that I was correct above when I claimed that
the version of the evdi kernel module and library shipped with Ubuntu
are newer than the version shipped with the installer available on
displaylink.com. I might be wrong about that.
* When I
With Ubuntu 19.10:
I am not able to reproduce the issue with a single monitor of a
different brand plugged into the DisplayLink adapter. There are three
differences here and I don't have the equipment available where I am
right now to narrow down which of them is relevant:
* one monitor instead o
Are you REALLY going to ship your next LTS release without screen
sharing in Wayland, when the code for supporting it is 100% implemented
and the security team appears to have approved it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: mutter (Ubuntu Eoan)
Status: Fix Committed => Confirmed
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1023
https://gitlab.gnome.org/GNOME/mutter/issues/1023
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/1023
Importance: Unknown
Sorry, I'm usually remote from the office where I have the displaylink
adapter which has this problem, so I was not able to test until I got to
the office instead.
I installed all updates in eoan-proposed and rebooted and then tried
logging into a Wayland session and using the displaylink adapter,
I can no longer reproduce it either. *shrug*
P.S. Hi Ted long time no see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860676
Title:
apt-get dist-upgrade -y hangs during e2fsprogs update
To man
e2scrub_all.timer restarts just fine; it's the e2scrub_reap.service
restart that's hanging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860676
Title:
apt-get dist-upgrade -y hangs during e2fsprog
Public bug reported:
My recent apt-get dist-upgrade -y hung here:
...
update-initramfs: deferring update (trigger activated)
e2scrub_all.service is a disabled or a static unit not running, not starting it.
I did a pstree on the apt-get process and saw this:
apt-get(31290)───dpkg(562)───e2fsprog
This is a huge functional regression. I can't believe it isn't already
fixed. Now it appears maybe it isn't even going to be fixed in 20.04.
wtf?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802614
Is this going to be fixed in Eoan?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853357
Title:
display (whole computer?) hangs when I attempt to use DisplayLink with
Wayland
To manage notificati
Public bug reported:
NOTE: I am reporting an issue with attempting to install Ubuntu 19.10
inside a Virtualbox VM. I ran ubuntu-bug to report this bug on the
_host_, but the issue is inside the VM, where I obviously can't run
ubuntu-bug because I can't get the installer to run. The information
aut
OK,so I just discovered that if I open gnome-shell-extension-prefs,
there's a switch in the upper right corner of the window, which
apparently disables all shell extensions, and I had that switched turned
off, though I have no idea how or when I did that. Turned it on and now
I can install extensio
Public bug reported:
I am using the DisplayLink driver for Ubuntu provided at
https://www.displaylink.com/downloads/ubuntu, which I think is the only
way to get DisplayLink fully working under Ubuntu? That is, DisplayLink
didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages,
and
It was just a few seconds before I captured the log, max 30 seconds,
probably less than half that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844808
Title:
in 19.10 can't delete file from deskto
Just reproduced it. `journalctl -b 0` output attached.
** Attachment added: "journalctl.zip"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1844808/+attachment/5306335/+files/journalctl.zip
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1894
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1894
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1894
Importance: Unknown
Status: Unknown
--
You received this bug notifica
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #920
https://gitlab.gnome.org/GNOME/mutter/issues/920
** Project changed: gnome-shell => mutter
** Changed in: mutter
Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1888 =>
gitlab.gnome.org/GNOME/mutter/issues #920
--
You r
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1888
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1888
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1888
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell (Ubuntu
No difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851554
Title:
can't install gnome shell extensions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
I take it back, it just happened again. Apparently it's intermittent.
I can't determine for certain whether it happens under X, because (a) as
I just noted, it's intermittent, and (b) my monitor has an entirely
different issue under X, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/18494
Yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851554
Title:
can't install gnome shell extensions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-
I am no longer able to reproduce this issue so I'm going to close it.
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851568
Title:
>Does it work with a new user on the same system?
Yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851554
Title:
can't install gnome shell extensions
To manage notifications about this bug go t
>What webbrowser do you use?
Chrome
>Did you try to install from gnome-software instead?
It doesn't work in gnome-software either. Additional behaviors observed
in gnome-software:
1) When I try to _uninstall_ the extension from inside gnome-software,
it says it can't uninstall it, but it actual
Public bug reported:
I have an ultrawide monitor plugged into my laptop. When I log into a
Wayland session, my monitor configuration (resolution, relative
position, which monitor is the primary) is not restored correctly. When
I unplug the monitor cable after logging in and plug it in again, the
c
The extension won't turn on in Wayland either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851554
Title:
can't install gnome shell extensions
To manage notifications about this bug go to:
https:
Public bug reported:
Here's what I'm trying to do:
1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/
2. Click the toggle switch to install it.
3. Use the extension after it is installed.
Here's what should happen:
1. I am prompted for confirmation to install the exten
I ordered a brand new, "premium" Roswell HDMI cable from Newegg and the
problem occurs with that cable as well.
Now that the problem has occurred with three different cables, two of
them new, with no adapters in the middle, I hope we can agree that it is
unlikely that this is a cable issue.
--
Y
I am somewhat surprised that you think the most likely explanation is a
cable issue. The likelihood of a bad cable being the issue when the
problem occurs with two different cables and is triggered by specific
apps seems, to me, vanishingly low.
Can you elaborate on why you consider that the most
[72227.300557] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR*
Unexpected DP dual mode adaptor ID 50
[72228.173908] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR*
Unexpected DP dual mode adaptor ID 50
[72229.956316] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR*
Unexpected
"gsettings set org.gnome.desktop.wm.preferences focus-new-windows
'strict'" doesn't seem to solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844809
Title:
clicking desktop notificat
"If you see changes like that after boot then please attach output from
'dmesg' showing the period of time when the change occurred."
I'm sorry, I'm not sure what you're asking me to watch for here. Can you
clarify?
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300916/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Ti
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300917/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
[X
FYI: While apport-collect was running, my screens went blank briefly and
then when they came back my monitor configuration was wrong: the ultra-
wide monitor was at a lower resolution than it's supposed to be and the
two monitors' relative positions were not configured correctly.
Unplugging the ult
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300918/+files/xdpyinfo.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notif
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300915/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300904/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300902/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
[X1
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300913/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300898/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
[X1 Ca
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300900/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300910/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Titl
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300903/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
[X1
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300912/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
[X
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300908/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300914/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300905/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300907/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300911/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
[X
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300901/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300909/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300906/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300899/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Tags added: apport-collected ubuntu
** Description changed:
I have an LG ultra-wide (2560x1080) monitor.
Sometimes when I plug it into my laptop, whose screen was working fine
before I plugged it in, both screens go black but nothing else happens.
I can still see
@kneutron were you in the state described above, i.e., had you updated
your 19.04 kernel but not rebooted after doing so before doing the 19.10
upgrade?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Can you clarify: are you saying that installing that oem-dmic-sof-
lp1825294 package is going to be the permanent solution to this problem,
or that you're asking us to test if that package solves the problem
before the change is incorporated into the official Ubuntu kernel?
--
You received this b
I tried a different cable. It didn't help.
Also, I can trigger my monitors freaking out as described above merely
by launching the Synology Drive Client when the ultra-wide monitor is
connected.
Also, the issue seems to be triggered even if the applet isn't visible
in my top bar, i.e., even if th
It's not clear to me how this can be a cable or monitor issue when it
only happens in Xorg and it happens much more frequently when one
particular app is running (see comment #4). Having said that, I will try
to find a spare HDMI cable and test.
I am not using an adapter, I'm plugging an HDMI cabl
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849656/+attachment/5300016/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849656
Tit
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849656/+attachment/5300014/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849656
T
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849656/+attachment/5300015/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849656
Title
>Please also try uninstalling (don't just turn them off) these
extensions...
If I see it happen again I will do that, because then it would be a
meaningful test, but so far I've only seen this happen once, so unless
it happens again so we can get some idea of how frequent it is, the
inconvenience
Public bug reported:
When I am using an ultra-wide monitor and I open a PostScript document
with gv, the document is vertically squished.
When I click on the zoom size at the top and change from "Natural Size"
(which, oddly, displays in the menu as "Natural[NL]Size", where "[NL]"
is a little N on
OK, this is really weird, but it appears that this problem only happens
(or, at the very least, happens much more frequently) when Synology
Drive Client is running, or more accurately, when the Synology Drive
Client applet is in my top bar.
Furthermore, sometimes (but not always) when I plug in my
The problem does not appear to happen under Wayland.
I am attaching a zip file containing four sets of the output of the
commands you requested spanning the time from before I plugged in the
HDMI cable to afterward, waiting long enough to confirm that I was
getting black screens rather than the co
Public bug reported:
I sat down at my computer this morning and unlocked the screen and saw
the behavior shown in the attached video. I waited a while and it never
stopped. I hit Alt-L to lock the screen again which worked, and then
unlocked it again, which worked.
ProblemType: Bug
DistroRelease:
Public bug reported:
The version of pip shipped in Ubuntu is 18.1.
Version 19.0 of pip was released on January 22, 9 months ago.
There are significant fixes in pip 19.
I'm not sure why pip wasn't upgraded for 19.10 as a matter of course
before it was released, but in any case, please upgrade it
So the failure mode I ran into was running the upgrade to 19.10 after
upgrading all disco packages but before rebooting.
In that case it seems like the upgrader needs to refuse to run if the
system needs to be restarted?
--
You received this bug notification because you are a member of Ubuntu
Bu
I was fully updated in disco before I upgraded to 19.10.
I think the problem is that it's not good enough for the tip disco
kernel to be updated. One old kernel version is saved even after
autoremove, and if the user doesn't run autoremove then I think any
number of old kernels could be saved, and
Wow, Gianfranco.
As someone who works on Debian / Ubuntu would it not be preferable for
you to make at least a modicum of effort to route an issue like this to
the appropriate people rather than merely repeatedly trying to close the
bug report?
In the short time since 19.10 was officially release
Public bug reported:
I have an LG ultra-wide (2560x1080) monitor.
Sometimes when I plug it into my laptop, whose screen was working fine
before I plugged it in, both screens go black but nothing else happens.
I can still see the mouse cursor and move it between the two monitors
(sometimes in the
Public bug reported:
I was prompted today while logged in to upgrade from 19.04 to 19.10.
I said yes and about halfway through the installation of packages my
login crashed.
I tried logging in a couple more times and sometimes got the "something
went wrong" screen of death and sometimes, remarka
The thing is, no matter how wide I resize the window, when I exit from
Tweaks and restart it, it goes back to the original size, with the left
tab bar invisible. This is not ideal.
Furthermore, frequently the title bar controls (X _ maximize <) just up
and disappear so I don't even see the left ar
*sigh*
The bug is not that the version of virtualbox in 19.10 only works with
the 19.10 kernel.
The bug is that if someone with virtualbox tries to upgrade to 19.10,
THE UPGRADE WILL FAIL BECAUSE OF THIS.
The upgrade needs to handle this problem, not just fail with no useful
explanation to the u
Public bug reported:
I imported an openvpn configuration with `nmcli c import type openvpn file
config.ovpn`.
After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off
automatic DNS servers and specify an IPv4 DNS server IP address explicitly.
I have /usr/lib/NetworkManager/c
Public bug reported:
Every time I open gnome-tweaks, it briefly shows the main screen with
"General", "Appearance", etc., down the left side, and then immediately
opens the "General" screen shown in the attached screenshot. I can't
figure out what's causing this or how to make it stop. This didn't
101 - 200 of 533 matches
Mail list logo
