Bug#930787: pulseaudio: Microphone base volume stuck at 8739/13%/-52.50dB - low volume vs alsa

2019-06-20 Thread Veek.M
Package: pulseaudio
Version: 10.0-1+deb9u1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Tried to record audio from my MIC

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Direct Alsa works and the recording is loud but with Pulseaudio started it
doesn't work - the volume is low. base volume: 8739 /  13% / -52.50 dB
index: 1
name: 

   * What was the outcome of this action?
tears

   * What outcome did you expect instead?
my charming voice on Youtube - microphone recording


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


-- System Information:
Debian Release: 9.9
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to C.UTF-8), LANGUAGE=en_IN.utf8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-11+deb9u4
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.26-0+deb9u1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1+deb9u1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-3
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18+deb9u1
ii  libsystemd0  232-25+deb9u11
ii  libtdb1  1.3.11-2
ii  libudev1 232-25+deb9u11
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3+deb9u1
ii  libx11-xcb1  2:1.6.4-3+deb9u1
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1+deb9u1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+deb9u1

Versions of packages pulseaudio suggests:
ii  paman0.9.4-1+b3
pn  paprefs  
ii  pavucontrol  3.0-3.1
ii  pavumeter0.9.3-4+b3
ii  udev 232-25+deb9u11

-- Configuration Files:
/etc/pulse/daemon.conf changed:
; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no
; high-priority = yes
; nice-level = -11
; realtime-scheduling = yes
; realtime-priority = 5
; exit-idle-time = 20
; scache-idle-time = 20
; dl-search-path = (depends on architecture)
; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa
; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0
; resample-method = speex-float-1
; enable-remixing = yes
; enable-lfe-remixing = no
; lfe-crossover-freq = 0
; flat-volumes = yes
; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20
; default-sample-format = s16le
; default-sample-rate = 44100
  default-sample-rate = 48000
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right
; default-fragments = 4
; default-fragment-size-msec = 25
; enable-deferred-volume = yes
; deferred-volume-safety-margin-usec = 8000
; deferred-volume-extra-delay-usec = 0

/etc/pulse/default.pa changed:
.fail
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
load-module module-detect
.endif
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
.ifexists module-gconf.so
.nofail
load-module module-gconf
.fail
.endif
load-module module-default-device-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-intended-roles
load-module module-sus

Bug#925048: debootstrap: --keyring= Release signed by unknown key (key id EF0F382A1A7B6500)

2019-03-19 Thread Veek.M
Package: debootstrap
Version: 1.0.89
Severity: important

Dear Maintainer,

   * What led up to the situation?
dpkg-deb -R debian-archive-keyring_2017.5_all.deb /tmp/
ls *.gpg|xargs -I{} debootstrap --download-only --force-check-gpg --keyring={} 
--variant minbase --arch amd64 --make-tarball=debian_amd64 stable 
/root/dbs_debian_amd64 https://debian.ethz.ch/debian

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
E: Release signed by unknown key (key id EF0F382A1A7B6500)
but
debootstrap --download-only --force-check-gpg  --variant minbase --arch amd64 
--make-tarball=debian_amd64 stable /root/dbs_debian_amd64 
https://debian.ethz.ch/debian
works

There's a problem with using --keyring=whatever.gpg


-- System Information:
Debian Release: 9.8
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages debootstrap depends on:
ii  wget  1.18-5+deb9u2

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2017.5
ii  gnupg   2.1.18-8~deb9u4

debootstrap suggests no packages.

-- debconf-show failed



Bug#885668: gddrescue --fill-mode=+ with a map file of 0x00000000 0x608336000 + has left the partition table intact?

2017-12-28 Thread Veek.M
Package: gddrescue
Version: 1.21-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
I posted on superuser because this looks to me like a bug
https://superuser.com/questions/1280671/gddrescue-fill-mode-with-a-map-file-of-0x-0x608336000-has-left-the

I first ran this command:
ddrescue --force /dev/sda /dev/null HGST_RMA.map

I just wanted a map file for blanking (therefore /dev/null).
I interrupted the run towards the end (Ctrl+C'd it).

Then I decided to blank the disk (/dev/zero):

$ sudo ddrescue --force --fill-mode=+ /dev/zero /dev/sda HGST_RMA.map
GNU ddrescue 1.21
Press Ctrl-C to interrupt
Initial status (read from mapfile)
filled size: 266742 MB,  filled areas: 43
remaining size:  233363 MB,  remaining areas: 151
Current status
filled size:  500106 MB,  filled areas:194,  current rate:  55115 kB/s
remain size:0 B,  remain areas:  0,  average rate:  71200 kB/s
current pos:  500107 MB,  run time: 54m 37s
Finished 

Then I ran:

$ fdisk -l /dev/sda
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xbf7dbd9f

Device BootStart   End   Sectors   Size Id Type
/dev/sda1   2048  62916607  6291456030G 83 Linux
/dev/sda2   62916608  67110911   4194304 2G 82 Linux swap / Solaris
/dev/sda3   67110912 976773167 909662256 433.8G 83 Linux

This is what the initial bit of my map file looks like:
# Mapfile. Created by GNU ddrescue version 1.21
# Command line: ddrescue --force --fill-mode=+ /dev/zero /dev/sda HGST_RMA.map
# Start time:   2017-12-28 17:37:14
# Current time: 2017-12-28 18:31:57
# Finished
# current_pos  current_status
0x7470BFD000 +
#  possize  status
0x  0x608336000  +
0x608336000  0x1000  -
0x608337000  0x380B8DD000  +
0x3E13C14000  0x1000  -
0x3E13C15000  0x00224000  +

By my own estimate the partition table should have been wiped clean because of 
the

0x  0x608336000  +
But that didn't happen..

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages gddrescue depends on:
ii  libc6   2.24-11+deb9u1
ii  libgcc1 1:6.3.0-18
ii  libstdc++6  6.3.0-18

gddrescue recommends no packages.

gddrescue suggests no packages.

-- no debconf information



Bug#841945: unattended: When i shutdown, randomly, the system pauses at 'Unattended upgrades' for a long time.

2016-10-24 Thread Veek.M
Package: unattended-upgrades
Version: 0.83.3.2+deb8u1
Severity: normal
File: unattended

Dear Maintainer,

   * What led up to the situation?
When i shutdown the box, randomly, the cursor hangs at 'Unattended upgrades
and then suddenly it spits out something about USB and mouse and scrolls 
forward. Hangs for over 30s.
  * What exactly did you do (or not do) that was effective (or
 ineffective)?
I tried recording it on a camera but it's random so difficult to capture
and the screen is reflective. It sounds an awfull lot like:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645919
but way more time - 30s
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/434835
   * What outcome did you expect instead?
I was hoping for a smooth shutdown vs it pausing.


-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages unattended-upgrades depends on:
ii  apt1.0.9.8.3
ii  apt-utils  1.0.9.8.3
ii  debconf [debconf-2.0]  1.5.56
ii  init-system-helpers1.22
ii  lsb-base   4.1+Debian13+nmu1
ii  lsb-release4.1+Debian13+nmu1
ii  python33.4.2-2
ii  python3-apt0.9.3.12
ii  ucf3.0030
ii  xz-utils   5.1.1alpha+20120614-2+b3

unattended-upgrades recommends no packages.

Versions of packages unattended-upgrades suggests:
ii  bsd-mailx  8.1.2-0.20141216cvs-2
ii  exim4-daemon-light [mail-transport-agent]  4.84.2-2+deb8u1

-- debconf information:
* unattended-upgrades/enable_auto_updates: false



Bug#822405: lynx: Cookie Saving -cookie_save_file not working

2016-04-23 Thread Veek.M
Package: lynx
Version: 2.8.9dev1-2+deb8u1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
1. I ran: lynx -cookie_save_file=/tmp/cookies google.com
2. It prompted me to allow a cookie and I did so.
3. I exited using 'q'.
4. There was no cookie in /tmp/cookies

5. I ran strace -f -o, there was no mention of an 'open' on that file.
I also checked Options to make sure i was not ignoring the cookie.

It would be nice if you guys could fix this bug quickly - I require lynx -dump 
and need to feed the website a cookie. The format of the cookie file is not 
known
therefore I need to save a cookie first.

-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (1000, 'stable'), (900, 'stable'), (750, 'testing'), (500, 
'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lynx depends on:
ii  lynx-cur  2.8.9dev1-2+deb8u1

lynx recommends no packages.

lynx suggests no packages.

-- no debconf information



Bug#797892: ntfs-3g: Automount, ntfs-3g: >> ntfs-3g: Unknown option '-s'

2015-09-03 Thread Veek.M
Package: ntfs-3g
Version: 1:2014.2.15AR.2
Severity: important

Dear Maintainer,

   * What led up to the situation?
I use autofs on Lenny. autofs doesn't work with NTFS.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I ran 'automount -v -d -f'
This is what I saw: >> ntfs-3g: Unknown option '-s'.
man mount states that:
-s Tolerate  sloppy  mount  options rather than failing.
This will ignore mount options not supported by a filesystem
type.
   * What was the outcome of this action?
ntfs-3g is supposed to accept tthe '-s' option and not b0rk.
Hence the bugrep.

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ntfs-3g depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  fuse   2.9.3-15+deb8u1
ii  libc6  2.19-18
ii  libfuse2   2.9.3-15+deb8u1
ii  libgcrypt111.5.0-5+deb7u2
ii  libgnutls262.12.20-8+deb7u2
ii  multiarch-support  2.19-18

ntfs-3g recommends no packages.

ntfs-3g suggests no packages.