Bug#717273: printer-driver-postscript-hp: HP LaserJet 1200: User can choose between two identical PS drivers

[Stefan Nagy]

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

Bug#743810: libcogl20: Visual artifacts in gnome shell activities view

[Stefan Nagy]

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 different screen resolutions.

When I use gnome-tweak-tool to
choose /usr/share/images/desktop-base/joy-wallpaper_1920x1080.svg
directly I can't reproduce this issue. The same applies to using any
other SVG, PNG oder JPG I tried.

I can reproduce this issue simply by changing the path for the desktop
background to /usr/share/images/desktop-base/joy.xml again.

For now I'm going to reassign this bug to desktop-base.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#743810: Visual artifacts in gnome shell activities view

[Stefan Nagy]

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

Bug#641751: grub2: Missing characters (Umlaute) on a encrypted system (LUKS on LVM)

[Stefan Nagy]

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.

This time I used LVM within an encrypted partition again, so /boot was
the only partition available at boot time (same as in September 2011
when I reported this bug). As of now it seems the font which was missing
before (unicode.pf2) is now installed not only in /boot/grub/ but also
in /boot/grub/fonts/.



[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617196#12


signature.asc
Description: This is a digitally signed message part

Bug#683762: On/Off button & LED indicator doesn't work on HP Folio 13 - 2000

[Stefan Nagy]

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] 
https://build.opensuse.org/package/view_file?file=xf86-input-synaptics.changes&package=xf86-input-synaptics&project=openSUSE%3A12.2&rev=62387336edb5473988dd9fc4fdba589a

[2] https://bugs.freedesktop.org/show_bug.cgi?id=39055#c15


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#730159: Screen corruption on gnome 3.8 with Intel HD 3000 graphics

[Stefan Nagy]

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 to merge the two reports. Sorry again.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684186:

[Stefan Nagy]

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 lowest values I get, at this point they won't change anymore.

At the same time 'acpi -b' reports a battery percentage of 2%.

2. Shortly after I connected the power supply and booted up: Note that
now the reported values are really strange now. Not only battery
percentage is 0% but also energy-full and energy-full-design is 0 Wh.

'acpi -b' also reports a battery percentage of 0%.

3. A few minutes later (still charging): Values seem to be back to
normal.


Please have a look at the output of 'gsettings list-recursively
org.gnome.settings-daemon.plugins.power' in comment #15, setting:
'percentage-action 2'. I assume this means that critical battery action
should be fired at a battery percentage of 2%.

As I said before, 'upower --dump' will never report a lower battery
percentage than 2.99967%. Maybe this is why the critical battery action
isn't executed?

I'll try to manipulate this value and report back later.
stefan@rosa:~$ upower --dump
Device: /org/freedesktop/UPower/devices/line_power_ACAD
  native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/ACPI0003:00/power_supply/ACAD
  power supply: yes
  updated:  Thu Nov  1 12:45:56 2012 (3222 seconds ago)
  has history:  no
  has statistics:   no
  line-power
online: no

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0A:00/power_supply/BAT1
  vendor:   13-17
  model:Venturi
  serial:   01317 01/24/2012
  power supply: yes
  updated:  Thu Nov  1 13:39:32 2012 (6 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   discharging
energy:  1.798 Wh
energy-empty:0 Wh
energy-full: 59.94 Wh
energy-full-design:  59.94 Wh
energy-rate: 8.88 W
voltage: 10.314 V
time to empty:   12.1 minutes
percentage:  2.99967%
capacity:100%
  History (rate):
1351773572  8.880   discharging
1351773542  8.868   discharging
1351773512  8.991   discharging
1351773482  9.490   discharging
stefan@rosa:~$ upower --dump
Device: /org/freedesktop/UPower/devices/line_power_ACAD
  native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/ACPI0003:00/power_supply/ACAD
  power supply: yes
  updated:  Thu Nov  1 13:50:13 2012 (53 seconds ago)
  has history:  no
  has statistics:   no
  line-power
online: yes

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0A:00/power_supply/BAT1
  vendor:   13-17
  model:Venturi
  serial:   01317 01/24/2012
  power supply: yes
  updated:  Thu Nov  1 13:50:48 2012 (18 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   charging
energy:  0 Wh
energy-empty:0 Wh
energy-full: 0 Wh
energy-full-design:  0 Wh
energy-rate: 0 W
voltage: 10.581 V
percentage:  0%
capacity:100%
  History (charge):
1351774213  0.000   unknown
  History (rate):
1351774213  0.000   unknown

Daemon:
  daemon-version:  0.9.17
  can-suspend: yes
  can-hibernateyes
  on-battery:  no
  on-low-battery:  no
  lid-is-closed:   yes
  lid-is-present:  yes
  is-docked:   yes
stefan@rosa:~$ upower --dump
Device: /org/freedesktop/UPower/devices/line_power_ACAD
  native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/ACPI0003:00/power_supply/ACAD
  power supply: yes
  updated:  Thu Nov  1 13:50:13 2012 (448 seconds ago)
  has history:  no
  has statistics:   no
  line-power
online: yes

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0A:00/power_supply/BAT1
  vendor:   13-17
  model:Venturi
  serial:   01317 01/24/2012
  power supply: yes
  updated:  Thu Nov  1 13:57:18 2012 (23 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   charging
energy:  2.397 Wh
energy-empty:0 W

Bug#684186:

[Stefan Nagy]

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% hibernation was never
executed. The battery just drained.

2. I assumed I would have to change the values of 'percentage-critical'
and 'percentage-action' – I chose 3 and 4 percent. Unexpectedly, this
didn't help at all, nothing really changed.

3. So I set 'org.gnome.settings-daemon.plugins.power
use-time-for-policy' to 'true' again and changed the values of 'time
critical' and 'time-action' to 720 and 600 seconds. But this didn't help
either, again nothing really changed.

Apart from that I observed the 'time to empty' value in the output of
'upower --dump' and realized that this value would never be less then 9
minutes. After it reaches 10 minutes it jumps up and down a bit for the
next minutes – until the battery drains.

To me it looks like there are two separate issues: 1. g-s-d doesn't do
what it should (my settings seem to be ignored) and 2. obviously the
values reported by upower aren't correct.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684186:

[Stefan Nagy]

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 or the kernel/acpi driver reporting incorrect values.
> 
> Michael 

Thanks, I'm going to open another bug report regarding the strange
values.

However, as mentioned in comment #47 it looks like there are two
seperate issues, since g-s-d still fails to execute actions on low
battery condition – even if I change the settings to meet the values
reported by upower. Or am I doing something wrong here?

Stefan


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#681743:

[Stefan Nagy]

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

Bug#692361: linux-image-3.6-trunk-amd64: ACPI display backlight brightness is set to zero at every boot-up

[Stefan Nagy]

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 settings is set to zero – I can
solve the problem by increasing the screen brightness but at the next boot this
setting will be lost, screen brightness is set to zero again. Since my media-
keys to change screen brightness don't work for now (see bug #683777) I
wouldn't be able to change the setting without an external display. As
described in bug #681743, setting the kernel boot parameter
i915.invert_brightness=1 works fine as workaround.

I looked into /sys/class/backlight/acpi_video0/brightness to confirm that it's
set to zero and realized that I have two entries in backlight: 'acpi_video0'
(with brightness set to 0, actual_brightness is 0) and 'intel_backlight' (with
brightness set to 4882, actual_brightness is 0). When I increase screen
brightness to 100% in GNOME settings, the values change to: 'acpi_video0'
brightness & actual_brightness 10; 'intel_backlight' brightness &
actual_brightness 4882.

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),
'intel_backlight' (brightness 4882, actual_brightness 4882). So the difference
between 3.2 and 3.6 seems to be that backlight brightness wasn't controlled by
the ACPI driver but the device specific driver in 3.2.

I tested this with vanilla kernel 3.6.4 and can confirm that this is an
upstream bug. I suppose this bug report is a duplicate of #681743 but since I'm
seeing this on another notebook (HP Folio 13-2000) than the original reporter
Jonathan Nieder asked me to open a new report.

Please tell me if you need more information.



-- Package-specific info:
** Version:
Linux version 3.6-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-1) ) #1 SMP Debian 3.6.4-1~experimental.1

** Command line:
BOOT_IMAGE=/vmlinuz-3.6-trunk-amd64 root=/dev/mapper/rosa-root ro quiet splash

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[   10.154473] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   10.170809] iTCO_vendor_support: vendor-support=0
[   10.174866] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[   10.174915] iTCO_wdt: Found a Cougar Point TCO device (Version=2, 
TCOBASE=0x0460)
[   10.175439] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   10.186166] iwlwifi :02:00.0: loaded firmware version 18.168.6.1
[   10.211152] input: HP TrueVision HD as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input4
[   10.211575] usbcore: registered new interface driver uvcvideo
[   10.211577] USB Video Class driver (1.1.1)
[   10.214850] iwldvm: Intel(R) Wireless WiFi Link AGN driver for Linux, 
in-tree:
[   10.214853] iwldvm: Copyright(c) 2003-2012 Intel Corporation
[   10.214872] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[   10.214875] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[   10.214876] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[   10.214878] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled
[   10.214880] iwlwifi :02:00.0: CONFIG_IWLWIFI_P2P enabled
[   10.214882] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 
1030 BGN, REV=0xB0
[   10.215001] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
[   10.230647] iwlwifi :02:00.0: device EEPROM VER=0x716, CALIB=0x6
[   10.230651] iwlwifi :02:00.0: Device SKU: 0x150
[   10.230654] iwlwifi :02:00.0: Valid Tx ant: 0x1, Valid Rx ant: 0x3
[   10.230745] Registered led device: phy0-led
[   10.243258] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[   10.245943] cfg80211: World regulatory domain updated:
[   10.245947] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   10.245951] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   10.245954] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   10.245957] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   10.245959] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   10.245962] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   10.435400] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[   10.524024] input: HP WMI hotkeys as /devices/virtual/input/input5
[   10.655051] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit 
banging on pin 2
[   10.784579] fbcon: inteldrmfb (fb0) is primary device
[   10.834902] rts_pstor: device scan complete
[   10.835282] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S.  

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

[Stefan Nagy]

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

Bug#684186: gnome-settings-daemon: fails to execute action on low battery condition

[Stefan Nagy]

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 identical to uptime. When
the adapter was plugged in while boot process, action on critical
battery will never be fired.

2) At low battery level the information UPower gets (from the kernel?)
is not correct. The reported battery level will never be lower than
2.99967% ('upower --dump') or 2% ('acpi -b'), time remaining never less
than around 5 minutes. gnome-settings-daemon's default is
'use-time-for-policy true' and 'time-action 120'. This status will never
be reached since the battery drains while time remaining is something
around 300 seconds.


I managed to manipulate the settings so that Gnome sends my notebook
into hibernation in two different ways:

1) I set 'time-critical 420' and 'time-action 300' and booted with the
AC adaptor plugged out, so that the status reported by 'upower --dump'
would be: 'line-power online: no'.

2) I set 'use-time-for-policy false', 'percentage-critical
4' (default=3),'percentage-action 3' (default=2) and booted with the AC
adaptor plugged out, so that the status reported by 'upower --dump'
would be: 'line-power online: no'.


Since to me it seems obvious that this is no gnome-settings-daemon bug,
I'm going to reassign it to UPower. Regarding the wrong battery levels
reported to UPower I already filed a bug against the kernel: #695634.


signature.asc
Description: This is a digitally signed message part

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

[Stefan Nagy]

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 identical to uptime. When
the adapter was plugged in while boot process, action on critical
battery will never be fired.

2) At low battery level the information UPower gets (from the kernel?)
is not correct. The reported battery level will never be lower than
2.99967% ('upower --dump') or 2% ('acpi -b'), time remaining never less
than around 5 minutes. gnome-settings-daemon's default is
'use-time-for-policy true' and 'time-action 120'. This status will never
be reached since the battery drains while time remaining is something
around 300 seconds.


I managed to manipulate the settings so that Gnome sends my notebook
into hibernation in two different ways:

1) I set 'time-critical 420' and 'time-action 300' and booted with the
AC adaptor plugged out, so that the status reported by 'upower --dump'
would be: 'line-power online: no'.

2) I set 'use-time-for-policy false', 'percentage-critical
4' (default=3),'percentage-action 3' (default=2) and booted with the AC
adaptor plugged out, so that the status reported by 'upower --dump'
would be: 'line-power online: no'.


I reassigned the bug I reported against gnome-settings-daemon to UPower:
#684186 However, UPower definitely receives incorrect values when
battery level is low. So I'm going to leave this bug open.


signature.asc
Description: This is a digitally signed message part

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

[Stefan Nagy]

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 doesn't seem that likely to be a firmware bug
> as this would be a problem for Windows power management as well.  (And
> there don't seem to be any firmware updates available for this model.)
> Did you leave Windows installed, and if so can you check whether that
> detects the nearly-empty battery properly?

No, I didn't. And since I'm writing my master theses on this notebook
right now I have no time to back up all data and setup Windows… I don't
know how relibale this information ist, but I just tested the battery
with the 'HP Unified Extensible Firmware Interface (UEFI) Support
Environment' and it passed.

Stefan.




signature.asc
Description: This is a digitally signed message part

Bug#684186: gnome-settings-daemon: fails to execute action on low battery condition

[Stefan Nagy]

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.


signature.asc
Description: This is a digitally signed message part

Bug#684186: UPower does not send line_power_ACAD events

[Stefan Nagy]

'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
correct status (ac adapter plugged in: 'no', ac adapter plugged out:
'yes'). However, since the status of
device /org/freedesktop/UPower/devices/line_power_ACAD isn't correct,
action on critical battery won't be fired when the ac adapter was
plugged at boot time.

'udevadm monitor --kernel --udev' shows that the kernel (and udev) never
sends an event for none of the two devices (ac adapter & battery). It
seems like UPower forces a battery status update every 30 seconds while
it doesn't force a status update for the ac adapter.

Maybe it would make sense if UPower would force an update not only for
the battery but also for the ac adapter.


signature.asc
Description: This is a digitally signed message part

Bug#665493: bug fixed in 3.6; patch

[Stefan Nagy]

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
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684331:

[Stefan Nagy]

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 external monitor, the notebook
monitor is deactivated. Now, I hold down the video-out hotkey for a
second or so and get the mirrored view as expected (the notebook monitor
gets activated and I see the same output on both monitors). But in
addition I get a 'p' in this message, right after the last word I wrote
before I switched to the other video mode.

Another way to change the video mode is to double-press the hotkey – it
works just like double clicking. And: I get just one 'p' (and not two as
expected). When I press the video-out hotkey once (and avoid holding it
down for a second or so) I just get one 'p' without any video mode
change. 

Now, I don't know what to do: obviously my original report was wrong but
there's still a bug… Should I close this report and open a new one?


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it

[Stefan Nagy]

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 request
– the network adapter just works.

Debian installer shouldn't ask me to install non-free firmware for a device
that works just as well without it.

My hardware: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit
Ethernet controller [10ec:8168] (rev 06)
Firmware file which debian installer requests: rtl_nic/rtl8168e-3.fw



-- 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/sh linked to /bin/dash


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it

[Stefan Nagy]

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
Description: This is a digitally signed message part

Bug#684968: debian-installer: requests non-free firmware for a device that works just as well without it

[Stefan Nagy]

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 care about my freedom as software user.

My notebook has an Intel WLAN adapter and a Realtek NIC – debian
installer tells me in both cases that my hardware needs proprietary
software to operate even if the consequences of not installing the
non-free firmware are completely different. My WLAN adapter doesn't work
at all when I decide not to install the firmware.

I don't think that it's a good solution to seperate non-free firmware
just to tell users to provide it while installation process. In my
opinion debian (installer) should provide more information about the
concrete consequences of not installing a specific firmware file: Will
the device work at all? What are the probable limitations?

Debian (installer) should enable users to make a decision here. Instead
right now it seems like the safe way in each and every case is to
install proprietary firmware – and everyone who decides not to install
it is on his/her own.

This is just my opinion (and that's why I reported this bug with
severity: wishlist).



[1] http://tinyurl.com/bp6pz9b


signature.asc
Description: This is a digitally signed message part

Bug#683690: Debian Installer stops at Detect Network Hardware

[Stefan Nagy]

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
http://d-i.debian.org/daily-images/amd64/daily/netboot/mini.iso I tried
out the wheezy Beta 1 release netboot image
(debian/dists/testing/main/installer-amd64/current/images/netboot/mini.iso)
– turns out that I can't reproduce the bug with this image neither.

However, I can reproduce this bug with all other Beta 1 release images
(DVD, CD, Netinst).

I don't really get it…


signature.asc
Description: This is a digitally signed message part

Bug#665493: linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)

[Stefan Nagy]

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 (CONFIG_HOTPLUG_PCI_ACPI=m).

The kernel changelog lists Ben Hutchings as author for this change:
- [x86] Change HOTPLUG_PCI_ACPI to built-in (Closes: #663433) [2]

The reason for this decision was that the ACPI PCI Hotplug driver didn't
get loaded on machines which need it for ExpressCard hotplugging to work
[3].

Since this bug got no attention at all on the kernel-pci mailinglist for
three months now [4] I wanted to file a bugreport upstream against
driver: pci – but I'm not sure what to do now since it doesn't seem to
be very safe to build-in this driver and maybe the debian kernel team
wants to reconsider this decision…?

Please tell me if this decision is final – even though the kernel fails
to load on at least two recent machines with the ACPI PCI Hotplug driver
build in. If it is I'll file a bugreport upstream.

Thanks,
Stefan.



P.S. The default kernel configuration for this item is
CONFIG_HOTPLUG_PCI_ACPI=n. I also had a look at this configuration item
in Ubuntu – it's set to CONFIG_HOTPLUG_PCI_ACPI=m.

[1] http://cateee.net/lkddb/web-lkddb/HOTPLUG_PCI_ACPI.html
[2]
http://packages.debian.org/changelogs/pool/main/l/linux/linux_3.2.23-1/changelog#version3.2.10-1
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663433
[4] http://thread.gmane.org/gmane.linux.kernel.pci/15559


signature.asc
Description: This is a digitally signed message part

Bug#665493: linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)

[Stefan Nagy]

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 the
upstream bug report soon.

> > P.S. The default kernel configuration for this item is
> > CONFIG_HOTPLUG_PCI_ACPI=n.
> 
> The default kernel configuration has a lot of features disabled that
> many users need.

I see.

> > I also had a look at this configuration item
> > in Ubuntu – it's set to CONFIG_HOTPLUG_PCI_ACPI=m.
> 
> Have you checked whether they add it to /proc/modules?

You mean if they add it to /etc/modules, right? I don't know, I haven't
checked this yet.

But this is maybe interesting: When I compile my kernel with
CONFIG_HOTPLUG_PCI_ACPI=m and put acpiphp in /etc/modules I can't
reproduce this bug even though I'm sure the module is loaded:

[   19.299137] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[   19.299341] acpiphp: Slot [1] registered

$ lsmod | grep acpiphp
acpiphp22567  0 


Stefan.


signature.asc
Description: This is a digitally signed message part

Bug#665493: linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)

[Stefan Nagy]

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 symptoms. So I wrote the bug report for my machine now.

Cheers,
Stefan.


signature.asc
Description: This is a digitally signed message part

Bug#665493: linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)

[Stefan Nagy]

Package: linux-2.6
Followup-For: Bug #665493

Dear Maintainer,

I'm seeing the same symptoms as the original reporter on a free install of 
wheezy on an HP Folio 13-2000.

Since I seem to be too stupid to compile a booting custom kernel I installed 
linux-image-3.2.0-0.bpo.2-amd64 (3.2.20-1~bpo60+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/sh linked to /bin/dash


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#683690: Debian Installer stops at Detect Network Hardware

[Stefan Nagy]

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 (B0N00AA#ABD)
Partitions:
/dev/sda1   ext2/boot
/dev/mapper/rosa-root   ext4/
/dev/mapper/rosa-home   ext4/home
/dev/mapper/rosa-swap   swapnone

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Since debian installer stopped at Detect Network Hardware as described in bug 
#681656 I tried out the workaround mentioned in Message #35.
After inserting "exit 0" directly after line "#!/bin/sh" in file 
/bin/check-missing-firmware I was able to proceed with the installation without 
any further problems.

After successful installation my kernel failed to boot as described in bug 
#665493.
As mentioned in Message #39 I have to use the kernel boot parameter pci=noacpi 
to avoid this problem.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20120712"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux rosa 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0104] (rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0116] 
(rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset 
Family LPC Controller [8086:1c49] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 
Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series 
Chipset Family SMB

Bug#683777: linux-image-3.2.0-3-amd64: some multimedia/action keys don't work

[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 brightness down), Fn+F3
(display brightness up), Fn+F12 (wireless on/off).

Other action keys work well out of the box like Fn+F6 (last music title), Fn+F7
(play/pause), Fn+F8 (next music title)…

I'm reporting this against linux-image-3.2.0-3-amd64 because I found a similar
report against evdev (bug #619466), in Message #10 Cyril Brulebois wrote:
"Try with evtest $device on a console, if there's nothing coming up, talk to
kernel
people."

Please tell me if you need more information.



-- Package-specific info:
** Version:
Linux version 3.2.0-3-amd64 (Debian 3.2.21-3) (debian-ker...@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Thu Jun 28 09:07:26 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-3-amd64 root=/dev/mapper/rosa-root ro quiet
pci=noacpi

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[9.856776] rts_pstor: waiting for device to settle before scanning
[   10.188137] ACPI: Battery Slot [BAT1] (battery present)
[   10.195507] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[   10.195753] iTCO_wdt: Found a Cougar Point TCO device (Version=2,
TCOBASE=0x0460)
[   10.195971] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   10.200688] Linux video capture interface: v2.00
[   10.200810] cfg80211: Calling CRDA to update world regulatory domain
[   10.279720] uvcvideo: Found UVC 1.00 device HP TrueVision HD (1bcf:2c07)
[   10.298792] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[   10.298796] Copyright(c) 2003-2011 Intel Corporation
[   10.298943] iwlwifi :02:00.0: PCI->APIC IRQ transform: INT A -> IRQ 18
[   10.298983] iwlwifi :02:00.0: setting latency timer to 64
[   10.299031] iwlwifi :02:00.0: pci_resource_len = 0x2000
[   10.299035] iwlwifi :02:00.0: pci_resource_base = c9001109
[   10.299037] iwlwifi :02:00.0: HW Revision ID = 0x34
[   10.299217] iwlwifi :02:00.0: irq 49 for MSI/MSI-X
[   10.299311] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N
1030 BGN, REV=0xB0
[   10.299469] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
[   10.315355] iwlwifi :02:00.0: device EEPROM VER=0x716, CALIB=0x6
[   10.315359] iwlwifi :02:00.0: Device SKU: 0X150
[   10.315363] iwlwifi :02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
[   10.315395] iwlwifi :02:00.0: Tunable channels: 13 802.11bg, 0 802.11a
channels
[   10.332763] iwlwifi :02:00.0: loaded firmware version 18.168.6.1
[   10.333293] Registered led device: phy0-led
[   10.336932] fbcon: inteldrmfb (fb0) is primary device
[   10.342565] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[   10.355636] cfg80211: World regulatory domain updated:
[   10.355639] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[   10.355643] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi,
2000 mBm)
[   10.355646] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi,
2000 mBm)
[   10.355649] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi,
2000 mBm)
[   10.355652] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi,
2000 mBm)
[   10.355654] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi,
2000 mBm)
[   10.361613] input: HP TrueVision HD as
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input5
[   10.361754] usbcore: registered new interface driver uvcvideo
[   10.361756] USB Video Class driver (1.1.1)
[   10.538938] Console: switching to colour frame buffer device 170x48
[   10.550081] fb0: inteldrmfb frame buffer device
[   10.550087] drm: registered panic notifier
[   10.550347] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor
0
[   10.550464] i801_smbus :00:1f.3: PCI->APIC IRQ transform: INT C -> IRQ
19
[   10.550486] ACPI: resource :00:1f.3 [io  0x4040-0x405f] conflicts with
ACPI region SMBI [io 0x4040-0x404f]
[   10.550497] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[   10.550641] snd_hda_intel :00:1b.0: PCI->APIC IRQ transform: INT A ->
IRQ 22
[   10.550812] snd_hda_intel :00:1b.0: irq 50 for MSI/MSI-X
[   10.550878] snd_hda_intel :00:1b.0: setting latency timer to 64
[   10.608483] input: HP WMI hotkeys as /devices/virtual/input/input6
[   10.855484] rts_pstor: device scan complete
[   10.855811] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S.   1.00
PQ: 0 ANSI: 0 CCS
[   10.855967] Bad LUN (0:1)
[   10.856277] Bad target number (1:0)
[   10.856596] Bad target number (2:0)
[   10.856916] Bad target number (3:0)
[   10.857235] Bad target number (4:0)
[   10.857555] Bad target number (5:0)
[   10.857875] Bad tar

Bug#683762: On/Off button & LED indicator doesn't work on HP Folio 13 - 2000

[Stefan Nagy]

Dear Maintainer,

it seems like this bug already got reported upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=39055

BTW, maybe this report is a duplicate of #609903 – I'm not sure since
the hardware of the original reporter seems to be slightly different
than mine (the LED is integrated into the TouchPad).

Cheers,
Stefan Nagy.


signature.asc
Description: This is a digitally signed message part

Bug#683777: linux-image-3.2.0-3-amd64: some multimedia/action keys don't work

[Stefan Nagy]

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.


signature.asc
Description: This is a digitally signed message part

Bug#681656: Detect Network Hardware stops Wheezy install

[Stefan Nagy]

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 debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684186: gnome-power-manager: Critical battery level doesn't lead to action (hibernate)

[Stefan Nagy]

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 my notebook
shuts down instead of going into hibernation - I already lost some work because
of this…

Sending my notebook into hibernation manually works without any problems.

Please tell me if you need more information.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
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/sh linked to /bin/dash

Versions of packages gnome-power-manager depends on:
ii  consolekit   0.4.5-3
ii  dbus-x11 1.6.0-1
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  dpkg 1.16.4.3
ii  gnome-settings-daemon3.4.2-4
ii  libc62.13-33
ii  libcairo21.12.2-2
ii  libglib2.0-0 2.32.3-1
ii  libgtk-3-0   3.4.2-2
ii  libpango1.0-01.30.0-1
ii  libupower-glib1  0.9.17-1
ii  notification-daemon  0.7.5-1
ii  upower   0.9.17-1

gnome-power-manager recommends no packages.

Versions of packages gnome-power-manager suggests:
ii  policykit-1  0.105-1

-- no debconf information


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684186: gnome-power-manager: Critical battery level doesn't lead to action (hibernate)

[Stefan Nagy]

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 true
org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate'
org.gnome.settings-daemon.plugins.power button-power 'suspend'
org.gnome.settings-daemon.plugins.power button-sleep 'hibernate'
org.gnome.settings-daemon.plugins.power button-suspend 'suspend'
org.gnome.settings-daemon.plugins.power critical-battery-action
'hibernate'
org.gnome.settings-daemon.plugins.power idle-brightness 30
org.gnome.settings-daemon.plugins.power idle-dim-ac false
org.gnome.settings-daemon.plugins.power idle-dim-battery true
org.gnome.settings-daemon.plugins.power idle-dim-time 90
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend'
org.gnome.settings-daemon.plugins.power lid-close-battery-action
'suspend'
org.gnome.settings-daemon.plugins.power notify-perhaps-recall true
org.gnome.settings-daemon.plugins.power percentage-action 2
org.gnome.settings-daemon.plugins.power percentage-critical 3
org.gnome.settings-daemon.plugins.power percentage-low 10
org.gnome.settings-daemon.plugins.power priority 1
org.gnome.settings-daemon.plugins.power sleep-display-ac 600
org.gnome.settings-daemon.plugins.power sleep-display-battery 600
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type
'suspend'
org.gnome.settings-daemon.plugins.power time-action 120
org.gnome.settings-daemon.plugins.power time-critical 300
org.gnome.settings-daemon.plugins.power time-low 1200
org.gnome.settings-daemon.plugins.power use-time-for-policy true


Thanks,
Stefan.


signature.asc
Description: This is a digitally signed message part

Bug#684186: gnome-power-manager: Critical battery level doesn't lead to action (hibernate)

[Stefan Nagy]

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

Bug#684331: gnome-settings-daemon: Media-key to switch to external monitor doesn't work

[Stefan Nagy]

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 this:
https://live.gnome.org/RandR#Handling_of_the_XF86Display_hotkey

While trying to define a custom keybinding I realized that this action key is
mapped to Super+P. In the meantime I read some bug reports like
https://bugzilla.gnome.org/show_bug.cgi?id=651571 with users complaining that
Super+P is a hardcoded shortcut (VIDEO_OUT_KEY) but shouldn't be. In dconf
editor I can see that in "org.gnome.settings-daemon.plugins.media-keys" "video-
out" is set to "p".

So from what I read my 'switch to external monitor'-key should just work –
but it doesn't…

Regards,
Stefan.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
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/sh linked to /bin/dash

Versions of packages gnome-settings-daemon depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  dpkg 1.16.4.3
ii  gsettings-desktop-schemas3.4.2-1
ii  libatk1.0-0  2.4.0-2
ii  libc62.13-33
ii  libcairo-gobject21.12.2-2
ii  libcairo21.12.2-2
ii  libcanberra-gtk3-0   0.28-4
ii  libcanberra0 0.28-4
ii  libcolord1   0.1.21-1
ii  libcomerr2   1.42.4-3
ii  libcups2 1.5.3-1
ii  libdbus-glib-1-2 0.100-1
ii  libfontconfig1   2.9.0-6
ii  libgcrypt11  1.5.0-3
ii  libgdk-pixbuf2.0-0   2.26.1-1
ii  libglib2.0-0 2.32.3-1
ii  libgnome-desktop-3-2 3.4.2-1
ii  libgnomekbd7 3.4.0.2-1
ii  libgnutls26  2.12.20-1
ii  libgssapi-krb5-2 1.10.1+dfsg-2
ii  libgtk-3-0   3.4.2-2
ii  libgudev-1.0-0   175-3.1
ii  libk5crypto3 1.10.1+dfsg-2
ii  libkrb5-31.10.1+dfsg-2
ii  liblcms2-2   2.2+git20110628-2.2
ii  libnotify4   0.7.5-1
ii  libnspr4 2:4.9.1-1
ii  libnspr4-0d  2:4.9.1-1
ii  libnss3  2:3.13.5-1
ii  libnss3-1d   2:3.13.5-1
ii  libpackagekit-glib2-14   0.7.5-2
ii  libpango1.0-01.30.0-1
ii  libpolkit-gobject-1-00.105-1
ii  libpulse-mainloop-glib0  2.0-3
ii  libpulse02.0-3
ii  libsqlite3-0 3.7.13-1
ii  libupower-glib1  0.9.17-1
ii  libwacom20.5-1
ii  libx11-6 2:1.5.0-1
ii  libxfixes3   1:5.0-4
ii  libxi6   2:1.6.1-1
ii  libxklavier165.2.1-1
ii  libxtst6 2:1.2.1-1
ii  nautilus-data3.4.2-1
ii  zlib1g   1:1.2.7.dfsg-13

Versions of packages gnome-settings-daemon recommends:
ii  pulseaudio  2.0-3

Versions of packages gnome-settings-daemon suggests:
ii  gnome-screensaver3.4.1-1
ii  metacity [x-window-manager]  1:2.34.3-2
ii  x11-xserver-utils7.7~3

-- no debconf information


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#681656: Detect Network Hardware stops Wheezy install

[Stefan Nagy]

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.

http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/current/ia64/iso-cd/debian-testing-ia64-netinst.iso
Here the missing firmware is detected and displayed, but not installed.
When I provide a USB stick with the firmware and tell the installer to
go ahead after a few seconds I get the same screen again.

BTW, I'd also say that this is a duplicate of #683849.


signature.asc
Description: This is a digitally signed message part

Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)

[Stefan Nagy]

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),
> 'intel_backlight' (brightness 4882, actual_brightness 4882). So the
> difference between 3.2 and 3.6 seems to be that backlight brightness
> wasn't controlled by the ACPI driver but the device specific driver in
> 3.2. 

I was having the same problem with linux-image-3.2.0-4-amd64 for some
time now, I guess since update 3.2.32-1.

However, this bug was fixed upstream. I tested the patch on top of
kernel v3.2.32-1 and it fixes the problem.
>From 117af51d695c78bfdf618a183664f0e9f3769b9a Mon Sep 17 00:00:00 2001
From: Zhang Rui 
Date: Sun, 2 Dec 2012 10:00:41 +0800
Subject: [PATCH] ACPI video: ignore BIOS initial backlight value for HP Folio
 13-2000.

Or else the laptop will boot with a dimmed screen.

Signed-off-by: Zhang Rui 
---
 drivers/acpi/video.c |   14 ++
 1 file changed, 14 insertions(+)

diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
index 1e0a9e1..58bddd3 100644
--- a/drivers/acpi/video.c
+++ b/drivers/acpi/video.c
@@ -389,6 +389,12 @@ static int __init video_set_bqc_offset(const struct dmi_system_id *d)
 	return 0;
 }
 
+static int video_ignore_initial_backlight(const struct dmi_system_id *d)
+{
+	use_bios_initial_backlight = 0;
+	return 0;
+}
+
 static struct dmi_system_id video_dmi_table[] __initdata = {
 	/*
 	 * Broken _BQC workaround http://bugzilla.kernel.org/show_bug.cgi?id=13121
@@ -433,6 +439,14 @@ static struct dmi_system_id video_dmi_table[] __initdata = {
 		DMI_MATCH(DMI_PRODUCT_NAME, "Aspire 7720"),
 		},
 	},
+	{
+	 .callback = video_ignore_initial_backlight,
+	 .ident = "HP Folio 13-2000",
+	 .matches = {
+		DMI_MATCH(DMI_BOARD_VENDOR, "Hewlett-Packard"),
+		DMI_MATCH(DMI_PRODUCT_NAME, "HP Folio 13 - 2000 Notebook PC"),
+		},
+	},
 	{}
 };
 
-- 
1.7.9.5

Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)

[Stefan Nagy]

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),
> 'intel_backlight' (brightness 4882, actual_brightness 4882). So the
> difference between 3.2 and 3.6 seems to be that backlight brightness
> wasn't controlled by the ACPI driver but the device specific driver in
> 3.2. 

I was having the same problem with linux-image-3.2.0-4-amd64 for some
time now, I guess since update 3.2.32-1.

However, this bug was fixed upstream. I tested the patch on top of
kernel v3.2.32-1 and it fixes the problem.
>From 117af51d695c78bfdf618a183664f0e9f3769b9a Mon Sep 17 00:00:00 2001
From: Zhang Rui 
Date: Sun, 2 Dec 2012 10:00:41 +0800
Subject: [PATCH] ACPI video: ignore BIOS initial backlight value for HP Folio
 13-2000.

Or else the laptop will boot with a dimmed screen.

Signed-off-by: Zhang Rui 
---
 drivers/acpi/video.c |   14 ++
 1 file changed, 14 insertions(+)

diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
index 1e0a9e1..58bddd3 100644
--- a/drivers/acpi/video.c
+++ b/drivers/acpi/video.c
@@ -389,6 +389,12 @@ static int __init video_set_bqc_offset(const struct dmi_system_id *d)
 	return 0;
 }
 
+static int video_ignore_initial_backlight(const struct dmi_system_id *d)
+{
+	use_bios_initial_backlight = 0;
+	return 0;
+}
+
 static struct dmi_system_id video_dmi_table[] __initdata = {
 	/*
 	 * Broken _BQC workaround http://bugzilla.kernel.org/show_bug.cgi?id=13121
@@ -433,6 +439,14 @@ static struct dmi_system_id video_dmi_table[] __initdata = {
 		DMI_MATCH(DMI_PRODUCT_NAME, "Aspire 7720"),
 		},
 	},
+	{
+	 .callback = video_ignore_initial_backlight,
+	 .ident = "HP Folio 13-2000",
+	 .matches = {
+		DMI_MATCH(DMI_BOARD_VENDOR, "Hewlett-Packard"),
+		DMI_MATCH(DMI_PRODUCT_NAME, "HP Folio 13 - 2000 Notebook PC"),
+		},
+	},
 	{}
 };
 
-- 
1.7.9.5

Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)

[Stefan Nagy]

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  I fear we haven't
> gotten to the bottom of this, since the quirk table entry only applies
> to your model whereas a fundamental fix would apply to all affected
> ones.

I know, but as I understand it, this issue is caused by a BIOS bug, so
there seems to be no way to provide a fundamental fix (at least that's
how I interpreted the mere existence of this quirk table).

Cheers,
Stefan.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684186: gnome-settings-daemon: fails to execute action on low battery condition

[Stefan Nagy]

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 / shouldn't expect their OS
to prevent data loss when their notebook's battery drains?


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

[Stefan Nagy]

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 fails to send my notebook into hibernation before it suddenly shuts
down – I already lost some work because of this. I reported this bug against
gnome-settings-daemon some months ago, see bug #684186. Since this seems to be
a hardware specific issue I'm filing a kernel bug now.

Sending my notebook into hibernation manually works without any problems.
linux-image-3.2.0-4-amd64 (3.2.32-1) is also affected by this bug. I also tried
various upstream kernel versions with no luck.

Please tell me if you need more information.



-- Package-specific info:
** Version:
Linux version 3.6-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-11) ) #1 SMP Debian 3.6.9-1~experimental.1

** Command line:
BOOT_IMAGE=/vmlinuz-3.6-trunk-amd64 root=/dev/mapper/rosa-root ro quiet 
video.use_bios_initial_backlight=0

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[   15.069087] lp: driver loaded but no devices found
[   15.075883] ppdev: user-space parallel port driver
[   15.342115] r8169 :01:00.0: eth0: link down
[   15.342252] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   15.345082] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
[   15.351778] iwlwifi :02:00.0: Radio type=0x2-0x2-0x1
[   15.438700] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
[   15.445461] iwlwifi :02:00.0: Radio type=0x2-0x2-0x1
[   15.530356] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   15.752174] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input12
[   15.769085] Ebtables v2.0 registered
[   15.791303] ip_tables: (C) 2000-2006 Netfilter Core Team
[   15.807600] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   16.757462] wlan0: authenticate with 70:72:3c:20:76:08
[   16.784911] wlan0: send auth to 70:72:3c:20:76:08 (try 1/3)
[   16.789363] wlan0: authenticated
[   16.789609] wlan0: waiting for beacon from 70:72:3c:20:76:08
[   16.890685] wlan0: associate with 70:72:3c:20:76:08 (try 1/3)
[   16.894768] wlan0: RX AssocResp from 70:72:3c:20:76:08 (capab=0x431 status=0 
aid=1)
[   16.908879] wlan0: associated
[   16.909000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   16.909253] cfg80211: Calling CRDA for country: CA
[   16.915674] cfg80211: Regulatory domain changed to country: CA
[   16.915684] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   16.915694] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2700 mBm)
[   16.915701] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
1700 mBm)
[   16.915707] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   16.915714] cfg80211:   (549 KHz - 571 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   16.915722] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
[   23.076233] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   24.559455] hid-generic 0005:045E:0700.0001: unknown main item tag 0x0
[   24.559610] input: Microsoft Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/bluetooth/hci0/hci0:36/input13
[   24.560410] hid-generic 0005:045E:0700.0001: input,hidraw0: BLUETOOTH HID 
v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 4C:EB:42:1A:52:01
[   49.396700] hid-generic 0005:045E:0762.0002: unknown main item tag 0x0
[   49.397057] input: Microsoft Bluetooth Mobile Keyboard 6000 as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/bluetooth/hci0/hci0:40/input14
[   49.399554] hid-generic 0005:045E:0762.0002: input,hidraw1: BLUETOOTH HID 
v0.13 Keyboard [Microsoft Bluetooth Mobile Keyboard 6000] on 4C:EB:42:1A:52:01
[ 1810.780322] hid-generic 0005:045E:0700.0003: unknown main item tag 0x0
[ 1810.780576] input: Microsoft Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/bluetooth/hci0/hci0:36/input15
[ 1810.781007] hid-generic 0005:045E:0700.0003: input,hidraw0: BLUETOOTH HID 
v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 4C:EB:42:1A:52:01
[ 3822.678138] fuse init (API version 7.20)
[ 5152.411809] hid-generic 0005:045E:0762.0004: unknown main item tag 0x0
[ 5152.411957] input: Microsoft Bluetooth Mobile Keyboard 6000 as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/bluetooth/hci0/hci0:40/input16
[ 5152.412398] hid-generic 0005:045E:0762.0004: input,hidraw1: BLUETOOTH HID 
v0.13 Keyboard [Microsoft Bluetooth Mobile Keyboard 6000] on 4C:EB:42:1A:52:01
[12633.041158] hid-generic 0005:045E:0700.0005: unknown main item tag 0x0
[12633.041292] input: Microsoft Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/bluetooth/hci

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

[Stefan Nagy]

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 the lowest value I get with 'acpi -b'
is 2% and about 00:06:00 seconds remaining. I've tested this again today
and I saw those values seconds before my battery drained and my notebook
shut down.

As mentioned in message #57 of bug #684186 I guess I'm affected by two
separate bugs here: g-s-d fails to execute actions on low battery
condition and at the same time ACPI reports incorrect battery values –
that's the reason why I opened another bugreport.

Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

[Stefan Nagy]

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 three seconds before my notebook finally shut
down I got 00:04:42 minutes left. For all this time percentage was at
2%.

After plugging in the AC adaptor and booting up I got 4% and 00:04:53
minutes "until charged" (!). I disconnected the AC adaptor again – now I
still had 4%, but just 00:00:15 seconds left. However, a few seconds
later I got 00:29:31 minutes remaining again.

If 'acpi' shows ACPI information (as the manpage states), ACPI
information can't be correct. For me this seems to be a kernel bug.

Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

[Stefan Nagy]

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:
- /org/freedesktop/UPower/devices/line_power_ACAD and
- /org/freedesktop/UPower/devices/battery_BAT1

I'll attach the output of 'upower --dump' (kernel 3.6.9-1). I had my AC
adaptor disconnected for more than 10 minutes – however, upower as well
as the GNOME indicator shows me I'm still connected and that my battery
has 100% left. At the same time 'acpi -b' gives me 93% (which makes
sense).

Maybe this is a upower bug?
Device: /org/freedesktop/UPower/devices/line_power_ACAD
  native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/ACPI0003:00/power_supply/ACAD
  power supply: yes
  updated:  Wed Dec 12 07:08:23 2012 (12018 seconds ago)
  has history:  no
  has statistics:   no
  line-power
online: yes

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0A:00/power_supply/BAT1
  vendor:   13-17
  model:Venturi
  serial:   01317 01/24/2012
  power supply: yes
  updated:  Wed Dec 12 07:08:28 2012 (12013 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   fully-charged
energy:  59.94 Wh
energy-empty:0 Wh
energy-full: 59.94 Wh
energy-full-design:  59.94 Wh
energy-rate: 0.011 W
voltage: 12.391 V
percentage:  100%
capacity:100%

Daemon:
  daemon-version:  0.9.17
  can-suspend: yes
  can-hibernateyes
  on-battery:  no
  on-low-battery:  no
  lid-is-closed:   yes
  lid-is-present:  yes
  is-docked:   yes

Bug#702673: PostScript drivers won't work for HP LaserJet 1200

[Stefan Nagy]

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 but without the logo (and
in addition I get another page with a error message).

When I said that the PostScript drivers 'won't work' I meant that I
can't print a CUPS test page. For practical reasons I did all the
testing with the CUPS test page…

> Reassigning to cups-filters because I do not see this as a scheduler
> problem. The README for that package is informative. Please see the
> "Selection of the renderer: Ghostscript or Poppler" and "POSTSCRIPT
> PRINTING DEBUG MODE" sections in particular.

Thanks for the hints. I followed the instructions provided in the README
file to change the default renderer for pdftops to Poppler with
lpadmin -p HP-LaserJet-1200 -o pdftops-renderer-default=pdftops

Since this didn't seem to change anything I also set the psdebug option
to get an uncompressed output and set the resolution limit with
lpadmin -p HP-LaserJet-1200 -o psdebug=true
lpadmin -p HP-LaserJet-1200 -o pdftops-max-image-resolution-default=1440

I didn't get anywhere with this, so I further reduced the resolution
limit until I finally got a full (but bad quality) printout of the test
page with pdftops-max-image-resolution-default=180.

> Note that a file in /tmp/printout should be capable of being viewed by
> a PostScript viewer such as gv.

I also cloned my print queue to a one which prints into a file with
cupsctl FileDevice=yes
lpadmin -p test -E -v file:/tmp/printout
-P /etc/cups/ppd/HP-LaserJet-1200.ppd

I printed a test page to the file and had no problems to view it with
gv. I'm stuck here… Any more ideas?

Thanks,
Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000

[Stefan Nagy]

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 bug).
> 
> The kernel driver doesn't do anything very interesting so it's actually
> very likely a BIOS bug.

You were right, this really seems to be a BIOS bug. I checked the
battery information in Windows with 'powercfg -energy': The reported
values for 'Design capacity' (= ENERGY_FULL_DESIGN) and 'Last full
charge' (= ENERGY_FULL) are the same: 59940.

At first I thought that Windows gets the correct values because the
charging level percentage reported by Windows corresponded to the
percentage reported by the 'HP Support Assistant' program which shows me
the correct battery info (including a realistic battery capacity value).

I don't know why or how this works, but the charging level percentage
seems to be quite accurate even if all the other reported values differ.
I also used a freeware tool in Windows to get more information on the
battery and it showed me the same info I get with
'cat /sys/class/power_supply/BAT1/uevent'.

> Apparently, for some systems and batteries, ACPI reports full capacity
> as 100 and current level as a percentage.  In this case the ACPI battery
> driver cannot know what the true full capacity is.  Its workaround is to
> assume it is equal to full design capacity.  Unfortunately there doesn't
> seem to be any way to find out whether this workaround was enabled.

The upstream maintainer, Lan Tianyu, provided a patch to comment the
quirk (see comment #6 in the upstream report). However, after applying
the patch the kernel reported the same values, so I guess the workaround
wasn't enabled in my case.

Since I can confirm that this is a BIOS bug I'm going to close this
report. For more information please have a look at the upstream bug
report.

Thanks,
Stefan.


signature.asc
Description: This is a digitally signed message part

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

[Stefan Nagy]

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 into hibernation.

When I changed this setting to 2 percent (in Windows 7) I was able to
reproduce this bug. So this really seems to be a firmware bug and not a
kernel bug. I'm in contact with the Hewlett Packard support now and hope
that they will fix their BIOS.

I'm going to keep the UPower bug open since UPower still fails to update
the status of the AC adapter but I'm going to close this bug since it
seems to be the BIOS which is responsible for the reported inaccurate
battery levels – not the kernel.

Thank you very much for your help!

Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#685224: [Pkg-utopia-maintainers] Bug#685224: can't configure for hidden SSID wlan

[Stefan Nagy]

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 type in 
the SSID and connect to a hidden wireless network.


Cheers,
Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#701043: installation-reports: Can't connect to Wi-Fi network in installation process when SSID broadcast is disabled

[Stefan Nagy]

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 router
everything works fine when I enable SSID broadcast.

When SSID broadcast is disabled the network (as expected) isn't shown in the
list of available networks, so I tried to add the SSID manually. When I do
this with WPA2 encryption the process would fail at the next step (key exchange)
, when I do it with WEP encyption or without any encryption the process fails
at DHCP configuration. There's no way to use a 'hidden' wireless network for
debian installation.

When SSID broadcast is enabled the network is shown in the list of available
networks and everything works fine, no matter which encryption mode I use.

Please tell me if you need more information.


-- Package-specific info:

Boot method: USB flash drive
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
 (20-Feb-2013 17:17)
Date: 2013-02-20

Machine: HP Folio 13-2000 Notebook PC
Partitions:
rootfs  rootfs 9611492 3843996   5279256   43% /
udevdevtmpfs 10240   0 102400% /dev
tmpfs   tmpfs   400544 7323998121% /run
/dev/disk/by-uuid/4f9dc00c-6e8b-431d-b71f-d7bbc5960ad8 ext4   9611492 384399
6   5279256   43% /
tmpfs   tmpfs 5120   0  51200% /run/lock
tmpfs   tmpfs  1727800 456   17273441% /run/shm
/dev/sdaext4 108895160  923724 1024397881% /home

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [OK]
Detect network card:[OK]
Configure network:  [E]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20130218-00:08"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux rosa 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0104] (rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0116] 
(rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1899]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Ser

Bug#701043: installation-reports: Can't connect to Wi-Fi network in installation process when SSID broadcast is disabled

[Stefan Nagy]

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". Trouble? Contact listmas...@lists.debian.org

Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000

[Stefan Nagy]

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 bug). I
suspect this issue to be part of my power problems reported in bug #695634 and
bug #684186 - my notebook fails to execute action (hibernate) on critical
battery condition. I'll add the information provided by UEFI (1.) and by upower
(2.).

(1.) Here's the information provided by the HP UEFI Support Environment:
Charge Capacity: 92%
Warranty Type: 1 year
Cycle Count: 187
Manufacturer: 13-17
Battery Age: 391 days
Serial Number: 01317 01/24/2012
Temperature: 36 °C
Design Capacity: 5400 mAh
Full Charge Capacity: 5020 mAh
Remaining Capacity: 2499 mAh
Current: 1797 mA
Battery Status: OK(1)
FAILURE ID: OK
Terminal Voltage: 11143 mV
Design Voltage: 11100 mV
Cell Voltage 1: 3710 mV
Cell Voltage 2: 3735 mV
Cell Voltage 3: 3700 mV
Cell Voltage 4: 0 mV
Status: 00C0
AC Power: No
CT Number: 6CLFH02BJ2E08M

(2.) Here's the information provided by upower ('upower --dump'):
Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:
/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0A:00/power_supply/BAT1
  vendor:   13-17
  model:Venturi
  serial:   01317 01/24/2012
  power supply: yes
  updated:  Wed Feb 20 23:57:03 2013 (23 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   discharging
energy:  28.771 Wh
energy-empty:0 Wh
energy-full: 59.94 Wh
energy-full-design:  59.94 Wh
energy-rate: 20.668 W
voltage: 11.103 V
time to empty:   1.4 hours
percentage:  47.9997%
capacity:100%



-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=4f9dc00c-6e8b-431d-b71f-d7bbc5960ad8 ro quiet

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[3.432525] iwlwifi :02:00.0: pci_resource_len = 0x2000
[3.432529] iwlwifi :02:00.0: pci_resource_base = c90011088000
[3.432533] iwlwifi :02:00.0: HW Revision ID = 0x34
[3.432781] iwlwifi :02:00.0: irq 47 for MSI/MSI-X
[3.432898] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 
1030 BGN, REV=0xB0
[3.433028] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
[3.448618] iwlwifi :02:00.0: device EEPROM VER=0x716, CALIB=0x6
[3.448620] iwlwifi :02:00.0: Device SKU: 0X150
[3.448623] iwlwifi :02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
[3.448652] iwlwifi :02:00.0: Tunable channels: 13 802.11bg, 0 802.11a 
channels
[3.483191] mtrr: type mismatch for b000,1000 old: write-back new: 
write-combining
[3.483196] [drm] MTRR allocation failed.  Graphics performance may suffer.
[3.483773] i915 :00:02.0: irq 48 for MSI/MSI-X
[3.483780] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[3.483783] [drm] Driver supports precise vblank timestamp query.
[3.483824] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[3.490239] iwlwifi :02:00.0: firmware: agent loaded 
iwlwifi-6000g2b-6.ucode into memory
[3.490248] iwlwifi :02:00.0: loaded firmware version 18.168.6.1
[3.490556] Registered led device: phy0-led
[3.496268] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[3.509769] input: HP TrueVision HD as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input4
[3.509853] usbcore: registered new interface driver uvcvideo
[3.509856] USB Video Class driver (1.1.1)
[3.831764] input: HP WMI hotkeys as /devices/virtual/input/input5
[4.086773] rts_pstor: device scan complete
[4.087092] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S.   1.00 
PQ: 0 ANSI: 0 CCS
[4.087242] Bad LUN (0:1)
[4.087546] Bad target number (1:0)
[4.087848] Bad target number (2:0)
[4.088152] Bad target number (3:0)
[4.088454] Bad target number (4:0)
[4.088758] Bad target number (5:0)
[4.089060] Bad target number (6:0)
[4.089314] Bad target number (7:0)
[4.089730] sd 6:0:0:0: Attached scsi generic sg1 type 0
[4.090411] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[4.116191] fbcon: inteldrmfb (fb0) is primary device
[4.308482] Console: switching to colour frame buffer device 170x48
[4.318392] fb0: inteldrmfb frame buffer device
[4.318397] drm: registered panic notifier
[4.325575] acpi device:33: registered as cooling_device6
[4.326327] inp

Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000

[Stefan Nagy]

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 
actually

very likely a BIOS bug.


I checked the situation in Windows 7 over the last days and I don't see 
the problem there. I can use the 'HP Support Assistant' in Windows to 
check the battery capacity and status – it seems to be the same tool as 
in the 'HP UEFI Support Environment'. The value 'Current' (in mAh) 
accords to the values (in percentage of 'Full Charge Capacity') reported 
by Windows.


This is why I don't think that this is a BIOS bug.

Can you send the contents of /sys/class/power_supply/BAT1/uevent so 
we

at least know what the kernel is reporting?


stefan@rosa:~$ cat /sys/class/power_supply/BAT1/uevent
POWER_SUPPLY_NAME=BAT1
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Unknown
POWER_SUPPLY_CYCLE_COUNT=0
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1110
POWER_SUPPLY_VOLTAGE_NOW=10872000
POWER_SUPPLY_POWER_NOW=14851000
POWER_SUPPLY_ENERGY_FULL_DESIGN=5994
POWER_SUPPLY_ENERGY_FULL=5994
POWER_SUPPLY_ENERGY_NOW=17982000
POWER_SUPPLY_MODEL_NAME=Venturi
POWER_SUPPLY_MANUFACTURER=13-17
POWER_SUPPLY_SERIAL_NUMBER=01317 01/24/2012

Regarding my original issue ('GNOME fails to execute action on critical 
battery condition') I just want to add that there seem to be three 
issues involved: one is really a BIOS bug (see the last comments of 
#695634), one at least seems to be a UPower bug (see #6841869) and then 
there's this one.


Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000

[Stefan Nagy]

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". Trouble? Contact listmas...@lists.debian.org

Bug#684186: Kernel doesn't produce any power related uevents on HP Folio 13-2000

[Stefan Nagy]

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 'udevadm control --log-priority=debug' – but without any
luck.

Since the kernel sends no power related uevents, UPower doesn't update
the status of the ac adapter (un/plugged). The value 'Updated' for
device /org/freedesktop/UPower/devices/line_power_ACAD reported by
UPower will always be similar to uptime, no matter how long that is and
how often I un/plugged the ac adapter in the meantime. When I booted
with the ac adapter plugged in and at some point I plug it out and
decided to work on battery my notebook will never be sent into
hibernation because UPower thinks the ac adapter is still plugged in. I
guess UPower expects an uevent from the kernel.

However, UPower seems to force an update of the battery status every 30
seconds (upowerd tells me: 'No updates on
supply /org/freedesktop/UPower/devices/battery_BAT1 for 30 seconds;
forcing update'), so the charging level reported by the battery status
applet in GNOME corresponds to the reported value
in /sys/class/power_supply/BAT1/uevent (POWER_SUPPLY_CAPACITY).

This bug was filed against UPower but now I realized that UPower waits
for uevents from the kernel regarding the battery and the ac adapter
status; but since there are no power related uevents from the kernel at
all I have reasons to this in fact is a kernel bug.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#702673: openprinting-ppds: Default (Postscript) driver for HP LaserJet 1200 doesn't work

[Stefan Nagy]

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 provided by
CUPS that doesn't work for my printer. I tried all drivers with the CUPS USB as
well as the CUPS HP backend, but this didn't seem to make any difference.

The drivers that work (I'm able to print a test page):
- HP LaserJet 1200 pcl3, hpcups 3.12.6 [en]
- HP LaserJet 1200 hpijs pcl3, 3.12.6 [en]
- HP LaserJet 1200 - CUPS+Gutenprint v5.2.9 [en]
- HP LaserJet 1200 Foomatic/lj4dith [en]
- HP LaserJet 1200 Foomatic/lj5gray [en]
- HP LaserJet 1200 Foomatic/ljet4 [en]
- HP LaserJet 1200 Foomatic/pxlmono [en]

The drivers that don't work (I'm not able to print a test page):
- HP LaserJet 1200 Postscript [en] *
- HP LaserJet 1200 Foomatic/Postscript [en]

Here's what happens when I try to print a test page with the Postscript driver:
CUPS says 'Busy - "Sending data to printer."' and the green LED on my printer
blinks green (which means something like 'receiving data') for about 22-23
minutes. After that two pages are printed: the first page is blank except for
the last 4cm of the page where I get a part of the frame of the text page; on
the second page i get an error message which differs for Postscipt and
Foomatic/Postscript. Here are the two versions:

HP LaserJet 1200 Foomatic/Postscript:
ERROR:
undefined
OFFENDING COMMAND:
 #$NH
STACK:
-mark-
-mark-
-mark-

HP LaserJet 1200 Postscript:
ERROR:
syntaxerror
OFFENDING COMMAND:

STACK:
-mark-
-mark-
-mark-

After printing this two pages the green LED on my printer continues to blink
for a few minutes, the CUPS status for the printer will remain 'Idle - "Sending
data to printer."' (forever).

Please tell me if you need more information.



-- System Information:
Debian Release: 7.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), 
(500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages openprinting-ppds depends on:
ii  python2.7.3-4
ii  xz-utils  5.1.1alpha+20120614-2

Versions of packages openprinting-ppds recommends:
ii  cups  1.5.3-2.15
ii  cups-client   1.5.3-2.15
ii  foomatic-filters  4.0.17-1

Versions of packages openprinting-ppds suggests:
pn  hpijs-ppds  

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#641751: grub2: Missing characters (Umlaute) on a encrypted system (LUKS on LVM)

[Stefan Nagy]

Package: grub2
Severity: minor

Seems like grub2 is missing some characters for the german translation when
everything but the boot-partition is encrypted. I get a "?" instead of ä, ü,
ö, ß…

I read in a german ubuntu-forum [1] that maybe grub2 is missing the
unicode.pf2-font, since it's placed in /usr/share/grub/. However, I had no luck
with the second workaround (to get a correct german translation)…

[1] http://forum.ubuntuusers.de/post/2598063/



-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#717273: printer-driver-postscript-hp: HP LaserJet 1200: User can choose between two identical PS drivers

[Stefan Nagy]

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 (recommended) (en)
HP LaserJet 1200 Postscript (recommended) (en)

These two drivers don't just sound identical, as far as I can tell they are (I
compared the PPD files). When I uninstall printer-driver-postscript-hp both
entries are gone.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages printer-driver-postscript-hp depends on:
ii  hplip 3.13.4-1+b1
ii  python2.7.5-2
ii  xz-utils  5.1.1alpha+20120614-2

printer-driver-postscript-hp recommends no packages.

printer-driver-postscript-hp suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#717273: printer-driver-postscript-hp: HP LaserJet 1200: User can choose between two identical PS drivers

[Stefan Nagy]

Hi,

I'm not sure… I don't get one DRV and one MFG/MDL pair; but there seems
to be a small difference between the two PPDs regarding the MDL:

/usr/lib/cups/driver/postscript-hp list | grep "LaserJet 1200"
"postscript-hp:0/ppd/hplip/HP/hp-laserjet_1200n-ps.ppd" en "HP" "HP
LaserJet 1200 Postscript (recommended)" "MFG:HP;MDL:HP LaserJet 1200;"
"postscript-hp:1/ppd/hplip/HP/hp-laserjet_1200n-ps.ppd" en "HP" "HP
LaserJet 1200 Postscript (recommended)" "MFG:HP;MDL:Hewlett-Packard HP
LaserJet 1200;"

In one case MDL is "HP LaserJet 1200", in the other case it is
"Hewlett-Packard HP LaserJet 1200"…

Cheers,
Stefan.



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) to choose from:
> > HP LaserJet 1200 Postscript (recommended) (en)
> > HP LaserJet 1200 Postscript (recommended) (en)
> > 
> > These two drivers don't just sound identical, as far as I can tell
> > they are (I compared the PPD files). When I uninstall
> > printer-driver-postscript-hp both entries are gone.
> 
> I think this is https://github.com/vitorbaptista/pyppd/issues/1
> 
> What do you think?
> 
> OdyX


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#702673: PostScript drivers won't work for HP LaserJet 1200

[Stefan Nagy]

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 which configuration I tried, after
some time (around 20 minutes) the HP LaserJet 1200 prints the following
error message:

ERROR:
syntaxerror
OFFENDING COMMAND:
bin obj seq, type=128, elements=97, size=28948, bad type
STACK:
-mark-
-mark-
-mark-

I found a way to get the test page printed with the Postscript-driver by
using the HPLIP backend instead of the USB backend – but it takes the
printer 26 minutes and 30 seconds (!).

I'd appreciate any further suggestions.

Thanks,
Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#702673: PostScript drivers won't work for HP LaserJet 1200

[Stefan Nagy]

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 print
> PDFs… I'll attach the output file.
> 
> This file to me always looks like the same (when I open it with gv for
> example) but it is small when I print one page with text and big when I
> print a lot of pages with pictures. Unfortunately if I try to print this
> file I get another error message.

I'm sorry – please just forget it.

I'm trying to get two printers to work and while testing the other one I
activated the starting banner option in the printing properties in
Evince some days ago :/

The file I attached last time is what I get when I print with the
starting banner activated; so this option doesn't seem to work. But I
get the same result with the PostScript PPD for the other printer so
this is really off topic…


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#717273: printer-driver-postscript-hp: HP LaserJet 1200: User can choose between two identical PS drivers

[Stefan Nagy]

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)
> > 
> > These two drivers don't just sound identical, as far as I can tell
> > they are (I compared the PPD files). When I uninstall
> > printer-driver-postscript-hp both entries are gone.
> 
> I think this is https://github.com/vitorbaptista/pyppd/issues/1
> 
> What do you think?

Sorry, I read the bug report on github more carefully now and realized
that the citation of Till Kamppeter in the last comment of vitorbaptista
is highly relevant in this context:

> Yes, the duplicate results for one and the same PPD are really a bug,
> but note that there are also cases where there really need to be more
> than one result. This is if a PPD has more than one "Product" line,
> meaning that it is for more than one printer model. Than each "Product"
> line must generate one result for this PPD. If there is only one
> "Product" line there should be only one result for this PPD.
> 
> AFAIR the bug is that there is one result line based on the "Product"
> line and another based on the "NickName" (or "ModelName"?). The
> "NickName"/"ModelName" should only be used if there is no "Product" line
> at all, otherwise one result for each "Product" line. The "Product" line
> (without parantheses) should be the MDL of the corresponding device ID,
> the MFG should come from the "Manufacturer" line in the PPD.

In my case the PPD has two "Product"-lines:
*Product: "(HP LaserJet 1200)"
*Product: "(Hewlett-Packard HP LaserJet 1200)"

Since the two lines don't represent two different printer models I'd say
one of those two lines could be deleted – and this would fix this bug.
Or is it possible that both lines are needed in some way?

Thanks,
Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#717273: printer-driver-postscript-hp: HP LaserJet 1200: User can choose between two identical PS drivers

[Stefan Nagy]

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:

*Product: "(HP LaserJet 1200)"
*Product: "(Hewlett-Packard HP LaserJet 1200)"

I'm going to file an upstream bug report.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#702673: PostScript drivers won't work for HP LaserJet 1200

[Stefan Nagy]

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,
> particularly taking into account PS file size and the time to print. The
> nature of the graphics being a possible source of trouble was touched on
> earlier in this report.
> 
> So I produced a Debian branded default-testpage.pdf (attached) based on
> Ubuntu's pdf. Not very expertly, I'll add, but the size of the PS file is
> only 356 KB and it prints quickly. My printer doesn't like the PS from
> Ghostscript so I had to use '-o pdftops-renderer-default=pdftops' with
> lpadmin.

Sorry for my late reply but I'm affected by at least two separate bugs
here and it takes me some more time to test this… However, I can confirm
that it takes my printer only around 30 seconds to print your testpage
when I use the HPLIP backend.

I realized that I had my cups configuration screwed up and restored it
yesterday, so now I have to start where I began.

I'm quite sure 1. that I'm running into troubles when I use the USB
backend and 2. that my printer doesn't like the PS from Ghostscript
neither. There are single pages of PDF documents which I can't print
because my printer runs out of memory (I get an error message after
20-30 minutes which states "memory full") while on Windows they are
printed after a few seconds.

After restoring the default cups configuration I'm able now to print the
default Debian CUPS testpage with the HPLIP backend – it takes around 26
minutes and 30 seconds, but it works (I always get the testpage instead
of an error message as stated in my original report).

I think it would be a good idea to open another bug report to address
both issues mentioned above separately. What do you think?

Thanks,
Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#718895: cups-filters: /usr/share/cups/data/default-testpage.pdf and transparency

[Stefan Nagy]

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.

The sources of the vector graphics are:
- Debian Logo http://www.debian.org/logos/openlogo.svg
- CUPS Logo https://commons.wikimedia.org/wiki/File:CUPS.svg
- Color wheel self-made, [1] was a great help
- rectangle with linear gradient self-made

Regards,
Stefan.



[1]
http://of-vim-and-vigor.blogspot.co.at/2012/01/conical-gradients-in-inkscape.html


default-testpage-debian.pdf
Description: Adobe PDF document

Bug#702673: PostScript drivers won't work for HP LaserJet 1200

[Stefan Nagy]

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 'blended' on
> top of any graphics on the page. Since we don't do full analysis of the
> PDF to determine what paints where, we have to render graphics to the
> page level transparency buffers just in case some later transparency
> group (that may have a BBox that is a subset of the page) must be blended
> onto some marks already made on the page level.
> 
> Trying to allow the printer PS RIP to render parts of the page outside the
> area where the transparency is actually used (as with an image with SMask)
> might work in simple cases, but rendering detail differences would make it
> impossible to have objects that cross "into" the area that is pre-rendered
> have the correct appearance (no glitches at the boundary, color matches,
> etc.)

When I print the PS file attached to my last message I see glitches at
the boundary of the bounding box of the image in the middle, the colors
(levels of gray in my case) don't match…

So as I understand it, in this case Adobe Reader produces a (relatively
small) PS file which is printed much faster but the appearance isn't
correct. Ghostscript on the other hand produces a correct appearance but
the printing speed is unacceptable.

In my opinion the ghostscript solution is better than the one Adobe
Reader chooses. There should be no compromises with the quality of the
result – and if I choose to print a page with 1200dpi I want to get a
high quality result. When I set the printing resolution to 600dpi I get
a PS file with 12.3 MB instead of 43.7 MB (@ 1.200dpi).

So in this case I'm not affected by a bug but have a problem with my
outdated hardware. Still, I'll have a look at the other issue mentioned
in the first part of Message #121 of this bug report.

And again I'd like to re-emphasize the craziness of the PostScript PPD
to be recommended for this printer.

I think 99% of all users would call it a bug if they'd have to wait 1.5
hours for a single page to get printed – even if they chose the highest
printing quality with a resolution of 1.200dpi. With the HPIJS PCL3 PPD
it takes the same printer only 18 seconds (!) to render and print the
same page in a comparable quality.

Could someone give me a hint against which package I could file this bug
(regarding the recommendation of the PostScript PPD)?

Thanks,
Stefan.



[1] http://bugs.ghostscript.com/show_bug.cgi?id=692959#c15


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#718895: cups-filters: /usr/share/cups/data/default-testpage.pdf and transparency

[Stefan Nagy]

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 created by a script – according to the page size (printable
area). So I have no idea how to replace the border line by a ruler.

> And a little rule with both inch and mm below the debian logo for the
> imperial units user in order to be nice and to debug scaling problem.

I think it would be better to have both metric and imperial units at the
borders.

Stefan.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#702673: PostScript drivers won't work for HP LaserJet 1200

[Stefan Nagy]

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 page into one big bitmap (A4 page
size with 1200dpi). The dimensions of the image are 9456 x 12532 px.

When you look at the original page you'll see that this doesn't make any
sense since the biggest part of the page consists of simple vector
graphics. So at least in this case to me it looks like my problem is
caused by the PS renderer.

Regards,
Stefan.



[1]
http://www.okiexecutiveseries.de/Includes/Pages/FileDownload.aspx?id=tcm:91-143325-16


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (permanent crashes)

[Stefan Nagy]

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
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
GLX_OML_swap_method, GLX_SGI_swap_control, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_INTEL_swap_event
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_framebuffer_sRGB, 
GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, 
GLX_INTEL_swap_event
GLX version: 1.4
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, 
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_EXT_texture_from_pixmap
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R200 (RV250 4C66) x86/MMX/SSE2 TCL DRI2
OpenGL version string: 1.3 Mesa 8.0.2
OpenGL extensions:
GL_ARB_multisample, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, 
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_copy_texture, 
GL_EXT_polygon_offset, GL_EXT_subtexture, GL_EXT_texture_object, 
GL_EXT_vertex_array, GL_EXT_compiled_vertex_array, GL_EXT_texture, 
GL_EXT_texture3D, GL_IBM_rasterpos_clip, GL_ARB_point_parameters, 
GL_EXT_draw_range_elements, GL_EXT_packed_pixels, GL_EXT_point_parameters, 
GL_EXT_rescale_normal, GL_EXT_separate_specular_color, 
GL_EXT_texture_edge_clamp, GL_SGIS_generate_mipmap, 
GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, 
GL_SGIS_texture_lod, GL_ARB_multitexture, GL_IBM_multimode_draw_arrays, 
GL_IBM_texture_mirrored_repeat, GL_ARB_texture_cube_map, 
GL_ARB_texture_env_add, GL_ARB_transpose_matrix, 
GL_EXT_blend_func_separate, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, 
GL_EXT_secondary_color, GL_EXT_texture_env_add, 
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, 
GL_INGR_blend_func_separate, GL_NV_blend_square, GL_NV_light_max_exponent, 
GL_NV_texgen_reflection, GL_SUN_multi_draw_arrays, 
GL_ARB_texture_border_clamp, GL_ARB_texture_compression, 
GL_EXT_framebuffer_object, GL_EXT_texture_env_combine, 
GL_EXT_texture_env_dot3, GL_MESA_window_pos, GL_NV_packed_depth_stencil, 
GL_NV_texture_rectangle, GL_ARB_occlusion_query, 
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, 
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, 
GL_ARB_window_pos, GL_ATI_fragment_shader, GL_EXT_texture_cube_map, 
GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_draw_buffers, 
GL_ARB_vertex_program, GL_ATI_draw_buffers, GL_ATI_texture_env_combine3, 
GL_EXT_stencil_wrap, GL_MESA_pack_invert, GL_ARB_half_float_pixel, 
GL_ARB_point_sprite, GL_ARB_vertex_buffer_object, 
GL_ATI_blend_equation_separate, GL_EXT_blend_equation_separate, 
GL_OES_read_format, GL_ARB_texture_rectangle, GL_EXT_texture_mirror_clamp, 
GL_EXT_texture_rectangle, GL_EXT_packed_depth_stencil, 
GL_ARB_vertex_array_object, GL_ATI_texture_mirror_once, 
GL_EXT_gpu_program_parameters, GL_OES_EGL_image, GL_ARB_copy_buffer, 
GL_ARB_robustness

64 GLX Visuals
visual  x   bf lv rg d st  colorbuffer  sr ax dp st accumbuffer  ms  cav
  id dep cl sp  sz l  ci b ro  r  g  b  a F gb bf th cl  r  g  b  a ns b eat

0x021 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8  0  0  0  0  0 0 None
0x022 24 dc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8  0  0  0  0  0 0 None
0x0d8 24 tc  0  24  0 r  . .   8  8  8  0 .  .  0  0  0  0  0  0  0  0 0 None
0x0d9 24 tc  0  24  0 r  . .   8  8  8  0 .  .  0  0  0 16 16 16  0  0 0 Slow
0x0da 24 tc  0  24  0 r  y .   8  8  8  0 .  .  0  0  0  0  0  0  0  0 0 None
0x0db 24 tc  0  24  0 r  y .   8  8  8  0 .  .  0  0  0 16 16 16  0  0 0 Slow
0x0dc 24 tc  0  24  0 r  . .   8  8  8  0 .  .  0 16  0  0  0  0  0  0 0 None
0x0dd 24 tc  0  24  0 r  . .   8  8  8  

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (screen corruptions & permanent crashes)

[Stefan Nagy]

Hello,

after updating xserver-xorg-video-radeon to version 1:6.14.4-1 I can't
reproduce the mentioned screen corruptions anymore, however I can still
reproduce the crashes.

One way to reproduce this bug is to open a window and then point the
mouse to the desktop switcher – gnome-shell crashes immediately (it's
just an example, there are numerous other ways).

Please tell me if I can provide more useful information on this.

Thanks,
Stefan.


signature.asc
Description: This is a digitally signed message part

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (permanent crashes)

[Stefan Nagy]

Sorry – now here's the backtrace…
Continuing.

Program received signal SIGPIPE, Broken pipe.
0xb75f4430 in __kernel_vsyscall ()
#0  0xb75f4430 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb736455b in writev ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
No symbol table info available.
#2  0xb779e87e in _XSERVTransSocketWritev (ciptr=0xb91beca8, buf=0xbf94e3d8, 
size=1)
at /usr/include/X11/Xtrans/Xtranssock.c:2174
No locals.
#3  0xb77a0e8f in _XSERVTransWritev (
ciptr=0xb91beca8, buf=0xbf94e3d8, 
size=1)
at /usr/include/X11/Xtrans/Xtrans.c:910
No locals.
#4  0xb77998d0 in FlushClient (
who=0xb94247b8, oc=0xb9429100, 
__extraBuf=0x0, extraCount=0)
at ../../os/io.c:938
before = 
remain = 
i = 
len = 0
oco = 0xb91c0198
connection = 25
trans_conn = 0xb91beca8
iov = {{iov_base = 0xb9422688, 
iov_len = 160}, {
iov_base = 0xb91b5230, 
iov_len = 3105575472}, {
iov_base = 0x0, 
iov_len = 2}}
padBuffer = "\000\000"
extraBuf = 0x0
written = 
padsize = 0
notWritten = 160
todo = 160
#5  0xb779857c in CloseDownConnection (
client=0xb94247b8)
at ../../os/connection.c:1035
oc = 0xb9429100
#6  0xb764cc09 in CloseDownClient (
client=0xb94247b8)
at ../../dix/dispatch.c:3445
really_close_down = 1
#7  0xb764d6b6 in Dispatch ()
at ../../dix/dispatch.c:451
clientReady = 0xb93da380
result = -1
client = 0xb94247b8
nready = 0
icheck = 0xb7813058
start_tick = 5580
#8  0xb763b26a in main (argc=10, 
argv=0xbf94e5c4, envp=0xbf94e5f0)
at ../../dix/main.c:287
i = 
alwaysCheckForInput = {0, 1}


signature.asc
Description: This is a digitally signed message part

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (permanent crashes)

[Stefan Nagy]

Am Montag, den 16.04.2012, 19:58 +0200 schrieb Julien Cristau:
> > Continuing.
> > 
> > Program received signal SIGPIPE, Broken pipe.
> 
> SIGPIPE is not a fatal signal, you need to tell gdb to ignore it, or
> hit continue.

Thanks! I'll attach the new backtrace.

Cheers,
Stefan.
Continuing.

Program received signal SIGPIPE, Broken pipe.
0xb755f430 in __kernel_vsyscall ()
Continuing.

Program received signal SIGPIPE, Broken pipe.
0xb755f430 in __kernel_vsyscall ()
Continuing.

Program received signal SIGTERM, Terminated.
0xb755f430 in __kernel_vsyscall ()
#0  0xb755f430 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb72d03fd in select ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
No symbol table info available.
#2  0xb76fef3c in WaitForSomething (
pClientsReady=0xb985d3d8)
at ../../os/WaitFor.c:232
i = 
waittime = {tv_sec = 550, 
  tv_usec = 834955}
wt = 0xbff2c1f4
timeout = 
clientsReadable = {fds_bits = {
0 }}
clientsWritable = {fds_bits = {
-1225670668, -1225670668, 
-1225738760, -1181589152, 
-1181548736, -1225670668, 
-1225738760, -1181589152, 
-1222155082, -1216958476, 
-1181589096, -1181859360, 
0, 14, -1216958476, 
-1184607168, -1222155082, 
-1181589028, -1217889395, 
-1181589152, -1184532648, 
-1181589152, -1217889395, 
-1181589152, -1182105216, 
17, -1217540868, 
-1221192768, -1222155082, 
-1221192768, -1223585804, 
-1184507216}}
selecterr = 
nready = 0
devicesReadable = {fds_bits = {
0, -1181743104, 200, 
-1221192768, -1222155082, 
-1221192768, -1184532968, 
-1074609880, -1222141123, 
-1221192768, 1024, 
-1216958476, -1181734992, 
16, -1218631457, 
-1221192768, -1222155082, 
-1221192768, -1181852744, 
-1218700688, -2147443907, 
24, -1216958476, 
-1221192768, -1222155082, 
-1221192768, 0, 
-1074609800, -1222141123, 
3, -1216958476, 
-1216958476}}
now = 
someReady = 
#3  0xb75b8432 in Dispatch ()
at ../../dix/dispatch.c:366
clientReady = 0xb985d3d8
result = 
client = 
nready = 
icheck = 0xb777e058
start_tick = 
#4  0xb75a626a in main (argc=10, 
argv=0xbff2c374, envp=0xbff2c3a0)
at ../../dix/main.c:287
i = 
alwaysCheckForInput = {0, 1}


signature.asc
Description: This is a digitally signed message part

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (permanent crashes)

[Stefan Nagy]

Am Montag, den 16.04.2012, 20:50 +0200 schrieb Julien Cristau:
> > Program received signal SIGTERM, Terminated.
> 
> So X is terminating normally.  If gnome-shell is crashing, you should
> run gdb against that, not the X server…

OK, I see – thanks.

I don't know if this is a useful backtrace now; I tried to follow
https://live.gnome.org/GnomeShell/Debugging but I can't say that I
really know what I'm doing here…

Cheers,
Stefan.
Continuing.
[New Thread 0xa2fc1b70 (LWP 6681)]
[New Thread 0xac9c3b70 (LWP 6692)]
[Thread 0xa2fc1b70 (LWP 6681) exited]

Program received signal SIGSEGV, Segmentation fault.
0xb4d2e325 in fetch_texel_2d_f_rgb888 (
texImage=0x9e4bde0, i=0, j=0, k=0, 
texel=0xa14a030)
at main/texfetch_tmp.h:704
704 main/texfetch_tmp.h: Datei oder Verzeichnis nicht gefunden.

Thread 8 (Thread 0xac9c3b70 (LWP 6692)):
#0  0xb77bd430 in __kernel_vsyscall ()
#1  0xb6c4f33b in read ()
   from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#2  0xb5c5a60b in ?? ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb5c85dd4 in ?? ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6c47c39 in start_thread ()
   from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#5  0xb5b8c12e in clone ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6

Thread 6 (Thread 0xb4102b70 (LWP 5741)):
#0  0xb77bd430 in __kernel_vsyscall ()
#1  0xb5b7e746 in poll ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2  0xb5c6dafb in g_poll ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb5c5f076 in ?? ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb5c5f77b in g_main_loop_run ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb4107524 in ?? ()
   from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
#6  0xb5c85dd4 in ?? ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb6c47c39 in start_thread ()
   from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#8  0xb5b8c12e in clone ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6

Thread 5 (Thread 0xb3901b70 (LWP 5742)):
#0  0xb77bd430 in __kernel_vsyscall ()
#1  0xb5b7e746 in poll ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2  0xb5c6dafb in g_poll ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb5c5f076 in ?? ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb5c5f77b in g_main_loop_run ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb60fa59a in ?? ()
   from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0xb5c85dd4 in ?? ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb6c47c39 in start_thread ()
   from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#8  0xb5b8c12e in clone ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6

Thread 4 (Thread 0xaf0f3b70 (LWP 5743)):
#0  0xb77bd430 in __kernel_vsyscall ()
#1  0xb5b7e746 in poll ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2  0xb5dabd16 in ?? ()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#3  0xb5d99f8a in pa_mainloop_poll ()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#4  0xb5d9a7e7 in pa_mainloop_iterate
()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#5  0xb5d9a8c4 in pa_mainloop_run ()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#6  0xb5dabc9e in ?? ()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#7  0xb555ea36 in ?? ()
   from /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-1.1.so
#8  0xb6c47c39 in start_thread ()
   from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#9  0xb5b8c12e in clone ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6

Thread 3 (Thread 0xae8d2b70 (LWP 5746)):
#0  0xb77bd430 in __kernel_vsyscall ()
#1  0xb6c4c20a in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#2  0xb71fa3aa in PR_WaitCondVar ()
   from /usr/lib/i386-linux-gnu/libnspr4.so.0d
#3  0xb72baffa in ?? ()
   from /usr/lib/libmozjs185.so.1.0
#4  0xb7200533 in ?? ()
   from /usr/lib/i386-linux-gnu/libnspr4.so.0d
#5  0xb6c47c39 in start_thread ()
   from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#6  0xb5b8c12e in clone ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6

Thread 2 (Thread 0xad9a9b70 (LWP 5815)):
#0  0xb77bd430 in __kernel_vsyscall ()
#1  0xb5b7e746 in poll ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2  0xb5dabd16 in ?? ()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#3  0xb5d99f8a in pa_mainloop_poll ()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#4  0xb5d9a7e7 in pa_mainloop_iterate
()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#5  0xb5d9a8c4 in pa_mainloop_run ()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#6  0xb5dabc9e in ?? ()
   from /usr/lib/i386-linux-gnu/libpulse.so.0
#7  0xb555ea36 in ?? ()
   from /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-1.1.so
#8  0xb6c47c39 in start_thread ()
   from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#9  0xb5b8c12e in clone ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6

Thread 1 (Thread 0xb51e0890 (LWP 5728)):
#0  0xb4d2e325 in fetch_texel_2d_f_rgb888 (texImage=0x9e4bde0, i=0, j=0, k=0, 
texel=0xa14a030)
at main/texfetch_tmp.h:704

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (permanent crashes)

[Stefan Nagy]

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.
> gnome-session-check-accelerated: Helper exited with code 256

Does it make any sense to switch to GNOME shell with 'gnome-shell
--replace' and add more information to this report? Or is there a way to
avoid fallback mode for testing purposes?

Thanks,
Stefan.


signature.asc
Description: This is a digitally signed message part

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (permanent crashes)

[Stefan Nagy]

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 part

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (permanent crashes)

[Stefan Nagy]

Am Montag, den 30.04.2012, 23:11 +0200 schrieb Julien Cristau:
> > BTW, this bug is still present in version 1:6.14.4-2.
> > 
> Is it reproducible with a newer libgl1-mesa-dri?

Yes, it is. I installed libgl1-mesa-dri 8.0.2-1 from experimental & the
bug is still reproducible.

I can reproduce the crashes aswell as the "other problem" (see original
report): "When I click on one of the applets in the panel (e.g. the
volume-, the bluetooth- or the network-applet) it takes up to 10 seconds
until the menu opens and CPU usage goes up to 100%." – Only it seems to
me as if it takes even longer now until the menues open after clicking…

Cheers,
Stefan.


signature.asc
Description: This is a digitally signed message part

Bug#586590: compiz: crash to metacity when tooltip is larger than width of screen

[Stefan Nagy]

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 -> General).



Debian Squeeze
compiz 0.8.4-4
radeon 1:6.14.2-1~bpo60+1
libreoffice 1:3.4.6-2~bpo60+1


signature.asc
Description: This is a digitally signed message part

Bug#667754:

[Stefan Nagy]

I'd like to add that I don't have any problems – apart from one minor
bug: https://bugs.freedesktop.org/show_bug.cgi?id=25883 – but a great
graphics performance using Gnome 2.30.2 & Compiz 0.8.4 on Squeeze.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#667754: xserver-xorg-video-radeon: [RV250] Gnome shell unusable (screen corruptions & permanent crashes)

[Stefan Nagy]

Hi,

06.04.2012, 18:43 +0200 Cyril Brulebois:
> > Versions of packages xserver-xorg-video-radeon suggests:
> > pn  firmware-linux  

The package firmware-linux-nonfree – which includes the Radeon
R200-family CP microcode (radeon/R200_cp.bin) – was already installed.
However, I tried to install the meta-package firmware-linux (with
firmware-linux-free) now without any effect.

In fact I can't even start GNOME Shell without the firmware installed,
by trying I would enter the fallback mode automatically.

Thanks,
Stefan.


signature.asc
Description: This is a digitally signed message part

Bug#772717: bluez: A2DP cannot work immediately after boot.

[Stefan Nagy]

I can't reproduce this bug anymore.

Bug#730159:

[Stefan Nagy]

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

Bug#776632: pulseaudio: fails to add bluetooth speakers as audio output device

[Stefan Nagy]

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 bluetooth off and on
> again and then connect the speakers again – after some attempts the speakers
> appeared in GNOME audio settings and I was able to use them. Yesterday I
> realized that it seems to work immediately if I restart bluetoothd before I 
> try
> to connect the speakers.

This turned out to be a bad shot. Sometimes it works after restarting
bluetoothd, sometimes it doesn't.
bluetoothd[1895]: Bluetooth daemon 5.23
bluetoothd[1895]: src/main.c:parse_config() parsing main.conf
bluetoothd[1895]: src/main.c:parse_config() Key file does not have key 
'DiscoverableTimeout'
bluetoothd[1895]: src/main.c:parse_config() Key file does not have key 
'PairableTimeout'
bluetoothd[1895]: src/main.c:parse_config() Key file does not have key 
'AutoConnectTimeout'
bluetoothd[1895]: src/main.c:parse_config() Key file does not have key 'Name'
bluetoothd[1895]: src/main.c:parse_config() Key file does not have key 'Class'
bluetoothd[1895]: src/main.c:parse_config() Key file does not have key 
'DeviceID'
bluetoothd[1895]: src/main.c:parse_config() Key file does not have key 
'ReverseServiceDiscovery'
bluetoothd[1895]: src/gatt.c:gatt_init() Starting GATT server
bluetoothd[1895]: src/adapter.c:adapter_init() sending read version command
bluetoothd[1895]: Starting SDP server
bluetoothd[1895]: src/sdpd-service.c:register_device_id() Adding device id 
record for 0002:1d6b:0246:0517
bluetoothd[1895]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[1895]: src/plugin.c:add_plugin() Loading hostname plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading autopair plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading policy plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading neard plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading sap plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading a2dp plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading avrcp plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading hog plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading health plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading gatt plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading scanparam plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading deviceinfo plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading alert plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading time plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading proximity plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading thermometer plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading heartrate plugin
bluetoothd[1895]: src/plugin.c:add_plugin() Loading cyclingspeed plugin
bluetoothd[1895]: src/plugin.c:plugin_init() Loading plugins 
/usr/lib/x86_64-linux-gnu/bluetooth/plugins
bluetoothd[1895]: src/plugin.c:add_plugin() Loading sixaxis plugin
bluetoothd[1895]: profiles/health/hdp.c:hdp_manager_start() Starting Health 
manager
bluetoothd[1895]: profiles/input/suspend-dummy.c:suspend_init() 
bluetoothd[1895]: profiles/input/suspend-dummy.c:suspend_init() Created 
suspend-dummy FIFO on /run/hogsuspend
bluetoothd[1895]: profiles/network/manager.c:read_config() 
/etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[1895]: profiles/network/manager.c:read_config() Config options: 
Security=true
bluetoothd[1895]: plugins/neard.c:neard_init() Setup neard plugin
bluetoothd[1895]: plugins/hostname.c:read_dmi_fallback() chassis: laptop
bluetoothd[1895]: plugins/hostname.c:read_dmi_fallback() major: 0x01 minor: 0x03
bluetoothd[1895]: plugins/sixaxis.c:sixaxis_init() 
bluetoothd[1895]: src/main.c:main() Entering main loop
bluetoothd[1895]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 2 op 0 
soft 0 hard 0
bluetoothd[1895]: Bluetooth management interface 1.6 initialized
bluetoothd[1895]: src/adapter.c:read_version_complete() sending read supported 
commands command
bluetoothd[1895]: src/adapter.c:read_version_complete() sending read index list 
command
bluetoothd[1895]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 1 op 0 
soft 0 hard 0
bluetoothd[1895]: src/rfkill.c:rfkill_event() RFKILL event idx 2 type 1 op 0 
soft 0 hard 0
bluetoothd[1895]: src/adapter.c:read_commands_complete() Number of commands: 47
bluetoothd[1895]: src/adapter.c:read_commands_complete() Number of events: 23
bluetoothd[1895]: src/rfkill.c:rfkill_event() RFKILL event idx 3 type 2 op 0 
soft 0 hard 0
bluetoothd[1895]: src/adapter.c:read_index_list_complete() Number of 
controll

Bug#776632: pulseaudio: fails to add bluetooth speakers as audio output device

[Stefan Nagy]

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) so that the speakers are added as output device when
I connect them… So now I can confirm that.

This report is probably a duplicate of #772717.



[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772717


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776636: pulseaudio: uses bluetooth speakers for audio output immediately after connection - but I can't control the volume

[Stefan Nagy]

> On Fri, Jan 30, 2015 at 8:10 AM, Stefan Nagy  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 I can still only control the internal speakers
with my keyboard / by using GNOME system menu.

> What is the gnome component that deals with sound?

If it's a gnome bug I guess it's a good idea to assign the report to
gnome-control-center.

Thanks,
Stefan.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776637: pulseaudio: resets the volume to 100% everytime I connect my bluetooth speakers

[Stefan Nagy]

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 it's always a
> > bad idea to connect my bluetooth speakers while listening to music, even if 
> > I
> > could lower the volume immediately (see bug 776636).
> >
> > I would expect pulseaudio to either preserve the volume I used on my other
> > audio output device (before I connected my bluetooth speakers) or to use a
> > moderate default volume level.
> >
> > Please tell me if I can provide any more useful information.
> 
> 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 speakers. I'll attach a
pulseaudio log file I already posted with report #776632.

I started pulseaudio, entered GNOME bluetooth settings, connected to my
bluetooth speakers and then entered GNOME audio settings. In this case I
was not affected by bug #776632, so the speakers were addded as audio
output device.

Thanks,
Stefan.
I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) fehlgeschlagen: Die 
Operation ist nicht erlaubt
I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) fehlgeschlagen: Die 
Operation ist nicht erlaubt
I: [pulseaudio] core-util.c: Successfully gained nice level -11.
I: [pulseaudio] main.c: Dies ist PulseAudio 5.0
I: [pulseaudio] main.c: Seitengröße ist 4096 Bytes.
I: [pulseaudio] main.c: System- ID ist d1eaf6bfa0e7963ebd090de1537e54cd.
I: [pulseaudio] main.c: System- ID ist 1.
I: [pulseaudio] main.c: Nutze Laufzeit-Verzeichnis /run/user/1000/pulse.
I: [pulseaudio] main.c: Nutze Zustands-Verzeichnis /home/stefan/.pulse.
I: [pulseaudio] main.c: Modul-Verzeichnis /usr/lib/pulse-5.0/modules benutzen.
I: [pulseaudio] main.c: Laufe im System-Modus: no
I: [pulseaudio] main.c: Neue hochauslösende Timer verfügbar! Guten Appetit!
I: [pulseaudio] cpu-x86.c: CPU flags: CMOV MMX SSE SSE2 SSE3 SSSE3 SSE4_1 
SSE4_2 
I: [pulseaudio] svolume_mmx.c: Initialising MMX optimized volume functions.
I: [pulseaudio] remap_mmx.c: Initialising MMX optimized remappers.
I: [pulseaudio] svolume_sse.c: Initialising SSE2 optimized volume functions.
I: [pulseaudio] remap_sse.c: Initialising SSE2 optimized remappers.
I: [pulseaudio] sconv_sse.c: Initialising SSE2 optimized conversions.
I: [pulseaudio] svolume_orc.c: Initialising ORC optimized volume functions.
I: [pulseaudio] module-device-restore.c: Successfully opened database file 
'/home/stefan/.pulse/d1eaf6bfa0e7963ebd090de1537e54cd-device-volumes'.
I: [pulseaudio] module.c: Loaded "module-device-restore" (index: #0; argument: 
"").
I: [pulseaudio] module-stream-restore.c: Successfully opened database file 
'/home/stefan/.pulse/d1eaf6bfa0e7963ebd090de1537e54cd-stream-volumes'.
I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; argument: 
"").
I: [pulseaudio] module-card-restore.c: Successfully opened database file 
'/home/stefan/.pulse/d1eaf6bfa0e7963ebd090de1537e54cd-card-database'.
I: [pulseaudio] module.c: Loaded "module-card-restore" (index: #2; argument: 
"").
I: [pulseaudio] module.c: Loaded "module-augment-properties" (index: #3; 
argument: "").
I: [pulseaudio] module.c: Loaded "module-switch-on-port-available" (index: #4; 
argument: "").
I: [pulseaudio] (alsa-lib)utils.c: could not open configuration file 
/usr/share/alsa/ucm/HDA Intel PCH/HDA Intel PCH.conf
I: [pulseaudio] (alsa-lib)parser.c: error: could not parse configuration for 
card HDA Intel PCH
I: [pulseaudio] (alsa-lib)main.c: error: failed to import HDA Intel PCH use 
case configuration -2
I: [pulseaudio] alsa-ucm.c: UCM not available for card HDA Intel PCH
I: [pulseaudio] alsa-util.c: Failed to set hardware parameters on plug:hw:0: 
Das Argument ist ungültig
I: [pulseaudio] (alsa-lib)control.c: Invalid CTL front:0
I: [pulseaudio] alsa-util.c: Unable to attach to mixer front:0: Datei oder 
Verzeichnis nicht gefunden
I: [pulseaudio] alsa-util.c: Successfully attached to mixer 'hw:0'
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC0D1c' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device iec958:0: Datei oder 
Verzeichnis nicht gefunden
I: [pulseaudio] alsa-util.c: Failed to set hardware parameters on plug:hw:0: 
Das Argument ist ungültig
I: [pulseaudio] (alsa-lib)control.c: Invalid CTL front:0
I: [pulseaudio] alsa-util.c: Unable to attach to mixer front:0: Datei oder 
Verzeichnis nicht gefunden
I: [pulseaudio] alsa-util.c: Successfully attached to mixer 'hw:0'
I: [pulseaudio] alsa-util.c: Failed to set hardware parameters on 
plug:surround40:0: Das Argument ist ungültig
I: [pulseaudio] (alsa-lib)pcm_params.c: Slave PCM not usable
I: [pulseaudio] (alsa-lib)pcm_params.c: Slave PCM not usable
I: [pulseaudio] als

Bug#776636: pulseaudio: uses bluetooth speakers for audio output immediately after connection - but I can't control the volume

[Stefan Nagy]

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

Bug#772717: bluez: A2DP cannot work immediately after boot.

[Stefan Nagy]

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 reconnect the
> bluetooth dongle (tested on a csr dongle with id 0a12:0001 and a broadcom
> BCM2046B1 dongle with id 0a5c:21e2, which is a multi-head device, along with a
> pair of pseudo-hci kb and mouse), or restart the bluetooth daemon, a2dp 
> devices
> can work like a charm (adding audio sink to pulseaudio works fine). If I
> connect the dongle to a cardbus usb host controller (rather than the host
> controller embedded in motherboard), which will only be powered and work after
> the kernel being booted, a2dp devices work fine.
> 
> It seems a2dp does not work properly if the dongle is powered before
> the kernel being booted.

Does it always work for you (adding audio sink to pulseaudio) when you
restart the bluetooth daemon? In my case sometimes it works (~80%),
sometimes it doesn't (~20%).


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777759: linux-image-3.16.0-4-amd64: When I use bluetooth speakers for audio output Wi-Fi stops working

[Stefan Nagy]

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 stay connected but I can't even
send or receive e-mails.

I'm affected by this bug on an HP Folio 13-2000 notebook with an Intel
Corporation Centrino Wireless-N 1030 [Rainbow Peak] [8086:008b] adapter. Since
I can't reproduce it with another notebook using the same WLAN and the same
bluetooth speakers I guess it's hardware related.



-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/rosa-root ro quiet splash

** Not tainted

** Kernel log:
[  154.133125] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  154.755897] wlan0: authenticate with 70:72:3c:20:76:08
[  154.766082] wlan0: send auth to 70:72:3c:20:76:08 (try 1/3)
[  154.768436] wlan0: authenticated
[  154.769119] wlan0: associate with 70:72:3c:20:76:08 (try 1/3)
[  154.773148] wlan0: RX AssocResp from 70:72:3c:20:76:08 (capab=0x431 status=0 
aid=2)
[  154.782186] wlan0: associated
[  154.782236] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  154.782302] cfg80211: Calling CRDA for country: CA
[  154.785394] cfg80211: Regulatory domain changed to country: CA
[  154.785399] cfg80211:  DFS Master region: FCC
[  154.785402] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[  154.785406] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 3000 
mBm), (N/A)
[  154.785410] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 1700 mBm), (N/A)
[  154.785415] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2400 mBm), (0 s)
[  154.785419] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 2400 
mBm), (0 s)
[  154.785422] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 3000 
mBm), (N/A)
[  161.990013] usb 1-1.2: new full-speed USB device number 6 using ehci-pci
[  162.182647] usb 1-1.2: New USB device found, idVendor=8086, idProduct=0189
[  162.182651] usb 1-1.2: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[  172.073227] input: 00:02:3C:49:93:08 as /devices/virtual/input/input17
[  662.130063] tun: Universal TUN/TAP device driver, 1.6
[  662.130068] tun: (C) 1999-2004 Max Krasnyansky 
[ 1727.831947] usb 2-2: new high-speed USB device number 2 using xhci_hcd
[ 1727.961783] usb 2-2: New USB device found, idVendor=1058, idProduct=1100
[ 1727.961792] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1727.961797] usb 2-2: Product: My Book 
[ 1727.961801] usb 2-2: Manufacturer: Western Digital 
[ 1727.961806] usb 2-2: SerialNumber: 57442D574341563530313235303133
[ 1727.979956] usb-storage 2-2:1.0: USB Mass Storage device detected
[ 1727.980136] scsi6 : usb-storage 2-2:1.0
[ 1727.980368] usbcore: registered new interface driver usb-storage
[ 1728.980093] scsi 6:0:0:0: Direct-Access WD   10EADS External  1.75 
PQ: 0 ANSI: 4
[ 1728.980932] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 1728.981261] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 
TB/931 GiB)
[ 1728.981599] sd 6:0:0:0: [sdb] Write Protect is off
[ 1728.981605] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 1728.982050] sd 6:0:0:0: [sdb] No Caching mode page found
[ 1728.982057] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 1729.003049]  sdb: sdb1
[ 1729.005054] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 1729.861553] sha256_ssse3: Using AVX optimized SHA-256 implementation
[ 1730.112760] EXT4-fs (dm-4): warning: maximal mount count reached, running 
e2fsck is recommended
[ 1730.121083] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: 
(null)
[ 2192.334964] usb 2-2: USB disconnect, device number 2
[ 2192.603577] usb 2-2: new high-speed USB device number 3 using xhci_hcd
[ 2192.733304] usb 2-2: New USB device found, idVendor=1058, idProduct=1100
[ 2192.733314] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2192.733319] usb 2-2: Product: My Book 
[ 2192.733323] usb 2-2: Manufacturer: Western Digital 
[ 2192.733327] usb 2-2: SerialNumber: 57442D574341563530313235303133
[ 2192.734329] usb-storage 2-2:1.0: USB Mass Storage device detected
[ 2192.734651] scsi7 : usb-storage 2-2:1.0
[ 2193.364260] usb 2-2: USB disconnect, device number 3
[ 3213.427171] input: 00:02:3C:49:93:08 as /devices/virtual/input/input18
[ 3375.406780] Loading kernel module for a network device with CAP_SYS_MODULE 
(deprecated).  Use CAP_NET_ADMIN and alias netdev- instead.
[ 4851.734371] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
[ 4851.742536] JFS: nTxB

Bug#776636: pulseaudio: uses bluetooth speakers for audio output immediately after connection - but I can't control the volume

[Stefan Nagy]

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 speakers are even used for audio output when
this module is not loaded… But there's no entry for example about
module-switch-on-port-available in the PulseAudio documentation [1].


[1]
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776637: pulseaudio: resets the volume to 100% everytime I connect my bluetooth speakers

[Stefan Nagy]

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 speakers. I'll attach a
> > pulseaudio log file I already posted with report #776632.
> >
> > I started pulseaudio, entered GNOME bluetooth settings, connected to my
> > bluetooth speakers and then entered GNOME audio settings. In this case I
> > was not affected by bug #776632, so the speakers were addded as audio
> > output device.
> 
> Thanks for this log. I'm currrently a bit busy to investigate this,
> but in the meantime please check this askubuntu post to see if
> anything applies to you:
> 
> http://askubuntu.com/questions/396841/how-can-i-save-my-bluetooth-headset-volume-settings


Thanks for your speedy answer and the link!

I didn't edit my /etc/pulse/default.pa but I'll attach this file anyway.
I'll also attach the output of 'pacmd list-modules'. Modules
module-device-restore and module-card-restore are both loaded.

I deleted ~/.config/pulse/ which contains the database with device
volumes several times before and tried it again now – but without any
luck.

Since it is mentioned that applications can override the default
settings I didn't use Rhythmbox this time but tried out Totem, VLC and
Iceweasel after connecting the speakers instead – also without any luck.

I had these speakers for some months now and connected them several
times every day. Every single time I connected them volume was set to
100%.

Please tell me if I can provide any more useful information.
#!/usr/bin/pulseaudio -nF
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software Foundation,
# Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.

# This startup script is used only if PulseAudio is started per-user
# (i.e. not in system mode)

.nofail

### Load something into the sample cache
#load-sample-lazy x11-bell /usr/share/sounds/gtk-events/activate.wav
#load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav
#load-sample-lazy pulse-coldplug /usr/share/sounds/startup3.wav
#load-sample-lazy pulse-access /usr/share/sounds/generic.wav

.fail

### Automatically restore the volume of streams and devices
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore

### Automatically augment property information from .desktop files
### stored in /usr/share/application
load-module module-augment-properties

### Should be after module-*-restore but before module-*-detect
load-module module-switch-on-port-available

### Load audio drivers statically
### (it's probably better to not load these drivers manually, but instead
### use module-udev-detect -- see below -- for doing this automatically)
#load-module module-alsa-sink
#load-module module-alsa-source device=hw:1,0
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output 
source_name=input
#load-module module-null-sink
#load-module module-pipe-sink

### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev 
support)
load-module module-detect
.endif

### Automatically connect sink and source if JACK server is present
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif

### Automatically load driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif

.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif

### Load several protocols
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix

### Network access (may be configured with paprefs, so leave this commented
### here if you plan to use paprefs)
#load-module module-esound-protocol-tcp
#load-module module-native-protocol-tcp
#load-module module-zeroconf-publish

### Load the RTP receiver module (also configured via paprefs, see above)
#load-module module-rtp-recv

### Load the RTP sender module (also configured via paprefs, see abo

Bug#777759: linux-image-3.16.0-4-amd64: When I use bluetooth speakers for audio output Wi-Fi stops working

[Stefan Nagy]

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 closed the bug. I don't really
understand why.

As I understand it he expects users to read the iwlwifi documentation
and try to disable module option bt_coex when they have Wi-Fi Bluetooth
problems. In my view it's a bug.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776636: pulseaudio: uses bluetooth speakers for audio output immediately after connection - but I can't control the volume

[Stefan Nagy]

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, neither with
my keyboard nor by using GOME system menu.

To gain control, I have to enter GNOME audio settings and mark the bluetooth
speakers' entry (pick the bluetooth speakers as audio output device).

I would expect to be able to control the active audio output device
immediately.

Please tell me if I can provide any more useful information.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser   3.113+nmu3
ii  libasound21.0.28-1
ii  libasound2-plugins1.0.28-1+b1
ii  libc6 2.19-13
ii  libcap2   1:2.24-6
ii  libdbus-1-3   1.8.12-3
ii  libfftw3-single3  3.3.4-2
ii  libgcc1   1:4.9.1-19
ii  libice6   2:1.0.9-1+b1
ii  libltdl7  2.4.2-1.11
ii  liborc-0.4-0  1:0.4.22-1
ii  libpulse0 5.0-13
ii  libsamplerate00.1.8-8
ii  libsm62:1.2.2-1+b1
ii  libsndfile1   1.0.25-9+b1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libstdc++64.9.1-19
ii  libsystemd0   215-10
ii  libtdb1   1.3.1-1
ii  libudev1  215-10
ii  libwebrtc-audio-processing-0  0.1-3
ii  libx11-6  2:1.6.2-3
ii  libx11-xcb1   2:1.6.2-3
ii  libxcb1   1.10-3+b1
ii  libxtst6  2:1.2.2-1+b1
ii  lsb-base  4.1+Debian13+nmu1
ii  pulseaudio-utils  5.0-13
ii  udev  215-10

Versions of packages pulseaudio recommends:
ii  pulseaudio-module-x11  5.0-13
ii  rtkit  0.11-2

Versions of packages pulseaudio suggests:
pn  paman
ii  paprefs  0.9.10-1
ii  pavucontrol  2.0-3
pn  pavumeter

-- Configuration Files:
/etc/pulse/daemon.conf changed [not included]

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-insta

Bug#776637: pulseaudio: resets the volume to 100% everytime I connect my bluetooth speakers

[Stefan Nagy]

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 always a
bad idea to connect my bluetooth speakers while listening to music, even if I
could lower the volume immediately (see bug 776636).

I would expect pulseaudio to either preserve the volume I used on my other
audio output device (before I connected my bluetooth speakers) or to use a
moderate default volume level.

Please tell me if I can provide any more useful information.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser   3.113+nmu3
ii  libasound21.0.28-1
ii  libasound2-plugins1.0.28-1+b1
ii  libc6 2.19-13
ii  libcap2   1:2.24-6
ii  libdbus-1-3   1.8.12-3
ii  libfftw3-single3  3.3.4-2
ii  libgcc1   1:4.9.1-19
ii  libice6   2:1.0.9-1+b1
ii  libltdl7  2.4.2-1.11
ii  liborc-0.4-0  1:0.4.22-1
ii  libpulse0 5.0-13
ii  libsamplerate00.1.8-8
ii  libsm62:1.2.2-1+b1
ii  libsndfile1   1.0.25-9+b1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libstdc++64.9.1-19
ii  libsystemd0   215-10
ii  libtdb1   1.3.1-1
ii  libudev1  215-10
ii  libwebrtc-audio-processing-0  0.1-3
ii  libx11-6  2:1.6.2-3
ii  libx11-xcb1   2:1.6.2-3
ii  libxcb1   1.10-3+b1
ii  libxtst6  2:1.2.2-1+b1
ii  lsb-base  4.1+Debian13+nmu1
ii  pulseaudio-utils  5.0-13
ii  udev  215-10

Versions of packages pulseaudio recommends:
ii  pulseaudio-module-x11  5.0-13
ii  rtkit  0.11-2

Versions of packages pulseaudio suggests:
pn  paman
ii  paprefs  0.9.10-1
ii  pavucontrol  2.0-3
pn  pavumeter

-- Configuration Files:
/etc/pulse/daemon.conf changed [not included]

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = ye

Bug#777759: linux-image-3.16.0-4-amd64: When I use bluetooth speakers for audio output Wi-Fi stops working

[Stefan Nagy]

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, less so on
earlier devices. This is why some people may face issues with devices
that are handled by iwldvm (pre-7260). For users of these devices who
have problems when WiFi and Bluetooth are running concurrently, we
suggest to disable BT Coex by loading iwlwifi with bt_coex_active=0 as a
module parameter."

I don't know how to proceed in this matter. If option bt_coex isn't
tested thoroughly on earlier devices and breaks Wi-Fi connections in
some cases – maybe it would be a good idea to disable it in debian?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776632: pulseaudio: fails to add bluetooth speakers as audio output device

[Stefan Nagy]

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 time it just works (they
appear in GNOME audio settings as audio output device). Sometimes the
first connection after boot fails – the speakers are connected but
disconnect after about 5-10 seconds. When I try it again, the connection
persists and the speakers appear in GNOME audio settings as audio output
device.

I have to test this some more but it seems to me that this could be a
kernel bug.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776632: pulseaudio: fails to add bluetooth speakers as audio output device

[Stefan Nagy]

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 debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#762370: upower: fails to execute action (HybridSleep) on critical battery condition

[Stefan Nagy]

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

After changing this setting my notebook should be sent into HybridSleep mode
when the battery's charging level reaches 2 percent. Indeed, when the battery
reaches PercentageAction, some action seems to be executed… To me it looks
like the notebook is sent into HybridSleep for some (maybe one or two) seconds,
just to wake up again, show me the login screen and then stay awake until my
battery drains completely.

I should mention that I am able to send my notebook to HybridSleep manually
with pm-suspend-hybrid without any problems (the same goes for pm-suspend and
pm-hibernate). Please tell me if I can provide any more useful information.

Stefan.


[1] see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695634



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages upower depends on:
ii  dbus   1.8.6-2
ii  libc6  2.19-11
ii  libdbus-1-31.8.6-2
ii  libdbus-glib-1-2   0.102-1
ii  libglib2.0-0   2.40.0-5
ii  libgudev-1.0-0 208-8
ii  libimobiledevice4  1.1.6+dfsg-3.1
ii  libplist2  1.11-3
ii  libupower-glib30.99.1-3
ii  libusb-1.0-0   2:1.0.19-1
ii  udev   208-8

Versions of packages upower recommends:
ii  policykit-1  0.105-6.1

upower suggests no packages.

-- Configuration Files:
/etc/UPower/UPower.conf changed:
[UPower]
EnableWattsUpPro=false
NoPollBatteries=false
IgnoreLid=false
UsePercentageForPolicy=true
PercentageLow=10
PercentageCritical=3
PercentageAction=2
TimeLow=1200
TimeCritical=300
TimeAction=120
CriticalPowerAction=HybridSleep


-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#814047: simple-scan: fails when I pick a scan resolution above 300 dpi

[Stefan Nagy]

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 was effective (or
 ineffective)?

In simple-scan settings I picked a scan resolution of 600 dpi. After it failed
I tested with scan resolution of 1200 and 2400 dpi – with the same result.

   * What was the outcome of this action?

When I started the scan the preview got updated very slowly and yerkily. After
finishing around 30% of the scan first the preview update stopped and then the
scanner stopped. I got the error messages "Failed to scan" and "Error
communicating with scanner". After some minutes the scanner (which seemed to
hang) restarted.

   * What outcome did you expect instead?

I expected to be able to scan with a higher resolution than 300 dpi without any
problems. I have no problems scanning with a higher resolution using xsane with
the same scanner.



-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages simple-scan depends on:
ii  adwaita-icon-theme   3.18.0-2
ii  dbus-x11 1.10.6-1
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-7
ii  libcairo-gobject21.14.6-1
ii  libcairo21.14.6-1
ii  libcolord2   1.2.12-1
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libglib2.0-0 2.46.2-3
ii  libgtk-3-0   3.18.6-1
ii  libgusb2 0.2.8-1
ii  libpackagekit-glib2-18   1.0.11-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libsane  1.0.25-2
ii  libsqlite3-0 3.10.2-1
ii  libusb-1.0-0 2:1.0.20-1
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

simple-scan recommends no packages.

simple-scan suggests no packages.

-- no debconf information
[+0,00s] DEBUG: simple-scan.vala:674: Starting Simple Scan 3.19.2, PID=4722
[+0,00s] DEBUG: Connecting to session manager
[+0,03s] DEBUG: ui.vala:2018: Loading state from 
/home/stefan/.cache/simple-scan/state
[+0,03s] DEBUG: ui.vala:1986: Restoring window to 1094x789 pixels
[+0,03s] DEBUG: ui.vala:1990: Restoring window to maximized
[+0,03s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0,03s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0,06s] DEBUG: scanner.vala:1447: sane_init () -> SANE_STATUS_GOOD
[+0,06s] DEBUG: scanner.vala:1453: SANE version 1.0.25
[+0,06s] DEBUG: scanner.vala:1514: Requesting redetection of scan devices
[+0,06s] DEBUG: scanner.vala:803: Processing request
[+0,13s] DEBUG: autosave-manager.vala:281: Autosaving book information
[+0,21s] DEBUG: ui.vala:2109: Saving state to 
/home/stefan/.cache/simple-scan/state
[+5,39s] DEBUG: scanner.vala:338: sane_get_devices () -> SANE_STATUS_GOOD
[+5,39s] DEBUG: scanner.vala:350: Device: 
name="hpaio:/net/HP_Color_LaserJet_Pro_MFP_M177fw?ip=10.0.0.4" 
vendor="Hewlett-Packard" model="HP_Color_LaserJet_Pro_MFP_M177fw" 
type="all-in-one"
[+12,25s] DEBUG: simple-scan.vala:404: Requesting scan at 2400 dpi from device 
'hpaio:/net/HP_Color_LaserJet_Pro_MFP_M177fw?ip=10.0.0.4'
[+12,25s] DEBUG: scanner.vala:1560: Scanner.scan 
("hpaio:/net/HP_Color_LaserJet_Pro_MFP_M177fw?ip=10.0.0.4", dpi=2400, 
scan_mode=ScanMode.COLOR, depth=8, type=ScanType.SINGLE, paper_width=0, 
paper_height=0, brightness=0, contrast=0)
[+12,25s] DEBUG: scanner.vala:803: Processing request
[+15,76s] DEBUG: scanner.vala:864: sane_open 
("hpaio:/net/HP_Color_LaserJet_Pro_MFP_M177fw?ip=10.0.0.4") -> SANE_STATUS_GOOD
[+15,76s] DEBUG: scanner.vala:885: sane_get_option_descriptor (0)
[+15,76s] DEBUG: scanner.vala:735: Option 0: name='option-cnt' title='Number of 
options' type=int size=4 cap=soft-detect
[+15,76s] DEBUG: scanner.vala:738:   Description: Read-only option that 
specifies how many options a specific devices supports.
[+15,76s] DEBUG: scanner.vala:885: sane_get_option_descriptor (1)
[+15,76s] DEBUG: scanner.vala:735: Option 1: name='mode-group' title='Scan 
mode' type=group size=0
[+15,76s] DEBUG: 

Bug#772717: bluez: A2DP cannot work immediately after boot.

[Stefan Nagy]

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
module-bluetooth-discover in fact works - but for the GDM pulseaudio
process, not the one that gets started with X11.

I verified that by connecting my bluetooth speakers in GDM (I can
connect to the last used paired device with a button). After connecting
the speakers, GDM used them for audio output immediately.

When I comment out module-bluetooth-discover in /etc/pulse/default.pa
as described in Comment 1 in the upstream gnome-bluetooth bug report
[1] and then add it to /usr/bin/start-pulseaudio-x11, the bluetooth
speakers get detected without any problems and are listed in gnome-
control-center audio settings.

So in my view this is no BlueZ bug. I think it would make sense to
reassign it to PulseAudio.



[1] https://bugzilla.gnome.org/show_bug.cgi?id=749208
[2] https://wiki.freedesktop.org/www/Software/PulseAudio/Documentation/
User/Modules/#index35h3
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414

Bug#772717: bluez: A2DP cannot work immediately after boot.

[Stefan Nagy]

Here's the upstream pulseaudio bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=90490