And now OPTIONS has to be exported,
and probably should be protected against being empty in the new file. So it
becomes ${OPTIONS:-} and ${1:-}
What else have I missed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Bother. There is a third problem, a scope issue of some sort.
The errors in ~/.xsession.error go away if "has_options" is moved from Xsession
to its own file in Xsession.d
I don't see why sourceing it should make any difference, but it does.
$ cat /etc/X11/Xsession.d/00
has_option () {
#
Public bug reported:
Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
reports and failed fixes for this over several years and releases.
There are a couple of problems in /etc/X11/Xsessions where it fails to
handle options, causing bogus error messages and, doubtless, many
Public bug reported:
Initially added epson c60 stylus but it installed with filter error.
Deleted printer from cups , added new printer.
Added the epson printer , selected the .ppd file that worked in 1904 and
clicked add printer.
Cups just sits and thinks.
Same happens if I use the
The bug seems to have "gone away" when using a DVD of an early March
beta version of Focal Fossa 20.04. It boots very happily with no
obvious display problems.
Sorry that I could not track down exactly what the problem was.
--
You received this bug notification because you are a member of
I'm not so sure that it is a kernel problem.
Bionic with the edge kernel 5.3.0-24 seems OK, although it has locked up once
or twice.
Eoan with kernel 5.3.0-23 misbehaves.
Could the XFCE desktop be important?
--
You received this bug notification because you are a member of Desktop
Packages,
Correction:
Rc7 sometimes boots in the standard way. Sometimes it goes to a black
screen.
Rc7 boots reliably from the *recovery* mode in the grub menu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in
@Morten
I think that all Ryzen motherboards are going to have UEFI firmware
rather than the old BIOS firmware - even though everyone keeps using the
old name.
If it is your computer and you know what you are doing you could turn
off secure boot. If you don't know, then don't do it.
I grabbed
Workarounds include;
use an older version of Ubuntu,
use a faster monitor,
use a video card (nVidia GT 710),
use a mainline kernel 5.4.0-050400rc6-generic
which also reports the VGA port as a VGA port.
But using a mainline kernel and a video card xrandr reports a 77 Hz refresh
rate
Public bug reported:
Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
55-75 Hz monitor.
Booting Xubuntu 19.10 live iso with safe graphics options did give a
stable desktop display, but
xubuntu@xubuntu:~$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0:
Public bug reported:
Wily Werewolf beta1 with various updates, including xubuntu-dev/xubuntu-
staging/ubuntu wily main, does not shutdown my hardware cleanly. It
needs to have the power button pressed. It is an old BIOS firmware
machine with an AMD cpu.
** Affects: software-center (Ubuntu)
Public bug reported:
In raring, lightdm successfully passed environment variables
(specifically $USER and $HOME) relating to the user logging in to a
session-startup-script specified in /etc/lightdm/lightdm.conf.
In saucy, the session-startup-script gets a very cut down environment,
with $HOME =
12 matches
Mail list logo
