[Touch-packages] [Bug 1799857] Re: sudo -p '' displays a password prompt which it shouldn't
Confirmed incorrect behavior in bionic. xenial and cosmic behave correctly. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1799857 Title: sudo -p '' displays a password prompt which it shouldn't Status in sudo package in Ubuntu: Confirmed Bug description: I have small script that invokes another shell script as root thus: #!/bin/bash echo "mypass" | sudo -p '' -S /usr/StorMan/StorMan.sh when running in 16.04 LTS this didn't display a password prompt which I understand to be correct behaviour. Since upgrading to 18.04.1 LTS the output looks like: amonra@Charon:~$ ./storman [sudo] password for amonra: which as far as I can determine is not correct. Thanks Dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 25 03:07:27 2018 InstallationDate: Installed on 2016-03-28 (940 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-10-22 (2 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1799857/+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 1752053] Re: nvidia-390 fails to boot graphical display
You're welcome, Ccdisle. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1799918] [NEW] Desktop Dock is invisible after relogin
Public bug reported: # Reproduction Instructions 1. Lock screen by pressing WIN+L 2. Relogin to Ubuntu Desktop # Current result The application dock is invisible. # Expected result The application dock is visible. HINT: I have 3 screens connected and moved the dock to the second screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 11:33:47 2018 InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1799918 Title: Desktop Dock is invisible after relogin Status in ubuntu-meta package in Ubuntu: New Bug description: # Reproduction Instructions 1. Lock screen by pressing WIN+L 2. Relogin to Ubuntu Desktop # Current result The application dock is invisible. # Expected result The application dock is visible. HINT: I have 3 screens connected and moved the dock to the second screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 11:33:47 2018 InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1799918/+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 1370953] Re: layout switch is delayed
I'm experiencing this bug on elementary OS 5.0. After looking through different reports I can see that it comes from ubuntu. Sad that there seems to be no progress on its resolution after several years :( Did somebody found a workaround with setxkbmap or something else? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Status in gconf package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1743216] Re: perl crashed with SIGABRT in _dbus_abort()
I installed xdg-utils 1.1.2-1ubuntu2.3 from Ubuntu:18.04/bionic- proposed. We will see if it still crashes or not. Thank you Iain for your work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1743216 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Invalid Status in xdg-utils package in Ubuntu: Fix Released Status in perl source package in Bionic: Confirmed Status in xdg-utils source package in Bionic: Fix Committed Status in perl source package in Cosmic: Invalid Status in xdg-utils source package in Cosmic: Fix Released Status in xdg-utils package in Debian: Unknown Bug description: [ Description ] When xdg-screensaver suspend refers to a window with invalid UTF-8 in its title, it will spawn a perl process that crashes with an assertion: dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. [ Fix ] Use decode() from the Encode module to replace invalid character sequences with U+FFFD, the replacement symbol. This is not a new dependency as Encode has been a perl core module since 5.8. [ QA ] I don't know how to get a window with such a title, so we can do two things. 1) 1. $ sudo -e $(which xdg-screensaver) # hack the script 2. Find the line "# Inhibit idle detection (flags = 8) with window name and ID." 3. Find the } on its own above that. Insert a new line afterwards and set the window name to be the same as the one in this bug, by pasting the code $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox"; 4. Save and exit 5. $ xwininfo 6. click some window, and copy the "Window id", which will be 0x 7. $ xdg-screensaver suspend In the bad case (before this bug is fixed) it should crash, and in the good case it should work. 8. Undo what you just did by running $ xdg-screensaver resume 2) Observe that the error bucket https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 has a reduction in report rate with the new versions. [ Regression potential ] If the code is bad then the window name passed to Inhibit() could be wrong. That shouldn't matter too much. If it is really bad then the program might crash for everybody and we'll see an increase in errors. [ Original description ] Errors Bucket - https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 crashed after launching the software updater ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-4 ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12 Uname: Linux 4.14.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 13:30:52 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2017-12-28 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201) Signal: 6SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1743216/+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 1785629] Re: [MIR] gupnp-av
* -doc package: I think we should promote it as well in main, if the -dev is promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first is lynx, in universe, www-browser is a virtual package not fullfiled?). In addition, it ships the doc in devhelp format (despite symlink from doc/ to gtk-doc/). I don't think anyway that those are needed, we don't tend to have -doc dep on a browser implementation. * Same remark than for the other MIR: let's look at enabling the testsuite during build + autopkgtests * Same kind of lintian warnings than for gupnp-dlna worths fixing or override + comments IMHO (gir-missing-typelib-dependency and typelib-package-name-does-not-match) Minor: - VCS could be updated in debian/control* Pasting from gupnp-dlna: I think some of the stuff should be addressed like test running before I give my +1. This part doesn't deal directly with the network, but as we are looking at the whole dlna stack, I will defer to the security team for a review from a security perspective. I didn't spot anything crazy in the code itself, but I prefer deferring to experts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp-av in Ubuntu. https://bugs.launchpad.net/bugs/1785629 Title: [MIR] gupnp-av Status in gupnp-av package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries, including the gupnp-dlna one * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is not being used during build, we are going to look at changing that * Dependendies The package uses standard desktop libraries that are already in main (gstreamer, glib) * Standards compliance the package is using standard packaging (dh10), the standards-version is 3.9.8, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+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 1799202] Re: SRU: update Python 3.7 to the 3.7.1 release
** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1799202 Title: SRU: update Python 3.7 to the 3.7.1 release Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Fix Committed Status in python3.7 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in python3-defaults source package in Cosmic: New Status in python3-stdlib-extensions source package in Cosmic: Fix Committed Status in python3.7 source package in Cosmic: Fix Committed Bug description: SRU: update Python 3.7 to the 3.7.1 release. 3.7.1 is the first maintenance release, update both 18.04 LTS and 18.10 to the release. For 18.10 it's just one bug fix compared to the release candidate 2. python3-stdlib-extensions also updates the modules to the 3.6.7 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799202/+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 1752053] Re: nvidia-390 fails to boot graphical display
Uncommenting "WaylandEnable=false " worked. Removing gdm3 did not work, I just got redirected to a tty3 login shell. Thanks again -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display
I just tested this. It worked for me as well. Thanks, Nebojša. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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
