[Touch-packages] [Bug 1894622] [NEW] Missing manpage for systemd-resolve
Public bug reported: On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz This means that man systemd-resolve fails. http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd- resolve.1.html exists and has a link on top to 20.04LTS: it points to http://manpages.ubuntu.com/manpages/focal/en/man1/systemd-resolve.1.html , that however 404's, and one ends up being redirected to Bionic's. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1894622 Title: Missing manpage for systemd-resolve Status in systemd package in Ubuntu: New Bug description: On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz This means that man systemd-resolve fails. http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd- resolve.1.html exists and has a link on top to 20.04LTS: it points to http://manpages.ubuntu.com/manpages/focal/en/man1/systemd- resolve.1.html , that however 404's, and one ends up being redirected to Bionic's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1894622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
I have a similar problem, but it involves headphones rather than Bluetooth -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341125] Re: Cannot enter floating point (double) numbers
Sorry, but I can still reproduce it. Precondition is that gdb is built with Python 3 support (and the one distributed with Ubuntu 14.10 is) and the current locale has a comma as decimal separator (I am using it_IT.UTF-8). At startup, gdb executes _initialize_python () (in file python/python.c): the following lines of code changhe the locale from C (which is the appropriate one, since gdb must be able to parse numbers that are valid in C language) to the one of the machine 1651 progname = concat (ldirname (python_libdir), SLASH_STRING, bin, 1652 SLASH_STRING, python, NULL); 1653#ifdef IS_PY3K 1654 oldloc = setlocale (LC_ALL, NULL); 1655 setlocale (LC_ALL, ); From this point on, gdb assumes that the decimal separator is a comma, and becomes unable to parse the number 1.0 ** Changed in: gdb (Ubuntu) Status: Fix Released = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1341125 Title: Cannot enter floating point (double) numbers Status in GNU Debugger: Unknown Status in gdb package in Ubuntu: New Bug description: (gdb) show version GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word. (gdb) p 1.0 Invalid number 1.0. Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b from today) recognises 1.0 just fine, as a double To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1341125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341125] Re: Cannot enter floating point (double) numbers
It works correctly if started as LC_NUMERIC=C gdb to force the correct locale -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1341125 Title: Cannot enter floating point (double) numbers Status in GNU Debugger: Unknown Status in gdb package in Ubuntu: New Bug description: (gdb) show version GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word. (gdb) p 1.0 Invalid number 1.0. Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b from today) recognises 1.0 just fine, as a double To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1341125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341125] Re: Cannot enter floating point (double) numbers
After further investigation it seems that gdb assumes that floating- point numbers use . as decimal mark, as these lines from c-exp.y show else if (!got_dot *p == '.') got_dot = 1; but, later, the function parse_float() (in parse.c) feeds the string into sscanf num = sscanf (copy, % DOUBLEST_SCAN_FORMAT %n, d, n); and, apparently, sscanf is locale-sensitive, so, if the current locale has , as decimal mark, sscanf will leave everything past the . sign unscanned. gdb, then, notices that something is unscanned and says invalid number -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1341125 Title: Cannot enter floating point (double) numbers Status in “gdb” package in Ubuntu: New Bug description: (gdb) show version GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word. (gdb) p 1.0 Invalid number 1.0. Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b from today) recognises 1.0 just fine, as a double To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1341125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341125] Re: Cannot enter floating point (double) numbers
Filed upstream bug https://sourceware.org/bugzilla/show_bug.cgi?id=17607 ** Bug watch added: Sourceware.org Bugzilla #17607 http://sourceware.org/bugzilla/show_bug.cgi?id=17607 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1341125 Title: Cannot enter floating point (double) numbers Status in “gdb” package in Ubuntu: New Bug description: (gdb) show version GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word. (gdb) p 1.0 Invalid number 1.0. Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b from today) recognises 1.0 just fine, as a double To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1341125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382987] [NEW] Firefox crashes when accessing Google Maps, likely related to graphics driver
Public bug reported: Using Ubuntu 14.04 and Firefox 33.0. When accessing the new Google Maps at https://www.google.com/maps/ the second time in a session, Firefox crashes. From the crash report, the crash occurs in the graphics driver r600_dri.so. This is a call stack, taken from Mozilla's crash report 1 r600_dri.so r600_dri.so@0x168a34 2 libgallium.so.0.0.0 libgallium.so.0.0.0@0x327e3 3 r600_dri.so r600_dri.so@0x5cba3f 4 r600_dri.so r600_dri.so@0x5cbaa7 5 r600_dri.so r600_dri.so@0x164a26 6 r600_dri.so r600_dri.so@0x16b7fe 7 r600_dri.so r600_dri.so@0xf73f3 The bug is also open upstream as https://bugs.freedesktop.org/show_bug.cgi?id=82109 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,move,place,vpswitch,regex,resize,gnomecompat,mousepoll,session,grid,animation,workarounds,unitymtgrabhandles,wall,wobbly,fade,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 19 17:17:28 2014 DistUpgraded: 2014-04-25 22:33:51,162 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:] InstallationDate: Installed on 2010-11-07 (1442 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MachineType: MSI MS-7623 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=10b9da6b-d735-48a7-bc45-2c1fc81183dd ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to trusty on 2014-04-25 (176 days ago) dmi.bios.date: 08/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V11.5 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 880GM-E41 (MS-7623) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV11.5:bd08/10/2010:svnMSI:pnMS-7623:pvr2.0:rvnMSI:rn880GM-E41(MS-7623):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7623 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Oct 19 10:01:46 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputspca561 KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImPS/2 Generic Wheel Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1382987 Title: Firefox crashes when accessing Google Maps, likely related to graphics driver Status in “mesa” package in Ubuntu: New Bug description: Using Ubuntu 14.04 and Firefox 33.0. When accessing the new Google Maps at https://www.google.com/maps/ the second time in a session, Firefox crashes. From the crash report, the crash occurs in the graphics driver r600_dri.so. This is a call stack, taken from Mozilla's crash report 1 r600_dri.so r600_dri.so@0x168a34 2 libgallium.so.0.0.0 libgallium.so.0.0.0@0x327e3 3 r600_dri.so r600_dri.so@0x5cba3f 4 r600_dri.so r600_dri.so@0x5cbaa7 5 r600_dri.so r600_dri.so@0x164a26 6 r600_dri.so r600_dri.so@0x16b7fe 7 r600_dri.so r600_dri.so@0xf73f3 The bug
[Touch-packages] [Bug 1341125] [NEW] Cannot enter floating point (double) numbers
Public bug reported: (gdb) show version GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word. (gdb) p 1.0 Invalid number 1.0. Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b from today) recognises 1.0 just fine, as a double ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1341125 Title: Cannot enter floating point (double) numbers Status in “gdb” package in Ubuntu: New Bug description: (gdb) show version GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word. (gdb) p 1.0 Invalid number 1.0. Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b from today) recognises 1.0 just fine, as a double To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1341125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
