Going on three months of an unacceptably broken desktop installation in
which not a single thumbnail will render. The lack of any
troubleshooting information or indication of what is wrong only adds to
the frustration.
What is the next step for addressing this issue?
--
You received this bug
Hey Georgia, thanks for your reply.
My output:
141 profiles are loaded.
1 profiles are in unconfined mode.
nautilus
23 processes have profiles defined.
(the rest are 0 like yours)
sudo aa-audit nautilus
Setting /usr/bin/nautilus to audit mode.
Warning: profile nautilus represents multiple
apparmor:
Installed: 4.0.0-beta3-0ubuntu3
Candidate: 4.0.0-beta3-0ubuntu3
Version table:
*** 4.0.0-beta3-0ubuntu3 500
500 https://mirrors.vcea.wsu.edu/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a member
Confused why this ticket is marked fix yet all of my Ubuntu 24 machines
fail to render a single thumbnail for any file.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2047256
I've also encountered this bug/crash since I always change the cursor to
DMZ-White when I install Ubuntu and I reckon other ex-Windows users might also
do. Before that I've noticed this weird "X" cursor when desktop was loading
(see attachement).
I've replicated the bug using only the live USB
** Changed in: subiquity
Importance: Undecided => Medium
** Changed in: curtin
Status: New => Triaged
** Changed in: curtin
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
@Jonas - please don't knowingly create duplicates.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1881932
Title:
subiquity isn't able to create btrfs subvolumes during installation
Public bug reported:
flatpak fails autopkgtest like so:
1125s Updating appstream branch
1125s Updating summary
1125s ok app with mismatched metadata (in summary) can't be installed
1125s test-metadata-validation.sh:158 - app with mismatched
metadata (in summary) can't be
Hi Kai-Heng,
It looks like you're working on this through Salsa. The debdiffs on
this bug mean that this shows in the sponsor queue, so I'm removing
Ubuntu Sponsors from this bug since there looks like no action to take
for Sponsors. Please re-subscribe Sponsors if you feel otherwise.
Thanks!
Other packages that have been tested and found to be impacted by this
bug have been added.
** Also affects: angelfish (Ubuntu)
Importance: Undecided
Status: New
** Changed in: angelfish (Ubuntu)
Status: New => Confirmed
** Also affects: privacybrowser (Ubuntu)
Importance:
removing
and
sudo update-mime-database /usr/share/mime
fixes the issue locally until the next update
** Summary changed:
- glob in mime/packages/freedesktop.org.xml is matching wrong files
+ in mime/packages/freedesktop.org.xml is matching wrong files
--
You
Public bug reported:
/usr/share/mime/packages/freedesktop.org.xml
line 10466 -> value="import Qt" offset="0:3000"
context:
is matching python files using Pyside
with imports like:
from PySide2.QtCore import Qt, QSettings, QSize
Marking invalid in systemd, other than long-standing udev rules being
involved I'm not sure this will be fixed in systemd.
Exploring if libblockdev with the s390 plugin enabled helps.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Also affects: libblockdev (Ubuntu)
No, only one that even has gnome in the name is network-manager-gnome.
I haven't had any freezing issue the last couple days, but will run and
post the journal commands next time it happens.
Still getting JS Error workspace is undefined and stack traces every
time I exit "activities" if my mouse
** Attachment added: "prevjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+attachment/5705142/+files/prevjournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Daniel,
Attached are the files from the two journal commands.
I have 2 .crash files in /var/crash:
_usr_bin_evolution.1000.crash
_usr_bin_nm-connection-editor.1000.crash
Is it worth doing the ubuntu-bug command on any/all of those?
I do see 50 error reports at https://errors.ubuntu.com/user/ID.
Public bug reported:
Ubuntu 22.04.3 LTS
gnome-shell[3218]: Can't update stage views actor
[:0x555e5db5c350] is on because it needs an
allocation.
gnome-shell[3218]: Can't update stage views actor
[:0x555e5fe0d310] is on because it needs an
allocation.
gnome-shell[3218]: Can't update stage
> it exposes a deficiency in the desktop
> environment in that the WM/shell's environment contains necessary
> env vars (e.g. ssh-agent variables) that are missing from the
> systemd --user / d-bus activation environment
--
You received this bug notification because you are a member of Ubuntu
No, wayland not affected.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2013255
Title:
changing screen brightness with keyboard hotkeys reacts very slow
To manage
Thanks, uploaded!
** Changed in: openbox (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2011751
Title:
openbox crashed with
Thanks for the patch, Aaron. I'm able to reproduce this bug using the
firefox f11 -> open link in new window, when using the live session of
the daily-live lubuntu iso. And the attached patch does seem to help.
Overall the patch is what I was hoping to see, but I will request some
changes.
*
Partial review of the patch so far. I haven't read much openbox code so
take this with a grain of salt.
https://bugzilla.icculus.org/show_bug.cgi?id=6669#c9 mentions a concern
that itPrev may still be pointing to invalid data. I share this
concern. I think some interesting testcases are what
Thanks for the report.
> do you think this bug will be corrected soon ? or i change parent
directory name of mountpoints ?
Probably better off changing the parent directory name, I'm afraid.
** Changed in: glib2.0 (Ubuntu)
Status: New => Triaged
** Changed in: glib2.0 (Ubuntu)
Public bug reported:
When I right-click an application from the Dock, the context-menu/dialog
comes up with the different options, but when I click on one of them,
for some reason, the context-menu/dialog appears one more time but in
the left screen and when I click again in the context option in
Public bug reported:
Within "Save As" dialogs from any desktop application, all navigation
operations, specifically the most common one of changing folders,
switches focus away from the file name input, resulting in the search
input box accepting keyboard input instead of the filename input box.
Hello,
Thank you for your feedback.
I hope we will have a solution, which we can deploy across our entire fleet. I
thank you and wish you good luck. Thank you for your work on this bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Any news ? :'(
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1948008
Title:
Copying and pasting files between desktop and Nautilus does not work
To manage notifications
Oh dear, do you have a vision to know if the fix is on? Do you have any
idea if there will be one? Because there are many of us who are affected
by this problem. And we have just switched our park to 20.04 :/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Hi,
We have a lot of computer using Ubuntu 20.04, in all of them, we can't
copy/paste between Desktop and Nautilus, Focal is impacted, when we will have a
fix ? a patch ? please ? We need to deploy it on all the computers in emergency.
Thank you in advance for your help.
--
You received this
Public bug reported:
A few changes for gspawn landed in the 2.67 series that had some bugs
which were later fixed and backported to 2.70 as seen in
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2394. These bugs
are present in 2.68 as on impish, but that series won't see any more
updates
possibly continued at https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4759#register-pane
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4759
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4759
--
You received this bug notification because you are a member of
** Changed in: trusty-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1285783
Title:
Right panel has a transparent background
To manage
** Changed in: hardy-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/326741
Title:
Update GIMP to version 2.4.7 in hardy-backports
To manage
** Changed in: hardy-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/151207
Title:
Error when trying to open a .wmf file, should use Gimp
To
** Changed in: oneiric-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/865907
Title:
Please backport tracker to Oneiric
To manage
I did that and it did seem to fix the problem.
I re-enabled Ubuntu Dock and it still is fixed though, so I'm not sure
what that means.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Relatively fresh install just after installing updates and a few pieces
of software.
Not sure what other info is needed other than all the info in the
attachment but let me know if there is anything else.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell
Just for reference, i ran into this problem once again tonight
(2021-07-30) on one of my xubuntu 20.04 systems. In this particular
case it was due to running another copy of eog under gdb (which somehow
made it out-of-reach to killall, and which i had forgotten about). I
don't think this is what
please reopen if this is still an issue for systemd
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1699360
Title:
package libpam-systemd:amd64
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
> This should fix the problem:
https://github.com/lxc/distrobuilder/pull/476
wow...all those 'fixes' lxd is adding look like things will continue to
break in bad ways, like this bug. ouch.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I have this problem as well, and it just started tonight (2021-05-25) on
my xubuntu 20.04 system. I have another xubuntu 20.04 machine on which
the problem does not occur. So, this may be transient, or mostly
unrelated to eog.
--
You received this bug notification because you are a member of
Public bug reported:
1) hirsute hippo
2) 3.38.4-1ubuntu2
3) Being able to properly select the icons I have on one of my two monitors
4) On one of the monitors, drag and select works correctly, on the second one,
however, it has a weird behaviour of selecting an incorrect area as seen in the
I'm marking this invalid for systemd (the patch there was reverted) and
fix released for plymouth, with the assumption this was fixed with the
patch for bug 1817738.
If anyone is able to reproduce the problem please add a comment.
--
You received this bug notification because you are a member
Unfortunately I can't reproduce this bug, even with the
0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for
sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2.
Also note that the [test case] in the description is wrong, that would
be correct with the systemd change
As suggested in the freedesktop bug, this probably was fixed with the patch
added for bug 1817738 which is this commit:
https://gitlab.freedesktop.org/plymouth/plymouth/-/commit/85d843af843589ce8538a59e5cb665b8253e380d
I haven't been able to reproduce this myself yet (when using the
plymouth
Public bug reported:
A colon in a file or directory name causes the operation to hang when
copying to a phone via ptp.
To reproduce:
On android phone:
1) plug usb cable between phone and computer
2) Go to settings. Search for USB. Click on "Standard USB configuration".
(Alternately, notice
Also: if the colon is in the name of a directory you are copying, the
directory gets created with the colon in the name, but any attempt to
put files in it hangs.
Deleting the colon-named things via Files does seem to work, though.
And transferring files with spaces, dashes, and umlauts in the
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notificatio
** Description changed:
+ [impact]
+
+ pam_umask, from /etc/passwd, is not honored in systemd --user instances
+
+ [test case]
+
+ on a desktop system, edit /etc/passwd to change the test user entry
+ (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
+ field). For example
> REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy
Gorilla), the issue had reappeared
I just tested with groovy and can't reproduce the issue; umask is
correct under gnome-terminal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Oy. Debian's ticketing system is the most archaic and arcane I've seen
in the past 20 years. But after jumping through the hoops several times,
here it is, (along with my email in clear for all to spam) -
https://bugs.debian.org/983291
** Bug watch added: Debian Bug tracker #983291
Public bug reported:
The package `fonts-noto-core` contains 150+ highly exotic fonts,
including cuneiform and hieroglyphics. These are high-quality but for
all practical intents and purposes, never needed all at once, not even
by a PhD in linguistics. 99%+ of the users will need only one language
Daniel,
To be honest, I'm not quite sure what this ticket is all about.
If it's just that people see these lines in their log, then surely, it's
not worth having an open ticket about.
On the other hand, I'm saying that I have been investigating this for
two weeks, and I can say with 95%
This is pretty nasty. I'm on a Dell laptop, running an oem kernel, with 20.04.1
lts, and some oem firmware for the nvidia prime tool. Anyway, a few times a
day, the laptop freezes up, no hid available. When I reboot by powering down
(only thing that works, not even ssh), I look into my logs,
Public bug reported:
I've pasted a number withe decimals in Calculator, and I want to
calculate 1.5 minus that number, so I press Home, then start typing
"1.5". That stops after "1".
My input looks like this, where "|" is the cursor:
0.230179408
|0.230179408
1|0.230179408
At that point, I
I no longer have access to the system in question, and haven't seen it
anywhere else, may as well close as abandoned.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1766938
Title:
autopkgtests pass for bionic for all archs, except once for i386, for
which I opened bug 1902554; the i386 test passed on retry.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification
autopkgtests pass for focal for all archs (except i386 which is expected
to fail for focal)
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in
Yes - "after login" means after I have successfully entered my password.
Also, I have not been able to locate the 'Ubuntu on Wayland' selection.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Attached prevboot.txt as instructed. Thanks for your assistance.
** Attachment added: "Output of 'journalctl -b-1 > prevboot.txt'"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901342/+attachment/5427638/+files/prevboot.txt
--
You received this bug notification because you are
Medium
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Focal)
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/392373
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1892358
Title:
The deficit here is not the action, but rather that the action is not
documented in any way except in the source.
>From the source there are two ways to open the editor, either by setting
the "Automatically launch when a new mail is edited" option and then
pressing any key in the Evolution
ok, very sorry for my delay in looking at this.
a quick scan of the results for x/b/f show:
ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r xenial -cv
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:53:00.893145-04:00'
88: boot-smoke FAIL non-zero exit
** Package changed: systemd (Ubuntu) => tracker (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1896756
Title:
tracker* startup is defined multiple times
To manage
hi @cpaelzer, sorry i missed reading this earlier, i'll give all the
test failures a look to see what can be done.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1892358
Title:
apport information
** Tags added: apport-collected focal
** Description changed:
I tried to use ubuntu-bug -w to identify the component for this bug by
clicking on a notification, but it failed with "xprop failed to
determine process ID of the window". Sorry.
- The bug is that
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1882023/+attachment/5405640/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1882023/+attachment/5405642/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1882023/+attachment/5405644/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1882023/+attachment/5405641/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1882023/+attachment/5405643/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
N, please don't mark this as invalid. This is the most annoying
notification on my wonderful Gnome desktop. It is so premature. First
off, it thinks my MX Logitech keyboard is a mouse and secondly, it
displays over and over long before the keyboard needs to be charged.
I use this
Looks like the removal of the solid background option was one dev's
dictatorial and narrow-minded decision. What can I say. Enjoy open
source.
https://www.reddit.com/r/gnome/comments/dayto8/can_someone_point_me_to_the_train_of/
--
You received this bug notification because you are a member of
A thousand thank yous.
Disabling 'desktop icons' from the extensions app fixes this for me.
Once disabled, even just the action of clicking on the toggle in the
extensions app has the same effect, the desktop becomes unresponsive
(though the mouse moves) for about 30 seconds, then finally the
** Tags removed: ddstreet
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1803993
Title:
Password appears on the VT1 screen
To manage notifications about this bug go to:
thanks Dan `killall -3 gnome-shell` keeps me sane. No longer need to
reboot everyday.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880405
Title:
High CPU and journal
I'm seeing something very similar.
Did a fresh install of 20.04 a week ago.
After being logged in half a day things really start slowing down.
Alt+Tab takes a few seconds to pop up, then you tab through to e.g. an
open Calculator instance and that takes 8 seconds to come to the
foreground.
** Attachment added: "Screenshot from 2020-07-17 15-33-50.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+attachment/5393306/+files/Screenshot%20from%202020-07-17%2015-33-50.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
lspci
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+attachment/5393305/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
As I recall, in the many ubuntu installations I did, it was one where I
put accountsservice on hold and then upgraded the system. Then, I run an
apt-get upgrade instead of apt, or something similar, so the hold was
not taken account of. I was afraid the PC would crash, but it did not,
it however
As I mentioned, I think the problem is not related to nvidia drivers. If I
install nvidia drivers I have to do it by first disabling automatic log in at
startup, otherwise I get a login loop after first reboot. If I disable
automatic log in, then I do not get any crash when upgrading
I just reinstalled focal ubuntu with "log in automatically" checked and
I recorded the journalctl and timed the error at approximately 14:31:54.
I am attaching the log. The errors you saw previously such as
(EE) NOUVEAU(0): [drm] failed to set drm interface version
appear at 14:31:56 so after
The newest log has errors as you said at 14:54:52 and the last line of
the log, probably when I saved it, reads 14:55:22. This means that
between the time of errors and time of log saving 30 seconds passed,
which seems correct as it is the amount of time it has taken me to ctrl-
alt-f3, enter
Public bug reported:
After a fresh install of Focal Fossa and running sudo apt update and
sudo apt upgrade, when the upgrade reaches "setting up accountsservice"
the PC freezes. After a reboot, the login screen did not appear anymore.
This was reproducible on another computer (laptop). I
I see a similar issue with the "Device not trusted yet" dialog when
plugging in an iPhone.
Is that the same bug? Please see the screenshot.
** Attachment added: "Device not trusted yet - text cut off, ellipsized"
Whew, this is a long bug.
So given comment 40 indicating part of this bug has been fixed in bug
1828639, and comment 42 indicating the any remaining patches should be
sent to debian, it seems to me that the ubuntu-sponsors team does not
need to be subscribed to this, as it's unclear what parts,
fyi, this was an intentional upstream change, thanks @vtapia for
pointing me to the upstream wiki:
https://wiki.samba.org/index.php/Samba_4.11_Features_added/changed#SMB1_is_disabled_by_default
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Please push out a fix for this ASAP, once this tight loop is hit the
machine becomes an unusable 100% CPU using mess. I know of several
others suffering exactly the same bug.
For me this can be reproduced by having a terminal using half the screen
(using CMD+LEFT), then switching to fullscreen
Still an annoying problem in Ubuntu 20.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1433774
Title:
When double clicking an executable bash script in file manager, it
opens
Public bug reported:
-
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
@seb128: Maybe I didn't notice the search being this undiscoverable, or
maybe I was using another theme that made it more obvious
@amr: "just start typing" is not a discoverability UX hint. Users don't
randomly start typing in dialogs without inputs. MAYBE the keyboard
fanatics will try '?', but
I have found a perfect reproducer; locking the screen (and so entering
standby) reproduces this 100% of the time.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
Public bug reported:
Sporadically, I see loss of the Riot-Desktop (https://github.com/vector-
im/riot-web/ care of https://packages.riot.im/debian/) app indicator
icon. This appears to be associated with the following log lines from
`journalctl /usr/bin/gnome-shell`
```
May 16 10:54:22 cube
** Also affects: dbus (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-terminal (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gnome-terminal
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/986
** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #986
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/986
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
I wanted to install a new package. Launched Ubuntu Software and... how
do I search for anything?
Search is a key function. It should be front and center. I couldn't see
it.
That was annoying enough that I wanted to file a bug against it. In the
process I did notice the lens
1 - 100 of 849 matches
Mail list logo
