Package: metacity
Version: 1:2.28.0-2
Severity: normal
When I use the close window button of the window bar, the window manager closes
a different window. When I double-click the window bar in order to maximize a
window, the window manager raises a different window and maximizes that. I'm
not
A recent update has fixed this problem for me.
Regards
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: base
Severity: critical
Justification: breaks the whole system
Due to recent package updates, my system no longer initializes reliably.
In particular, sometimes lvm disks are not mounted and no dhcp client is
started.
-- System Information:
Debian Release: squeeze/sid
APT prefers
So, now a recent update seems to have restored the master channel
setting and muted all other channels.
Regards
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Simon Paillard wrote:
retitle 528913 upgrade-reports: master ALSA setting muted at boot
thanks
On Sun, May 17, 2009 at 10:12:42AM +0200, Michael Burschik wrote:
It's even worse than suspected. The master setting seems to be muted
after every reboot.
Does this section of the Lenny
A recent package update seems to have fixed this problem for me.
Regards
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: gnome-screensaver
Version: 2.26.1-1
Severity: normal
The screen saver no longer activates.
-- System Information:
Debian Release: squeeze/sid
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable')
Architecture: amd64
Package: gnome
Version: 1:2.24.3~2squeeze1
Severity: normal
The number pad no longer works when using gnome. They still function normally
when using TWM or the console.
-- System Information:
Debian Release: squeeze/sid
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'),
Package: scribus-ng
Version: 1.3.5.dfsg~svn20090208-2
Severity: normal
File: scribus
Scribus fails to print on my Phaser6120. As far as I can tell, nothing happens.
There is no error message, and nothing to be seen in the CUPS log files. Scribus
is the only application I have this problem with.
Package: libaccess-bridge-java-jni
Version: 1.26.0-1
Severity: normal
java.lang.UnsatisfiedLinkError: Can't load library:
/usr/lib/jvm/java-6-openjdk/jre/lib/ext/libjava-access-bridge-jni.so
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1666)
at
It's even worse than suspected. The master setting seems to be muted
after every reboot.
Regards
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-15lenny2
Severity: critical
Justification: breaks the whole system
Since the kernel bails out before writing to disk, this is pretty much all
I know.
-- Package-specific info:
-- System Information:
Debian Release: squeeze/sid
APT prefers
Package: upgrade-reports
Severity: normal
After upgrades on May 13, sound suddenly stopped working because the master
setting of the ALSA mixer had been muted. Phonon is among the packages I
installed on
May 13, but I can't say whether that is the package responsible. I have
appended a
list of
Package: update-manager
Version: 0.68.debian-7
Severity: important
When running the smart upgrade feature of the update-manager, I get the
following error message:
Could not apply changes!
Fix broken packages first.
Since there is no indication which packages are broken, let alone how
Andreas Bombe wrote:
Could you please test if the Hindi/Devanagari input method issue is
still applicable to a Debian version of anki later than 0.9.6-1? Or
better yet if this is an actual anki bug? (Does it also happen on a
fresh test account or a different installation?)
I just tried
One further factoid: while the devanagari characters were not displayed
in the buffer, they were displayed in the minibuffer.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: emacs22
Version: 22.2+2-3
Severity: normal
I have set up emacs to display Devanagari as described in emacswiki.
However, this does not work as expected.
The Devanagari characters in the HELLO file are not displayed. If I
set the input method to devanagari-itrans, I can enter text, but
Package: abiword
Version: 2.6.4-4
Severity: normal
Whenever I select insert symbol from the abiword menu, the program crashes
with the following warning:
(abiword:4002): Pango-WARNING **: shaping failure, expect ugly output.
shape-engine='BasicEngineFc', font='Standard Symbols L 32', text=''
Package: iceweasel
Version: 3.0.1-1
Severity: normal
Tags: l10n
When displaying http://en.wikipedia.org/wiki/Scooby_doo#The_Scooby_clones
in Iceweasel, the text iScooby-Doo, Where Are You!/i is partially
displayed in Devanagari. I will attach a screenshot to the bug report later
if possible.
--
Package: abiword
Version: 2.6.4-4
Severity: normal
When I start up abiword, the font used is too small to see anything (maybe
one point), although the toolbar shows Times New Roman 12-point. I can
switch to some other font and work as usual. If I press Ctrl-space, the
font display in the toolbar
Package: anki
Version: 0.9.6-1
Severity: important
I have configured my desktop to optionally use the m17n-hi-itrans input method
for Hindi/Devanagari. This works fine in AbiWord and OpenOffice, for example,
but not for anki. I have configured my deck to use Lohit Devanagari for the
Hindi field
Package: grub
Version: 0.97-41
Severity: important
When trying to install the latest kernel update, the command
/bin/bash /usr/sbin/update-grub 2.6.25-2-amd64 /boot/vmlinuz-2.6.25-2-amd64
hangs indefinitely. After some checks, it becomes clear that the command
grub-probe
Package: udev
Version: 0.114-2
Severity: important
# /etc/fstab: static file system information.
#
# file system mount point type options dump pass
UUID=3d8468a3-0396-4637-865e-203a863b4452 / ext3
defaults,errors=remount-ro 0 1
Package: gdm
Version: 2.20.3-1
Severity: minor
On shutdown, DGM crashes with the following error (from /var/log/messages):
kernel: gdm[3200]: segfault at 0018 rip 2ac96c6a8cb8 rsp
7fff41539ba0 error 6
I am currently running 2.6.24, but the problem also occurs with Debians
Package: emacs22-gtk
Version: 22.1+1-2.1
Severity: normal
E: emacs22-gtk: subprocess post-installation script returned error exit status 1
E: emacs-goodies-el: dependency problems - leaving unconfigured
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500,
Package: gimp
Version: 2.4.1-1
Severity: normal
I tried to open a location using various valid URLs. I was able to download the
files and open them with gimp, so the images themselves were not the problem.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy:
Original-Nachricht
Datum: Wed, 19 Sep 2007 16:36:07 +
Von: [EMAIL PROTECTED]
An: Michael Burschik [EMAIL PROTECTED]
Betreff: Bug#443197 closed by maximilian attems [EMAIL PROTECTED] (Re:
Bug#443197: linux-image-2.6.22-2-amd64: Kernel sometimes fails to detect ide
Package: linux-image-2.6.22-2-amd64
Version: 2.6.22-4
Severity: critical
Justification: breaks the whole system
The kernel sometimes fails to detect or name the ide disk hdb correctly and
calls it hdf instead
(ok, this might be a udev problem). The system then is unbootable. The error
occurs
Subject: xsane seems to be scanning, but isn't
Package: xsane
Version: 0.99+0.991-2
Severity: grave
Justification: renders package unusable
Xsane seems to scan, but doesn't actually. A progress bar is displayed
and a completely black image is scanned, but the scanner does not
actually do
Package: kooka
Version: 4:3.5.5-3
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20
Package: kooka
Version: 4:3.5.5-3
Severity: grave
Justification: renders package unusable
Kooka seems to scan, but doesn't actually. A progress bar is displayed
and a completely black image is scanned, but the scanner does not
actually do anything. Xsane suffers from the same problem (I am
Steve Langasek wrote:
On Sat, Nov 25, 2006 at 04:40:46PM +0100, Michael Burschik wrote:
The command migrate_passwd.pl /etc/passwd marks all passwords
in /etc/shadow as {crypt} passwords, although they are clearly
{md5} passwords and are marked as such by $1$.
How does this break
Package: migrationtools
Version: 46-2.1
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale:
I can confirm that 2.6.18 detects the SATA disk.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
00:00.0 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc.
Package: installation-reports
Boot method: CD
Image version: Sarge 3.1r0a (i386), etch beta3 daily build (today, amd64)
Date: 16 Sept 2006
Machine: No name with ASUS P5VD2-MX mainboard
Processor: Intel Core2 Duo
Memory: 1024 MB
Partitions: none
Output of lspci and lspci -n:
Base System
Package: guile-1.6-doc
Version: 1.6.7-1
Severity: minor
Guile documentation describes only the iota procedure
of SRFI-1, but boot-9 defines a iota procedure of
arity 1, which is not documented.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-k7
Locale:
Package: base
Severity: important
As S36discover is run after S35mountall.sh, my non-root
SCSI disk was not mounted at boot time. Moving discover
to S32discover resolved the issue.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_US,
38 matches
Mail list logo
