Turns out after a fresh reboot the memory usage isn't much different
after I close all apps and VmData for gnome shell is only about 400MB.
So, perhaps this isn't the smoking gun I thought it was.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thanks @vanvugt, this was helpful. I'm running ubuntu 23.10. It's been
about a week since I rebooted and I noticed swap usage was quite high.
I've got 32GB of RAM and am a developer with a bunch of stuff open at
once. Decided to investigate. Closed everything, but left just gnome
running and a
Works for me.
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2027844
Title:
opening
Tried building gnome-control-center from source and running gnome-
control-center-goa-helper under valgrind, no memory errors detected.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Public bug reported:
I've tried about 15 times in a row now to add a Google account in GNOME
control center, and every time it has hung at some point in the process
before letting me enter my password.
Sometimes it hangs before it even asks for my Google username.
Sometimes it hangs right after
*** This bug is a duplicate of bug 2002624 ***
https://bugs.launchpad.net/bugs/2002624
I am not able to reproduce this merely by locking and unlocking my
screen so I don't think this is the same as #2002624.
--
You received this bug notification because you are a member of Ubuntu
Desktop
I believe so. For example I believe I've noticed it in the Settings app.
I will keep an eye out and confirm here when I see it in another app.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "2023-09-07_11-35.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+attachment/5698315/+files/2023-09-07_11-35.png
--
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:
Recently when I go to minimize, maximize, or close a window (I have the
minimize and maximize buttons enabled in Tweaks) I discover that the
buttons are invisible. I know they're there, just invisible, because I
can click where they should be visible and the expected thing
This was a PEBKAC issue. I was opening the Unity sharing control panel
instead of the GNOME sharing control panel.
I have no idea why the Unity sharing control panel is still on my computer. I
thought unity was gone. ;-)
Is it safe to remove it?
** Changed in: gnome-control-center (Ubuntu)
1) Is crash reporting fixed? Ref:
https://bugs.launchpad.net/launchpad/+bug/2033653
2) Do you still need the crash report given your comment above?
--
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:
The most recent Mantic turned off Screen Sharing, which was previously
turned on.
When I go to turn it on in the sharing control panel, i see that sharing
is completely disabled, i.e., the rocker switch at the top of the window
is off, presumably because the only kind of
Public bug reported:
With the most recent Mantic updates gnome-shell is regularly, but not
every time, crashing and showing me the "Oops!" screen and forcing a
logout when I type Alt-F2 r RET (using X11, obviously, since AFAIK that
still isn't supported in Wayland).
ProblemType: Bug
Well, _this_ is fascinating.
I downloaded and built gimp from source:
sudo apt install dpkg-dev devscripts
cd /tmp
sudo apt source gimp
sudo apt build-dep gimp
cd gimp-2.10.34
sudo debuild
Then I modified app/gimp-2.10 to use "exec gdb" instead of "exec" to run
gimp.
Then I made sure gdb would
I ran gimp under gdb and got the more useful stack trace below, though
there still isn't enough info to figure out what's going on.
#0 __wcslen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
#1 0x76ad0d8e in __GI___wcsxfrm_l
(dest=0x0, src=0x0, n=0, l=) at
I tried removing ~/.config/GIMP to see if starting from scratch would
fix the crash. No luck.
--
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/2031907
Title:
gimp is segfaulting on
Still happening.
** Tags added: regression-release
--
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/2031907
Title:
gimp is segfaulting on startup
To manage notifications about this
Public bug reported:
Unfortunately it appears that gimp catches segfaults and I can't figure
out how to disable that so I can't report this crash with appport.
Here's the bug information in the pop-up that gimp displays when it
catches the segfault:
```
GNU Image Manipulation Program version
Public bug reported:
1. Click the sound icon in the upper right corner of the screen.
2. Click the arrow next to the sound slider.
3. Select "Sound Settings".
4. Observe how the control panel window that opens up is empty.
5. If you then click on a different control center section and then click
** Attachment added: "same page which demonstrates this issue"
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2023588/+attachment/5679706/+files/sample.pdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
Public bug reported:
Just downloaded my credit card statement PDF and opened it with evince.
Fonts are all messed up. Tried mupdf; also messed up. Opened it in
Chrome, everything is fine. See attached screenshots of how a particular
paragraph in the PDF looks in Chrome, evince, and mupdf.
Also
OK, yes, it turns out that mouse focus vs. click focus is indeed the
differentiator for me, but it's a bit more complicated than that. If I
have focus set to mouse when I log in, then this bug manifests even if I
change focus to click. If I have focus set to click when I log in, then
this bug does
Logged out, rebooted, made sure all packages are up-to-date, none of it
made a difference.
--
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/2013216
Title:
Single click on title bar
What do I do about the fact that I am unable to edit the status of the
bug to indicate that it is not fixed? File a new bug?
--
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/2013216
This bug is not fixed. Still happening for me in Xorg on Mantic.
--
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/2013216
Title:
Single click on title bar does not transfer focus to
This issue is NOT fixed in 44.1-1ubuntu1. I don't know whether that's
because the fix from upstream didn't get included in that package
somehow, or whether the upstream bug is not actually the root cause of
the issue reported here. If I launch an emacs window with the new
version of mutter in
Note: the "Sometimes Emacs launches as a tiny window" issue happens
*even when Emacs is explicitly launched with -g 80x35 on the command
line*.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I marked this as affecting gnome-shell as well as Emacs because the
problem of Emacs launching with a tiny window instead of the properly
sized window is occurring even when I downgrade to the older Emacs debs,
so that's apparently a problem with the new gnome-shell, not with the
new Emacs?
**
I dug into this a little and encountered a whole slew of issues, such
that I'm really unsure how to file them or under what packages.
I'm using nvidia-driver-525 with one monitor plugged directly into the
back of my computer and a second monitor plugged into a DisplayLink hub.
The DisplayLink
Well, that one was just closed, so removing the duplicate link because
otherwise this one won't get any attention?
** This bug is no longer a duplicate of private bug 2011426
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Not 100% certain but I think this is one of the times I was
spontaneously logged out:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011426
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Nope I'm on the current 6.1 kernel.
--
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/2011317
Title:
gnome-shell spontaneously logging me out when screen locked, laptop
lid
This is happening for me on machines with a single display (laptop, no
external monitor connected), so if that other bug is accurate that it's
just about multi-monitor displays, then that's not the problem here.
I'll try without extensions and see what happens.
--
You received this bug
Public bug reported:
With recent gnome-shell in Lunar, some of my windows, seemingly at
random, are launching with weird title bars that don't reflect the title
bar settings I have configured.
E.g., the font in the title bar is not the same as for other windows,
and the buttons on the right when
So far this is only happening on one of the three machines on which I
run current Lunar, and all three of the machines have different hardware
profiles, so I'm wondering if perhaps this isn't actually a gnome-shell
issue but rather a hardware issue. I've noticed that the machine on
which this
Public bug reported:
In the short time since I've installed the recent GNOME updates in
Lunar, I've been logged out spontaneously at least three times while my
laptop lid was closed and screen locked and I wasn't doing anything with
my computer. Perhaps the attached logs will help you figure out
Public bug reported:
In the short time I've had the newest GNOME updates for Lunar, my gnome-
shell has hung twice.
The first time I had just logged into a Google account in Chrome, and it
popped up the window asking me if I wanted to switch to a new Chrome
profile rather than logging into that
Public bug reported:
After the most recent Lunar updates (i.e., with the newest GNOME) my
gnome-shell got into a state where clicking on the title bar of a window
wouldn't raise the window (or do anything else), while clicking inside
the window raised it as expected. The problem went away after I
This appears to be fixed in current Lunar.
--
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/1990861
Title:
can no longer click on speaker icon in system tray menu to mute/unmute
Public bug reported:
1. Open Settings.
2. Go to Online Accounts.
3. Add a Google account, or if you already have one, click on it, to open the
Google Account window.
4. Toggle one of the rocker switches from on to off or vice versa.
5. Observe that at this point the window becomes unresponsive
Public bug reported:
Hello
We have 3 Lenovo P15s laptops used for development at vHive.ai
We use Ubuntu 20.04
After updating drivers (no special configuration, just click update), WebGL
stops working. It is jittery and then crashes (Chrome browser). Reproducible:
fresh install works ok, but
Public bug reported:
My desktop has wired ethernet and I keep Bluetooth disabled when I'm not
using it for security reasons. Because of this the shell decides I'm in
"Airplane mode" and highlights the button in the system tray menu and
sticks the airplane mode icon in the system tray. Even if I
Public bug reported:
I have the shell configured to lock the screen when I close the lid and
go to sleep after 20 idle minutes on battery power.
Immediately before I opened my laptop and unlocked it to submit this
bug, the laptop was unplugged from battery power and sitting with the
lid closed
Public bug reported:
In Jammy, if I opened the system menu (click on system tray in top right
corner of screen) and clicked the little speaker icon it would mute my
audio, and then if I clicked again it would unmute.
That icon is no longer clickable in Kinetic.
ProblemType: Bug
DistroRelease:
Public bug reported:
I have GNOME configured to lock the screen when the screen is blanked,
and to blank the screen when the lid is closed:
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
org.gnome.desktop.screensaver lock-delay uint32 0
org.gnome.desktop.screensaver
*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593
Welp, I had disabled the proprietary nvidia driver because I use a
DisplayLink hub and DisplayLink was really unhappy about nvidia, but I
just tried it again with the current nvidia driver and it appears to
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1983483/+attachment/5606794/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1983483/+attachment/5606793/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1983483/+attachment/5606792/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
apport information
** Attachment added: "GstreamerVersions.txt"
https://bugs.launchpad.net/bugs/1983483/+attachment/5606791/+files/GstreamerVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
When I try to play a video with totem it either crashes or hangs my
display (mouse cursor still moves but nothing else works and I have to
reboot). The crash is inside nouveau drivers, so this may be a nouveau
1) Your comment does not address the stack trace I am getting, shown
above, from the apport script in totem-common.
2) The crash is not being uploaded successfully to the crash tracker
either; see
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983294/comments/2
.
3) I understand that
Removing gstreamer1.0-vaapi does make this particular crash go away, but
then I get another one. See bug 1983483.
See also bug 1983481 about the fact that I was unable to report either
the crash in this bug or the crash in bug 1983483 with ubuntu-bug or
apport-cli.
--
You received this bug
Public bug reported:
When I try to play a video with totem it either crashes or hangs my
display (mouse cursor still moves but nothing else works and I have to
reboot). The crash is inside nouveau drivers, so this may be a nouveau
bug rather than a totem bug. I can't report it with ubuntu-bug
Public bug reported:
When totem crashes and I try to report the crash with ubuntu-bug, one of
two things happens:
1) Sometimes after the dialog pops up and I click the "Send" button,
ubuntu-bug immediately exits without doing anything:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
OK, I installed debug symbols and ran totem inside gdb, and this looks
like the most common crash listed there, i.e., bug 1973570:
(gdb) where
#0 ___pthread_mutex_destroy (mutex=mutex@entry=0x0) at
./nptl/pthread_mutex_destroy.c:31
#1 0x77e282a0 in g_rec_mutex_impl_free (mutex=0x0) at
Presumably it doesn't have a stack trace because it didn't upload
successfully. I don't know how to fix that.
It's crashing reliably for me but it isn't producing a new crash each
time in /var/crash, just the first one is there.
apport-cli isn't working either. I tell it to send the report and
Public bug reported:
Totem is crashing on launch.
I see in /var/crash that the crash was reported, with crash id
affaa5ef-11fd-11ed-a50a-fa163e55efd0, but when I try to run ubuntu-bug
on the crash file it reports this:
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Public bug reported:
The Python files in the indicator-keyboard package are being installed
in /usr/lib/python3.8 instead of /usr/lib/python3.10.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: indicator-keyboard 0.0.0+19.10.20190716-0ubuntu3
ProcVersionSignature: Ubuntu
This also affects me too. It's more of an annoyance (at least in my
case), as clicking the back arrow in the top left corner, and then
clicking on the video thumbnail temporarily fixes the issue. It's
opening video files directly that causes this glitch for me.
--
You received this bug
Public bug reported:
In a brand new account created just to test this issue, gnome-terminal
has a dark background and light fonts even when the GNOME them is set to
light. I am not sure if this is a new issue in Jammy, but it sure is
frustrating that when I switch to light mode every app switches
I just installed another round of new Jammy updates on the laptop where
gnome-extensions-app was crashing, and it's not crashing anymore. I
don't know if it's the installing of the updates that fixed this or if
it's an intermittent issue and just not happening at the moment. Hard to
tell since no
I have two machines with Jammy on them and this is happening reliably on
one but not the other.
On the one where it's happening, it happens even immediately after I've
updated all out-of-date packages and rebooted the machine.
I don't know why it's not generating a crash report. :-(
--
You
Public bug reported:
$ /usr/bin/gnome-extensions-app
Segmentation fault (core dumped)
There's nothing in /var/crash.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-prefs 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux
Yes they are Reminders from the Calendar app. For a Google account.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1966614
Title:
I am getting calendar notification pop-ups
Public bug reported:
I keep getting calendar notification pop-ups -- at the top middle of my
screen -- even though in the calendar settings in Notifications I have
"Notification Popups" turned off.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-calendar 41.2-3
ProcVersionSignature:
Public bug reported:
1. Have some GNOME shell extensions installed (I have Allow Locked Remote
Desktop, Mpris Indicator Button, Removable Drive Menu, User Themes, plus
built-ins Desktop Icons NG, Ubuntu AppIndicators, Ubuntu Dock).
2. Open the Extensions app.
3. Confirm that the switch at the
Public bug reported:
After running "sudo apt upgrade" and approving the listed packages, the
following error occurred after unpacking a number of packages:
dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
No longer reproducible for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1952556
Title:
Jammy, attempt to log into Xorg session, "Oh no! Something has gone
wrong."
Public bug reported:
1. Your local computer should be in a time zone other than UTC.
2. Save the attached sample.ics to your Desktop.
3. Double-click on it to import it into GNOME Calendar.
4. Save the imported event. Observe that it is saved at the correct time in
your calendar.
5. In GNOME
1) ~/.local/share/gnome-shell/extensions is empty
2) I reproduced this issue with Chromium and there is no Chromium crash
in /var/crash, nor is there an error report for Chromium tied to my
whoopsie ID.
Since the chromium snap is provided by Canonical and this issue is
reproducible with Chromium
(Though why _Wayland_ is crashing when I'm trying to log into an _Xorg_
session and the options menu on the login screen says that I have Xorg
selected remains a mystery.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Problem still occurs with mprisindicatorbutton, batime, and
allowlockedremotedesktop completely uninstalled. Can't uninstall multi-
volume because neither Extensions app nor extensions.gnome.org say it's
installed.
Probably relevant crash:
** Attachment added: "screenshot showing no multi-volume@tigersoldier"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+attachment/5544070/+files/extensions%20app.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I removed 'mprisindicatorbut...@jasonlg1979.github.io',
'bat...@martin.zurowietz.de', and 'allowlockedremotedesk...@kamens.us',
but GNOME doesn't seem to think I have 'multi-volume@tigersoldier'
installed, so I'm not sure where you got that from or what to do with
it. See attached screenshot of
Public bug reported:
In Jammy when I have Chrome running and I log out of a Wayland session
and then log back in and restart Chrome it says it wasn't shut down
correctly.
I'm pretty sure in earlier releases Chrome was given the opportunity to
shut down cleanly when I logged out, but :shrug: I
Public bug reported:
On Jammy, I log out of a Wayland session, click my name on the login
screen, go down to the options menu and select Ubuntu on Xorg, enter my
password, get "Oh no! Something has gone wrong. A probleme has occurred
and the system can't recover. Please log out and try again.
I logged out immediately after logging in again as described above, then
went to log in again and checked the options menu, and it correctly had
"Ubuntu on Xorg" selected as my session type, but when I finished
logging in I was in a Wayland session, not an Xorg session. So for some
reason my
It looks like the overview that normally launches when you click at the
super key, but without search bar and without the possibility to leave
the view again (via ESC Key, etc.). Only logging out and in again solves
the problem.
--
You received this bug notification because you are a member of
I made a photo as the problem appeared the last time, this is the view
in which I got stuck in.
As soon as the bug appears again, I'll follow the given steps to record
the problem.
** Attachment added: "PXL_20210506_201849766.jpg"
Can you please read what other people have said before commenting.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1813441
Title:
Can no longer drag and
lol PEBKAC issue. I had an sshfs session running on another computer and
whenever I rebooted it was reconnecting. Sorry to trouble you. That's
for telling me how to figure it out.
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
--
You received this bug notification because
It says "No inhibitors", and yet there is still no one else logged in
remotely and it is still claiming that there is when I try to restart.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
With all current Hirsute updates as of today, when I reboot my machine
and then immediately after logging in select Power Off/Log Out and then
Restart... the warning that pops up claims that I am logged in remotely
(see attached screenshot) when I am not. As I said, I just
I want to thank you from the bottom of my heart for taking time out of
what I'm sure is a very busy schedule to educate poor little me, who is
so ignorant that I've only been working on open source and commercial
software for over 30 years and using Linux since the early days of
Slackware and at
Claiming that Ubuntu could simply have stuck with the previous version
of GNOME when shipping the LTS release is failing to see the forest for
the trees. Many factors go into the decision of what version of a
critical package like GNOME to put in a release. Ubuntu looked at all of
those factors
Three notes:
1. Ubuntu has addressed this in 21.04 by shipping gnome-shell-extension-
desktop-icons-ng by default.
2. Note that you can fix this yourself in any earlier version of Ubuntu
by installing that extension directly from extensions.gnome.org (
I don't understand why you are asking me for a crash report. You don't
need a crash report to know what is going on here. I described to you
exactly what is going on and exactly how to reproduce the issue: gdm
fails in the way I described if libpam-fprintd isn't installed, and the
web of
I figured out the problem. When I upgraded packages today, it
uninstalled fprintd-clients but did not install libpam-fprintd.
/etc/pam.d/gdm-fingerprint says that gdm is supposed to open
pam_fprintd.so, but it couldn't because it wasn't available any longer.
I have no understanding of the
Public bug reported:
After today's update to all of the current Hirsute packages, I can't
login in. When I click on my username on the gdm3 login screen, it
immediately displays with shaking the error "Sorry, that didn't work.
Please try again." It does this three times, and then sends me back to
GNOME now supports remote desktop sharing in Wayland, but it isn't
enabled in Ubuntu. Apparently one of the prerequisites for being able to
enable it in Ubuntu was recompiling mutter with support for it, and that
has now been done in Hirsute. What else needs to be done in Hirsute to
make this
Even with that version of mutter installed I still don't see screen
sharing as an option under sharing in the settings app when logged in
under Wayland. Are there other packages that need to be updated before
screen sharing will be available in Wayland sessions, and are there open
bug tickets for
Darn it, I tested this like three times before reporting it, but I can
no longer reproduce the issue. Sorry to bother you.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
I have my laptop configured to suspend automatically after 20 minutes of
idle time when on battery power. See screenshot attached showing these
settings.
This worked fine in 20.04. It is not working in 20.10: the laptop is not
suspending even after far more than 20 minutes
Public bug reported:
This problem seems to come and go. It was gone in Ubuntu 20.04 and it's
back in Ubuntu 20.10.
I have both Flameshot and Yubico Authenticator configured to launch on
login. They are supposed to put app indicator icons in the top bar. The
icons are not there even though both
unfortunately since 'upgrading' to evince 3.28.4
Gallium 3.1 18.04 bionic
it is no longer apparent to me that there is a transparency option
available
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
ubuntu-bug evince
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in evince
The problem cannot be reported:
This is not
I can confirm that this bug is no longer present in 20.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1842298
Title:
Evince printing glitches on PDF documents from JHEP
To
The default position should be that the system creates an 'application' for
each .desktop in ~/.local/share/applications.
it does not, and is rather particular...
in my case requiring full addresses was the issue.
even then, add to favourites was not immediately available,
which is
I am having a similar experience.
I installed a brand new version 20.04lts today
I can find no instructions that work for me.
in particular 'Allow Launching' is not available
https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux
NB the executable is
1 - 100 of 1596 matches
Mail list logo
