It happens for me, too. There is no mouse cursor when X starts up,
before I've logged in. So, it doesn't matter what window manager I
use. I am using GDM3 as my display manager. I tried to switch to KDM
but it didn't work.
If there's anything you'd like me to try, some data you'd like me
It happens for me, too. There is no mouse cursor when X starts up,
before I've logged in. So, it doesn't matter what window manager I
use. I am using GDM3 as my display manager. I tried to switch to KDM
but it didn't work.
If there's anything you'd like me to try, some data you'd like me
The cursor has disappeared for me, as well. I haven't tried nearly as
many things as Harald has, but I observe that it happens as soon as X
starts up, before I log in, so it doesn't matter which desktop
environment I use. (I happen to use Xfce.) I'm logging in through
gdm3. I tried to use
Package: cinnamon
Version: 1.7.4-2.2+b2
Severity: normal
Dear Maintainer,
Cinnamon 2.2 was released a few days ago. Please package it for Debian.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign
On 05/07/2011 04:01 PM, Cyril Brulebois wrote:
Hi,
Jonathan Guthrie jguth...@brokersys.com (07/05/2011):
On this laptop, using the built-in display, one of the resolutions
(1360x768) is unavailable because when it is selected, the entire
display is slanted. That is, a vertical bar
I'm sure that the cups maintainers are aware of all this, but it might
be of interest to users who all of a sudden can't print, so I'm
commenting on the defect.
I was unable to locate a copy of the version 0.12.0-2.1 version of
libpoppler5 to downgrade to, so I investigated the issue with the
I don't know how it happened, either, but this bug bit me, too.
I upgraded my amd64 architecture laptop from ftp.us.debian.org around
7 AM CST (13:00 or so UTC) and was unable to come out of hibernation
later.
--
Jonathan Guthrie (jguth...@brokersys.com)
Sto pro veritate
http://www.brokersys.com
Package: libpam-krb5
Version: 3.14-1
Severity: grave
Justification: renders package unusable
After updating libpam-krb5 on two different systems, it became impossible
for non-root users to log in, and attempting to log in results in a message
like this being printed on this screen:
[
On Mon, 2009-07-20 at 07:32 -0700, Russ Allbery wrote:
Jonathan Guthrie jguth...@brokersys.com writes:
After updating libpam-krb5 on two different systems, it became impossible
for non-root users to log in, and attempting to log in results in a message
like this being printed
On Mon, 2009-07-20 at 11:28 -0700, Russ Allbery wrote:
Thanks, that ended up being enough information. Could you try this patch
and see if it fixes your problem? It works for me.
The patch works for me, as well. Thanks again for your prompt response.
This time, copying to the defect as
I had the same problem until I installed the libatlas3gf-base package.
Perhaps there is a dependency missing somewhere.
!DSPAM:39,4a32a5a1125339072512875!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
The problem is that the type of LOG_DB_PATH is a unicode string and
sqlite3.connect expects that parameter to be a string. I think it
likely that this package should be modified to accept unicode strings as
well as ASCII for that parameter.
--
Jonathan Guthrie [EMAIL PROTECTED]
Sto Pro Veritate
On Mon, Dec 03, 2007 at 09:21:28AM +0100, Loïc Minier wrote:
On Sun, Dec 02, 2007, Jonathan Guthrie wrote:
After today's upgrade, no matter which session I try to start, gdm fails to
start that session and starts the Failsafe xterm session instead. I can
manually start gnome-session
On Mon, Dec 03, 2007 at 01:59:46PM +0100, Loïc Minier wrote:
On Mon, Dec 03, 2007, Jonathan Guthrie wrote:
I have both a .profile and an /etc/profile and after some trial and
error, it turns out that commenting out a single line in .profile causes
my normal gnome session to work. I am much
Package: gdm
Version: 2.20.2-1
Severity: important
After today's upgrade, no matter which session I try to start, gdm fails to
start that session and starts the Failsafe xterm session instead. I can
manually start gnome-session and it works, but it will not start
automatically.
So far, I
, should I submit it upstream, because it's
definitely the upstream source that is broken, or will you guys do that?
While I'm thinking about it, someone should open a wishlist bug to allow
for the building of gdb-friendly binaries without the manual fiddling I
had to do.
--
Jonathan Guthrie [EMAIL
On Wed, 2007-04-18 at 13:52 +0200, Sven Arvidsson wrote:
On Tue, 2007-04-17 at 19:53 -0500, Jonathan Guthrie wrote:
On Wed, Apr 18, 2007 at 12:04:17AM +0200, Sven Arvidsson wrote:
If this still is a problem, can you try version 0.16 from the
experimental archive?
http
I understand that it is necessary to enable PAE to fix some problem or
other. However, enabling PAE in the dom0 requires that PAE be enabled
in all the domU's, and most other operating systems do not offer support
for PAE. Further, I am primarily interested in Xen so that I can run
multiple
Package: xchat-gnome
Version: 1:0.13-1+b1
Severity: important
When I attempt to start xchat-gnome, it opens a window and begins to draw
it. Then, I get a dialog that says The Application 'XChat-GNOME IRC Chat'
has quit unexpectedly. It has left this output in the terminal that I ran
it from:
0
- runtime
gabber recommends no packages.
-- no debconf information
--
Jonathan Guthrie ([EMAIL PROTECTED])
Sto pro veritate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: linux-image-2.6.16-2-xen-686
Version: 2.6.16-18
Severity: normal
Some time ago, I installed a Xen Dom0 under Debian using
linux-image-2.6.16-1-xen-686. Recently, I've installed two Xen Dom0's
under Debian using linux-image-2.6.16-2-xen-686, and I added that kernel
to the working Xen
Package: gnats
Version: 4.1.0-0
Severity: important
Tags: patch
After installing gnats, I discovered that any attempts to connect to the
gnatsd resulted in two log file entries in syslog that look like this:
May 11 15:23:34 gaia gnatsd[13743]: connect from :::192.168.19.254
. It appears
to me to be the result of duplicating the ports line in /etc/cupsd.conf
and /etc/cups/cups.d/ports.conf
--
Jonathan Guthrie ([EMAIL PROTECTED])
Sto pro veritate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
23 matches
Mail list logo
