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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906919
Title:
Saving a file in gedit crashes desktop
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
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
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906919
Title:
Saving a file in gedit crashes desktop to login
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to 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:
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't know if this is the right package
** Package changed: ubuntu => update-notifier (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908038
Title:
Settings for auto-check for updates
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
*** 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
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 Ubuntu
Bugs, which is
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
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
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
** Attachment removed: "AlsaInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443423/+files/AlsaInfo.txt
** Attachment removed: "CurrentDmesg.txt"
*** 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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908064
Title:
[Multiple bluetooth speakers, playback]
Thanks for your reflection.
You are of course right that there are some problems to overcome, and
that the conversation part is one of them. I don't imagine that any
solutions are going to be immediately apparent, which is why I hope that
someone will start thinking about it sooner rather than
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
Public bug reported:
I have "automatically check for updates" in Software & Updates set to
Never. This is not respected, since the software updater window pops up
regularly prompting about new updates.
Technically it could be that it's literally respected, since it's
possible that the updates
Overly sensitive palm detection was also the only cause I could think
of. Yes, as you suspected all tracking stops the moment it detects "down
palm" even after it has reverted back to only "down". Thanks for the
tool to confirm it!
Thanks for the link, I'll see if I can report it there.
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
Public bug reported:
I performed an upgrade of 20.10 to 21.04 (using the -d option) which
completed successfully and prompted a reboot, and now the boot process
doesn't get past the EFI OS selection screen. Instead I'm treated to a
nice light show from the connected USB keyboard's backlight —
Thanks for the info! You are spot on and -- you guessed it – the
hardware is a MacBook Air 2012, 13".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925814
Title:
20.10 → 21.04 upgrade non booting,
Public bug reported:
I upgraded from 20.10 to 21.04 (using the -d option) and after a
successful upgrade my keyboard layout doesn't work at all anymore
resulting in a system where I'm unable to type properly. I have no idea
which package, nor what other details are relevant.
I used the "Dvorak
I've absolutely no idea which package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926034
Title:
Upgrade from 20.10 to 21.04 makes keyboard layout unusable
To manage notifications about this
Congratulations, that has to be by far the least constructive reply and
action I've ever seen on this bug tracker. Or any bug tracker for that
matter.
If you personally don't know which package it belongs to then at least
have the common decency to let someone who does have an opportunity to
Public bug reported:
Well, strictly speaking I don't know which package I found this bug in.
I only know that the only package that showed up when I searched for the
tool named "ubuntu-bug" is this one. I don't generally know how I'm
supposed to identify a package, especially for a certain
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920776
Title:
Source window raised on drag-n-drop -- drag-n-drop destination window
not raised while
Hello,
It concerns the default file manager as the drag source in Gnome
desktop. X11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920776
Title:
Source window raised on drag-n-drop --
Public bug reported:
Dragging and dropping is pretty difficult owing to the fact that when
you grab something in a window (the source window), e.g. a file in a
file manager window, that source window is put on top of other windows
-- including the intended destination window for the drag-n-drop.
Public bug reported:
I drag an ubuntu 20.10 iso into the source file section, I get a cursor
showing that the action will "+" the file to the list, I let go, and
nothing happens.
I have to click "Other" and unintuitively drag the file into that window
before I can actually add it.
Ubuntu 20.10
Public bug reported:
I don't feel comfortable seeing my backup drives of 1+ TB being listed
alongside actually reasonable destination devices like 8 GB sandisk usb
sticks. It's unnerving just seeing them listed, no matter how
technically correct it might be. I don't want to repeatedly expose
Public bug reported:
When initiating a write to disk, the confirmation dialog asks me if I'm
"sure I want to write the image to the device". That's not actionable
information.
Which device? At this point I want a confirmation that I selected the
correct device, but that's not explicit
** Attachment removed: "UsbCreatorLog.txt"
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1920783/+attachment/5479144/+files/UsbCreatorLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Window raised when drag-n-drop source, window not raised while hovering over
it during drag-n-drop
+ Source window raised on drag-n-drop -- drag-n-drop destination window not
raised while hovering over it
--
You received this bug notification because you are a member of
That might be because I don't know which package it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920776
Title:
Source window raised on drag-n-drop -- drag-n-drop destination window
not
> It would then tell the user "I'm not going to send this request to
samba as it will complain about the share name games already being a
valid system user name".
You wouldn't tell the user that. If the desired result is possible by
avoiding using `net usershare` then by "isolate" I mean "perform
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 Ubuntu
I'm having trouble to determine whether messages are directed at me or
are general discussion of potential fixes. If at me then thank you for
the workaround, although I'm sure the first one will work. Don't worry
about me. If not, it sounds like you've found the problem. It's not
really expected
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
** 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
Well, I don't know much about how bug statuses are used. As I see it you
don't need more info from me so I'm going to assume that the status
definitions aren't accurate here.
What does "incomplete" mean? And "won't fix"?
Does "won't fix" include:
- Not putting any pressure on samba to make
/etc/samba/smb.conf is attached. I have not touched it since system
install afaik.
This is the first time I try to share anything on the system. The only
existing share I can see in Files is "$print" so I have no immedately
tangible clue as to why it should refuse.
I also tried sharing with the
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
Hello,
Thank you for your reply.
Thanks for clarifying. Just trying to follow along in the reasoning and
gauge what kind of bug reports have any effect and are worth reporting
in the future.
You are right, samba seems to have been installed by me and is
technically not part of Ubuntu. Managing
I've no idea which package and dont want to risk immediate closure by
guessing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936199
Title:
Monitor wakes to login screen a few seconds after
Public bug reported:
"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.
It is not constructive to obscure menus and tooltips with always on top
windows any
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
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.
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938596
Title:
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938596
Title:
Always
** 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: "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
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
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
apport information
** Tags added: apport-collected impish wayland-session
** Description changed:
Suspend has worked fine previously, where I press the power button and
my MacBook Air (2012) goes to sleep.
Now, after pressing the power button, the screen turns off for a few
seconds
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532203/+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/1936199
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532204/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532205/+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/1936199
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532206/+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/1936199
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532208/+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/1936199
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532207/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936199
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532215/+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/1936199
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532214/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532216/+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/1936199
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532217/+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/1936199
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532218/+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/1936199
Title:
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532220/+files/acpidump.txt
** Description changed:
Suspend has worked fine previously, where I press the power button and
my MacBook Air (2012) goes to sleep.
Now, after
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532219/+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/1936199
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532209/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936199
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532210/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936199
Title:
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532211/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936199
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532213/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1936199/+attachment/5532212/+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/1936199
Private bug reported:
When the system is suspended it will wake at exactly 15 minute intervals
to display the lockscreen. Seemingly indefinitely.
Both the "automatic suspend" setting and the "empty/clear screen"
setting in system power settings are set to 15 minutes.
I have not tried changing
Public bug reported:
Reporting a bug using ubuntu-bug invariably seems to attach my system
username to the bug description. If I try to edit that description in
order to remove the username, it succeeds, but I'm not informed that
every version of the description is being saved and published
Public bug reported:
Suspend has worked fine previously, where I press the power button and
my MacBook Air (2012) goes to sleep.
Now, after pressing the power button, the screen turns off for a few
seconds and then I'm presented with the login screen. No matter how
carefully I press the power
87 matches
Mail list logo
