(In reply to NolanK from comment #193)
Just to set the record straight: The fork you mentioned did NOT fix this
bug. If fixed bug 1690395 with the (hacky) fix suggested in bug 1690395
comment #13. We agree 100% with the statement from bug 1690395 comment
#31.
--
You received this bug
The window just never appears, no error message that I can see
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885369
Title:
Deja Dup won't start from GNOME applications menu
To manage
It doesn't seem like it: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/tree/debian.raspi/config/config.common.ubuntu?h=raspi#n7282
I'm currently trying to recompile linux-image-5.4.0-1008-raspi on RPi4
with USB_DWC2_DUAL_ROLE=y
--
You received this bug notification
Really nice information. You can get tech help at a remote location
through https://www.canonprintersupport247.com/blog/fix-canon-printer-
error-code-e31/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
problem occurred becauuse symlink /initrd.imgpointed to old disco
initrd, resolved by forcibly recreating it, for now...?
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: initramfs-tools 0.133ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname:
as of this morning's updates, this problem seems to have disappeared.
I've been able to log out and back in several times to my ubuntu wayland
session, at least on my i915 machine (the dell laptop).
nb: this morning's updates updated gnome-session-bin and ubuntu-session
to 3.33.92-1ubuntu1, gdm3
My point regarding gnome-session-wayland.target is that if we're seeing
different filenames for that file (assuming they're functionally the
same) and mine definitely comes from gnome-session-bin, does that
suggest we're running different gnome-session-bin versions? And seeing
as you're not
minor contextual note: It took me a little while to get the other
machine, ssh in (offending ssh key to resolve), call up this page to
remind me of the exact commands. The point of which is to say, these
weren't taken *immediately* after the logout, but at least a minute
later, certainly beyond
journalctl -b output as attached
loginctl as below:
rachel in ~ at rainbow
➜ loginctl
SESSION UID USER SEAT TTY
1 1000 rachel seat0 tty2
3 1000 rachel pts/0
2 sessions listed.
rachel in ~ at rainbow
➜ loginctl show-session 1
Id=1
User=1000
Name=rachel
Timestamp=Tue 2019
It is definitely /usr/lib/systemd/user-gnome-session-wayland.target.
dpkg -S on that file gives gnome-session-bin which is on version
3.33.90-2ubuntu2. dpkg -S on the .service file gives no match.
This problem didn't start on upgrade to the 5.2 kernels, which happened
a few weeks(?) earlier, but
With --systemd removed as directed I still ended up stuck on a black
screen, except this time it had a flashing white text cursor in the top
left.
(BTW reboots occurred between each test, somewhat perforce...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I tried (just now) deliberately leaving it longer than 30 seconds to
come back after a logout. In fact left it longer than 60 seconds.
Nothing happening. I wasn't logged in via ssh as well at the time (I
hadn't thought the systemd --user instance was related to the ssh
session before so presumably
the i915 one (Dell XPS 13 9370) is the one with automatic login enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841915
Title:
black screen, unresponsive, after logout from gnome Wayland
As attached.
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286165/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
... and the other affected machine (just checked it's still affected
today after latest updates)
** Attachment added: "lspcik-dell.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286167/+files/lspcik-dell.txt
--
You received this bug notification because you
Only affects Wayland sessions, not x11. I should have mentioned it
earlier, it's been my default for some time now (because #1827428 which
still affects latest 19.10) and I forgot.
It also seems not to be the upstream bug, unless the discussion there is
going off in the wrong directions. They now
there are no crash files relating to when this happens. Currently
sitting at the machine that *doesn't* have autologin enabled, where it's
just happened again, there is nothing in /var/crash relating to this.
(nextcloud client keeps crashing, and there are crash files relating to
that, the most
additionally as it does seem to involve console switching and you might
think kernel to be relevant to that, i tried again after the most recent
kernel upgrade in 19.10 (5.2.20-15-generic). no change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Network connection does not die. (It appeared to first time but I think
that's just my ongoing random - and irrelevant here - avahi issues on
this machine.)
But gnome-shell is *not* running after triggering the bug, so sudo
killall on it just produces "gnome-shell: no process found". So that was
Public bug reported:
on logout the screen is black, the system is unresponsive and has to be
restarted. (Untested by me yet, but I expect ssh-ing in and restarting
gdm would work.)
I believe this may be already reported upstream here:
https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's
A bit more detail to reproduce this that I think was missed out before:
It happens when the configured desktop mode/scaling is set to a
fractional value. You can have that experimental xrandr setting set, but
be configured to scaling of 100% or 200% (but see below on latter) and
you won't see
My bug got marked a duplicate of this one but with the latest change
that might be wrong: It affected me on a machine with AMD graphics, not
nVidia. BTW I recently tried it again on the offchance it had been fixed
since (by re-enabling the xrandr scaling setting), and it had not. Also
not fixed on
Hello?
Still affecting Disco.
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770915
Title:
command not found: -antigen-env-setup
To manage notifications about this bug go
NB: Post-upgrade upgraded to nvidia-driver-418 from restricted (didn't
re-enable graphics-drivers ppa) and all so far seems well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831070
Title:
Public bug reported:
Just happened trying to upgrade a machine in two immediate steps
bionic->cosmic->disco.
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: nvidia-dkms-390 390.116-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ditto upgrading in two steps bionic->cosmic->disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827099
Title:
package shared-mime-info 1.10-1 failed to install/upgrade: triggers
looping,
It does appear to be related to the xrandr scaling experimental feature,
after all. Revert that to default and the issue disappears. Guessing
that probably makes it a mutter bug, and being of an experimental
feature at that is hopefully of interest to someone but not urgent. In
view of that didn't
difference. In the
Displays Prefs there is no second "Unknown" display to disable. (The
machine has precisely one display, and that's all Settings sees. It's a
desktop, not a laptop, and it only has an AMD Vega integrated graphics.
It also has only one mouse.)
rachel@twilight:~$ xinput --list
⎡
Public bug reported:
This looks like a truly ancient bug: #12072. And a slightly less ancient
one #38535. But here it is in 19.04.
Every time I log into gnome, I see a "System problem detected" dialog. I
click on the button to report the problem, and the dialog disappears.
While the dialog is
i didn't freshly install to see it but i did create a new user, to be
sure I had utterly default settings and yes, it's there right from the
get-go with certain apps including terminal. but only in x11 (which of
course *is* still the default in ubuntu). I switched to wayland and this
problem went
mutter 3.30.2-1~ubuntu18.10.4 doesn't appear to solve this issue in
ubuntu budgie.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering
trying to get that screenshot was how i discovered it *does* appear to
be retaining stuff for a while at least. :-) I'll try to do so next time
I'm there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
actually i think cookies are being held for at least a while, as,
sitting in the cafe, I can log out and in, and even reboot, and get
logged directly back into the hotspot. But when I come back the next day
I'm asked if I even want to accept cookies. It's that being asked to
accept cookies every
i mean literally http web cookies from the portal page. if you ignore
the network login app (as was the case before it worked reliably), it
shows up in your normal browser. This does remember cookies, so you
don't get asked if you want to accept cookies every time you go there.
What the portal
Public bug reported:
This is with respect to the gnome-shell-portal-helper, part of the
gnome-shell package, which opens its own browser window to prompt for a
wifi hotspot login. It all works fine except one little papercut:
Could it remember cookies? So when I go back to the same hotspot most
Bug only affects X11 sessions.
I had a random urge to try out Wayland again. This issue does not arise
in Wayland. Apps that were affected under X11 are taking input focus
quite happily when launched from shell in Wayland.
--
You received this bug notification because you are a member of Ubuntu
it's not generally slow enough for the latter to be an issue. :-) Even
if I just go nice and slow. Click... window opens... it doesn't have
focus... It continues to not have focus until I do something that would
give it focus in the normal fashion, like clicking on it, clicking on
its dock
confirmed, gedit seems to be immune for some reason. pretty much
anything else i tried is not; calculator, terminal, libreoffice,
nautilus...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817924
sublime text, slack also immune, firefox, thunderbird are not... so ok
it's not universal but *lots* of apps are affected, and the pattern
doesn't seem to be gnome/not-gnome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI problem remains with all those extensions removed.
BTW one does tend to notice it most with apps you type into. I first
noticed with terminal, where I'm used to click, then start typing, and
it's suddenly become click, click-again, then start typing. With an app
you'd tend first to click into
NB: If you launch an app from a terminal, eg: gnome-calculator, it
*does* then get the input focus; just not when launched from gnome-
shell. That's why I didn't think it was a mutter bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Observed on upgrading to disco-proposed today...
When launching an app from the dock or from the applications grid (so i
believe it's a gnome-shell thing rather than a dock thing), the app
opens, but does not get the input focus. You have to either click in the
window, or
Follow up comment on the upstream bug pointed to a commit where it
suggests the rp_filter default should actually now be 2 rather than 1:
https://github.com/systemd/systemd/commit/230450d4e4f1f5fc9fa4295ed9185eea5b6ea16e
Think at this point I need to just let you guys talk amongst yourself.
:-)
Reporting back on this:
The opinion there seems to be that the problem is down to the sys
net.ipv4.conf.*.rp_filter values being set to 1 instead of defaulting to
0. This is done in the procps package, and I'm guessing is the way it is
as a protection against IP spoofing. kernel doc page I was
Public bug reported:
As per subject. This package defines the file
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which
defines the uri for the connectivity check to be http://connectivity-
check.ubuntu.com
This hostname does not resolve to an IPv6 address. Therefore, even if
the
As it recurred again today and showed no signs of correcting itself like
it did on Friday, I went ahead and reported it upstream, here:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Noted. I see there's no report of anything similar already, and if it
was the sort of problem it looked like to me, people would be screaming
blue murder about it, so I think I'll wait and see if it recurs or
becomes an ongoing problem, rather than a one-off. Maybe my LAN was
having a bad hair
this:
rachel@rainbow:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG60000 wlp2s0
0.0.0.0 192.168.1.254 0.0.0.0 UG20100 00 enp63s0
True. And I can confirm it's not listed in my plugins at all. (There's
just Cisco OpenH264 and Widevine). Only potentially-relevant extension
is Disable HTML5 Autoplay, which if anything should *stop* any video
being played before it gets to the software that does it.
Only other thing that
I agree it's a bit of a nightmare. It was the start of the day and I
literally just had Firefox-Next open, and Slack (using the app, not via
Firefox). No video had been posted to slack. I can only think some
random embedded video went by on the timeline or activities column in
tweetdeck (the
Sure, just thought I'd better say something as it was my report
originally. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723615
Title:
gnome-shell crashed with SIGSEGV in
FWIW I can't reproduce this any more either; since 18.04 in fact I've
had no problems with gnome-shell crashing. The monitor very nearly
always does wake up when it's supposed to now (some difference in the
dpms signal being sent? Previously it would always wake for windows and
just had a hard
FWIW I have *not* seen this since upgrading to Bionic. It was probably
fixed sooner, when they said it was, but at some point I gave up on
Artful because of various gnome-shell problems including this, went back
to Mac, and tried again with a fresh Bionic install, where they almost
all seem to
Public bug reported:
The Software app launched by itself this morning to offer me a system
firmware (uefi bios) update of my Dell 9370. Presumably in its role as a
front-end to fwupd. That's not the bug, that's brilliant, that's pretty
much my last remaining reason to keep a Windows partition
I hid my earlier posts because I reckoned they were noise, tbh. This one
less so. :-)
I have replaced the firmware files with those from the windows driver as
described above and in the linked-to askubuntu. It worked brilliantly
for a few days, no problems at all, but just now failed: Similar to
typically it waited for me to report that it worked before failing.
Proving a negative blah indeed.
This time my wifi adapter also didn't come back. I suspect this isn't
entirely unrelated as aren't they actually the same physical device? In
fact that almost makes it weird that usually *only*
Catching up as I came at this from another direction. Having got a
Windows-installed XPS 13 9370 and installed 18.04 freshly on it itself,
its default suspend mode is s2idle, which means lots of battery life
gets lost while suspended. But no bluetooth problems. See askubuntu:
** This bug is no longer a duplicate of bug 1763892
144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767264
Title:
Window
*** This bug is a duplicate of bug 1771501 ***
https://bugs.launchpad.net/bugs/1771501
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libapparmor1:amd64 2.12-4ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libapparmor1:amd64 2.12-4ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptdaemonVersion: 1.1.1+bzr982-0ubuntu19
Architecture:
Related, but not the same as in Ubuntu this is affecting xorg as well.
Not just wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767264
Title:
Window manager refresh rate is different from
Can confirm this is an issue in ubuntu 18.04. Also affects Ubuntu Budgie
(reported it here: https://bugs.launchpad.net/ubuntubudgie/+bug/1767264)
which uses the same window manager as gnome shell (mutter).
Animations/window dragging are locked to 60fps regardless of actual
monitor refresh rate
belately thought of trying: running sudo update-initramfs -k all -c
produced no errors for both currently installed kernels:
rachel@spitfire:~$ sudo update-initramfs -k all -c
update-initramfs: Generating /boot/initrd.img-4.15.0-21-generic
update-initramfs: Generating /boot/initrd.img-4.15.0-20
Public bug reported:
kernel upgrade appeared to go OK actually; on the *second* reboot after
that, this appeared after login.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux
Not sure how relevant, but I tried setting CLUTTER_VBLANK=none to see if
forcing the use of my video card's driver would have any effect, but it
causes the entire desktop to freeze and need to be force closed.
** Description changed:
Ubuntu Budgie 18.04
+ budgie-desktop 10.4
The refresh
Public bug reported:
(This may actually be an Empathy problem, as I understand it's providing
the backend)
If an IRC server allows for an SSL/TLS connection (eg: it's a ZNC
proxy), but is using a self-signed certificate, Polari, correctly the
first time, shows a dialog asking if I want to
to use KDE back in the day.
--
Rachel
On 15/03/18 13:39, dwilches wrote:
>
>
> Rachel, no need to switch to Mac to avoid this problem. What I ended up
> doing was this:
>
> $ sudo add-apt-repository ppa:kubuntu-ppa/backports
> $ sudo apt update && sudo apt upgrade
Well, my bug #1756036 just got (automatically-i-think) marked as a
duplicate of this one, and I'm on 18.04 (gnome-shell 3.27.92-0ubuntu1)
So that's one, Daniel. ;-) I'd been getting this on some mornings, but
the bug report was getting rejected because of outdated packages until
this morning.
*** This bug is a duplicate of bug 1724439 ***
https://bugs.launchpad.net/bugs/1724439
Daniel's latest comment on that bug shows that it looks like it doesn't
affect 3.27. This is 3.27. It's a shame those attachments got deleted...
--
You received this bug notification because you are a
Public bug reported:
There's an ongoing issue with gnome-shell crashing during or on exit
from screen lock. I am no longer able to report when this happens
because apport silently refuses to send the bug report.
If the automatic whoopsie dialog opens at all (it doesn't, often), and I
click to
It failed to hold true on day 2 anyway, as today the session didn't
survive the overnight sleep. But in any case I re-checked the bug of
mine that was marked a duplicate of this one, and saw as it was during
one of my brief try-outs with wayland, is irrelevant to my current
gnome-session woes, as
Interesting
For what it's worth: On seeing #44 I tried turning off notification
popups and lock screen notifications and left it overnight. On waking I
had the usual problems I often (not always) have with my monitors
persuading them to wake up (one of them is a model with a known issue
with
In fact I'm already on 387.22 which, I see from a nearby post on the
same forum, has the same fix:
https://devtalk.nvidia.com/default/topic/1025794/unix-graphics-
announcements-and-news/linux-solaris-and-freebsd-driver-387-22/
It hasn't helped.
TBH I don't think it applies as (fx: me reading up
Just poking in to say this is still happening, and not magically fixed
by Artful's release date. It happened today, but trying to ubuntu-bug
the crash file failed. (It just quit when I clicked Continue.)
One difference today: Thinking maybe my screen-sleep woes were partly
because of gnome shell
... and they survive at least a short screen lock too. Sorry for the
multiple posts. Everyone ignore when anyone says to install sni-qt to
fix qt app indicator issues. it doesn't, it makes things worse! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
just as an aside, relating to comments #13 and #14... removing sni-qt
*did* help. I have my appindicators back in xorg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712866
Title:
icons from qt
(confirmed stays fixed after a longer sleep (actual suspend) too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712866
Title:
icons from qt applications disappear after screen lock/sleep
To
Confirmed on my Wayland system: after a short lock-screen test, both my
qt indicators, enpass and nextcloud-client, survive the lock period.
With respect to another comment above, both of these are the wrong size,
the nextcloud one being half its proper size, and the enpass one being
the correct
i have sni-qt installed already, i believe as a result of following an
earlier hint to the same effect. It didn't actually have any discernible
effect for me. (In fact, I wonder if I should remove it...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I definitely have 17.10.2 installed, from proposed.
On my Xorg system: In fact since this bug was first reported, things
have actually gotten worse, in that these days these icons hardly ever
appear *at all* from the original login, let alone disappearing after a
screen lock. 17.10.2 hasn't fixed
Yes, I see what you see: the borders around the tabs are missing. Not
just on the Security prefpane, on all of them, that have tabs.
But that's all that's wrong. (Or at least all that's obviously wrong.)
So while I can corroborate you, I think it's a different error and
should have a separate bug
Attached.
I'm using the Arc theme across the desktop, but no Thunderbird theme (or
rather, the default).
** Attachment added: "Screenshot from 2017-10-19 18-44-31.png"
Looks fine to me in 1:52.4.0+build1-0ubuntu2. I see the tabs just as
they are in the other pref panes.
Even if not, it would be a highly localised and minor problem, not at
all like the completely broken, unusable user interface, with large
parts missing or unstable, that we had as of the
Adding this to *this* bug, despite the "Fix Released", because it
exactly matches the original post for this bug, whereas the others I've
encountered and reported on are different:
Oct 14 20:02:45 fleetfoot gnome-shell[12750]:
meta_monitor_manager_get_logical_monitor_from_number: assertion
bug #1723615 came up with this fix in place. Whack-a-mole! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
I had one crash after applying this yesterday (and rebooting): it
crashed right out to the console, not even to the login screen, and when
I tried logging in again the session failed to start. But since a second
reboot it's apparently been fine. This bug went away, and so too has my
bug #1720149
Public bug reported:
This may relate to this item in the changelog for this version of gdm3:
* Drop 95_hide_x11_sessions_with_nvidia_kdms.patch:
- No longer needed with nvidia-384
I noticed before this version that indeed, if I enabled modeset on
nvidia-387 (which actually worked), I only
It just happened, so attached the crash file that was generated. NB:
gnome-shell 3.26.1-0ubuntu2
mutter 3.26.1-1
libmutter-1-0 3.26.1-1
NB: I notice there's also a libmutter-0-0 installed, possibly a hangover
from the original zesty install. but ldd $(which gnome-shell) indicates
it's linked to
I’m afk today but will try to get this information on Wednesday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720149
Title:
gnome-shell segv on wake from display or system sleep
To manage
That wouldn't surprise me. I've seen other reports, on IRC, to the same
effect. Sadly, displayport is not optional here, not if I actually want
to run my monitors at full resolution.
Someone mentioned it being a "known bug" in mutter? However they didn't
link to it and I wasn't at the keyboard at
Seems to have gone away with recent upgrades. I can't tell exactly which
as I was attempting to use wayland under amd and even under nvidia-387
(which worked fine except for a couple of random system freezes during
closing windows). Back on nvidia/xorg because of that (although not
exhaustively
Confirmed fixed for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721189
Title:
Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
To manage notifications about this bug go to:
Public bug reported:
I wanted to use GnomeWeb to run Tweetdeck as a saved web application. So
I installed epiphany-browser, navigated to tweetdeck.twitter.com, logged
in, and then attempted to save it as a web application. This all seemed
to work, as well as Tweetdeck itself running apparently
Public bug reported:
I hit p by accident. I'll be removing the keybinding now I found
it, in org.gnome.mutter.keybindings switch-monitor. It's too common a
keystroke I hit when working under macOS that I'm just too likely to hit
it by accident. But that's my problem.
But it wouldn't be a problem
I got here because my apport-raised bug #1721492 apparently
automatically got marked as a duplicate of this. I'm not so sure:
This happened after a kernel upgrade to 4.13.0-14-generic. Yesterday I
was happily using this system in a wayland session using nouveau. On
reboot with this update, all I
/var/log/history.log section as per above post
** Attachment added: "part-history.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1505409/+attachment/4962744/+files/part-history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: rachel 1809 F pulseaudio
/dev/snd/controlC2: rachel 1809 F pulseaudio
/dev/snd/controlC0: rachel
Public bug reported:
Today I learned from omgubuntu how to reset my gnome/ubuntu desktop
settings (dconf reset -f /), and thought I'd do it, seeing as I had
upgraded from a Zesty install at an earlier stage of 17.10's pre-release
period, and further customised as time went on in the normal way of
Attaching second screenshot referred to in original post...
** Attachment added: "Screenshot from 2017-10-02 11-04-16.png"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720760/+attachment/4960369/+files/Screenshot%20from%202017-10-02%2011-04-16.png
--
You received this bug
ok, same symptoms occurred with the default theme. So after all it looks
like the shell theme has nothing to do with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720149
Title:
gnome-shell
1 - 100 of 514 matches
Mail list logo
