[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH
This kind of behaviour (letting pass three years and still not fixing this silly to adhere to a known and used standard) is the exact reason I stopped advicing Ubuntu to people. Because it is the exact thing that let people say "this shitty GNU/Linux you adviced me does never work! It took me 5 minutes to start noticing bugs!". It still happens in Ubuntu 19.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1588562 Title: Please add ~/.local/bin to the default $PATH Status in bash package in Ubuntu: Fix Released Status in bash source package in Xenial: Fix Released Status in bash package in Debian: Fix Released Bug description: Starting in Xenial, 'pip install' by default places executables into ~/.local/bin. This is the de-facto standard place to put per-user executables -- for example, Fedora/Redhat puts it on the $PATH by default, and PEP 370 makes it the standard place for unprivileged installs of Python packages to put their scripts. But unfortunately, Ubuntu's does *not* add this directory to $PATH by default, which means that 'pip install' doesn't actually work -- any scripts that are installed are inaccessible, and every user has to manually add this to their PATH. Ubuntu should put ~/.local/bin onto PATH by default. Minor details (discussed with @doko at the PyCon sprints): - this should go at the beginning of PATH rather than the end, in accordance with Debian policy saying that more-local paths go before more-upstream paths. (This is inconsistent with how Fedora/RH do it, but consistent with how Python itself searches for packages.) - this will be added to /etc/skel/profile, so that it won't change any existing user accounts; it will only be applied to user accounts created *after* this change lands - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be added to PATH unconditionally, even if the directory doesn't exist. This is important to avoid a nasty trap for new users, where the first time they try to install a Python package they have to restart their shell. Since this only applies to new accounts, the directory will always start out nonexistent/empty, so having it in $PATH won't cause any unexpected changes in behavior. - possibly it would make sense to set this in /etc/environment or /etc/skel/.gnomerc or similar, so that it would also apply to non-shell processes (e.g. if the user wants to add a global key-binding to launch a Python program, then generally ~/.profile *doesn't* affect the environment where this command gets executed, and that can frustrate and confuse users if a command works fine from the terminal but not from a keybinding). But we should defer this discussion for the future, because even if this is a good idea, it isn't a good idea in a Xenial stable update. Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562/+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 1785154] Re: libsystemd-dev dependencies not satisfied
I rebuilt the package changing its dependencies to the available packages and everything worked fine. -- 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/1785154 Title: libsystemd-dev dependencies not satisfied Status in systemd package in Ubuntu: Invalid Bug description: "Following packages lacks these dependencies: libsystemd-dev : Depends: libsystemd0 (= 237-3ubuntu10) but version 237-3ubuntu10.3 is going to be installed" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libsystemd-dev (not installed) Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 3 03:02:02 2018 InstallationDate: Installed on 2017-01-12 (567 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-07-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785154/+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 1785154] [NEW] libsystemd-dev dependencies not satisfied
Public bug reported: "Following packages lacks these dependencies: libsystemd-dev : Depends: libsystemd0 (= 237-3ubuntu10) but version 237-3ubuntu10.3 is going to be installed" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libsystemd-dev (not installed) Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 3 03:02:02 2018 InstallationDate: Installed on 2017-01-12 (567 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-07-24 (9 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- 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/1785154 Title: libsystemd-dev dependencies not satisfied Status in systemd package in Ubuntu: New Bug description: "Following packages lacks these dependencies: libsystemd-dev : Depends: libsystemd0 (= 237-3ubuntu10) but version 237-3ubuntu10.3 is going to be installed" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libsystemd-dev (not installed) Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 3 03:02:02 2018 InstallationDate: Installed on 2017-01-12 (567 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-07-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785154/+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 1720820] Re: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes.
Uninstalling gstreamer1.0-vaapi does not solve the issue for me. -- 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/1720820 Title: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: WORKAROUNDS Just for totem: sudo apt remove gstreamer1.0-vaapi Or to workaround in all players: sudo apt remove mesa-va-drivers ORIGINAL DESCRIPTION Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with AMD Fury graphics card and open source drivers. Video output is just a black frame and crash happens within just a few seconds after video playback starts. Could not reproduce bug on two older Intel laptops with iGPU's where hardware acceleration seemed to work fine under Wayland. Issue is only present on Wayland, not x. I can get hardware accelerated video playback working on Wayland with 'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only way I have found so far. Even in mpv, no other option than vaapi-copy works. gst-play-1.0 outputs the following error: ERROR Internal error: could not render surface for file:///*** ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 totem 3.25.90.1-0ubuntu3 gstreamer1.0-vaapi:amd641.12.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+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 1775877] [NEW] Totem not playing videos after upgrade to 18.04
Public bug reported: After the update, totem does not play any video. the only error is about some gtk widget. Gstreamer works, since gst-launch-1.0 playbin uri=file:///file.mp4 correctly plays the video. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.0-1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jun 8 17:30:28 2018 SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to bionic on 2018-05-29 (9 days ago) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1775877 Title: Totem not playing videos after upgrade to 18.04 Status in gstreamer1.0 package in Ubuntu: New Bug description: After the update, totem does not play any video. the only error is about some gtk widget. Gstreamer works, since gst-launch-1.0 playbin uri=file:///file.mp4 correctly plays the video. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.0-1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jun 8 17:30:28 2018 SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to bionic on 2018-05-29 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1775877/+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 1772891] Re: [REGRESSION][chtrt5645 - chtrt5645, playback] libasound2 update broke sound
Solved with sudo wget https://raw.githubusercontent.com/plbossart/UCM/master/chtrt5645/HiFi.conf -O /usr/share/alsa/ucm/chtrt5645/HiFi.conf Why does not ubuntu team just use this file for alsa-data? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1772891 Title: [REGRESSION][chtrt5645 - chtrt5645, playback] libasound2 update broke sound Status in alsa-driver package in Ubuntu: New Bug description: After upgrading libasound2, libasound-data, libasound-dev with the update of this morning, speakers result as "unplugged" and headphones result as "plugged" and do not work even when really plugged. I've downgraded those packages but still no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.17.0-999-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: steven 1360 F...m pulseaudio /dev/snd/pcmC0D0p: steven 1360 F...m pulseaudio /dev/snd/controlC0: steven 1360 F pulseaudio CurrentDesktop: GNOME Date: Wed May 23 12:46:46 2018 InstallationDate: Installed on 2017-01-12 (495 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:chtrt5645 failed Symptom_Card: Audio interno - chtrt5645 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: steven 1360 F...m pulseaudio /dev/snd/pcmC0D0p: steven 1360 F...m pulseaudio /dev/snd/controlC0: steven 1360 F pulseaudio Symptom_Type: No sound at all Title: [chtrt5645 - chtrt5645, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-04-06 (46 days ago) dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X205TA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-02-16T15:02:32.152615 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1772891/+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 1772891] [NEW] [REGRESSION][chtrt5645 - chtrt5645, playback] libasound2 update broke sound
Public bug reported: After upgrading libasound2, libasound-data, libasound-dev with the update of this morning, speakers result as "unplugged" and headphones result as "plugged" and do not work even when really plugged. I've downgraded those packages but still no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.17.0-999-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: steven 1360 F...m pulseaudio /dev/snd/pcmC0D0p: steven 1360 F...m pulseaudio /dev/snd/controlC0: steven 1360 F pulseaudio CurrentDesktop: GNOME Date: Wed May 23 12:46:46 2018 InstallationDate: Installed on 2017-01-12 (495 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:chtrt5645 failed Symptom_Card: Audio interno - chtrt5645 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: steven 1360 F...m pulseaudio /dev/snd/pcmC0D0p: steven 1360 F...m pulseaudio /dev/snd/controlC0: steven 1360 F pulseaudio Symptom_Type: No sound at all Title: [chtrt5645 - chtrt5645, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-04-06 (46 days ago) dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X205TA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-02-16T15:02:32.152615 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1772891 Title: [REGRESSION][chtrt5645 - chtrt5645, playback] libasound2 update broke sound Status in alsa-driver package in Ubuntu: New Bug description: After upgrading libasound2, libasound-data, libasound-dev with the update of this morning, speakers result as "unplugged" and headphones result as "plugged" and do not work even when really plugged. I've downgraded those packages but still no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.17.0-999-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: steven 1360 F...m pulseaudio /dev/snd/pcmC0D0p: steven 1360 F...m pulseaudio /dev/snd/controlC0: steven 1360 F pulseaudio CurrentDesktop: GNOME Date: Wed May 23 12:46:46 2018 InstallationDate: Installed on 2017-01-12 (495 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:chtrt5645 failed Symptom_Card: Audio interno - chtrt5645 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: steven 1360 F...m pulseaudio /dev/snd/pcmC0D0p: steven 1360 F...m pulseaudio /dev/snd/controlC0: steven 1360 F pulseaudio Symptom_Type: No sound at all Title: [chtrt5645 - chtrt5645, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-04-06 (46 days ago) dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X205TA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf:
