Celebratory fireworks from me.
It seems to work. For ubuntu the only difference is
[Service]
ExecStartPre=/usr/share/gdm/generate-config
becomes
[Service]
ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config
I have a proper ubuntu gnome session running with gdm, an external
monitor
ubuntu user Hon Weng Chong has emailed me as he continues to investigate the
problem.
He believes he has proof that it is is GDM configuration issue and has provided
the following fix
Hey Tim,
I figured out a hack solution to the GDM prime issue. If you replace
/lib/systemd/system/gdm3
The user I referred to in the last comment has proposed changes to
/lib/systemd/system/gdm3.service
to fix the problem.
I have added his proposed changes to this report:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716857
--
You received this bug notification because you are a
Another user has report this on the nvidia linux board. This user reproducts
the problem exactly, and reports a workaround which narrows down the problem. I
haven't yet verified this workaround.
While this user has both intel and nvidia, he/she does not appear to be using a
laptop.
Hey guys, I
Ciro, you have reported "works for me" but you have not confirmed that
you are actually trying to reproduce the bug. The problem occurs when
using modeset=1. You do not mentioned that here or in your related
answer on askubuntu
If you are not using modeset=1, which is essential for people using
Is likley the same issue as this one:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1725169?comments=all
--
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/1705369
Title:
Marco - If you are referring to my comments, I freely admit my linux
knowledge is very limited.
As a client upgrading from 17.04 I do not, and seemingly have no way of
knowing, what a valid configuration is in this respect. I'm not using
Unity any more, and am using Ubuntu (Xorg) rather than the
nvidia (not
> optimus)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu
#22 worked for me, after logout/login.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1620806
Title:
gedit edit window is transparent when using Ambiance and Radiance
themes
To
> https://bugs.launchpad.net/bugs/1714881
>
> Title:
> no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not
> optimus)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions
>
--
Tim Richar
** Summary changed:
- no gdm3 greeter with nvidia quadro and modeset=1
+ no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not
optimus)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Context:
17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia
driver.
ubuntu desktop (gnome shell), fresh install
ThinkPad W520 in Nvidia Optimus bios mode.
Nvidia profile.
Result:
no external monitors are detected.
xrandr does not even list them
As of the latest updates to gdm3, I still can't boot with my laptop when it's
in discrete mode (nvidia graphics only). Does not get to the greeter.
syslog is full of countless repetitions of "Stopping NVIDIA persistence
Daemon".
CPU must be high because the fan comes on. I've reported this but
Daniel, with the latest 17.10 the nvidia problems are now more specific and
easier to reproduce.
Neither of my Thinkpads gets to the login screen in discrete Nvidia mode iff
modeset=1 is used.
In hybrid graphics, the session starts, I suspect this is due to the
intel driver being available.
Public bug reported:
This is to track
https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1
causes loop, does not launch greeter "
I don't know if this is an nvidia bug or a gdm3 bug but it requires both
to reproduce.
[reply] [−] Description t...@tim-
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714881/+attachment/4943940/+files/Error_syslog
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
repository.
On 28 August 2017 at 21:08, Tim Richardson <t...@tim-richardson.net>
wrote:
> Thanks Doug, that bug report is exactly as the nvidia forum so you and I
> are doing the same thing.
>
> On 28 August 2017 at 02:41, Doug McMahon <1706...@bugs.launchpad.net>
> wro
cation because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1706474
>
> Title:
> gdm3 nvidia modeset=1 is broken, external screens don't work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/170647
HI Doug, it could be hardware dependent although my two Optimus laptops are
very mainstream (both Quadro). It's more likely to be configuration (I hope)
How do you achieve modeset=1? How do you confirm that you have Prime Sync
working? I use xrandr --verbose | grep PRIME
regards
Tim
On 27
Looking at the gnome-shell code, there is nothing to lockdown the "log
in as another user" button on the lock screen. It appears to only remove
the "Switch User" item from the system menu.
can you file an upstream bug at bugs.gnome.org for this one, and report
back the bug number here so we can
actually no I don't think it would be caused by that above mentioned
patch.
--
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/1712548
Title:
Gnome 3 lock screen does not respect
This will be in gnome-shell. There is a small chance its caused by the
lightdm user switching patch.
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Sorry, that was premature. I had not enabled modeset=1 properly.
After doing that
a) in Optimus mode, only the laptop display works. The nvidia settings control
panel opens, but it detects no screens.
b) in discrete nvidia BIOS mode, gdm is stuck in a greeter loop when trying to
start a Gmome or
On the newer machine, the P50, I reinstalled 17.10 ubuntu yesterday,
with pre-release packages enabled. It is using gdm3. It works, even with
nvidia modeset=1 and external monitors. It is not obvious to me which
updated packages have fixed this, since I also tried pre-release on the
broken
It is also broken on a ThinkPad W520, which is much older hardware
(although still supported by current nvidia drivers). The Nvidia driver,
gdm3, gnome (or gnome ubuntu) and modeset=1 is broken. Replace gdm3 with
lightdm, and everything works.
--
You received this bug notification because you
And also note that modeset=1 is not designed to activate wayland. It is
necessary to use the Prime Synchonization feature of the new nvidia
drivers, which is actually a feature of X 1.19
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Update & simplication.
This bug affects 17.10 & 17.04 with the current LTS support nvidia drivers.
This bug affects both my laptops with nvidia hardware.
External monitors are not necessary to reproduce.
Reproduction is simple.
1. Activate the nvidia hardware using discrete mode. Therefore no
subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1706474
>
> Title:
> gdm3 nvidia modeset=1 is broken, external screens don't work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions
>
--
boots to black screen when using Nvidia drivers (on a
> desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>
--
Tim Richardson
** Bug watch added: GNOME Bug Tracker #78447
Maybe https://bugzilla.gnome.org/show_bug.cgi?id=784470
** Bug watch added: GNOME Bug Tracker #784470
https://bugzilla.gnome.org/show_bug.cgi?id=784470
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
For what it's worth, nvidia Optimus requires the integrated display to
be modeset=1, this is what you mean by "nomodeset would break laptops",
I assume. Should we be reporting this upstream?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 1705369 ***
https://bugs.launchpad.net/bugs/1705369
** This bug has been marked a duplicate of bug 1705369
Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop
with an Intel GPU)
--
You received this bug notification because you
What's the bug report for hybrid systems? I can't get gdm working with
modeset=1 (aiming to get PRIME sync working). Is good in lightdm. There
are so many bug reports with similar symptoms.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
1706474
>
> Title:
> gdm3 nvidia modeset=1 is broken, external screens don't work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions
>
--
Tim Richardson
** Attachment added: "syslog"
bug
> report.
> https://bugs.launchpad.net/bugs/1706474
>
> Title:
> gdm3 nvidia modeset=1 is broken, external screens don't work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions
>
--
Tim Ri
I have the same symptoms as this bug with 17.04 and the new 375.82
driver if I am use modesetting with gdm. With lightdm it works fine.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "xrandr output"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+attachment/4921331/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Attachment added: "nvidia-bug-report"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+attachment/4921327/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Public bug reported:
ubuntu 17.04 with gnome desktop.
The laptop is a Thinkpad p50 with a quadro M1000M.
To get this bug I am using the hybrid graphics mode.
This problem occurs with 375.82 and also with the new 384 driver.
When using gdm3 and
options nvidia_375_drm modeset=1
the greeter only
that was provided by an external plugin in the past, but of course
upstream gnome-control-center no longer supports those panels.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1694962/+subscriptions
--
Tim Lunn
dark...@fastmail.fm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bug
** Also affects: gnome-session via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864592
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
** Also affects: libgweather (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Changed in: libgweather (Ubuntu)
Status: New => Fix Released
** Also affects: libgweather (Ubuntu Zesty)
Importance: Undecided
** Also affects: libgweather (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libgweather (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
right, I apparently mixed up invalid pointer: 0x00 bug at some point,
and now my SRU is on the wrong bug! thanks for pointing it out. I'll
sort it out
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
1693964 was a cut and paste fail.
bug 1616651 was the correct one.
The stacktrace is different but it is hitting the same codepath that was
suffering memory corruption.
#2 0x7f4c502ef06b in gweather_location_unref (loc=0x55e7b5c95700) at
gweather-location.c:396
i =
loc =
This bug appears to have been fixed in 2012. So marking as fix released.
** Bug watch added: GNOME Bug Tracker #677969
https://bugzilla.gnome.org/show_bug.cgi?id=677969
** Changed in: gnome-control-center
Importance: Critical => Unknown
** Changed in: gnome-control-center
Status:
** Bug watch added: GNOME Bug Tracker #780861
https://bugzilla.gnome.org/show_bug.cgi?id=780861
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=780861
Importance: Unknown
Status: Unknown
** Also affects: gnome-desktop3 (Ubuntu)
Importance: Undecided
** Changed in: gdm3 (Ubuntu)
Status: Triaged => Fix Released
--
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/1565178
Title:
Screen lock broken after release upgrade
To manage
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-gnome
Importance: Undecided
Status: New
** Changed in: ubuntu-gnome
Milestone: None => artful
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1693992 ***
https://bugs.launchpad.net/bugs/1693992
** This bug is no longer a duplicate of bug 1550941
gdm-session-worker crashed with SIGABRT in g_assertion_message()
** This bug has been marked a duplicate of bug 1693992
*** This bug is a duplicate of bug 1693992 ***
https://bugs.launchpad.net/bugs/1693992
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1693992
#3 0x7f66c8a93dfa in g_assertion_message_expr
(domain=domain@entry=0x7f66c880cf52 "AccountsService",
file=file@entry=0x7f66c880dc52 "act-user-manager.c", line=line@entry=2564,
func=func@entry=0x7f66c8810438 <__func__.28806> "load_users",
expr=expr@entry=0x7f66c880ee28
*** This bug is a duplicate of bug 1616651 ***
https://bugs.launchpad.net/bugs/1616651
** This bug has been marked a duplicate of bug 1616651
gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free():
invalid pointer: 0x082dcf30 ***
--
You received this bug
from the stacktrace on errors.u.c, it looks like that is happening under
wayland. It looks to me like Xwayland under the gdm3 gnome-shell greeter
session is the one that is crashing. This runs under wayland by default.
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
**
*** This bug is a duplicate of bug 1616651 ***
https://bugs.launchpad.net/bugs/1616651
** This bug is no longer a duplicate of bug 1693964
Menu Bar Becomes Unresponsive On Lock Screen
** This bug has been marked a duplicate of bug 1616651
gnome-shell assert failure: *** Error in
This may be a duplicate of bug 1693964
--
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/1688534
Title:
gnome-shell crashed with SIGSEGV in strlen() from g_strdup() from
*** This bug is a duplicate of bug 1616651 ***
https://bugs.launchpad.net/bugs/1616651
** This bug is no longer a duplicate of bug 1693964
Menu Bar Becomes Unresponsive On Lock Screen
** This bug has been marked a duplicate of bug 1616651
gnome-shell assert failure: *** Error in
oops that should have been bug 1616651
--
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/1688534
Title:
gnome-shell crashed with SIGSEGV in strlen() from g_strdup() from
*** This bug is a duplicate of bug 1616651 ***
https://bugs.launchpad.net/bugs/1616651
** This bug is no longer a duplicate of bug 1693964
Menu Bar Becomes Unresponsive On Lock Screen
** This bug has been marked a duplicate of bug 1616651
gnome-shell assert failure: *** Error in
*** This bug is a duplicate of bug 1616651 ***
https://bugs.launchpad.net/bugs/1616651
** This bug is no longer a duplicate of bug 1688209
gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free() from
gweather_location_unref() from g_boxed_free() from boxed_finalize()
** This
*** This bug is a duplicate of bug 1616651 ***
https://bugs.launchpad.net/bugs/1616651
This looks like a duplicate of bug 1693964 based on the stacktrace
** This bug has been marked a duplicate of bug 1693964
Menu Bar Becomes Unresponsive On Lock Screen
--
You received this bug
*** This bug is a duplicate of bug 1616651 ***
https://bugs.launchpad.net/bugs/1616651
** This bug is no longer a duplicate of bug 1688209
gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free() from
gweather_location_unref() from g_boxed_free() from boxed_finalize()
** This
** Description changed:
+
+ [Impact]
+ Backport git patch that fixes memory corruption in libgweather that is
causing gnome-shell to crash. This is particularly bad on wayland as it causes
the user to lose their sessions
+
+ I believe this should also fix bug 1688208 and potentially a couple
** Also affects: libgweather (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The interactive tests could be useful if autopilot ever grows clutter
support, that is something I have never got around to working on though.
So for the time being the unit tests are the important ones.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
This can be reproduced by the following steps:
1. Ensure org.gnome.Weather.Application locations is not set (as per default
setting)
2. Disable Location Services
3. gnome-shell will crash
** Bug watch added: GNOME Bug Tracker #782893
https://bugzilla.gnome.org/show_bug.cgi?id=782893
** Also
** Also affects: ubuntu-gnome
Importance: Undecided
Status: New
** Changed in: ubuntu-gnome
Milestone: None => artful
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
After upgrading to artful systemd-resolved is failing to resolve dns. It
seems DNSSEC validation is failing but shouldnt that be disabled by
default like it was in zesty?
$ systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Still exist in Ubuntu 16.10 64Bit, file roller 3.22.1.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1058274
Title:
File Roller segfault on open
To manage notifications
Public bug reported:
Suddenly, as of a couple of days ago, Evolution stopped connecting to
the network. After a bit of digging, I found that I can invoke it with
the GIO_USE_NETWORK_MONITOR environment variable set to "base", and then
it works just fine.
--> this works <--
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Released
--
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/1602737
Title:
PCI RoCE Interface could not be renamed from
** Also affects: linux (Ubuntu Yakkety)
Importance: Critical
Assignee: Tim Gardner (timg-tpi)
Status: Confirmed
** Also affects: systemd (Ubuntu Yakkety)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: Won't Fix
** Changed in: linux (Ubuntu Yakkety
linux 4.8.0-11.12
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Released
--
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/1602737
Title:
PCI RoCE
I filed a debian bug ages ago re fcitx (can't find it atm, I will try
dig it up later).
Basically the debian accessibility guys were against my proposed
changes.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server
I was having the same issue in Arch Linux, and I solved it by installing
the xwayland package (called xorg-server-xwayland in Arch). Try this:
sudo apt-get install xwayland
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
gnome-shell does not use gnome-screensaver, it has its own builtin
lockscreen (provided you are also using gdm)
Also Screen Lock is activated via +L these days
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1592177
Title:
Built-in search almost impossible to
I can reproduce this in yakkety with the following command:
yelp ghelp://usr/share/doc/pspp/pspp.xml#ONEWAY
seems to be an issue with the uri parsing
** Information type changed from Private to Public
** Also affects: yelp (Ubuntu)
Importance: Undecided
Status: New
** Tags added:
XDG_CURRENT_DESKTOP=Unity gedit
(gedit:31630): Gtk-CRITICAL **: Error building template class
'GeditWindow' for an instance of type 'GeditWindow': .:2:8041 Invalid
object type 'GeditCloseButton'
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Same problem in Lubuntu 16.04, eog 3.18.2.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
https://bugs.launchpad.net/bugs/1545872
Title:
Eye of gnome show menus in full screen in gnome session fallback mode
To
Hi,
Thanks for your bug report, there are people on #ubuntu-gnome, you just need
to ask a question and then be patient!
Anyway I can confirm this issue on 3.20 (w/ gnome3-staging)
(gnome-control-center.real:18529): AccountsService-WARNING **:
SetIconFile call failed:
I have not seen that crash here.
It looks like it is failing to create the open_button menu, which uses
the pan-down-symbolic icon. I don't see how that icon could be missing
though, its part of adwaita-icon-theme (which is also used by ubuntu
themes)
** Changed in: ubuntu-gnome
Milestone:
Andrew, was this with stock 16.04, or do you have gnome3-staging
enabled?
** Package changed: gnome-settings-daemon (Ubuntu) => mutter (Ubuntu)
** Changed in: ubuntu-gnome
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: ubuntu-gnome
Status: Confirmed => Fix Released
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to accountsservice in Ubuntu.
** Changed in: gnome-software (Ubuntu)
Status: Incomplete => Triaged
** Also affects: ubuntu-gnome
Importance: Undecided
Status: New
** Also affects: ubuntu-gnome/xenial
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Adding a UI element for a few hardware specific issues does not seem
like a good idea, especially when I can guarantee upstream won't take
those patches. Likely they can be fixed for the specific devices by udev
rules or similar.
Marking gnome-control-center invalid
** Changed in:
I didnt see that you are using Unity. u-s-d also launches syndaemon with
the "-t" option, which means motion won't be disabled, just clicking
and scrolling. Perhaps the "Synaptics Off" patch would help, atleast on
supported hardware.
I am not sure that Unity7 has been ported to use libinput, I
However at least on my laptop it is still falling back to using
syndaemon. That is launched with "-t" option and has been since 2012.
commit c1b2b478ec71b907e4af736d62c1a81ad400f902
Author: Bastien Nocera
Date: Mon Jun 18 11:51:09 2012 +0100
mouse: Only inhibits mouse
Possibly related to this commit.
commit b23917f0a279aba4599cdc7a5b34055f3d8975ba
Author: Ondrej Holy
Date: Wed Apr 8 12:39:48 2015 +0200
mouse: Do not disable touchpad buttons
Touchpad buttons are disabled also if touchpad is disabled using
"Device Enabled"
** Also affects: ubuntu-gnome
Importance: Undecided
Status: New
** Changed in: ubuntu-gnome
Milestone: None => yakkety
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
** Bug watch added: Mozilla Bugzilla #1234158
https://bugzilla.mozilla.org/show_bug.cgi?id=1234158
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1234158
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Also affects: ubuntu-gnome
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1576576
Title:
Update to 3.20 needs work and coordination
Nikita, please try to provide actual justification for wanting a feature
when reporting feature bugs, you know like providing a use-case for why
it would be useful.
In this case however, I agree with upstream that adding a feature to
work around broken hardware seems like a waste, and I certainly
I know there is an issue on Xenial where positions get lost on monitor
changes (like adding/removing a monitor) but is anyone seeing the
settings disappear on xenial across reboots?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Also affects: ubuntu-gnome/xenial
Importance: Undecided
Status: New
** Changed in: ubuntu-gnome/xenial
Status: New => Confirmed
** Changed in: ubuntu-gnome/xenial
Milestone: None => xenial.1
** Also affects: ubuntu-gnome/trusty
Importance: Undecided
Status: New
Hi, this has been fixed upstream. If you still have issues, please fully
update with:
sudo apt-get update
sudo apt-get upgrade
and check again. If it isn't working, please restart. Finally, if you're
fully up to date (check again after the restart) please post back here,
and we will
Public bug reported:
Currently, Software Update says "Please restart the computer to begin
using your updated software" (something I thought was no longer required
as of kernel 4.X - but I digress).
http://imgur.com/fQzxHnG
I wish to access the settings as there seems to be an issue with the
Daniel,
Except the google chrome packages do declare the dependencies, its the fact
that dpkg and presumably gnome-software don't do any dependency resolution.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in
** Also affects: gnome-software (Ubuntu)
Importance: Undecided
Status: New
--
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/bugs/1571905
Title:
GNOME Software Center -
201 - 300 of 1780 matches
Mail list logo