[Bug 1839894] Re: Installing Ubuntu 18.04.3 LTS alongside Windows 10 (Dual Boot) causes grub install to fail with fatal error
I've encountered the same issue while installing Kubuntu 20.04. In my case it was resolved by checking FS with dosfsck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839894 Title: Installing Ubuntu 18.04.3 LTS alongside Windows 10 (Dual Boot) causes grub install to fail with fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1839894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
@katastic Interestingly I've also noticed video output problems in VLC on my Lenovo Ideapad L340-17API. In my case video is present in VLC but quality is quite poor, video looks interlaced even though it is not. Workaround: reconfigure VLC to use another video output module and probably restart VLC. This command made video quality in VLC normal for me: sed -i 's/.*vout=.*/vout=gles2/' ~/.config/vlc/vlcrc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
I noticed that after boot with badly initialized GPU idle power consumption is 2-2.5 higher than after normal boots. But this can be fixed by putting laptop to suspend and waking it. Therefore I've extended my workaround from #3 to this: [Service] Type=oneshot ExecCondition=/bin/sh -c "journalctl -fk | grep -Fm1 'amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser'" ExecStart=/usr/bin/echo 'Not good. Restarting display-manager' ExecStart=/usr/bin/systemctl restart display-manager.service ExecStart=/usr/bin/sleep 3 ExecStart=/usr/bin/echo 'Brief suspend to fix power consumption' # Note that mode has to be "mem". "freeze" does not fix power consumption. ExecStart=/usr/sbin/rtcwake --mode mem --seconds 3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1009766] Re: Clipboard not working in RemoteApps
Should be fixed in FreeRDP 2.0: https://github.com/FreeRDP/FreeRDP/pull/3934 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009766 Title: Clipboard not working in RemoteApps To manage notifications about this bug go to: https://bugs.launchpad.net/freerdp/+bug/1009766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
This issue is not 100% reproducible. It happens after 50% of reboots and I can't figure out regularity. But I managed to contrive a workaround! ``` $ cat /etc/systemd/system/fix-graphics-after-boot.service [Unit] Description=Restart display-manager if amdgpu initialization failed After=display-manager.service JobRunningTimeoutSec=30 [Install] WantedBy=graphical.target [Service] Type=oneshot ExecCondition=/usr/bin/dash -c "journalctl -fk | grep -Fm1 'amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser'" ExecStart=/usr/bin/systemctl restart display-manager.service ``` After you've created such file don't forget to enable it: systemctl enable fix-graphics-after-boot.service The idea of this service is to scan kernel logs for 30 seconds after display-manager is started and if there is signs that amdgpu initialization failed then restart display-manager. Works for me! Though adds 15 seconds delay for 50% of boots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] Re: Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
** Summary changed: - Xorg freeze + Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1870971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] [NEW] Xorg freeze
Public bug reported: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel: amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu] апр 05 20:46:45 kernel: amdgpu_job_timedout+0x103/0x130 [amdgpu] апр 05 20:46:45 kernel: drm_sched_job_timedout+0x44/0x90 [gpu_sched] апр 05 20:46:45 kernel: process_one_work+0x1eb/0x3b0 апр 05 20:46:45 kernel: worker_thread+0x4d/0x400 апр 05 20:46:45 kernel: kthread+0x104/0x140 апр 05 20:46:45 kernel: ? process_one_work+0x3b0/0x3b0 апр 05 20:46:45 kernel: ? kthread_park+0x90/0x90 апр 05 20:46:45 kernel: ret_from_fork+0x22/0x40 апр 05 20:46:45 kernel: ---[ end trace fb203c8f6a7afd49 ]--- ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64
[Bug 1268326] [NEW] locate spawns very CPU hungry find process
Public bug reported: /etc/cron.daily/locate job spawns find process which very aggressively uses CPU. Full scan of filesystem of HDD on my laptop takes about 40 minutes and almost all of that time one core is 100% occupied by find. Here is the command that runs /usr/bin/find / -ignore_readdir_race \( -fstype NFS -o -fstype nfs -o -fstype nfs4 -o -fstype afs -o -fstype binfmt_misc -o -fstype proc -o -fstype smbfs -o -fstype autofs -o -fstype iso9660 -o -fstype ncpfs -o -fstype coda -o -fstype devpts -o -fstype ftpfs -o -fstype devfs -o -fstype mfs -o -fstype shfs -o -fstype sysfs -o -fstype cifs -o -fstype lustre_lite -o -fstype tmpfs -o -fstype usbfs -o -fstype udf -o -fstype ocfs2 -o -type d -regex '\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex$\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\)\|\(^/var/lib/schroot/mount$\)' \) -prune -o -print0 After brief investigation I found that CPU strain is produced by filesystem type checks. For example, here is original command benchmark (with additionally excluded /home/snapshots directory which contains dozens of BTRFS snapshots with too many files): time sudo /usr/bin/find / -ignore_readdir_race \( -fstype NFS -o -fstype nfs -o -fstype nfs4 -o -fstype afs -o -fstype binfmt_misc -o -fstype proc -o -fstype smbfs -o -fstype autofs -o -fstype iso9660 -o -fstype ncpfs -o -fstype coda -o -fstype devpts -o -fstype ftpfs -o -fstype devfs -o -fstype mfs -o -fstype shfs -o -fstype sysfs -o -fstype cifs -o -fstype lustre_lite -o -fstype tmpfs -o -fstype usbfs -o -fstype udf -o -fstype ocfs2 -o -type d -regex '\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex$\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\)\|\(^/var/lib/schroot/mount$\)\|\(^/home/snapshots$\)' \) -prune -o -print0 | pv > /dev/null 57,1MB 0:13:17 [73,3kB/s] [ <=> ] real13m17.647s user6m2.983s sys 6m41.837s And here is benchmark of command with severely shortened filesystem check list: time sudo /usr/bin/find / -ignore_readdir_race \( -fstype afs -o -fstype binfmt_misc -o -fstype proc -o -fstype autofs -o -fstype devpts -o -fstype devfs -o -fstype sysfs -o -fstype tmpfs -o -fstype usbfs -o -type d -regex '\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex$\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\)\|\(^/var/lib/schroot/mount$\)\|\(^/home/snapshots$\)' \) -prune -o -print0 | pv > /dev/null 57,1MB 0:05:04 [ 192kB/s] [ <=> ] real5m4.092s user2m24.112s sys 2m39.951s Each excluded filesystem greatly speeds up the process. This is really annoying, as somehow daily cron jobs sometimes start even if my laptop is running on battery o_O (AFAIK anacron avoids running periodic jobs ). I checked the same find command on onther PC with arch linux, and it used less than 10 seconds of CPU time with comparable number of files, so it is possible, that something is wrong with ubuntu find version or somehow related to ubuntu VFS specifics. Also locate may check mounted filesystem and do not include unused filesystems when compiling command for find. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: locate 4.4.2-6ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Jan 12 17:27:24 2014 Dependencies: findutils 4.4.2-6ubuntu1 gcc-4.8-base 4.8.1-10ubuntu9 libc6 2.17-93ubuntu4 libgcc1 1:4.8.1-10ubuntu9 multiarch-support 2.17-93ubuntu4 InstallationDate: Installed on 2012-07-01 (559 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: findutils UpgradeStatus: Upgraded to saucy on 2014-01-02 (10 days ago) ** Affects: findutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268326 Title: locate spawns very CPU hungry find process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1268326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1102094] Re: Powertop drains battery
** Description changed: - In idle mode my notebook consumes ~10W, but when I launch powertop 2.1 - power consumption doubles. + In idle mode my notebook Samsung 300E5Z consumes ~10W, but when I launch + powertop 2.1 power consumption doubles. I check power consumption by monitoring /sys/class/power_supply/BAT1/current_now (it's value raises from 90 to 170 when powertop runs) CPU temperature reported by lm-sensors raises by 8 °C after powertop launch. It does not look like powertop uses CPU much though: top shows <10% CPU usage and according to cpufreq-info CPU stays at 800MHz As soon as I exit from powertop power usage returns to idle. Purging and reinstall powertop package does not help. I also tried removing /var/cache/powertop/saved_*.powertop but it did not help, either (BTW, I suppose saved_parameters.powertop should be cleaned by package purge...) Powertop 1.97 used to work well before upgrade to 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: powertop 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Sun Jan 20 20:31:22 2013 InstallationDate: Installed on 2012-07-01 (203 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: powertop UpgradeStatus: Upgraded to quantal on 2012-10-21 (90 days ago) ** Attachment added: "Dmidecode info" https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/1102094/+attachment/3490733/+files/dmidecode.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1102094 Title: Powertop drains battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/1102094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1102094] [NEW] Powertop drains battery
Public bug reported: In idle mode my notebook Samsung 300E5Z consumes ~10W, but when I launch powertop 2.1 power consumption doubles. I check power consumption by monitoring /sys/class/power_supply/BAT1/current_now (it's value raises from 90 to 170 when powertop runs) CPU temperature reported by lm-sensors raises by 8 °C after powertop launch. It does not look like powertop uses CPU much though: top shows <10% CPU usage and according to cpufreq-info CPU stays at 800MHz As soon as I exit from powertop power usage returns to idle. Purging and reinstall powertop package does not help. I also tried removing /var/cache/powertop/saved_*.powertop but it did not help, either (BTW, I suppose saved_parameters.powertop should be cleaned by package purge...) Powertop 1.97 used to work well before upgrade to 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: powertop 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Sun Jan 20 20:31:22 2013 InstallationDate: Installed on 2012-07-01 (203 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: powertop UpgradeStatus: Upgraded to quantal on 2012-10-21 (90 days ago) ** Affects: powertop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1102094 Title: Powertop drains battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/1102094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085402] Re: Wrong auto selection of microphone input
1) I have found discussions regarding this problem https://lists.ubuntu.com/archives/ubuntu-studio-devel/2011-December/003768.html 2) As a temporary solution I have changed in conf files in /usr/share/pulseaudio/alsa-mixer/paths in all sections regarding boost 'volume = merge' to 'volume = zero'. I would like to find solution that will not break after PulseAudio package upgrade. ** Summary changed: - Wrong auto selection of microphone input + PulseAudio overuses 'Boost' control of microphone input producing bad audio quality -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085402 Title: PulseAudio overuses 'Boost' control of microphone input producing bad audio quality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1085402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085402] Re: Wrong auto selection of microphone input
Raymond, I have attached verbose PA log of microphone
plugging/unplugging. It does not seem to contain valuable info though.
Checking volume levels with alsamixer lead to interesting results. It
turns out that I have common 'Capture' control for both source ports and
separate controls 'Internal Mic Boost' and 'Mic Boost'. Source volume is
a sum of 'Capture' and corresponding 'Boost'.
PA prefers increasing boost volume when it sets source volume, so boost
goes up to 100% even at 28% source volume.
So I ended up with one of the boost controls maximized when I was making
my records. By switching to 'wrong' port I have moved boost to wrong
control, leaving current port without boost and thus without noise.
To illustrate this behavior a dumped amixer control levels for source
volumes from 1% to 102% with following script
for v in {1..102}; do
echo "Setting volume=$v%"
pactl set-source-volume 1 $v%
amixer scontents | sed -n "/'Capture'\|'Internal Mic Boost'/,/^ Front
Right/p"
echo
done > volume_amixer.log
You can check log of PulseAudio (volume_pulse.log) while performing this
test as well.
--
Finally:
It seems wrong, that PulseAudio prefers to increase 'Boost' control over
'Capture' control. 'Boost' should not be increased from zero value if
increasing 'Capture' control is enough to get overall requested volume.
** Attachment added: "volume_amixer.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1085402/+attachment/3449877/+files/volume_amixer.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085402
Title:
Wrong auto selection of microphone input
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1085402/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085402] Re: Wrong auto selection of microphone input
** Attachment added: "PulseAudio log of volume test" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1085402/+attachment/3449872/+files/volume_pulse.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085402 Title: Wrong auto selection of microphone input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1085402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085402] Re: Wrong auto selection of microphone input
** Attachment added: "PulseAudio log of plugging/unplugging mic" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1085402/+attachment/3449871/+files/pulse-switch.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085402 Title: Wrong auto selection of microphone input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1085402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085402] [NEW] Wrong auto selection of microphone input
Public bug reported: Om my notebook PulseAudio detects 2 ports on embedded sound card: 1)analog-input-microphone-internal 2)analog-input-microphone PulseAudio module "module-switch-on-port-available" chooses as default port #2 after external microphone is attached and switches back to port #1 after external mike removal. This behavior seems right. However, if I record sound with auto selected port, audio quality is very poor. There is loud noise in background. But if I switch to "wrong" port audio quality becomes great. E.g. I have to manually select "analog-input-microphone-internal" port when I attach external mike and vice versa. Example of record: http://self-perfection.homeip.net/files/2012/external_ru.flac (652 KiB) This record is made via headset microphone. During first half of record source port analog-input-microphone was selected then i switched to port analog-input-microphone-internal. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: self 2150 F pulseaudio self 2255 F xfce4-volumed Date: Sat Dec 1 16:34:31 2012 InstallationDate: Installed on 2012-07-01 (152 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to quantal on 2012-10-21 (40 days ago) dmi.bios.date: 04/03/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 06QB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300E4Z/300E5Z/300E7Z dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr06QB:bd04/03/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4Z/300E5Z/300E7Z:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4Z/300E5Z/300E7Z:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E4Z/300E5Z/300E7Z dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085402 Title: Wrong auto selection of microphone input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1085402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1050551] Re: [xubuntu] CapsLock warning on login screen is unvisible (colorscheme issue)
** Description changed: If CapsLock is turned on accidentally on login screen then a warning sign (exclamation mark in triangle) appears in password field. It is not obvious what does this icon mean, so it seems that average user would try to read the tooltip of the icon. However, out of the box in xubuntu 12.04 the tooltip of this warning icon is written with white letters on very light yellow background, so it is completely unreadable (check attached screenshot). So if user accidentally turns on CapsLock on login screen he/she will be - unable to login and would figure out what is the reason. + unable to login and would not figure out what is the reason. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Thu Sep 13 22:21:16 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Tags added: lightdm xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1050551 Title: [xubuntu] CapsLock warning on login screen is unvisible (colorscheme issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1050551] Re: [xubuntu] CapsLock warning on login screen is unvisible (colorscheme issue)
** Attachment added: "Tooltip screenshot" https://bugs.launchpad.net/bugs/1050551/+attachment/3312885/+files/xubuntu-lightdm-capslock-bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1050551 Title: [xubuntu] CapsLock warning on login screen is unvisible (colorscheme issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1050551] [NEW] [xubuntu] CapsLock warning on login screen is unvisible (colorscheme issue)
Public bug reported: If CapsLock is turned on accidentally on login screen then a warning sign (exclamation mark in triangle) appears in password field. It is not obvious what does this icon mean, so it seems that average user would try to read the tooltip of the icon. However, out of the box in xubuntu 12.04 the tooltip of this warning icon is written with white letters on very light yellow background, so it is completely unreadable (check attached screenshot). So if user accidentally turns on CapsLock on login screen he/she will be unable to login and would figure out what is the reason. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Thu Sep 13 22:21:16 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1050551 Title: [xubuntu] CapsLock warning on login screen is unvisible (colorscheme issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
