Public bug reported:
When having e.g. a 7 rows high window (with two tabs) and maximizing +
unmaximizing it, the result is a 6 rows high window. Repeat it and it
goes to 5, 4, and finally 3 rows in height. It doesn't shrink past 3
rows.
It is especially noticeable with a long narrow window along
Public bug reported:
The dock is wasting its entire screen edge of valuable edge pixels by
not reacting to actual clicks on them.
I have the dock on the left edge.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
ProcVersionSignature: Ubuntu
** Attachment added: "Illustrating how a Files window's context menu is hidden
by another, always on top Files window"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938596/+attachment/5515157/+files/aot%20on%20context%20menu.png
--
You received this bug notification because
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1938596/+attachment/5515006/+files/monitors.xml.txt
** Attachment removed: "GsettingsChanges.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938596/+attachment/5515003/+files/GsettingsChanges.txt
**
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1938596/+attachment/5515003/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1938596/+attachment/5515005/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1938596/+attachment/5515004/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected hirsute wayland-session
** Description changed:
"Always on top" windows are meant to be on top of other non-transient
windows (its peers), but they're also on top of other windows' transient
GUI components like context menus and tooltips.
Thank you for your suggestions, I will look into it. If there's a
particular point that could be made clearer then I'll absolutely submit
a screenshot and try and clarify it.
As for ubuntu-bug, I did run it. It guided me to report a bug against an
Xorg package. Would you say that that would've
Public bug reported:
I press ctrl+shift+f to do a search.
The search field is focused and I input my keywords with the keyboard.
I perform the search.
I use the mouse to select and copy another piece of text in the terminal window
in order to do another search.
I press ctrl+shift+f again.
The
Thanks for moving it to the right place
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1920776
Title:
Source window raised on drag-n-drop -- drag-n-drop destination window
not
Thanks for the suggestion for a workaround.
If true, sounds like an unreasonable limitation and implementation
detail worthy of someone's attention, considering it is entirely
reasonable to create a share called "games".
--
You received this bug notification because you are a member of Desktop
** Description changed:
The power saving section of system settings has the title "Power saving"
(all GUI text is translated to English in this report, but I suspect the
wording is similar enough in the English localization of the UI that the
points still stand). There are some problems
Public bug reported:
The power saving section of system settings has the title "Power saving"
(all GUI text is translated to English in this report, but I suspect the
wording is similar enough in the English localization of the UI that the
points still stand). There are some problems with that
Public bug reported:
I'm just guessing package name since I can't simply read my way to that
information in the GUI...
I'm trying to share my games folder on the network by right clicking and
selecting the Share on local network option.
I tick Share this folder, and confirm. I expected the
Public bug reported:
I don't know if this has to do with libinput, I'm just guessing.
When using a 2012 Macbook Air the trackpad regularly stops tracking
individual finger movements during use (the cursor stops responding to
movement). Once I lift my finger and once again touch the trackpad it
Hello and thank you for following up.
Thank you for your suggestions. I will look into them.
I will be on the lookout for new crashes and report them here.
While uninstalling the unofficial desktop icon extension would seem like
a good idea in the context of this bug report, that would result
*** This bug is a duplicate of bug 1797002 ***
https://bugs.launchpad.net/bugs/1797002
** Attachment removed: "AlsaInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443423/+files/AlsaInfo.txt
** Attachment removed: "CurrentDmesg.txt"
Just a FYI, I'm a bit confused regarding the ID. The .uploaded file has
a timestamp earlier than the .crash file (about 12 hours earlier than
when I actually experienced the crash most recently) and the .uploaded
file doesn't change its contents after running ubuntu-bug, even as
superuser.
It
*** This bug is a duplicate of bug 1797002 ***
https://bugs.launchpad.net/bugs/1797002
I understand. I was assuming that gnome-shell was big enough to warrant
at least one person who could view private reports, and that the message
suggested a mistake.
Thanks for the info.
--
You received
Thanks for taking a look.
I see. Found it - UUID from crash.uploaded: 362c2716-4051-11eb-
8be3-fa163ee63de6
Thank you for the suggestion. Did you spot any specific indication that
that extension was the source of the crash? Anyway, if you do, I can
reach out to them.
--
You received this bug
I also ran 'ubuntu-bug /var/crash/_my_crash_report.crash' for my crash
report, and was led to believe that a new bug would be created as a
result (in another issue I was there told to "tell us the ID of the
newly-created bug" after running that command), but I was given no
information by the time
When trying to mark this bug as private I get the message "The bug will
become invisible because there is no-one with permissions to see Private
bugs". Is that a mistake? Shouldn't someone be able to see it?
--
You received this bug notification because you are a member of Desktop
Packages,
*** This bug is a duplicate of bug 1797002 ***
https://bugs.launchpad.net/bugs/1797002
Thank you for the suggestion. I tried what you suggested in another bug
(for gnome-shell) and got the message "The bug will become invisible
because there is no-one with permissions to see Private bugs" --
Public bug reported:
This matches the title of
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I
don't want to assume it is the same considering that was allegedly fixed
three years ago.
journal:
dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8
Hello,
Thank you for looking at this issue.
If source code propagate downstream, then I think it would be a good
idea to come up with a system that propagates bug reports upstream.
If that effort is underway I will consider registering on arbitrary
other bug trackers in the meantime as a
I will be deleting all attachments, unless you think any of them are
strictly necessary?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1908064
Title:
[Multiple bluetooth
Thanks for the suggestions. Closing the settings window makes the
problem disappear. Good call.
Unlike the reporter in the linked bug I wouldn't exactly call that a
"solution" (and certainly not "simple") since there is very little
chance I would consider closing the settings window before
Public bug reported:
Constant stuttering sound, stuttering at maybe 10 times/second. More
than one speaker with the same symptoms.
Speakers work in Windows 10 / macOS 10.14+ running on same hardware.
Same speakers work on Ubuntu Mate 18.04 32 bit running on different
hardware.
Remote control
So where can one find the desktopManager.js file that would need the
fix? I can't find a single mention online of where system bundled gnome
extensions are located.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
A glance through journal.txt did not give me confidence that it wasn't
bleeding all sorts of info, since my name was on every line.
Here's a relevant excerpt:
```
I can recreate the crash at will so I can do that zero to many times
depending on what you need.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1906919
Title:
Saving a file in
Thank you for demonstrating interest. Here is the link that you
requested:
https://errors.ubuntu.com/oops/b287c9e0-3850-11eb-86ea-fa163e6cac46
More info:
The crash only happens when saving a file residing on the desktop. Upon saving,
the entire desktop blinks, suggesting some heavy-handed
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1906919/+attachment/5441353/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1906919/+attachment/5441356/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1906919/+attachment/5441355/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1906919/+attachment/5441354/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected groovy wayland-session
** Description changed:
When saving a file in gedit (or whatever the default text editor is) it
crashes my entire desktop, and I end up on the login screen.
ubuntu 20.10
+ ---
+ ProblemType: Bug
+ ApportVersion:
I tried, but I apparently used the wrong account and now it just refuses
every time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1906919
Title:
Saving a file in gedit crashes
39 matches
Mail list logo