I agree, Xorg still provides the best experience with NVIDIA.
--
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/1969566
Title:
Default to Xorg on NVIDIA-only systems
To manage
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Impish)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notif
** Changed in: nvidia-settings (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
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/1876052
Title:
Nvi
I still can't reproduce the problem here. I am attaching the output of
lspci -vvv.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5358377/+files/lspci.txt
--
You received this bug notification because you are a member of
@Daniel: I tested this on an NVIDIA only system. I am going to test
again on a fresh focal installation, to see if it makes any difference.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
I have just updated an Eoan installation to Focal, enabled auto-login,
and I can't reproduce the problem. I am using the 440.64 driver, and
nvidia-drm.modeset is disabled. I can also see the bootsplash.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I think forcing all users (even on systems that don't use the NVIDIA
driver) to run X with root privileges would be a little heavy-handed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
@Martin: comment #13 says that autologin works without problems with
nouveau.
@all: are you able to use auto-login if add the following line to your
/etc/X11/Xwrapper.config and reboot?
needs_root_rights = yes
--
You received this bug notification because you are a member of Ubuntu
Desktop
Unfortunately, I can't reproduce the problem on my system, running the
435 driver in 19.10.
What I don't see on my system is the following error from logind:
Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (EE) Error
systemd-logind returned paused fd for drm node
Compare this from
I can't reproduce the problem here on my nvidia system with the 418
driver.
--
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/1822478
Title:
[regression][nvidia] All on screen text is
@Fink: I would like to see powertop when you don't use bbswitch (and the
Nvidia GPU is on). More specifically, I would like to know if you can
disable the Nvidia GPU using the "Tunables" tab from powertop.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Pe4enko: Here is your problem:
NVRM: API mismatch: the client has the version 410.66, but
NVRM: this kernel module has the version 390.87. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.
It looks like you installed the 410.66 driver
@Dan: I would like to see your /var/log/gpu-manager.log when in power
saving mode.
@Fink: please install powertop, launch it by typing "sudo powertop", and
get to the "device stats" tab, to see what's drawing power. You can
attach a screenshot of that.
--
You received this bug notification
also, we do not rely on bbswitch any more.
--
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: PRIME Power Saving mode draws too much power
To manage notifications
@Krzysztof: The NVIDIA GPU is more powerful, but also more power hungry
than the Intel GPU. This is why you are seeing such a high power
consumption.
If you select the Intel GPU, through prime-select, then you will lose
the HDMI, but power consumption should also go down. If it doesn't, it
is a
@Gregor: that shouldn't be an issue any more, assuming that you are
using the latest updates, and that you are using the nvidia driver from
the ubuntu archive.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
@Fernando: we don't support hybrid graphics without using a display
manager, as that would prevent gpu-manager from running at the right
time.
@Michael: I can only assume there was some failure somewhere when
setting the power state of the NVIDIA GPU (the dmesg output might help).
There are
@Krzysztof: I don't think your GPU is the same as Andrew's. Please
attach your /var/log/gpu-manager.log
--
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: PRIME Power
@Leandro: please attach your /var/log/gpu-manager.log , as that might
give me a clue about your system.
--
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: PRIME Power
@Andrew: sorry, but your GPU is supported only by the 340 legacy driver,
and we do not support hybrid graphics with that driver.
--
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
@Stefan: it seems to me that you didn't install nvidia-prime from the
Ubuntu archive.
@Renato: does it solve your problem if you install lightdm, and you use
it instead of gdm?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
@Anton: you are using gdm3, right? (you can check it with "ps aux | grep
gdm")
@Josh: this bug report: LP: #1797147
--
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:
drebrait brian-murray
> cantfind dodger-forum fvkigg happy-snizzo ilvipero janitor lmfranco
> luiscastro193 mapengyu matlit mhr3 mikhailnov new-mohammads nikperrakis
> odysei renatoapdo sil2100 tjaalton ubname unkraut2 vlad-svitlichniy vorlon
> ximex xintx-ua zdv80
> Launchpad-Bug-Re
@Renato: I might have a fix for external display in 18.10. If it works
correctly, I'll backport it to 18.04.
@Luiz: Gdm 3 creates one main X (or XWayland) session, and then starts
an additional X for the user session. It's the default behaviour.
I suspect PRIME synchronisation is only meant to
@Arthur: you probably need to install the 32 bit libraries manually from
-proposed. Try with the following command:
sudo apt install libnvidia-gl-390:i386/bionic-proposed
as for 2), I would need some logs such as /var/log/gpu-manager.log after
reproducing the problem.
--
You received this bug
@Aurelijus: not yet. I am going to add support for lightdm and for sddm
in the next update.
--
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: PRIME Power Saving mode
gt; Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: albertomilone andrebrait brian-murray cantfind
> dodger-forum happy-snizzo ilvipero janitor luiscastro193 mapengyu
> mikhailnov odysei sil2100 tjaalton ubname vlad-svitlichniy vorlon ximex
> xintx-ua
> Launchpad-Bug-Re
@ubname: installing the meta-package worked here, but you can install
the single packages manually:
sudo apt install libnvidia-gl-390/bionic-proposed libnvidia-compute-390
/bionic-proposed libnvidia-decode-390/bionic-proposed libnvidia-
encode-390/bionic-proposed
o
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: albertomilone andrebrait brian-murray cantfind
> dodger-forum happy-snizzo ilvipero janitor luiscastro193 mikhailnov odysei
> sil2100 tjaalton ubname vorlon ximex xintx-ua
> Launchpad-Bug-Reporter: Alberto Milone (
@Aurelijus: please follow these steps for testing:
1) Enable the bionic-proposed repositories
2) Create /etc/apt/preferences.d/proposed-updates with the following
content:
Package: *
Pin: release a=bionic-proposed
Pin-Priority: 400
3) Update the list of packages:
sudo apt-get update
4)
@Steve, Brian: I have re-uploaded ubuntu-drivers-common 1:0.5.2.1, now
with code to prevent shipping the __pycache__ cruft. While running
debdiff against 1:0.5.2 will still mention the cruft, if you run
"lintian -v ubuntu-drivers-common_0.5.2.1.dsc --pedantic", lintian won't
complain about
** Tags removed: verification-failed-bionic
** Tags added: verification-needed-bionic
--
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: PRIME Power Saving mode draws
@Serhiy Zahoriya: sorry but ubuntu-drivers-common (1:0.5.2.1) doesn't
seem to be in bionic-proposed yet. No wonder things failed.
--
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
On Mon, 27 Aug 2018 at 23:01, Mikhail Novosyolov <1778...@bugs.launchpad.net>
wrote:
> Can you please explain why is nvidia-fallback needed? It worked without
> it before.
>
I am trying to remove it with this SRU.
--
Alberto Milone
--
You received this bug notificat
rce package as uploaded appears to have a lot of cruft in various
> __pycache__ directories. This ought to be cleaned up.
>
>
This should not be a problem in my last upload.
--
Alberto Milone
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
@monogato: please give us time to get all the components into the
-proposed repository first.
--
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: PRIME Power Saving
rs-common; component=main; status=In Progress;
> importance=High; assignee=alberto.mil...@canonical.com;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: albertomilone andrebrait cantfind ilvipero
ivers-common; component=main; status=In Progress;
> importance=High; assignee=alberto.mil...@canonical.com;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: albertomilone andrebrait cantfind ilvipe
The drm_mode_get_hv_timing() function (used in the required kernel
commit) depends on a non trivial amount of other changes, and I don't
think a backport would be easy, or safe. That commit will be available
in Linux 4.17, though, so we are going to get the fix in Ubuntu 18.10.
** Changed in:
signee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-settings (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nvidia-settings (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: nvidia-settings (Ubuntu Bionic)
Status: New => In Pr
Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-390
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => High
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albe
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
ecided => High
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1777099
Title:
** Changed in: mutter (Ubuntu)
Status: In Progress => Triaged
--
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/1752123
Title:
Force 8bit RGB config
To manage notifications
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: mutter (Ubuntu)
Status: New => In Progress
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
@Doug: we are going to leave PRIME systems alone in any case. This bug
report is about non hybrid systems. You are using the intel GPU to drive
the screen, and that is why X11 + KMS works for you. As far as I know,
Wayland doesn't support that yet.
--
You received this bug notification because
** Bug watch added: GNOME Bug Tracker #784470
https://bugzilla.gnome.org/show_bug.cgi?id=784470
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=784470
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: gdm3 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Public bug reported:
Due to a current limitation in the nvidia binary driver, when enabling
KMS (to use Wayland), any X11 sessions will crash.
Ideally, GDM would check if modesetting is enabled in the nvidia driver,
and blacklist the X11 sessions.
The following command can tell you whether the
I suspect gdm is not calling gpu-manager, which would make it a bug in
gdm.
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
@Jean: please attach your /var/log/gpu-manager.log
** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
** Changed in: unity-settings-daemon (Ubuntu Trusty)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: unity-settings-daemon (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Just an update: I've backported a system that should work better than
single quirks. This is also what AceLan tested for me.
I've made a merge request into the bazaar branch of unity-settings-
daemon, so that my code can be reviewed and accepted into 14.10. As soon
as the merge is complete, we'll
** Description changed:
+ Expected results:
+ The touchscreen continues to operate as in step 1, allowing you to manipulate
items on the display that contains the touchscreen. The touchscreen does not
interact with windows, etc on the external monitor
+
+ Actual results:
+ The touchscreen is
Yes, the Dell Inspiron 20 Model 3048 works without quirks because it
uses an eDP connector.
I've just implemented a quirks system which should fix the Dell OptiPlex
9030 AIO and possibly other Dells with similar specs.
Please try the updated packages available here:
Ok, I've corrected the quirk for the OptiPlex and I've added one for the
Inspiron 2350.
Please try the updated packages available here:
http://people.canonical.com/~amilone/lp1287341/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
@Acelan: please download the following binary, run it on that system,
and attach the output:
http://people.canonical.com/~amilone/simple-xinput
Also please attach your /var/log/Xorg.0.log and the output of the
xinput list --long command.
Note: in this case there's no need to reproduce the
ok, what happens if you type:
killall unity-settings-daemon
unity-settings-daemon --debug mylog.log
then reproduce the problem and attach the log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
The problem with all-in-one systems that don't use connectors such as
eDP is that we don't have a generic way to match the display with the
input device. This means that we have to quirk such systems using the
display EDID and the input controller.
--
You received this bug notification because
AceLan: please attach the output of the following commands for all the
all-in-one systems you have available (with no external screens
connected):
1) xrandr --verbose
2) xinput list --long
3) /var/log/Xorg.0.log
You can collect the data using a livecd of Ubuntu 14.04
--
You received this bug
I've built packages for both i386 and amd64 with my fix. You will find
them here:
http://people.canonical.com/~amilone/lp1287341/
Please install the package for your architecture, then log out, log back
in, and try to reproduce the problem.
It would be interesting to test my fix on laptops with
I've gone through all the relevant upstream commits, and here are my
conclusions:
1) The upstream code covers the use case of Wacom tablets with built-in
displays (which, although useful, is not the use case discussed in this
bug report). It would be way too much code to backport, especially for
I already have a prototype that solves the use case mentioned in this
bug report.
Apparently upstream also has code that fixes the same issue and covers
more use cases. It doesn't seem like a small amount of code though. For
this reason I'll take some time to see if a backport is possible or
Just as an update, I'm working on some code that will detect the touch
screen, couple it with the laptop's screen, and map the touch input
device onto the output whenever the screen configuration changes (e.g.
on rotations, when new outputs become available, etc.). This won't
require any user
** Changed in: unity-settings-daemon (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1287341
Title:
Touchscreen controls
@Steve: please attach the output of the following commands:
xinput list
Then look at the output and see what id matches your touchscreen (e.g.
id=12), and finally type:
xinput list-props $the_id_you_found
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: unity-settings-daemon (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1287341
Title
@Tim: as for permission, maybe the gdm user doesn't have the same
permissions as a standard user?
As for the stop script, wouldn't that require GDM to be stopped (rather
than just X)?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gnome-desktop3 (Ubuntu)
Status: In Progress = Fix Released
** Changed in: gnome-desktop3 (Ubuntu Precise)
Status: In Progress = Fix Committed
** Changed in: gnome-desktop3 (Ubuntu Saucy)
Status: In Progress = Fix Committed
--
You received this bug
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Invalid = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1224254
Title:
xrandr Xerrors with the
look for the primary output. This solves the problem in
libgnome-desktop.
** Also affects: gnome-desktop-3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-desktop-3 (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: gnome-settings-daemon
** Package changed: gnome-desktop-3 (Ubuntu) = gnome-desktop3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1224254
Title:
xrandr Xerrors with the nvidia
-desktop3 (Ubuntu Precise)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** No longer affects: gnome-settings-daemon (Ubuntu Precise)
** No longer affects: nvidia-graphics-drivers-319 (Ubuntu Precise)
** Changed in: xserver-xorg-video-modesetting (Ubuntu Precise)
Status: New
** Patch added: debdiff for trusty
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1224254/+attachment/3922068/+files/gnome-desktop3_3.8.4-0ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Bug watch added: GNOME Bug Tracker #719784
https://bugzilla.gnome.org/show_bug.cgi?id=719784
** Also affects: gnome-desktop via
https://bugzilla.gnome.org/show_bug.cgi?id=719784
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Changed in: gnome-desktop3 (Ubuntu Saucy)
Importance: Undecided = High
** Changed in: gnome-desktop3 (Ubuntu Saucy)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: xserver-xorg-video-modesetting (Ubuntu Saucy)
Status: New = Triaged
** Changed in: xserver
I can reproduce this when using the nvidia driver and offloading
rendering to it using RandR on an NVIDIA Optimus system. This is what
nvidia-prime does and what NVIDIA suggests on their website.
I've assigned the bug report to both the nvidia driver and the
modesettings driver since they are
Apparently, if I use the intel driver instead of the modesettings
driver, I can't reproduce the problem. This is not a bug in the nvidia
driver, it's definitely an issue in the modesetting driver.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I take back what I said, I had a false positive. I probably know what's
going on but I need to investigate this a little further.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Invalid = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1224254
Title
Yes, same problem without passing the self (I've just noticed that the
parent widget is not needed)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1248152
Title:
GObject
This is really a limitation in the RandR implementation of the fglrx
driver which doesn't support dynamic front buffer reallocation. There is
nothing we can do about this.
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because
** Changed in: linux-restricted-modules-envy-2.6.24 (Ubuntu)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/118605
Title:
[fglrx] freezes upon
** Changed in: gnome-settings-daemon (Ubuntu Lucid)
Assignee: Alberto Milone (albertomilone) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/432814
** Changed in: hundredpapercuts
Assignee: Alberto Milone (albertomilone) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/410636
Title:
Right-click should
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Alberto Milone (albertomilone) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/563276
Title
if you're using the nvidia driver you might want to set the resolution
using the nvidia-settings tool
--
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/1029089
Title:
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) = Sam Spilsbury (smspillaz)
** Project changed: compiz = compiz-core
** Changed in: compiz (Ubuntu)
Status: New = Triaged
** Changed in: compiz
** Also affects: compiz
Importance: Undecided
Status: New
--
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/1043759
Title:
Display settings confirmation dialog
Ignore my comment, it was an issue with the mode that I was using on my
HDTV.
--
Jerky h.264 video playback
https://bugs.launchpad.net/bugs/647063
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gst-plugins-good0.10 in ubuntu.
--
I don't why but this update makes my XVID MPEG-4 (624 x 352) videoclips
stutter when I play them. If I install 0.10.25-4ubuntu1 I'm unable to
reproduce the issue. This is weird as I don't think flvdemux is used for
XVID MPEG-4.
--
Jerky h.264 video playback
https://bugs.launchpad.net/bugs/647063
** Changed in: hundredpapercuts
Status: In Progress = Confirmed
--
Right-click should not pre-light first option, too easy to accidentally select
the first Context-menu option.
https://bugs.launchpad.net/bugs/410636
You received this bug notification because you are a member of Ubuntu
** Changed in: hundredpapercuts
Status: Confirmed = In Progress
--
Right-click should not pre-light first option, too easy to accidentally select
the first Context-menu option.
https://bugs.launchpad.net/bugs/410636
You received this bug notification because you are a member of Ubuntu
@GiBSON: I think you're experiencing a different bug. Please file a new
bug report about it.
@Roman: it looks like Robert Ancell re-enabled that patch
(91_correct_rgba_use.patch) in nautilus 1:2.30.1-1ubuntu1
--
Nautilus crashes when there are multiple XScreens
** Changed in: hundredpapercuts
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: hundredpapercuts
Status: Triaged = In Progress
--
Right-click should not pre-light first option, too easy to accidentally select
the first Context-menu option.
https
I've provided a patch in the upstream bug report.
Here's a PPA with my patched gtk+ for both Lucid and Maverick, if you want to
test it:
https://launchpad.net/~albertomilone/+archive/papercuts
--
Right-click should not pre-light first option, too easy to accidentally select
the first
@Shannon
Please remove the repository that you added (as it's an html page), then follow
the instructions available on this page:
https://launchpad.net/+help/soyuz/ppa-sources-list.html
and use the following PPA:
ppa:albertomilone/proprietary-video-improvements
--
Mouse and keyboard stop
I have uploaded the fix in Ubuntu Lucid, however my upload will be
approved only after Lucid's RC is released.
In the meantime, if you want to test the driver, you can install it from my PPA
(as soon as the packages are built):
I've reverted my changes to the gnome-settings-daemon and I did the same
with synaptics driver default settings. Now we're more compliant with
upstream's default settings (both Gnome and synaptics use 1 3 2 instead
of 1 2 3).
I definitely agree that a we need an easy way to make this configurable
1 - 100 of 192 matches
Mail list logo
