Hello,
it seems the new linux image package from experimental
linux-image-5.4.0-trunk-amd64 does not exhibit the GPU initialization
failure problem.
boot log for this kernel version has:
[2.405213] i915 :00:02.0: VT-d active for gfx access
[2.405347] i915 :00:02.0: vgaarb:
Package: gdm3
Version: 3.20.1-1
Severity: important
When logging in with gdm3, after a few minutes, the screen goes completely
black and locks up. The only operation that is still possible at this point is
pressing the power button to shut down the computer. Using lightdm, I do not
have this
Hello,
I can no longer reproduce this problem with the current wget version, so if
there are no other reports of this, you close this bug.
Thanks,
Bart.
Package: wget
Version: 1.16.3-3
Severity: normal
Hello,
since the upgrade to wget 1.17, my ~/.netrc file is no longer used to provide
authentication information in http requests. I did an strace of the wget
execution, and it looks like it is still reading the file, but in the end it
cannot
Package: gdm3
Version: 3.14.2-2
Severity: important
After a recent update, the greeter for gdm3 does not start anymore. Instead the
infamous 'Oh no something went wrong" is displayed, with a "Logout" button that
cycles back to that same error page.
When I configure automatic login, I get a
Package: openjdk-7-jdk
Version: 7u79-2.5.5-1
Severity: normal
The priority for update-alternatives of the java and javac in the openjdk-7
package are not the same. On my system, I have three versions of openjdk
installed (6, 7, and 8).
$ update-alternatives --display javac
javac - auto mode
to gnome-keyring 3.4.1-4, which is the current version in
wheezy and sid. Does the bug still appear?
On 03/08/12 16:22, Bart Vanhaute wrote:
Package: xul-ext-gnome-keyring
Version: 0.6.3-1
Followup-For: Bug #681203
Hello,
I might be experiencing the same problem as the reporter
Package: xul-ext-gnome-keyring
Version: 0.6.3-1
Followup-For: Bug #681203
Hello,
I might be experiencing the same problem as the reporter described.
This is the scenario I am using:
1/ go to a web site that requires basic authentication, but where the keyring
does not have the needed
Package: apport
Version: 1.94.1-1
Severity: important
Tags: upstream
Please package version 2.0.1 of appport to fix a SEGV when using apport-gtk
with Adwaita theme. The bug is detailed in
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/937249 and makes the
apport tool virtually useless.
Package: systemd
Version: 44-1
Severity: normal
With a recent update, systemctl now depends on liblzma.so.5, and this library
is installed under /usr, This renders my system which has a separate /usr
partition, completely unbootable.
I do know that having a separate /usr partition is not
This bug seems to be caused by having multiple instances running of the
telepathy-butterfly MSN handler. I have no idea how this can be the case,
or how to reproduce it, but the problem can be fixed by killing the
currently running instances and manually starting a new one. I leave it to
your
Package: telepathy-butterfly
Version: 0.5.15-2.1
Severity: important
I can no longer see my MSN contacts anymore in empathy. Neither offline nor
online contacts are shown. All actions related to MSN contacts are disabled
(add contact, search for contact).
My MSN account seems to go online
Hello,
FYI, the start-here-32.png slave alternative of start-here.svg is part
of gnome-colors-common. If you remove that package (and it's
dependencies), the gnome-icon-theme installs without a problem. I
think the two packages will have to agree on a naming scheme for the
start-here
Hello,
the reported bug has been solved for me: I can start up X11 without any
problems. There are indeed (sometimes) problems with lid-close and
shutdown that result in a complete lock-up, as Jose Manuel reported. But
to me, these are very different from this bug: in these cases, it is for
On Wed, 2007-07-04 at 00:38 +0200, Brice Goglin wrote:
Do you still have the PP_STATUS and allocate pages warnings in X log?
No PP_STATUS, but still the allocate pages warning:
$ grep '^(WW)' Xorg.0.log
(WW) Including the default font
path
Hello,
great news: the newest version in unstable, 2:2.1.0-1, has solved the
black screen for me. Though there was no indication that the upstream
bug was solved.
Thanks,
Bart.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hello,
Incidentally, I also tested this same driver, and I agree. However there
is some additional information in the upstream bug that could help the
Xorg developers... There is a suggestion about using i810switch, but I
could not make the described workaround to work for me.
I also tried the
Package: pulseaudio
Version: 0.9.5-7
Severity: normal
whenever some sound is send to the pulseaudio daemon, it exits with the
following message:
pulseaudio: modules/module-alsa-sink.c:176: do_write: Assertion
`memchunk-memblock
memchunk-memblock-data memchunk-length
Package: xserver-xorg-video-intel
Version: 2:2.0.0-1
Severity: important
After upgrade to this newest driver the X server fails to show anything
on my dell latitude D505, with intel 82852/855GM integrated graphics
device. When gdm starts up, I see some flicker, including a (possible)
quick
Hi,
because only amd64 versions of the package is available, I was trying to
build the package myself in a debootstrap chroot. However the package
did not build properly:
# codegen helper, should be the same code whatever the build-time
# python runtime
mkdir
Hi again,
sorry for not checking immediately, I've been a little too trigger-happy
here. In fact, the package failed to build properly (only atk and pango
modules were being build) because of missing dependencies.
After installing libxcb-xlib0-dev and libpthread-stubs0-dev packages,
the build
Hello,
some additional information about my failure to use JkMountFile of
mod_jk:
I added debug output to the function uri_worker_map_load in
native/common/jk_uri_worker_map.c:
jk_log(l, JK_LOG_INFO, loading '%s', uw_map-fname);
And in /var/log/apache2/mod_jk.log I read:
... loading
On Wed, 2006-11-01 at 00:11 -0300, Gustavo Noronha Silva wrote:
I actually found the problem, and it would be great if you guys could
try out the package I'm making available here:
http://people.debian.org/~kov/stuff/libgksu2-0_2.0.3-1_i386.deb
It includes a small patch to fix the problem,
On Mon, 2006-10-30 at 23:53 -0300, Gustavo Noronha Silva wrote:
Em Mon, 30 Oct 2006 18:20:31 +0100
Bart Vanhaute [EMAIL PROTECTED] escreveu:
The bug about not being able to open display only occurs when the
password is retreived from the gnome keyring. If I do not store the
password
Package: libapache2-mod-jk
Version: 1:1.2.18-2
Severity: normal
The JkMountFile directive does not appear to work. The directive should point to
a file containing mount points
(see http://tomcat.apache.org/connectors-doc/config/apache.html)
Mount point specified in a apache .conf file are
Package: gksu
Version: 2.0.0-1
Followup-For: Bug #395462
The bug about not being able to open display only occurs when the password
is retreived from the gnome keyring. If I do not store the password, and type
it in each time when doing the gksu, there is no problem connecting to the
display.
Package: eclipse-ecj
Version: 3.1.2-2
Severity: normal
The eclipse-ecj contains a broken symbolic link in /usr/share/ant/lib:
jdtcore.jar links to ../../eclipse/plugins/org.eclipse.jdt.core_3.1.1.jar but
should probably link to ../../eclipse/plugins/org.eclipse.jdt.core_3.1.2.jar
I don't know
Package: libxerces2-java
Version: 2.8.0-1
Severity: critical
Justification: breaks unrelated software
This package depends on libjaxp1.2-java, however there is a symbolic link
/usr/share/java/xmlParserAPIs.jar refering to jaxp-1.3.jar.
Additionally, if I try to run ant (which depends on
Package: python-gnome2-extras
Version: 2.14.0-1
Severity: minor
The description of this package still includes:
This package is a dependency package, which selects the right package
for the default Python version (currently v2.3).
Because of the python policy transition, this is no longer the
Hello,
this bug only occurs when /apps/metacity/general/raise_on_click is
false.
The bug is actually a duplicate of #360791 filed on metacity.
Bart.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: x11-common
Version: 1:7.0.11
Severity: normal
If I reinstall x11-common (because I wronly removed the X
symlink, see e.g. bug 362685), the post-install script fails:
Setting up x11-common (7.0.11) ...
rmdir: /usr/X11R6/bin: Not a directory
x11-common postinst error: Could not remove
Hello,
just a note: when I associated yelp with the application/docbook+xml
mime type in an attempt to fix this bug, yelp recursively started to
open a new window each time a help file was opened. That was rather
difficult to get out of.
Cheers,
Bart.
--
To UNSUBSCRIBE, email to [EMAIL
On Tue, 2006-03-28 at 14:08 -0800, Jamie Zawinski wrote:
xscreensaver is trying to disavow write permission into (e.g.) group
cdrom, and it can't.
Had your group list contained only one element, bartvh, it would
not have called setgroups at all (see comments in driver/setuid.c).
I
Hello,
This new version (4.24-1) claims to have solved the problem of
xscreensaver not starting due to a crash in getgroups(), and as such
closed this bug. However, I still experience the same error on startup:
$ xscreensaver
xscreensaver: couldn't setgroups to bartvh (1000): Operation not
Package: libxul0d
Version: 1.8.0.1-6
Severity: grave
Justification: renders package unusable
An update to this version of xulrunner makes galeon and epiphany crash
on startup. Perhaps they both need to rebuild, but I am filing against
the xulrunner because there seems nothing in the changelog
On Mon, 2005-11-28 at 02:34 -0800, Jamie Zawinski wrote:
when I compile and run this, I get:
setgroups: Operation not permitted
Note that xscreensaver (4.23) only calls setgroups if it needs to: if
the group list already contains only the one group that is intended,
it doesn't call
Hello,
after upgrading my xscreensaver package, I still have the same problem
starting xscreensaver. (Actually I had my xscreensaver set u+s, and
forgot about the problem until this upgrade.)
I downloaded the source code of xscreensaver, and the code fails when it
tries to call setgroups such
Package: rails
Version: 0.13.1-1
Severity: grave
Justification: renders package unusable
$ rails /tmp/test
/usr/share/rails/railties/bin/../lib/../../activesupport/lib/active_support/clean_logger.rb:13:in
`remove_const': constant Logger::Format not defined (NameError)
from
Package: xscreensaver
Version: 4.21-5
Severity: grave
Justification: renders package unusable
The xscreensaver daemon does not start at all. All I get is :
$ xscreensaver
xscreensaver: couldn't setgroups to bartvh (1000): Operation not permitted
I already tried the following:
- reinstalled
In my opinion, the evolution-plugins package does not contain the
exchange connector.
$ dpkg -L evolution-plugins | grep exchange
/usr/lib/evolution/2.2/plugins/org-gnome-exchange-account-setup.eplug
/usr/lib/evolution/2.2/plugins/liborg-gnome-exchange-account-settings.so
Package: galeon
Version: 1.3.19-1
Severity: minor
After upgrade of galeon to this latest version, each time I submit a
form over an insecure connection (plain http), I get the same warning
dialog twice. The same is true for other warnings, like entering a
secure site, etc.
-- System
41 matches
Mail list logo
