I can't reproduce this bug for some time now.
Several months ago I wanted to see if I can still reproduce it, so I
commented out 'load-module module-switch-on-connect' in
/etc/pulse/default.pa
I wanted to test it for some days but then I forgot about it – it just
worked (for several months now).
Package: simple-scan
Version: 3.32.2.1-1
Severity: normal
Dear Maintainer,
My original report #814047 was closed but since the bug still exists I open a
new report.
* What led up to the situation?
I wanted to scan a photo with a higher scan resolution than 300 dpi (that's the
setting I
Sorry, please ignore my last comment. I enabled auto-login for my user
in Gnome and didn't need the mentioned workaround. When I disable auto-
login I can still reproduce this bug.
Tianming Xie, are we affected by the same bug? I don't want to reassign
the report to PulseAudio since I'm not the
Hi,
thanks for your rapid reply!
Am Montag, den 08.08.2016, 16:55 +0200 schrieb Laura Arjona Reina:
> Thanks for caring and thanks for offering Debian merchandise!
I owe Debian a lot (I'm a Debian user for several years now) and I just
love it. So I'm really happy to print Debian t-shirts.
>
Package: www.debian.org
Severity: wishlist
Dear Maintainer,
I'm the owner of common·shirts, one of the listed companies on the merchandise
page. My shop is located in Vienna, Austria but since there is no information
about the location of companies on the merchandise page a lot of people for
I can't reproduce this bug anymore.
Hello Jörg,
> After a look at your log files my first opinion was disk full or
> memory error.
>
> Please can you check your disk space and run memtest?
There are around 100 GB free space in my home-partition and 3 GB in my
root-partition available. I'll run memtest over night, but I really
Hello Jörg,
I managed to test this with another notebook – with the same result.
I'm running memtest on the notebook I used before for some hours now
without any errors. I keep it running over night and tell you if a
memory error is found.
Is there a log file or anything else helpful I can
Package: simple-scan
Version: 3.19.2-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I wanted to scan a photo with a higher scan resolution than 300 dpi (that's the
setting I always used for documents without any problems).
* What exactly did you do (or not do) that
Even more interesting is an upstream gnome-bluetooth bug report [1].
As I understand it, the pulseaudio module module-bluetooth-discover [2]
is responsible for detecting available bluetooth audio devices using
BlueZ. GDM starts a pulseaudio process [3] before the user does and
Here's the upstream pulseaudio bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=90490
Please have a look at Bug #805414. At least in my case this problem was
apparently caused by GDM capturing the A2DP sink.
After following the guide in the Debian wiki to prevent GDM from
capturing the A2DP sink on session start [1] I can't reproduce this
bug anymore.
[1]
After testing this for two months now I just wanted to mention that I
was wrong (see my last comment): I had the iwlwifi module option bt_coex
disabled all the time but I was and I am still affected by this bug
(same behavior as originally reported).
--
To UNSUBSCRIBE, email to
Because I was affected by a Wi-Fi Bluetooth coexistence bug (when I use
bluetooth speakers for audio output Wi-Fi stops working, see bug
#59), I disabled iwlwifi module option bt_coex.
After disabling bt_coex the behavior when I connect my bluetooth
speakers changed significantly: most of the
The upstream maintainer closed the bug because he's sure he won't find
the time to fix it (see upstream bug report). He added the following
info to Linux Wireless wiki:
Having bluetooth and WiFi running at the same time is a challenge.
These scenarios have been tested thoroughly on 7260 and up,
The upstream maintainer suggested to disable iwlwifi module option
bt_coex. I created a file /etc/modprobe.d/iwlwifi.conf with the
following content:
options iwlwifi bt_coex_active=0
Since I did that and rebooted I can't reproduce this bug anymore. After
my confirmation the upstream maintainer
Am Donnerstag, den 12.02.2015, 10:30 -0300 schrieb Felipe Sateler:
Does this problem occur after disconnecting and reconnecting the
speakers? If so, please provide a verbose log of pulseaudio[1] where
you connect the bluetooth speakers.
This problem occurs every time I connect my
I found a workaround for this bug: When I load the pulseaudio module
module-switch-on-connect by adding this entry to /etc/pulse/default.pa
load-module module-switch-on-connect
I can control the volume of my bluetooth speakers immediately when they
are connected.
I don't understand why the
Package: src:linux
Version: 3.16.7-ckt4-3
Severity: normal
Dear Maintainer,
often when I use my bluetooth speakers for audio output, my Wi-Fi connection
becomes unusable slow. When I stop the playback and wait a few seconds I can
use Wi-Fi again.
The Wi-Fi connection never breaks completely, I
I guess I'm affected by this bug, my report (originally reported against
pulseaudio) was merged with this one. I tested this with two different
notebooks (internal bluetooth adapters: Intel Wireless-N 1030 / Qualcomm
Atheros AR5B22).
In my original report I attached a bluetoothd log file.
If I
This seems to be an upstream bug.
I have the exact same problem when I use the GNOME 3.14 live demo image
from http://www.gnome.org/getting-gnome/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Fri, Jan 30, 2015 at 8:10 AM, Stefan Nagy pub...@stefan-nagy.at wrote:
This sounds like a gnome bug. The volume control is remembering the
old device (internal speakers?) and setting the volume there.
Yes, while the bluetooth speakers are used for audio output after
connection immediately
Am Mittwoch, den 11.02.2015, 09:58 -0300 schrieb Felipe Sateler:
When I connect my bluetooth speakers (and when I'm not affected by bug
776632,
so the speakers are identified as audio output device), they are used for
audio
output immediately – and the volume is always set to 100%. So
I'll add a bluetoothd log file to this report.
I started the Bluetooth daemon, entered GNOME bluetooth settings,
connected to my bluetooth speakers and then entered GNOME audio
settings. The speakers were not added as audio output device.
Over the last months I used to disconnect them, switch
After finding a related bug report [1] (reported against bluez) I tried
to connect the speakers after boot several times (around 20 attempts
with two different notebooks). Before that I didn't realize that I
_always_ have to restart bluetoothd (or deactivate and reactivate the
bluetooth adapter)
Package: pulseaudio
Version: 5.0-13
Severity: normal
Dear Maintainer,
When I connect my bluetooth speakers (and when I'm not affected by bug 776632,
so the speakers are identified as audio output device), they are used for audio
output immediately – and the volume is always set to 100%. So it's
Package: pulseaudio
Version: 5.0-13
Severity: normal
Dear Maintainer,
When I connect my bluetooth speakers (and when I'm not affected by bug 776632,
so the speakers are identified as audio output device), they are used for audio
output immediately, as expected - but I can't control the volume,
Package: upower
Version: 0.99.1-3
Severity: important
Dear Maintainer,
because of a firmware bug [1] my notebook won't be sent into hibernation when
the battery reaches a critical level unless I edit line
UsePercentageForPolicy=false to UsePercentageForPolicy=true in
/etc/UPower/Upower.conf
fixed 730159 3.12.2-3
thanks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
The openSUSE patches by Takashi Iwai seem to have caused other problems
and were dropped two years ago [1]. The maintainer Peter Hutterer closed
(wontfix) the upstream bug report two months ago [2].
[1]
I did a fresh install of Debian Jessie last week and realized that this
issue seems to be solved in grub2 2.00-22.
Some time after I reported this bug I found out that the workaround
mentioned in message #12 of bug 617196 [1] worked for me. Since then I
didn't check if this is still a problem.
Sorry, I totally forgot that I myself reported this bug against
server-xorg-video-intel in November last year. I reported the same bug
in April against libcogl, in the meantime it turned out that this in
fact is a gnome-shell bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743810
I'm going
Probable duplicates of this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724739
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743837
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This bug seems to be related to the use of the debian default desktop
background (wallpaper). I love it, so I never tried to change it…
Using gnome-tweak-tool I realized that the path for the default
wallpaper is /usr/share/images/desktop-base/joy.xml The XML points to
four different SVGs for
This bug was fixed in pyppd by Till Kamppeter, see
https://github.com/OdyX/pyppd/commit/5ddd8b3ea7ca4476d61ec2133f1a3639133f4576
Thanks,
Stefan.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am Montag, den 19.08.2013, 16:41 +0200 schrieb Bastien ROUCARIES:
The nec plus ultra will be to have rule at every the border (graduated
in mm). It will be allow to get margin right and to debug margin
problem
Sorry, I only know how to work with simple vector graphics. AFAIK the
borders are
The best explanation why it actually makes sense that the entire page is
rendered as a bitmap I found at the ghostscript bug tracker (by Ray
Johnston) [1]:
BTW, the reason that the entire page is rendered as an image is that the
PDF transparency model requires any transparent region to be
Hi Brian,
I had a look at this bug report now and I'd like to contribute a vector
graphic version of your default test page. The template is smaller (20.4
vs. 59.3 kB) as well as the resulting PostScript file (153.1 kB vs. 250
kB). Obviously, the printing quality (of the designs) is much better.
In the second case I mentioned in my last message the default renderer
produces a PostScript file with 43.7 MB when I print a single page (the
first page of the document downloaded here [1]).
I opened this file (and the original page) with Inkscape and realized
that the renderer converts the hole
tags 717273 upstream
thanks
I believe this bug affects HPLIP upstream: I downloaded the source code
of the current version of hplip (3.13.7) from the project's website
http://hplipopensource.com – the original PPD
in /prnt/ps/hp-laserjet_1200-ps.ppd.gz includes the two mentioned lines:
Hi Brian,
I'm pretty well convinced that the PostScript interpreter on my printer
is not up to the job of processing Ghostscript's PS, which its developers
maintain is valid PS. At the same time I wonder whether the graphics in
Debian's present default-testpage.pdf contribute to the problem,
Hi OdyX,
when I install printer-driver-postscript-hp I get two new drivers for
my printer model HP LaserJet 1200 in CUPS (I use the web-based
administration interface) to choose from:
HP LaserJet 1200 Postscript (recommended) (en)
HP LaserJet 1200 Postscript (recommended) (en)
Am Donnerstag, den 25.07.2013, 15:10 +0200 schrieb Stefan Nagy:
Seems like last time I only tried to print a test page to
file:/tmp/printout – and that worked.
Now I tried to print a lot of different documents and found out that I
never get the expected result but always the same page when I
Hi Brian,
Printing using the usb backend has changed since Squeeze was released. My
knowledge of things USB is sparse but it might be the suggestions made in bug
#697970 could help.
I tested the configurations suggested in comment #81 of bug #697970 now,
but none of them helped. No matter
.
Am Donnerstag, den 18.07.2013, 21:40 +0200 schrieb Didier 'OdyX' Raboud:
Le jeudi, 18 juillet 2013 19.21:28, Stefan Nagy a écrit :
when I install printer-driver-postscript-hp I get two new drivers for
my printer model HP LaserJet 1200 in CUPS (I use the web-based
administration interface
Package: printer-driver-postscript-hp
Version: 3.13.4-1
Severity: minor
Dear Maintainer,
when I install printer-driver-postscript-hp I get two new drivers for my
printer model HP LaserJet 1200 in CUPS (I use the web-based administration
interface) to choose from:
HP LaserJet 1200 Postscript
Am Donnerstag, den 21.02.2013, 00:50 + schrieb Ben Hutchings:
while my BIOS/UEFI reports a battery charge capacity of 92% for my notebook-
battery, upower still reports a charge capacity of 100% (AFAIK upower gets
this
information from the kernel - I believe this to be a kernel ACPI
In general I should mention that I am able to print text files and
bitmaps. To me it seems like the problems appear in documents with
simple graphics (that can be vectorized?).
When I print a LibreOffice text document with the logo of my university
in the upper right corner I get the whole page
Package: openprinting-ppds
Version: 20120523-1
Severity: normal
Dear Maintainer,
when I connect my local printer (HP LaserJet 1200) with a USB cable to my
computer, the printer is automatically set up with the PostScript PPD ('HP
LaserJet 1200 Postscript [en]') driver, which is the only driver
No matter if I'm on battery (discharging) or have the ac adapter plugged
in (charging), if I'm plugging the ac adapter in or out – I don't see
any power related uevents from the kernel with 'udevadm monitor' or
'udevadm monitor --kernel'. I also tried to change the logging priority
of udevadm with
I tested this also with debian kernel linux-image-3.7-trunk-amd64
(3.7.8-1~experimental.1) and with upstream kernel v3.7.9. Please tell me
if I can provide more useful information.
Stefan.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
while my BIOS/UEFI reports a battery charge capacity of 92% for my
notebook-
battery, upower still reports a charge capacity of 100% (AFAIK
upower gets this
information from the kernel - I believe this to be a kernel ACPI
bug).
The kernel driver doesn't do anything very interesting so it's
Hi Daniel,
I just found this report by accident and I think this is no bug. There
is a possibility to configure a hidden wifi network manually: When you
click the 'network settings'-option, choose 'Wireless' and then, in the
drop-down-menu 'Network Name' choose the option 'Other…' you can
Package: installation-reports
Severity: normal
Tags: d-i
Dear Maintainer,
network configuration in debian installer fails when I try to setup a Wi-Fi
network with disabled SSID broadcast. I can reprocude this with encryption
(WEP and WPA2) aswell as without any encryption. With the same WLAN
Sorry, I forgot to add that I have no problems connecting to the same
'hidden' wireless networks in GNOME (after debian installation). The
problem only occurs in debian installer.
Stefan.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Package: src:linux
Version: 3.2.35-2
Severity: normal
Dear Maintainer,
while my BIOS/UEFI reports a battery charge capacity of 92% for my notebook-
battery, upower still reports a charge capacity of 100% (AFAIK upower gets this
information from the kernel - I believe this to be a kernel ACPI
In the meantime I had the opportunity to test this on another HP Folio
13-2000 which is running Windows 7. The user wasn't affected by this bug
only because the default settings for 'critical battery level' were set
to 5 percent – so when the battery reached 5 percent the notebook would
be sent
'upower --monitor' shows that the battery status is updated every 30
seconds ('device changed') while the ac adapter status will never be
updated.
When I plug in/out the ac adapter I get a message 'daemon changed' next
time the battery status gets updated; after that 'on battery' shows the
I found this related upstream bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=45321
However, I tried out the workaround mentioned in Comment 4 and it didn't
work for me. I compiled my kernel with CONFIG_ACPI_PROCFS_POWER=y, but
UPower still fails to update the status of the AC adapter.
I tested this the whole day and eventually got a clearer picture of this
bug. gnome-settings-daemon fails to send my notebook into hibernation
because of two separate issues:
1) UPower fails to update the status of the AC adaptor. 'upower --dump'
shows that the time of last update is always
I tested this the whole day and eventually got a clearer picture of this
bug. gnome-settings-daemon fails to send my notebook into hibernation
because of two separate issues:
1) UPower fails to update the status of the AC adaptor. 'upower --dump'
shows that the time of last update is always
Ben Hutchings wrote:
And presumably not very old (upower reports that the 'full' value is
the same as the 'full-design' value).
I bought the notebook half a year ago, so yes, the battery is quite new.
However, I don't see any similar quirk in the battery driver for any
other models, and this
Ben Hutchings wrote:
Is this a genuine HP or third party battery?
It's a genuin HP battery.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I just realized that UPower doesn't update the status of
/org/freedesktop/UPower/devices/line_power_ACAD (no matter which kernel
I use). It seems like the date in line 'updated:' is always identical to
uptime.
With kernel 3.6.9 however it gets even worse: both devices are affected
by this now:
-
Ben Hutchings wrote:
You confirmed that hibernation works and that GNOME is properly
detecting the low battery level, so I don't see how this is a kernel
bug. The decision to hibernate is a matter of userland policy, so I
think you were right with #684186.
I'm not so sure about this since
I tested this some more by observing the output of 'acpi -a'. When my
battery is low the values (percentage, time remaining) jump.
Two minutes before my notebook suddenly shut down I got 00:05:00 minutes
left, a few seconds later 00:04:34 minutes, then 00:04:46 minutes,
00:04:54 minutes… Two or
Michael Gilbert wrote:
Unfortunately, there is no consistent or standardized behavior when
the battery runs out. If you let that happen, you take the risk of
losing unsaved data.
I'm not sure I'm getting your point (english isn't my first language)…
Are you saying that users in general can't
Package: src:linux
Version: 3.6.9-1~experimental.1
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
when my notebook's battery runs out (reaches a critical state), GNOME isn't
able to send it into hibernation. GNOME reports low as well as critical battery
level but
Am Montag, den 05.11.2012, 12:45 +0100 schrieb Stefan Nagy:
Since I didn't encounter this problem before
linux-image-3.6-trunk-amd64 I had a look at these settings on
linux-image-3.2.0-4-amd64 with normal backlight brightness:
'acpi_video0' (brightness 0, actual_brightness 0
Am Montag, den 05.11.2012, 12:45 +0100 schrieb Stefan Nagy:
Since I didn't encounter this problem before
linux-image-3.6-trunk-amd64 I had a look at these settings on
linux-image-3.2.0-4-amd64 with normal backlight brightness:
'acpi_video0' (brightness 0, actual_brightness 0
Hi Jonathan,
This patch does not seem to be part of linux-next nor in lenb's tree,
unfortunately. Please let us know when it is accepted upstream.
OK, sure. I presumed it was accepted already since Zhang Rui marked it
as RESOLVED CODE_FIX.
Based on https://bugs.launchpad.net/bugs/1066211 I
Package: src:linux
Version: 3.6.4-1~experimental.1
Severity: normal
Tags: upstream
Dear Maintainer,
everytime I boot, my notebook's display stays black since kernel linux-
image-3.6-amd64. I'm using an external display most of the time and so I found
out that the backlight brightness in GNOME
At least in my case this is an upstream bug – I tested this with the
vanilla kernel v3.6.4 and got the same results.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am Donnerstag, den 01.11.2012, 22:27 +0100 schrieb Michael Biebl:
upower uses a different interface to query the battery state then e.g.
acpi.
upower uses the sysfs interface, which you can check manually.
If those values are incorrect, this might either be an indication fro
broken hardware
I'll attach the output of 'upower --dump' for three different
situations:
1. Shortly before my notebook battery drains: Note that the reported
battery percentage is 2.99967%, time to empty is 12.1 minutes. I have
seen the exact same values over a period of more than 10 minutes – those
are the
I took some time to test this, here are the results:
1. I changed 'org.gnome.settings-daemon.plugins.power
use-time-for-policy true' to false. As expected, at 3% I got a warning
message, that battery level was critical – and since I knew that my
battery would drain while upower would report 3%
It took me some time to find out that the video-out hotkey works when I
hold it down for a second or so. But no matter if I hold it down for
some time or not: I'd always get a 'p'.
For example: Let's say I want to change the video mode while writing
this message in Evolution. I'm using my
I can confirm that the bug is fixed in kernel 3.6 and that applying the
patch provided by Jeroen in Message #71 (PCI: acpiphp: check whether
_ADR evaluation succeeded) on top of 3.2.30 solves the problem.
Thanks!
Stefan.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Here's the upstrem report:
https://bugzilla.kernel.org/show_bug.cgi?id=46481
Since I filed the bug against the ACPI PCI Hotplug driver I didn't want
to decide if we (me and the original reporter Jeroen Nijhof) are
affected by the same bug – all I know is that the build-in driver causes
similar
As the original reporter pointed out, this bug is triggered by a change
in the debian kernel configuration regarding the ACPI PCI Hotplug driver
[1]. Since kernel update linux-image-3.2.0-2-amd64 (3.2.10-1) this
driver is build in (CONFIG_HOTPLUG_PCI_ACPI=y) instead of being compiled
as a module
Am Sonntag, den 26.08.2012, 13:37 -0700 schrieb Ben Hutchings:
Please test Linux 3.5 (packaged in experimental) and if that has the
same problem then open an upstream bug report.
OK – I already tested linux-image-3.5-trunk-amd64
(3.5.2-1~experimental.1) the bug is still present, so I'll file
Christian PERRIER wrote:
Quoting Brian Masinick (masin...@yahoo.com):
That's great! Where can I get a build to verify the fix?
This should be in the daily builds:
http://d-i.debian.org/daily-images/
I suggest picking the *netboot* image.
After successfully installing
Package: debian-installer
Severity: wishlist
Tags: d-i
Dear Maintainer,
I have a notebook with a realtek nic which doesn't need any non-free firmware
files to operate. However, debian installer requests me to install non-free
firmware. It doesn't make any difference if I install it or reject the
Am Mittwoch, den 15.08.2012, 11:53 +0100 schrieb Brian Potkin:
What else can the installer do other than pass on the request from the
kernel? Please don't shoot the messenger.
Sorry – I wasn't sure to which package this bug belongs… Could you
reassign it please?
Thanks,
Stefan.
signature.asc
Am Mittwoch, den 15.08.2012, 20:21 +0200 schrieb Bjørn Mork:
The driver firmware request is required to enable those who want to load
the optional firmware. Just ignore it if you don't want to.
I'm not saying debian installer shouldn't recommend / ask for non-free
firmware at all [1] but I do
I tried daily build images and want to confirm what Brian Potkin says in
Message #46 of bug #683849:
http://d-i.debian.org/daily-images/amd64/daily/netboot/mini.iso
This image just works. The missing firmware is properly detected,
displayed and installed.
Hi Michael,
Are you running gnome in classic mode (fallback) or shell?
I'm running gnome-shell.
Is gnome-settings-daemon running?
Yes, it's running.
What's the output of
gsettings list-recursively org.gnome.settings-daemon.plugins.power
org.gnome.settings-daemon.plugins.power active
By the way, lid-close-ac-action 'suspend' lid-close-battery-action
'suspend' don't work either – nothing happens when I close the lid.
Should I write another report for this?
signature.asc
Description: This is a digitally signed message part
Package: gnome-settings-daemon
Version: 3.4.2-4+b1
Severity: normal
Dear Maintainer,
I have a hotkey/multimedia key/action key (Fn+F4) on my notebook's keyboard to
switch to external monitors/projectors etc. I thought it would be a normal
XF86Display-key so what I expected was something like
Package: gnome-power-manager
Version: 3.4.0-2
Severity: important
Dear Maintainer,
on my notebook (HP Folio 13-2000) the gnome power manager settings regarding
the action taken when battery reaches a critical level are ignored.
I get notifications that the battery level is low but then suddenly
I tried to install beta 1 now – this bug is still present:
http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-dvd/debian-wheezy-DI-b1-amd64-DVD-1.iso
The workaround mentioned in Message #35 works for me.
Cheers,
Stefan.
--
To UNSUBSCRIBE, email to
into the TouchPad).
Cheers,
Stefan Nagy.
signature.asc
Description: This is a digitally signed message part
Dear Maintainer,
seems like some Ubuntu users were also affected by this bug (on the same
notebook model) [1] and already reported it upstream [2].
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974568
[2] https://bugzilla.kernel.org/show_bug.cgi?id=43097
Cheers,
Stefan Nagy
Package: src
Version: 3.2.21-3
Severity: normal
Dear Maintainer,
some multimedia/action keys of my notebook don't work. Neither xev nor showkey,
evtest or xinput report anything at all when I press (Fn together with) certain
keys.
Affected are the following combinations: Fn+F2 (display
Package: installation-reports
Severity: important
Tags: d-i
-- Package-specific info:
Boot method: USB memory stick
Image version:
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
(2012-07-16)
Date: 2012-07-16
Machine: HP Folio 13 - 2000
+1) – and it works.
Cheers,
Stefan Nagy.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin
Am Samstag, den 26.05.2012, 00:00 +0200 schrieb Julien Cristau:
Don't disable 3d support?
I didn't disable 3D support (see attached glxinfo-output).
Cheers,
Stefan.
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
After installing some updates – sorry, I don't know which was the
relevant one, I assume gnome-shell – I'm forced into GNOME fallback mode
now; I suppose my graphics hardware got blacklisted.
xsession-errors contains the following lines:
gnome-session-is-accelerated: No hardware 3D support.
I can reproduce this bug with the radeon-driver. Everytime I hover over
a footnote which contains a lot of text in LibreOffice compiz crashes.
The best workaround for me at this point is to deactivate all tooltips
('Tips' and 'Extended tips') in LibreOffice (Tools - Options -
LibreOffice -
Dear Maintainer,
is the backtrace I attached last time of any use? Should I file this bug
against gnome-shell? However, I'd be glad to provide more infomation.
BTW, this bug is still present in version 1:6.14.4-2.
Thanks,
Stefan.
signature.asc
Description: This is a digitally signed message
1 - 100 of 108 matches
Mail list logo
