I too get the "error failed to initialize HAL" when starting up Gnome.
When I change to KDE at startup, is "seems" to start normally, but if I
try to use Konqueror to browse files, - i.e. by clicking on a folder -
Konqueror hangs.
Also, if I recall corrrectly, when I clicked on the KDE main menu,
I should add that I am using the most current version of the kernel -
2.6.15-26-386
--
hal-device-manager does not load
https://launchpad.net/bugs/31517
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I deeply, deeply regret to say that I was completely unable to find any
workaround for this problem, other than to install open suse 10.1, which
worked with the hardware flawlessly. Could I suggest that we raise the
priority of this problem to High, as it completely precludes one from
running Ubun
Also on 21.10 sync does not work
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1866999
Title:
gnome-calendar does not sync with Google Calendar
To manage notifications abo
I have the same error after a clean install (today) of 17.10 using
nvidia 384.98 driver in an xorg gnome session. I presume the screensaver
failure is responsible for a failure to switch users.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
I would like to confirm that I have the same problem (as "NoOp") on a test
system (inability to login using gdm login screen).
It is ok when using AutomaticLogin.
I have a single user on the system.
It failed after an update somewhere between 26 March to 6 April (I was away for
a week, came back
For me the system as standard with one user "crt" (or at least via standard
updates) has a frozen gdm login screen as described by others.
Modify /etc/gdm/custom.conf to add the following:
[daemon]
AutomaticLogin=crt
AlwaysLoginCurrentSession=false
AutomaticLoginEnable=true
TimedLoginEnable=false
I have determined that (on my system) disabling the Nvidia video driver fixes
this problem.
When using the Nvidia video driver the following is found in the Xorg.0.log
file:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e937b]
1: /usr/bin/X (0x8048000+0x61c7d) [0x80a9c7d]
2: (vdso) (__ker
By "disabling" I mean using the "System->Administration->Hardware
Drivers" and then specifying "Remove" as the action against Nvidia
proprietary driver.
Xorg.0.log.old is a better place to look as it seems that when X crashes
and restarts the crash log is remained .old, and the new instance of X
w
It appears that https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/553200";>bugs.launchpad.net/ubuntu/+source/gdm/+bug/553200
describes the problem that has been described in this thread.
I will be watching that thread from now on.
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchp
A refinement (in 10.10 2.6.35-25-generic #44-Ubuntu) is that whilst the
dialog is locked for mouse input, it is still possible to TAB around to
action the buttons which otherwise are not accessible via the mouse.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
** Package changed: totem (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/2091864
Title:
Cannot enter luks password at boot after kernel 6.8.0-50 upgrade
To manage
Public bug reported:
Upgraded Ubuntu 24.04 software, including kernel 6.8.0-50, after which
upon booting the luks password couldn't be entered (dialog
unresponsive). Was able to boot 6.8.0-49. Could boot 6.8.0-50 with quiet
splash commented out - with text input.
Added i915 (my video driver) to /
13 matches
Mail list logo
