I have billions of
Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: Error
executing command as another user: Not authorized
Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: This
incident has been reported.
Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDae
Are you using any gnome-shell extensions? If so then please try
uninstalling all of them, and reboot.
--
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/1816896
Title:
Laptop (HP E
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1816896/+attachment/5240525/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1816896/+attachment/5240526/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
https://bugs.launchpad.net/bugs/1816896/+attachment/5240527/+files/modified.conffile..etc.gdm3.custom.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
apport information
** Tags added: apport-collected
** Description changed:
This problem is new in Ubuntu 18.10; it did not occur with 18.04.
When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics,
comes out of resume, often the UI is unresponsive. Typically I get a
bla
** Changed in: gdm3 (Ubuntu)
Status: Expired => New
** Changed in: gnome-shell (Ubuntu)
Status: Expired => New
--
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/180940
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpa
Personally, I have not encountered that when using ubuntu or fedora and
simply swapping gdm3 for lightdm but it's good that the other bug report
has a fix. It looks like a hidpi bug; none of my monitors are hidpi.
On Thu, 21 Feb 2019 at 12:50, Stefano <1716...@bugs.launchpad.net>
wrote:
> The pro
The mouse cursor moving is handled by the Xorg process, so if nothing
else is responding then that suggests the problem is entirely in gnome-
shell.
To start, please run this command to send us more information about the
machine:
apport-collect 1816896
** Package changed: xorg-server (Ubuntu)
Thanks for the quick response.
It sounds like the bug(s) would still exist in the latest mutter/gnome-
shell code so please report the problem to the Gnome developers here:
https://gitlab.gnome.org/GNOME/mutter/issues
and then tell us the new issue ID.
--
You received this bug notification b
The problem with the lightdm workaround is that many had this cursor
issue:
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1770948
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad
No problem. There's a working patch (apparently) in the Mesa bug:
https://bugs.freedesktop.org/show_bug.cgi?id=109594
** Changed in: totem (Ubuntu)
Status: New => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a
In that case I would agree with the theory this is likely nvidia-related
(or a new regression).
The only other yardstick I have at the moment is my bionic desktop for
which gnome-shell has been running for 5 days and RSS=293MB.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Package changed: gnome-control-center (Ubuntu) => xorg-server
(Ubuntu)
** Package changed: xorg-server (Ubuntu) => gdm3 (Ubuntu)
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop
You have been subscribed to a public bug:
This problem is new in Ubuntu 18.10; it did not occur with 18.04.
When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics,
comes out of resume, often the UI is unresponsive. Typically I get a
black screen, a screen with just the GNOME top b
Sebastien Bacher, could you create a [0]package with the version of [1
]"gnome-keyring 3.31.90"? My intention is to confirm or inform what
happens with this version of the application. Thanks!
[0] https://people.canonical.com/~seb128/lp1816458
[1] https://gitlab.gnome.org/GNOME/gnome-keyring/tags/
Yes I was talking about the gdm3 workaround
--
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/1716857
Title:
gdm3, hybrid nvidia with modeset=1, no external monitors detected
To manag
Public bug reported:
This problem is new in Ubuntu 18.10; it did not occur with 18.04.
When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics,
comes out of resume, often the UI is unresponsive. Typically I get a
black screen, a screen with just the GNOME top bar, or what the scree
There are two workarounds mentioned: swap to lightdm and manipulate gdm3
start. I think you refer to the gdm3 startup changes when you say it causes
problems with suspend/resume (which I didn't try).
The other workaround is changing display manager to lightdm (or sddm, the
KDE display manager).
swa
In the current 19.04 (disco) it works well.
On feb 20 2019, at 1:29 du, Balázs Pere wrote:
> When I choose a certain file type, the correct hits appears for a second, but
> after that all hits come back.
>
> On Feb 20 2019, at 1:28 pm, Balázs Pere wrote:
> > New packages in
> > https://launchp
This bug was fixed in the package shotwell - 0.30.2-0ubuntu1
---
shotwell (0.30.2-0ubuntu1) disco; urgency=medium
* New upstream version
- Fix issues with google and flickr not being able to log in
(lp: #1620336)
* debian/patches/git_notification_segfault.patch:
- re
Yes but this workaround is going to create others issue for suspend and
resume.
--
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/1716857
Title:
gdm3, hybrid nvidia with modeset=1, no
Daniel,
I tried Bloom on Ubuntu 18.10 and things have partially improved. Left
mouse clicks inside the text boxes now move the current selection point in
the text as expected. Left clicking on the gear button usually brings up
the Styles dialog (a javascript dialog), but the next left click alway
This happens now on 18.04. I can use the shares from a Linux machine for
several hours after reboot. But eventually it will stop working getting
above error message.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launch
Created attachment 143415
libdrm_ignore_deadlock
--
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/1797882
Title:
At dual monitor intel_do_flush_locked failed: Resource deadlock
Created attachment 143414
fix intel_blit.c
fix error_patch2
--
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/1797882
Title:
At dual monitor intel_do_flush_locked failed: Resourc
Some more investigation, understanding and adding 2 other possible fixes for
the problem.
The problem occurs at Ubuntu 18.10 only at gdm3 with wayland using dual monitor.
It is not occuring with wayland at single monitor.
It totally doesnot occur if gdm3 is not using wayland.
At ubuntu 18.04 the s
Never stop the process 'gnome-keyring-daemon', I must close it with
'kill -9 '.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1816458
Title:
Full load
To manage notificatio
Should be fixed with https://gitlab.gnome.org/GNOME/shotwell/issues/97
** Changed in: shotwell (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchp
** Also affects: gnome-terminal (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** No longer affects: gnome-terminal (Ubuntu Xenial)
--
You received this bug notification because you are a member of
** No longer affects: libdrm (Ubuntu)
** No longer affects: xserver-xorg-video-intel (Ubuntu)
** Bug watch added: freedesktop.org Bugzilla #109594
https://bugs.freedesktop.org/show_bug.cgi?id=109594
** Also affects: totem via
https://bugs.freedesktop.org/show_bug.cgi?id=109594
Importanc
Upstream might have an idea but there is nothing special in those
backtraces, is seems to just be waiting for event, were they taken at
the time of the issue when happening?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring
't a a bt' worked. Do you need any other information?
** Attachment added: "gdb-gnome-keyring-daemon-v4.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240218/+files/gdb-gnome-keyring-daemon-v4.txt
--
You received this bug notification because you are a
When I choose a certain file type, the correct hits appears for a
second, but after that all hits come back.
On Feb 20 2019, at 1:28 pm, Balázs Pere wrote:
> New packages in
> https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16410497
> leaves unchanged this bug.
>
> On Feb 19 20
It seems to work well. Sometimes it hang up, shows "searching" in the
right bottom corner of nautilus window. If I delete back some characters
in the input field, it starts to work again.
On Feb 20 2019, at 9:11 am, Sebastien Bacher wrote:
> Yes, it's fixed in the Disco serie, I've uploaded a tes
New packages in https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/ppa/+build/16410497 leaves unchanged this bug.
On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote:
> Indeed, that seems fixed in the current Ubuntu serie but buggy in
> bionic, potentially something we want to fix in a SRU
>
>
*daemon
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1816458
Title:
Full load
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome
't a a bt' worked. Do you need any other information? Please, just let
him know.
** Attachment added: "gdb-gnome-keyring-daemon-v3.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240207/+files/gdb-gnome-keyring-daemon-v3.txt
--
You received this bug not
** Attachment added: "gdb-gnome-keyring-deamon-v2.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240206/+files/gdb-gnome-keyring-deamon-v2.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
't a a bt' worked. Do you need any other information? Please, just let
him know.
(gdb) t a a bt
Thread 5 (Thread 0x7f3c397af700 (LWP 3618)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f3c3bf8aa3a in g_cond_wait_until (cond=cond@entry=0x5570a0d86c08,
mutex=mutex@e
't a a bt' worked. Do you need any other information? Please, just let
him know.
** Attachment added: "gdb-gnome-keyring-deamon.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240204/+files/gdb-gnome-keyring-deamon.txt
--
You received this bug notificat
Uninstalling all extensions did not seem to make a difference; the
gnome-shell process is back up to 10G RSS after an hour.
--
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/1815550
@robert-ancell, I addition of this interface to the ubuntu-master,
ubuntu-3-30, and ubuntu-3-28 branches as well as snap-store. Can you
please include this in your next round of SRUs for cosmic, bionic and
xenial? I wasn't sure which branch to use for xenial.
** Also affects: gnome-software (Ubu
While I am working on multiple different performance problems right now,
startup time is not one of them.
Can you please focus this bug (reword it) to be about one specific
problem? And log new bugs for other problems.
Is the load time of Firefox the main problem? If so, then do other apps
launch
The text is for the original Linux kernel SRU, Artful and earlier.
--
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/1745032
Title:
AC adapter status not detected on Asus
one shouldn't make promises. Follows ASAP. Give me a few days.
--
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/1813825
Title:
"driverless" printer workflow has bad usab
The issue is with systemd, /lib/systemd/systemd-timedated is part of
that package
What's the output of those commands
- dpkg -l | grep systemd
- debsums systemd
?
** Package changed: gnome-control-center (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member
** Package changed: ubuntu => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Tags added: performance
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.la
You have been subscribed to a public bug:
My Ubuntu 18.4 is very slow and take time to load like Firefox and other
thinks on my laptop and it most be a bug in the system.
Regardes
Jan Hallholm Sweden
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignatu
Yes, it's fixed in the Disco serie, I've uploaded a test package to
https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/ppa/+build/16410497
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.n
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic)
Status: In Progress => Fix Released
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1816702
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
your gdb prompt shows you managed to attach the process, can you try to
type 't a a bt' instead if 'continue'?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1816458
Title:
F
How do you envision it to work? Having a split screen which twice the
same page on the left/right for example? What's the usecase?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bug
56 matches
Mail list logo
