Confirmed in Ubuntu 23.04. The issue happens on my external monitor
(2560x1440@60Hz) set as primary monitor and located above the laptop's
internal FullHD display (both physically and virtually). Background with
no elements on it is only displayed on my secondary monitor (laptop
screen when
An issue with the same symptoms (still valid in Ubuntu 23.04) is also
reported against GNOME Shell at https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/3135.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3135
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3135
--
Ge-org Brohammer have you also tried the new AMD Catalyst 14.6 beta
from official AMD's webpage?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1267650
Title:
fglrx
The installation is just about running:
chmod +x amd*
./amd* --buildpkg Ubuntu/trusty
sudo dpkg -i *.deb
But you would need to install some build dependencies (exact steps
should be here:
http://wiki.cchtml.com/index.php/Ubuntu_Trusty_Installation_Guide#Before_you_start).
Anyway, I tested all the
I can confirm this behavior since fglrx 12.11 if I am right. The only
exception was fglrx-updates package from Ubuntu 13.04 repository which I
am using now (the fglrx package from the same repository causes system
freeze like all the other versions do).
Relevant (unsolved) threads are probably:
The bug has already been reported upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=642814
** Bug watch added: GNOME Bug Tracker #642814
https://bugzilla.gnome.org/show_bug.cgi?id=642814
--
You received this bug notification because you are a member of Desktop
Packages, which is
Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=642814
** Package changed: gvfs (Ubuntu) = gvfs
** Changed in: gvfs
Importance: Low = Unknown
** Changed in: gvfs
Status: Confirmed = Unknown
** Changed in: gvfs
Remote watch: None = GNOME Bug Tracker #642814
--
You
Public bug reported:
An error window popped up when installing upstream kernel version
3.7.0-030700rc1.201210161007 (amd64) from http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.7-rc1-quantal/
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: fglrx 2:9.000-0ubuntu3
ProcVersionSignature:
Closing as this happened due to the lack of the *_all.deb kernel
package in the 3.7-rc1-quantal version folder.
** Changed in: fglrx-installer (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I have a Valgrind log using a wrapper for /usr/lib/gvfs/gvfsd-gphoto2 as
Sebastien adviced.
However, I have not managed to copy more than a 19MB (RAW photo file), thus I
am not sure if it will help. All bigger files (videos) ended up with time out
error as the Valgrind memchecks take probably
I can confirm the strange behavior. The ext4 devices show as unmounted
in the Devices section in Nautilus when gparted is started and show up
as mounted in the Computer section in nautilus (so they are present
twice in the left Nautilus panel). They disappear from Unity panel
completely.
--
You
Thanks, removing the ~/.gstreamer-0.10 directory did solve the issue for
me too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/856988
Title:
totem cannot play quicktime file
A similar thing happens to me when I click to write a new email (or to
response) - it opens in fullscreen but with no gaps and neither the top
panel is accessible nor application switcher (Alt+Tab doesn't do
anything) and if I move to another desktop, I can only see the wallpaper
but with no icons
I am experiencing the same behavior after upgrading to Ubuntu 11.10.
Furthermore, I can see the shadow below the top panel and left panel
disappear and Nautilus segfaults on startup.
** Summary changed:
- Desktop icons become invisable
+ Desktop icons become invisible
--
You received this bug
I can confirm this issue on Ubuntu 11.10 (upgraded from 10.04). I am not
able to close gnome-system-monitor the usual way by clicking on the red
cross in the top left corner, I have to kill it from the processes list.
** Tags added: amd64 oneiric
--
You received this bug notification because
I agree with you, absolutely. This is an annoying consequence of the
gnome-screensaver removal or whatever has been done.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
By the way, I would like to mention that there is a similar, possibly
related bug report concerning locking the screen when the lid is closed
(without hibernation) - bug #871047
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
17 matches
Mail list logo