The fix suggested by hgrie works for me. ibus-setup is running ibus-
daemon, which immediately fixed the issue and lasts until logout.
I note that adding 'ibus-daemon --xim' as a startup application is a
permanent fix for the issue in my case.
--
You received this bug notification because you ar
I tried steps 1, 2 and 3, but it doesn't change a thing: the crash
occurs, the message "totem: Fatal IO error 11 (Resource temporarily
unavailable) on X server :1." is spawned in the terminal, but no .crash
file is generated.
--
You received this bug notification because you are a member of Ubunt
OK. Can you please attach a log file showing the IO error with some more
context?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1780475
Title:
Fatal IO error 11 on totem startup whe
Hello Jeremy, or anyone else affected,
Accepted evolution into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/evolution/3.28.5-0ubuntu0.18.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Sorry Daniel, I don't understand what you need. The bug occurs
immediately after I try to launch totem:
juloliv@juloliv:~$ totem
Gdk-Message: 10:52:39.290: totem: Fatal IO error 11 (Resource temporarily
unavailable) on X server :1.
There is no particular "context": it crashes all the time, as so
There is an ongoing bionic SRU in bionic-proposed still. Please help
verifying it as without it release we can not proceed with reviewing
this upload.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bu
** Also affects: nautilus (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1713581
Title:
nautilus crashed with SIGSEGV i
Can we escalate this issue somehow? Where does it have to be fixed?
Upstream?
What about certification? Can that help to escalate the issue?
- https://certification.ubuntu.com/hardware/201712-26045/ (ThinkPad X1 Carbon
6th Generation)
- https://certification.ubuntu.com/hardware/201603-20841/ (De
Sorry, I spend so much time debugging Xorg server crashes that for a
moment I forgot this was about totem...
Please try running the following commands before running totem:
ulimit -c unlimited
export GDK_SYNCHRONIZE=1
totem
Hopefully the crash still occurs.
Now look in either:
* the cur
** Also affects: nautilus (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1782681
Title:
Upgrade to 3.26.4 and SRU it
T
Is there any reason why suddenly the version number for the SRU is
1:3.26.4-0~ubuntu18.04.1 ? Not sure we ever had a scheme like this
before. To me it seems like the security-team's versioning of
1:3.26.4-0ubuntu0.18.04.1 would fit better and be more consistent with
what we have in other series.
Yes. To escalate the issue please report it to the Gnome developers
here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues
and then tell us the new bug ID.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a memb
Anyone?
This is clearly a bug in Nautilus
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1783364
Title:
Preference 'recursive-search' is ignored when set to 'never'
To manag
I've done that and the bug still occurs, but it doesn't generate any
core or crash file.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1780475
Title:
Fatal IO error 11 on totem star
Public bug reported:
Ubuntu 18 shows only black output on 3 monitor display screencast. I'm
using desktop with videocard with 3 display output (HDMI, VGA, DVI). On
dual monitor, screecast works fine while on 3 monitors the output is
only black screen.
** Affects: gnome-shell (Ubuntu)
Importa
...I actually see this is some versioning scheme used by the desktop
team for gnome-related packages (just saw it in mutter as well). Seeing
that Robie approved of uploads with this versioning fir mutter, I
suppose you can re-upload it without changing the version number...
--
You received this b
I just had this on 18.04 after applying this upgrade via software-
updater. At least I think that's the cause.
Start-Date: 2018-08-13 08:00:02
Commandline: aptdaemon role='role-commit-packages' sender=':1.123'
Install: linux-image-4.15.0-30-generic:amd64 (4.15.0-30.32, automatic),
linux-headers-
GNOME Shell bug #480 created, https://gitlab.gnome.org/GNOME/gnome-
shell/issues/480
--
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/1765356
Title:
"Show Applications" button tr
apport information
** Tags added: apport-collected bionic
** Description changed:
I found a bug in ubuntu At the login screen
buster/sid
Linux 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
I use my work laptop and today when I came ba
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1786046/+attachment/5174712/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bug
Can you clarify what applet?
Can you take photo and attach it here please.
--
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/1786694
Title:
calendar applet doesn't connect wi
** Merge proposal linked:
https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352973
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1782152
Title:
GDM
** Merge proposal linked:
https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352973
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU:
** Merge proposal linked:
https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352976
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1782152
Title:
GDM
Here is their answer:
> The default Ubuntu session is not upstream GNOME. In particular
> the dash is replaced with a Unity-style dock, so please test
> with the non-default "pure GNOME" session first.
Can the team at Canonical that deals with the Unity-style dock verify
the behavior is not intro
** Merge proposal linked:
https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352976
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU:
** Tags added: bionic cosmic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1767431
Title:
restore type-ahead find, again
To manage notifications about this bug go to:
https://bu
** Tags added: bionic cosmic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1164016
Title:
restore type-ahead find
To manage notifications about this bug go to:
https://bugs.laun
Sorry, but I forgot one thing.
When the screen turns black, I can recover the graphical session
switching between a virtual console and the console that is supporting
the graphical session with alt+control+f5 and alt+control+f2 or
alt+control+f1.
No issues with nomodeset so far.
--
You received
I can't completely understand what GNOME developers are trying to achieve!
This functionality was used for years.
Ubuntu 14.04 LTS and 16.04 are not affected.
But 18.04 LTS and 18.10 are trying to perform search after entering first
letter.
The patch for Nautilus in 18.04 LTS is available (see
You have been subscribed to a public bug:
When: adding a new VPN connection under: VPN type "Password"
Problem: the "Save" button remains greyed out unless a "CA Certificate" is
chosen.
Expected solution: a way to disable the "CA Certificate" setting.
Comments:
My VPN provider (TU Darmstadt) do
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Sounds like this is a problem with the Network Manager OpenVPN plugin
rather than OpenVPN itself, so I'm retasking the bug.
** Package changed: openvpn (Ubuntu) => network-manager-openvpn (Ubuntu)
--
You receive
** No longer affects: 0ad (Ubuntu)
** No longer affects: libproxy
** No longer affects: libproxy (Ubuntu)
** No longer affects: cjs (Ubuntu)
** Project changed: cinnamon-project => cjs (Ubuntu)
** Changed in: cjs (Ubuntu)
Importance: Unknown => Undecided
** Changed in: cjs (Ubuntu)
*** This bug is a duplicate of bug 1164016 ***
https://bugs.launchpad.net/bugs/1164016
** This bug has been marked a duplicate of bug 1164016
restore type-ahead find
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in U
> I can't completely understand what GNOME developers are trying to achieve!
> 18.04 LTS and 18.10 are trying to perform search after entering first letter.
The underlying assumption seems to be that when you type the name of a
file, the only thing you may possibly want is to search for that file,
Public bug reported:
Steps to reproduce:
1. have `file1` somewhere
2. make symbolic link to `file1` as `symlink1` (for example with Nautilus:
Create Link or )
3. rename `file1` to new name (now `symlink1` is broken)
4. try to edit `symlink1` properties to point to the new name
Expected results:
Since this versioning was used in some other packages, I've used this,
but if you prefer another versioning we can change that.
I've not strong opinions on that, just I find this more readable.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
I also did some more verification with the graphical frontend and the
apt-clone file restored, and it worked perfectly well, with libc6
upgraded first. Progress reporting was a bit weird as it went to 100%
for the libc stuff, and then down again, but it could be worse.
** Tags removed: verificatio
There is a fundamental difference between search (what you do when you
don't know where something is) and navigate (what you do when you know
exactly where something is, and want to go there). Why the gnome team
have chosen to conflate them, and their mental state while doing so, is
anyone's guess.
Indeed, that was fixed in gnome-shell 3.29.4 while in cosmic we've
3.29.90
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Andrea Azzarone (azzar1)
--
You received this bug notification because you a
Hello Rachel, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Jimmy, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Marco, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Marco, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello errors.ubuntu.com, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new packag
Hello Leon, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Ferdinand, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
https://bugs.launchpad.net/bugs
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.24
---
ubuntu-release-upgrader (1:18.04.24) bionic; urgency=medium
* DistUpgradeController.py: Remove an unnecessary debugging entry when
calculating the debs to remove.
ubuntu-release-upgrader (1:18.04.23) bio
** Merge proposal linked:
https://code.launchpad.net/~3v1n0/ubuntu/+source/glib2.0/+git/glib2.0/+merge/353003
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1764779
Title:
Nau
The verification of the Stable Release Update for ubuntu-release-
upgrader has completed successfully and the package has now been
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the event tha
This bug was fixed in the package libreoffice -
1:5.1.6~rc2-0ubuntu1~xenial4
---
libreoffice (1:5.1.6~rc2-0ubuntu1~xenial4) xenial; urgency=medium
* debian/libreoffice-mysql-connector.triggers.in,
debian/libreoffice-wiki-publisher.triggers.in:
- removed, file path triggers d
I suggested to test with MATE's compositing window manager "marco" also.
Any results?
Another test case would be to use xfwm4 with disabled compositor plus
"compton" (standalone compositing manager).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Marc, do you have logs for
journalctl /usr/bin/gnome-shell
when this happens?
Anyway feel free to open a bug for that.
--
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/1783311
Title:
I didn't try 'marco' because I didn't know what that is. Installing it
now.
totem used with 'marco' and 'compton' are not washed out, but strangely
transparent. See attached image for 'marco' -- compton is the same just
no messages on stderr from compton.
** Attachment added: "totem.with.marco
Public bug reported:
Ubuntu 18.04
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.4
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
gdm3:amd64: Install
libgdm1:amd64: Ins
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1786851
Title:
package gdm3 3.28.2-0ubuntu1.4 failed to install/upgrade: installed
gdm3 package
Looks like the next step would be to test with an older NVIDIA driver
version from the Ubuntu repository, and maybe with the slightly newer
version 390.77 from the NVIDIA website also.
** Changed in: xfce4 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification becaus
What does "status: invalid" mean?
In XFCE > Settings > Additional Drivers > Additional Drivers, it's
currently set to "NVIDIA Corporation GF106M [GeForce GTX 460M] "[x] Using
NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested)".
Other options are "[ ] Using NVIDIA bindary driver
Public bug reported:
In the past week or two, cosmic has failed to finish booting in about
half of all cases (on multiple machines). The problem is that the
graphical login screen never appears. Instead the machine stays on a
text console.
WORKAROUND:
I can force the system to finish booting and
*** This bug is a duplicate of bug 1725384 ***
https://bugs.launchpad.net/bugs/1725384
Sorry, I forgot the Ubuntu dock is a separate component.
Now I look at the Ubuntu dock bugs this sounds like bug 1730281, which
is presently marked as a duplicate of bug 1725384. So this bug should
probably
It looks like the upstream bug is actually:
https://github.com/micheleg/dash-to-dock/issues/196
** Tags added: artful bionic
** Bug watch added: github.com/micheleg/dash-to-dock/issues #196
https://github.com/micheleg/dash-to-dock/issues/196
** Also affects: dash-to-dock via
https://githu
xfce4 (Ubuntu) → Invalid means that Theo believes this bug is not a bug
in xfce4. But it is still a bug in another component(s).
See that task and others at the top of the page.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in
I've tracked down the offending source code:
https://gitlab.gnome.org/GNOME/gtk/blob/master/gdk/x11/gdkmain-x11.c#L242
and unfortunately it will just exit without leaving a crash or dump file
:(
Just an idea: Please try this to see if it stops the problem from
happening:
sudo apt remove mesa-
Interesting. That sounds similar to bug 1786872.
Are you sure your bug title is correct?
"Screen randomly turns black minutes after
successfully login with GDM"
Have you really logged in with your username and password *before* the
bug occurs? Or do you just mean the machine has booted when
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1786046
Title
1. What is the resolution of your monitors?
2. Please run this command to send us more information:
apport-collect 1786757
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
*** This bug is a duplicate of bug 1774039 ***
https://bugs.launchpad.net/bugs/1774039
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1774039, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1766137 ***
https://bugs.launchpad.net/bugs/1766137
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
This seems due to the 0010-set-language.patch in accountsservice. It
means when Settings chooses a locale (e.g. en_US.UTF-8) this is changed
to en_US in accountsservice. When Settings uses this to select the
current language it doesn't match against any entry.
** Changed in: gnome-control-center
Public bug reported:
[Impact]
Changing language in Settings doesn't show currently selected language.
[Test Case]
1. Open Settings
2. Go to "Region & Language" panel
3. Click on "Language"
Expected result:
The list of available languages shows the current language selected.
Observed result:
No
Public bug reported:
[Impact]
Selecting a language from Settings always shows the names in English (e.g.
German) instead of the name in the native language (e.g. Deutsch).
[Test Case]
1. Open Settings
2. Go to "Region & Language" panel
3. Click on "Language"
Expected result:
A list of languages
** Summary changed:
- Languages always shown with english names
+ Languages always shown with English names
--
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/1786881
Title
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1786883/+attachment/5174967/+files/journal.txt
** Description changed:
The cosmic login screen flickers to black a few times on boot and then
finally settles on using Xorg instead of Wayland.
I c
Incomplete. Since I logged this bug gdm3 has upgraded and I get bug
1786883 instead.
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1786757/+attachment/5174969/+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
Public bug reported:
The cosmic login screen flickers to black a few times on boot and then
finally settles on using Xorg instead of Wayland.
I can tell because from ssh user 'gdm' is running:
/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/121/gdm/Xauthority
-background none -noreset -keept
apport information
** Tags added: apport-collected bionic
** Description changed:
- Ubuntu 18 shows only black output on 3 monitor display screencast. I'm
- using desktop with videocard with 3 display output (HDMI, VGA, DVI). On
- dual monitor, screecast works fine while on 3 monitors the output
** Attachment added: "journal2.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1786883/+attachment/5174970/+files/journal2.txt
--
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/
In both cases I see:
Aug 14 11:40:46 kab gnome-shell[890]: X Wayland crashed; exiting
Aug 14 11:49:16 kab gnome-shell[890]: X Wayland crashed; exiting
which would explain why the Wayland option is missing when I finally get
a login screen.
Unfortunately there are no crash files or core dumps :(
Monitor 1 1600 x 900 VGA
Monitor 2 1600 x 900 VGA
Monitor 3 1680 x 1050 DVI
--
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/1786757
Title:
screencast no output on 3 display moni
Please also run these commands and send us the output:
glxinfo
xrandr
--
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/1786757
Title:
screencast no output on 3 display moni
** Attachment added: "journal3.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1786883/+attachment/5174971/+files/journal3.txt
** Summary changed:
- [regression] Login screen flickers to black a few times on boot and then
finally settles on using Xorg instead of Wayland
+ [regress
When you say "screencast" what tool are you using there?
--
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/1786757
Title:
screencast no output on 3 display monitor
To manage noti
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-contro
[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:/
I'm using the built-in screencast by pressing CTRL+ALT+SHIFT+R
--
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/1786757
Title:
screencast no output on 3 display monitor
To manag
See attached xrandr output
** Attachment added: "xrandr output"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+attachment/5174972/+files/xrandr
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ub
See attached glxinfo
** Attachment added: "glxinfo output"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+attachment/5174973/+files/glxinfo
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu
*** This bug is a duplicate of bug 1725384 ***
https://bugs.launchpad.net/bugs/1725384
See also https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1765356
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubu
Thanks.
Your desktop size of 4880x1085 is likely the factor here. I find that
surprising because apparently the AMD Cedar GPU shouldn't max out until
textures reach 16384x16384 [1].
Maybe it's a video encoding limitation then, such as [2] [3].
The Gnome shell developers might know already, so pl
and then tell us the ID of the new bug.
--
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/1786757
Title:
screencast no output on 3 display monitor
To manage notifications about t
Removing mesa-va-drivers and gstreamer-1.0-vaapi fixed the bug. Thanks a
lot for your help!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1780475
Title:
Fatal IO error 11 on totem s
93 matches
Mail list logo
