Public bug reported:
I have a server machine with an ASPEED BMC (kernel driver `ast`) and a
Radeon Pro WX 4100 (driver `amdgpu`). If I try to log into a KDE
Wayland session or a Gnome Wayland session, it crashes back to the login
screen, with the same innermost level in the traceback.
What I'd l
Same for me: I can use xrandr manually in an Xorg session, but not in
the Wayland sesson.
>From some stuff I read online, it seems like Gnome is trying to prevent
you from making the virtual resolution too low, but if it's already too
low, now you're stuck like that, and it really ought to be up t
I managed to add the U7 Echelon to the config file:
"Xonar U7 Echelon Ed_" 1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1498129
Title:
Asus Xonar U7 S/PDIF output not recogni
I have an Ubuntu 15.10 that's up to date, and I'm still seeing the
"rejected" message.
The seemingly most relevant file is
/etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf, from the
network-manager config file. None of the rules in that file seem to
handle all the "(unset)" fields.
** Al
** Bug watch added: GNOME Bug Tracker #757714
https://bugzilla.gnome.org/show_bug.cgi?id=757714
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=757714
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
** Summary changed:
- Connecting to GDM via XDMCP crashes it
+ Connecting to GDM via XDMCP crashes it (GdmXdmcpDisplay shouldn't be abstract)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
I've enabled XDMCP in GDM, and created an xinetd service for VNC via
XDMCP.
Any time I try to connect via VNC, gdm crashes, taking down the local display
as well.
After that, gdm won't start again until I kill the "orphaned" local display.
It looks like the fix is a single-
More specifically, the critical file from ubuntu-gnome-default-settings is:
/usr/share/glib-2.0/schemas/20_ubuntu-gnome-default-settings.gschema.override
If you remove that file and update schemas (one way is "dpkg-reconfigure
libglib2.0-0"), gdm won't start properly.
If you re-add the file and
On my workplace Thinkpad W530 (Quadro K1000M in discrete-only mode),
"EnableBrightnessControl=1" does in fact expose a working "Backlight" property
via xrandr.
Unfortunately, Gnome is looking for a property called "BACKLIGHT", and falls
back to /sys/class/backlight when it's not found.
See https
** This bug is no longer a duplicate of bug 947748
Brightness control not working after latest update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/947919
Title:
Can
*** This bug is a duplicate of bug 947748 ***
https://bugs.launchpad.net/bugs/947748
In my case, I'm using an nvidia card on a Thinkpad, with
EnableBrightnessControl set.
On at least the Intel driver, xrandr --verbose presents both 'BACKLIGHT' and
'Backlight'.
The nvidia driver (with EnableB
I can confirm that it seems to be ConsoleKit killing the session, because it's
taking out both DRI and audio.
This bug should probably renamed -- it's not merely an i915 issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in
12 matches
Mail list logo
