[Bug 2058415] Re: Reading binary data in paraview broken by libexpat1 update
This also affects libdune-grid-dev by breaking the `subsamplingvtktest` test of the package. Steps to reproduce this locally: 1. Create a new dune module using `duneproject testvtk`, adding `dune-grid` as dependency. 2. Create subdirectory `dune/grid/io/file/test/` in `testvtk` 3. Copy the file `dune-grid/dune/grid/io/file/test/checkvtkfile.hh` from the dune-grid sources to `testvtk/dune/grid/io/file/test/`. 4. Overwrite file ´testvtk/src/testvtk.cc` by the test `dune-grid/dune/grid/io/file/test/subsamplingvtktest.cc` from the dune-grid sources. 5. Build the module using `dunecontrol all` and run `testvtk/build-cmake/src/testvtk`. The same failure will probably show up when executing the tests while rebuilding the package `libdune-grid-dev`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary data in paraview broken by libexpat1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2058415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058415] Re: Reading binary data in paraview broken by libexpat1 update
** Also affects: dune-grid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary data in paraview broken by libexpat1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2058415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058415] Re: Reading binary data in paraview broken by libexpat1 update
Here's a corresponding bug report for debian sid: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064762 ** Bug watch added: Debian Bug tracker #1064762 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064762 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary data in paraview broken by libexpat1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/2058415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058415] Re: Reading binary data in paraview broken by libexpat1 update
** Summary changed: - Reading binary date broken by libexpat1 update + Reading binary data in paraview broken by libexpat1 update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary data in paraview broken by libexpat1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/2058415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058415] Re: Reading binary date broken by libexpat1 update
This problem looks related and has been reported for arch: https://discourse.paraview.org/t/i-cannot-read-a-vtp-file-i-could-open- yesterday-can-someone-try-to-open-it/13938 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary date broken by libexpat1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/2058415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058415] [NEW] Reading binary date broken by libexpat1 update
Public bug reported: The recent update of libexpat1 to version 2.5.0-2ubuntu0.1 broke Paraview. In particular reading vtu files containing binary data fails since this update. When trying to open files that worked fine before, Paraview now reports a parsing error like this one: ERROR: In vtkXMLParser.cxx, line 376 vtkXMLDataParser (0x5b0ac36fc970): Error parsing XML in stream at line 21, column 0, byte index 1036: not well-formed (invalid token) ERROR: In vtkXMLReader.cxx, line 521 vtkXMLUnstructuredGridReader (0x5b0ac3d3b670): Error parsing input file. ReadXMLInformation aborting. The problem disappears when reverting libexpat1 to version 2.5.0-2. ** Affects: expat (Ubuntu) Importance: Undecided Status: New ** Affects: paraview (Ubuntu) Importance: Undecided Status: New ** Attachment added: "This file triggers the problem." https://bugs.launchpad.net/bugs/2058415/+attachment/5757256/+files/example.vtu ** Also affects: expat (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary date broken by libexpat1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/2058415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055761] Re: tracker-extract-3 crashed with SIGSYS in epoll_wait()
I've seen this on today's daily release. Fresh installation on Yoga 7i Gen 9 (Intel 155H) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055761 Title: tracker-extract-3 crashed with SIGSYS in epoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/2055761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1973565] Re: Upgrade to 21.10 not working
Thanx! That makes sense. I will try that out man. 16. maj 2022 15.55 skrev Nick Rosbrook <1973...@bugs.launchpad.net>: > Hi Carsten, > > Looking at the attached VarLogDistupgradeMainlog.txt, it looks like the > mirror you are using does not have information for the impish release: > > 2022-05-15 12:30:21,956 DEBUG examining: 'deb > https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu > focal main restricted universe multiverse' > 2022-05-15 12:30:21,956 DEBUG found apt-cacher/apt-torrent style uri > https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu > 2022-05-15 > <https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu2022-05-15> > 12:30:21,956 DEBUG verifySourcesListEntry: deb > https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu > impish main restricted universe multiverse > 2022-05-15 12:30:21,957 DEBUG url_downloadable: > https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu/dists/impish/Release > 2022-05-15 > <https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu/dists/impish/Release2022-05-15> > 12:30:21,957 DEBUG s='https' n='mirrors.tuxedocomputers.com' > p='/ubuntu/mirror/archive.ubuntu.com/ubuntu/dists/impish/Release' q='' > f='' > 2022-05-15 12:30:22,043 DEBUG error from httplib: 'HTTP Error 404: Not > Found' > > Please select another mirror and try the upgrade again. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1973565 > > Title: > Upgrade to 21.10 not working > > Status in ubuntu-release-upgrader package in Ubuntu: > Incomplete > > Bug description: > The upgrade process stops after loading new sources. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubuntu-release-upgrader-core 1:20.04.38 > ProcVersionSignature: Ubuntu 5.15.0-10025.25~20.04.2tux2-tuxedo 5.15.30 > Uname: Linux 5.15.0-10025-tuxedo x86_64 > ApportVersion: 2.20.11-0ubuntu27.23 > Architecture: amd64 > CasperMD5CheckResult: skip > CrashDB: ubuntu > Date: Mon May 16 05:37:21 2022 > PackageArchitecture: all > ProcEnviron: >LANGUAGE=en_US:en >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/usr/bin/zsh > SourcePackage: ubuntu-release-upgrader > UpgradeStatus: Upgraded to focal on 2022-05-16 (0 days ago) > VarLogDistupgradeAptlog: >Log time: 2022-05-15 12:30:07.603201 >Log time: 2022-05-15 12:30:12.869023 >Log time: 2022-05-16 05:37:13.154811 >Log time: 2022-05-16 05:37:23.414960 > VarLogDistupgradeTermlog: > > modified.conffile..etc.default.apport: [modified] > modified.conffile..etc.update-manager.release-upgrades: [modified] > mtime.conffile..etc.default.apport: 2021-10-15T13:24:35.449679 > mtime.conffile..etc.update-manager.release-upgrades: > 2022-04-23T15:37:01.302653 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973565/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973565 Title: Upgrade to 21.10 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973565] [NEW] Upgrade to 21.10 not working
Public bug reported: The upgrade process stops after loading new sources. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-10025.25~20.04.2tux2-tuxedo 5.15.30 Uname: Linux 5.15.0-10025-tuxedo x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 16 05:37:21 2022 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2022-05-16 (0 days ago) VarLogDistupgradeAptlog: Log time: 2022-05-15 12:30:07.603201 Log time: 2022-05-15 12:30:12.869023 Log time: 2022-05-16 05:37:13.154811 Log time: 2022-05-16 05:37:23.414960 VarLogDistupgradeTermlog: modified.conffile..etc.default.apport: [modified] modified.conffile..etc.update-manager.release-upgrades: [modified] mtime.conffile..etc.default.apport: 2021-10-15T13:24:35.449679 mtime.conffile..etc.update-manager.release-upgrades: 2022-04-23T15:37:01.302653 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973565 Title: Upgrade to 21.10 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969438] Re: heartbeat (1:3.0.6-10build1) amd64 uses "eth0" on Ubuntu Server 20.04.4
** Project changed: launchpad => heartbeat (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969438 Title: heartbeat (1:3.0.6-10build1) amd64 uses "eth0" on Ubuntu Server 20.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heartbeat/+bug/1969438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956148] [NEW] package mariadb-common 1:10.3.32-0ubuntu0.20.04.1 failed to install/upgrade: »installiertes mariadb-common-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 z
Public bug reported: Tried to install mariadb after unsuccessful install of mysql and purging mysql. Purge of mysql doesn't removed /etc/mysql files. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mariadb-common 1:10.3.32-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 1 16:39:28 2022 Dependencies: mysql-common 5.8+1.0.5ubuntu2 ErrorMessage: »installiertes mariadb-common-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück InstallationDate: Installed on 2020-08-28 (490 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mariadb-10.3 Title: package mariadb-common 1:10.3.32-0ubuntu0.20.04.1 failed to install/upgrade: »installiertes mariadb-common-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.mysql.mariadb.cnf: [deleted] ** Affects: mariadb-10.3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956148 Title: package mariadb-common 1:10.3.32-0ubuntu0.20.04.1 failed to install/upgrade: »installiertes mariadb-common-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1956148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779933] Re: Unable to log in through guest network captive portal
I just experienced the same problem on Ubuntu 20.04 at a Best Western hotel in London. It's kind of a dealbreaker if you're travelling and need to work, so would be good to have it fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779933 Title: Unable to log in through guest network captive portal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1779933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910908] Re: Web-login page for captive portals not opening on public wireless networks
I experienced this recently while staying on a hotel in London. While I managed to get online on my Android phone, it was annoying - would be good to see it fixed so it works out of the box. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910908 Title: Web-login page for captive portals not opening on public wireless networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1910908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928186] Re: upgrade from 18.04 to 20.04
Hallo, danke für die schnelle Antwort. Nachdem ich python-minimal deinstalliert habe, konnte ich das System upgraden! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928186 Title: upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1928186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928186] [NEW] upgrade from 18.04 to 20.04
Public bug reported: sudo do-release-upgrade Neue Veröffentlichungen von Ubuntu werden gesucht Holen:1 Signatur der Aktualisierungsanwendung [1.554 B] Holen:2 Aktualisierungsanwendung [1.340 kB] Es wurden 1.342 kB in 0 s geholt (0 B/s) »focal.tar.gz« wird gegenüber »focal.tar.gz.gpg« legitimiert »focal.tar.gz« wird entpackt Zwischenspeicher wird gelesen Paketverwaltung wird überprüft Paketlisten werden gelesen … Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen. … Fertig OK http://archive.ubuntu.com/ubuntu bionic InRelease OK http://archive.ubuntu.com/ubuntu bionic-updates InRelease OK http://archive.ubuntu.com/ubuntu bionic-security InRelease OK http://archive.ubuntu.com/ubuntu bionic-backports InRelease Es wurden 0 B in 0 s geholt (0 B/s) Paketlisten werden gelesen … Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen. … Fertig Prüfe auf installierte Snaps Berechne Snap-Größenanforderung Informationen zu Paketquellen werden aktualisiert OK http://archive.ubuntu.com/ubuntu focal InRelease OK http://archive.ubuntu.com/ubuntu focal-updates InRelease OK http://archive.ubuntu.com/ubuntu focal-security InRelease OK http://archive.ubuntu.com/ubuntu focal-backports InRelease Es wurden 0 B in 0 s geholt (0 B/s) Paketverwaltung wird überprüft Paketlisten werden gelesen … Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen. … Fertig Änderungen werden berechnet Änderungen werden berechnet Es konnte nicht ermittelt werden, welche Systemaktualisierungen verfügbar sind Ein unlösbares Problem trat während der Berechnung der Systemaktualisierung auf. Wenn keine dieser zutrifft, melden Sie bitte den Fehler mithilfe des Befehls 'ubuntu-bug ubuntu-release-upgrader-core' in einem Terminal. Wenn Sie dies selbst untersuchen möchten, finden Sie in den Protokolldateien unter »/var/log/dist-upgrade« Details zur Systemaktualisierung. Schauen Sie sich insbesondere »main.log« und »apt.log« an. Ursprünglicher Systemzustand wird wieder hergestellt Wird abgebrochen Paketlisten werden gelesen … Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen. … Fertig ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 5.4.0-73.82~18.04.1-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed May 12 10:15:21 2021 InstallationDate: Installed on 2019-11-03 (555 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-05-12 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928186 Title: upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1928186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874842] Re: Nimbus Sans font substituting Helvetica is not being displayed correctly while using Mozilla Firefox
A detailed description of the problem: https://nolanlawson.com/2020/05/02/customizing-fonts-in-firefox-on-linux/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874842 Title: Nimbus Sans font substituting Helvetica is not being displayed correctly while using Mozilla Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1874842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902832] Re: lftp support broken - exits with error_code -11
Yes, I am sure. I tested it on another server that did not do the updates yet. It must have been one of these packages because we do daily backups and these were the only ones that were updated between the successful and failed run. I tried downgrading but apt is not very smart and would remove too many packages, and these are live systems so I did not dare to do it. Please note that switching to ncftp was successful as a workaround, so it something that only affects lftp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902832 Title: lftp support broken - exits with error_code -11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1902832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902832] Re: lftp support broken - exits with error_code -11
** Project changed: duplicity => duplicity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902832 Title: lftp support broken - exits with error_code -11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1902832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898904] Re: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel'
Thanks grofaty, I'm a not so technical user and you instructions work fine. I did it! Only one question: The terminal output ends with: patching file /usr/lib/calibre/calibre/utils/ipc/server.py Failed to parse old style options string with error: 'ascii' codec can't decode byte 0xd9 in position 1: ordinal not in range(128) Is there anything to worry about? When I download a tecnical file, I never know where to put it. Can you give some advice? Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898904 Title: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884525] Re: Cannot start calibre
*** This bug is a duplicate of bug 1898904 *** https://bugs.launchpad.net/bugs/1898904 OS xubuntu 20.04 LTS when I try to start calibre I get the following output ~$ calibre Traceback (most recent call last): File "/usr/bin/calibre", line 20, in sys.exit(calibre()) File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre main(args) File "/usr/lib/calibre/calibre/gui2/main.py", line 543, in main listener = create_listener() File "/usr/lib/calibre/calibre/gui2/main.py", line 514, in create_listener return Listener(address=gui_socket_address()) File "/usr/lib/calibre/calibre/utils/ipc/server.py", line 110, in __init__ self._listener._unlink.cancel() AttributeError: 'NoneType' object has no attribute 'cancel' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884525 Title: Cannot start calibre To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1884525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718720] Re: Sensors plugin settings lost and can't be set in 17.10
This Bug is old but still not fixed. There is also a ticket in the debian bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851407 Ubuntu 20.04.1 LTS (focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718720 Title: Sensors plugin settings lost and can't be set in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-sensors-plugin/+bug/1718720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892524] [NEW] Issues with context configuration of intrinsic web applications
Public bug reported: All context configuration files at https://salsa.debian.org/java- team/tomcat9/-/tree/master/debian/context for Apache Tomcat's built-in admin applications (as well as for /docs and /examples) contain a `path` attribute, which shall specify the webapp's URL context path. However, according to Apache Tomcat's documentation, this attribute must only be used when statically defining a context in server.xml. In all other circumstances, the path will be inferred from the filenames used for either the .xml context file or the docBase (https://tomcat.apache.org/tomcat-9.0-doc/config/context.html#Common_Attributes). As of Apache Tomcat 9.0 (since 2018-02-27) a warning message is logged, stating that the path specified in context.xml has been ignored: The path attribute with value [/manager] in deployment descriptor [/etc/tomcat9/Catalina/localhost/manager.xml] has been ignored In order to get rid of that warning log messages (one for each application), the superfluous path attribute should be removed. The context configuration files of the admin applications (manager.xml and host-manager.xml) that are actually installed in /etc/tomcat9/Catalina/localhost/ are significantly different to the corresponding original context.xml files. The latter limit access to 127.0.0.1 and also setup a sessionAttributeValueClassNameFilter suitable for use with CSRF Prevention Filter, which is added to these two apps in web.xml. Not limiting access to localhost may be intentional for Debian/Ubuntu, but setting the Manager's sessionAttributeValueClassNameFilter accordingly may be a good idea in order to make session persistence work correctly with CSRF Prevention Filter (which must store complex values (like (Linked)?HashMaps) in the session's attributes). Source package: tomcat9 (9.0.31-1) ** Affects: tomcat9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892524 Title: Issues with context configuration of intrinsic web applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/1892524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876296] Re: Broken CURL operations
The problem seems to be related to broken HTTP/2 status line support in libphobos. There is some patch available, which hopefully will appear in the GDC package soon. This should fix all packages using GDC for compilation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876296 Title: Broken CURL operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dub/+bug/1876296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877167] [NEW] package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: upgrade from 18.04.4 to 20.04 server ProblemType: Package DistroRelease: Ubuntu 20.04 Package: dbus 1.12.16-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 6 18:02:25 2020 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-05-05 (1 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: dbus Title: package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877167 Title: package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1877167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877165] [NEW] package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to install/upgrade: triggers looping, abandoned
Public bug reported: upgrade from 18.04.4 to 20.04 server ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 6 18:02:25 2020 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-05-05 (1 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877165 Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1877165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876293] [NEW] Broken CURL support with GDC
Public bug reported:
The GDC runtime access to the libcurl is broken. CURL operations abort
with unexpected error codes.
Test programm:
```
import std.net.curl;
import std.stdio;
void main()
{
HTTP http = HTTP();
auto data = get("https://acme-staging-v02.api.letsencrypt.org/directory;,
http);
writeln(data);
}
```
Compile this program and run it.
$ gdc curldownload.d -o curldownload -g
$ ./curldownload
std.net.curl.HTTPStatusException@/usr/lib/gcc/aarch64-linux-gnu/10/include/d/std/net/curl.d(1071):
HTTP request returned status code 0 ()
??:? pure @safe bool std.exception.enforce!(bool).enforce(bool, lazy
object.Throwable) [0x7faf82d3]
??:? char[] std.net.curl._basicHTTP!(char)._basicHTTP(const(char)[],
const(void)[], std.net.curl.HTTP) [0xd4d9384b]
??:? char[] std.net.curl.get!(std.net.curl.HTTP, char).get(const(char)[],
std.net.curl.HTTP) [0xd4d92833]
??:? _Dmain [0xd4d9272f]
??:? ???[0x7fc808bb]
??:? ???[0x7fc80c2f]
??:? _d_run_main [0x7fc80d9f]
??:? main [0xd4d927a3]
??:? __libc_start_main [0x7f6da08f]
??:? ???[0xd4d92603]
The same issue also impacts the 'dub' package. It is *not* possible to
update/fetch packages from code.dlang.org.
I compiled 'ldc2' from sources in its latest version. The code snippet
works fine, when compiled with ldc- Also 'dub', when recompiled with
ldc2, works fine.
So there is some problem with gdc and its access to libcurl. Maybe
broken library bindungs? Some issue with ARM32 and ARM64 archs (same
problem with ARM32(gnueabihf))?
Issue also reported on dlang.org :
https://issues.dlang.org/show_bug.cgi?id=20380
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdc-10 10-20200411-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-1008.8-raspi 5.4.29
Uname: Linux 5.4.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27
Architecture: arm64
CasperMD5CheckResult: skip
Date: Fri May 1 12:19:49 2020
SourcePackage: gcc-10
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gcc-10 (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug arm64 focal uec-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876293
Title:
Broken CURL support with GDC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1876293/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876296] [NEW] Broken CURL operations
Public bug reported: The official dub package fails to operate properly with libcurl. It aborts with unexpected error in runtime. $ /usr/bin/dub --version DUB version 1.19.0-1build2, built on Mar 24 2020 $ /usr/bin/dub upgrade -v Using dub registry url 'https://code.dlang.org/' Refreshing local packages (refresh existing: true)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/cschlote/.dub/packages/local-packages.json Looking for local package map at /home/cschlote/build/dlang/lzd/.dub/packages/local-packages.json Determined package version using GIT: lzd 0.3.4+commit.3.g1026347 Refreshing local packages (refresh existing: false)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/cschlote/.dub/packages/local-packages.json Looking for local package map at /home/cschlote/build/dlang/lzd/.dub/packages/local-packages.json Found dependency silly 1.0.2 Upgrading project in /home/cschlote/build/dlang/lzd Search for versions of silly (1 package suppliers) Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback package supplier registry at https://code-mirror.dlang.io/ failed with 'Failed to download https://code-mirror.dlang.io/api/packages/infos?packages=%5B%22silly%22%5D_dependencies=true=true'. Fallback package supplier registry at https://dub-registry.herokuapp.com/ failed with 'HTTP request returned status code 503 (Service Unavailable)'. Package silly not found in registry at https://code.dlang.org/ (fallbacks registry at https://code-mirror.dlang.io/, registry at https://dub-registry.herokuapp.com/): HTTP request returned status code 0 () Return for silly: [1.0.2] Dependency resolution result: silly: 1.0.2 Refreshing local packages (refresh existing: false)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/cschlote/.dub/packages/local-packages.json Looking for local package map at /home/cschlote/build/dlang/lzd/.dub/packages/local-packages.json Found dependency silly 1.0.2 However, a dub version compiled with ldc2 (also compiled from sources) works fine: $ /usr/local/bin/dub upgrade -v Using dub registry url 'https://code.dlang.org/' Refreshing local packages (refresh existing: true)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/cschlote/.dub/packages/local-packages.json Looking for local package map at /home/cschlote/build/dlang/lzd/.dub/packages/local-packages.json Determined package version using GIT: lzd 0.3.4+commit.3.g1026347 Refreshing local packages (refresh existing: false)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/cschlote/.dub/packages/local-packages.json Looking for local package map at /home/cschlote/build/dlang/lzd/.dub/packages/local-packages.json Found dependency silly 1.0.2 Upgrading project in /home/cschlote/build/dlang/lzd Search for versions of silly (1 package suppliers) Return for silly: [1.0.2, 1.0.1, 1.0.0, 0.8.2, 0.8.1, 0.8.0, 0.7.1, 0.7.0, 0.6.0, 0.5.0, 0.4.3, 0.4.2, 0.4.1, 0.4.0, 0.3.0, 0.2.1, 0.2.0, 0.1.1, 0.1.0, 0.7.0-alpha, ~master] Dependency resolution result: silly: 1.0.2 Refreshing local packages (refresh existing: false)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/cschlote/.dub/packages/local-packages.json Looking for local package map at /home/cschlote/build/dlang/lzd/.dub/packages/local-packages.json Found dependency silly 1.0.2 The problem prevents the use of all packages on code.dlang.org as it aborts with 'https://code-mirror.dlang.io/, registry at https://dub- registry.herokuapp.com/): HTTP request returned status code 0 ()'. Problem is related to Bug #1876293 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: dub 1.19.0-1build2 ProcVersionSignature: Ubuntu 5.4.0-1008.8-raspi 5.4.29 Uname: Linux 5.4.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Fri May 1 12:36:37 2020 SourcePackage: dub UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dub (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876296 Title: Broken CURL operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dub/+bug/1876296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876293] Re: Broken CURL support with GDC
Recompiling libcurl from sources and copying the library binaries over the 'official' ones in /usr/libs/ also fixed the problem in the past. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876293 Title: Broken CURL support with GDC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1876293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1772148] Re: Mount.cifs does not work without keyutils being installed
Hi Andreas,
I'll see what I can do..but it may take a few months, due to the
upcoming semester...I think your hunch is correct, I just need to
re-establish an environmet to reproduce the defect (in a virtual box).
In the meantime: have fun!
Carsten
Den ons. 14. aug. 2019 kl. 16.01 skrev Andreas Hasenack :
>
> Hello Carsten, thanks for coming back to us
>
> I have a feeling this is about secrets stored in the keyring, so any
> clue around that area would help. In the end we might just put keyutils
> back as a Recommends, but I would like to understand in which scenario
> this is needed.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772148
>
> Title:
> Mount.cifs does not work without keyutils being installed
>
> Status in cifs-utils package in Ubuntu:
> Confirmed
>
> Bug description:
> In 17.10 you could mount a cifs network-drive via
>
> > sudo mount -t cifs //xx.yy.zz/abc t -o
> vers=1.0,username=xx,sec=ntlm,uid=1000,gid=1000,iocharset=utf8,domain=DD
>
> having cifs-utils (and smbclient) installed manually.
>
> But in 18.04 (both with SMB1 and moving til SMB3) it does not work
> until keyutils has been installed.
>
> The only error I see, when the cifs mount is not working, is a -2
> error ("mount error(2): No such file or directory" or "CIFS VFS:
> cifs_mount failed w/return code = -2"):
>
> mbmount> sudo mount -t cifs //xx.yy.zz/abc t --verbose -o
> vers=3,username=xx,sec=ntlmv2,uid=1000,gid=1000,iocharset=utf8,domain=DD,nounix
> Password for x:
> mount error(2): No such file or directory
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
>
> Smbmount> dmesg | tail
> [ 89.915840] [UFW BLOCK] IN=wlp4s0 OUT=
> MAC=28:16:ad:18:e7:87:00:18:4d:4f:f5:1c:08:00 SRC=10.88.128.13
> DST=192.168.1.3 LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=17677 PROTO=TCP SPT=445
> DPT=55514 WINDOW=0 RES=0x00 RST URGP=0
> [ 89.916307] [UFW BLOCK] IN=wlp4s0 OUT=
> MAC=28:16:ad:18:e7:87:00:18:4d:4f:f5:1c:08:00 SRC=10.88.4.188 DST=192.168.1.3
> LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=5527 PROTO=TCP SPT=445 DPT=52714
> WINDOW=0 RES=0x00 RST URGP=0
> [ 362.580011] FS-Cache: Loaded
> [ 362.592410] FS-Cache: Netfs 'cifs' registered for caching
> [ 362.592495] Key type cifs.spnego registered
> [ 362.592498] Key type cifs.idmap registered
> [ 362.752492] CIFS VFS: BAD_NETWORK_NAME: \\xx.yy.zz\abc
> [ 362.787329] CIFS VFS: cifs_mount failed w/return code = -2
> [ 381.832633] CIFS VFS: BAD_NETWORK_NAME: \\xx.yy.zz\abc
> [ 381.870721] CIFS VFS: cifs_mount failed w/return code = -2
>
> > apt install keyutils
> ...
>
> Smbmount> sudo mount -t cifs //xx.yy.zz/abc t --verbose -o
>
> vers=3,username=xx,sec=ntlmv2,uid=1000,gid=1000,iocharset=utf8,domain=DD,nounix
>
> >MOUNT OK HERE>
>
> Smbmount> dmesg | tail
> [ 89.916307] [UFW BLOCK] IN=wlp4s0 OUT=
> MAC=28:16:ad:18:e7:87:00:18:4d:4f:f5:1c:08:00 SRC=10.88.4.188 DST=192.168.1.3
> LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=5527 PROTO=TCP SPT=445 DPT=52714
> WINDOW=0 RES=0x00 RST URGP=0
> [ 362.580011] FS-Cache: Loaded
> [ 362.592410] FS-Cache: Netfs 'cifs' registered for caching
> [ 362.592495] Key type cifs.spnego registered
> [ 362.592498] Key type cifs.idmap registered
> [ 362.752492] CIFS VFS: BAD_NETWORK_NAME: \\xx.yy.zz\abc
> [ 362.787329] CIFS VFS: cifs_mount failed w/return code = -2
> [ 381.832633] CIFS VFS: BAD_NETWORK_NAME: \\xx.yy.zz\abc
> [ 381.870721] CIFS VFS: cifs_mount failed w/return code = -2
> [ 432.322763] CIFS VFS: BAD_NETWORK_NAME: \\xx.yy.zz\abc
>
> Keyutils were not manually installed in my 17.10 system. And I am
> aware of the change in default SMB versions from kernel 4.13.5 and on
> (cause me to insert the vers=1.0 in the mount options):
>
> From man mount.cifs:
>"The default since v4.13.5 is for the client and server to negotiate the
> highest possible
>version greater than or equal to 2.1. In kernels prior to
>v4.13, the default was 1.0. For kernels between v4.13 and v4.13.5 the
> default is 3.0."
>
> And there are no fundamental change in the packages for cifs-utils, as
> I can see (both suggests to use keyutils!).
>
> My 17.10:
> Package: cifs-utils
> Status: install ok installed
> Priority: optional
> Section: otherosfs
> Installed-Size: 229
> Maintainer: Ubuntu Developers
> Architecture: amd64
> Version: 2:6.7-1
> Replaces: smbfs (<< 2:4.0~rc1-1)
> Depends: samba-common, libc6 (>= 2.17), libcap-ng0, libkeyutils
Re: [Bug 1772148] Re: Mount.cifs does not work without keyutils being installed
Hi Andreas,
Should I try to produce some info to you regarding the "Mount.cifs"
defect?
It was a long time since I last saw it, so it may take some time to
dig up again...but it seems to be worthwhile to generate some
additional debug info to you.
Please write, if there are particular details you are looking for,
otherwise I will try to follow your outline in the email, looking for
keys in keystores. But it may take some time, due to the upcomming
semester, and lots of new students!
Regards
Carsten Eie Frigaard
Den ons. 3. jul. 2019 kl. 22.31 skrev Andreas Hasenack :
>
> It's not as simple as that, I can mount cifs shares just fine on 18.04
> without having keyutils installed. I tried the exact same command line
> as in comment #1, bar the username/domain, against a synology DS216 NAS,
> and it worked just fine:
>
> $ sudo mount -t cifs //ds216.lowtech/downloads --verbose -o
> vers=3,username=andreas,sec=ntlmv2,uid=1000,gid=1,iocharset=utf8,domain=LOWTECH,nounix
> Password for andreas@//ds216.lowtech/downloads: *
> mount.cifs kernel mount options:
> ip=10.10.1.5,unc=\\ds216.lowtech\downloads,vers=3.0,file_mode=0644,dir_mode=0755,vers=3,sec=ntlmv2,iocharset=utf8,nounix,uid=1000,gid=1,user=andreas,domain=LOWTECH,pass=
>
> $ mount -t cifs
> //ds216.lowtech/downloads on /ds216/downloads type cifs
> (rw,nosuid,nodev,noexec,relatime,vers=3,sec=ntlmv2,cache=strict,username=andreas,domain=LOWTECH,uid=1000,forceuid,gid=1,forcegid,addr=10.10.1.5,file_mode=0644,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user)
>
> Do you guys have a pam module or something else storing keys in the
> kernel keyring, which cifs-utils is trying to use in your case? Try
> "keyctl show", as root and as your user.
>
> Something else you could try is enabling cifs debugging, as outlined
> here:
>
> https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting#Enabling_Debugging
>
>
> The first two "echo" commands fail here, but the one to cifsFYI works, and
> produces a bit more information in dmesg.
>
> Let's see if any of this helps us get to the root of the problem.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772148
>
> Title:
> Mount.cifs does not work without keyutils being installed
>
> Status in cifs-utils package in Ubuntu:
> Confirmed
>
> Bug description:
> In 17.10 you could mount a cifs network-drive via
>
> > sudo mount -t cifs //xx.yy.zz/abc t -o
> vers=1.0,username=xx,sec=ntlm,uid=1000,gid=1000,iocharset=utf8,domain=DD
>
> having cifs-utils (and smbclient) installed manually.
>
> But in 18.04 (both with SMB1 and moving til SMB3) it does not work
> until keyutils has been installed.
>
> The only error I see, when the cifs mount is not working, is a -2
> error ("mount error(2): No such file or directory" or "CIFS VFS:
> cifs_mount failed w/return code = -2"):
>
> mbmount> sudo mount -t cifs //xx.yy.zz/abc t --verbose -o
> vers=3,username=xx,sec=ntlmv2,uid=1000,gid=1000,iocharset=utf8,domain=DD,nounix
> Password for x:
> mount error(2): No such file or directory
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
>
> Smbmount> dmesg | tail
> [ 89.915840] [UFW BLOCK] IN=wlp4s0 OUT=
> MAC=28:16:ad:18:e7:87:00:18:4d:4f:f5:1c:08:00 SRC=10.88.128.13
> DST=192.168.1.3 LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=17677 PROTO=TCP SPT=445
> DPT=55514 WINDOW=0 RES=0x00 RST URGP=0
> [ 89.916307] [UFW BLOCK] IN=wlp4s0 OUT=
> MAC=28:16:ad:18:e7:87:00:18:4d:4f:f5:1c:08:00 SRC=10.88.4.188 DST=192.168.1.3
> LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=5527 PROTO=TCP SPT=445 DPT=52714
> WINDOW=0 RES=0x00 RST URGP=0
> [ 362.580011] FS-Cache: Loaded
> [ 362.592410] FS-Cache: Netfs 'cifs' registered for caching
> [ 362.592495] Key type cifs.spnego registered
> [ 362.592498] Key type cifs.idmap registered
> [ 362.752492] CIFS VFS: BAD_NETWORK_NAME: \\xx.yy.zz\abc
> [ 362.787329] CIFS VFS: cifs_mount failed w/return code = -2
> [ 381.832633] CIFS VFS: BAD_NETWORK_NAME: \\xx.yy.zz\abc
> [ 381.870721] CIFS VFS: cifs_mount failed w/return code = -2
>
> > apt install keyutils
> ...
>
> Smbmount> sudo mount -t cifs //xx.yy.zz/abc t --verbose -o
>
> vers=3,username=xx,sec=ntlmv2,uid=1000,gid=1000,iocharset=utf8,domain=DD,nounix
>
> >MOUNT OK HERE>
>
> Smbmount> dmesg | tail
> [ 89.916307] [UFW BLOCK] IN=wlp4s0 OUT=
> MAC=28:16:ad:18:e7:87:00:18:4d:4f:f5:1c:08:00 SRC=10.88.4.188 DST=192.168.1.3
> LEN=40 TO
[Bug 1063140] Re: Drag and Drop position ignored by xfdesktop
Ah, thanks for the clarification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063140 Title: Drag and Drop position ignored by xfdesktop To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1063140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063140] Re: Drag and Drop position ignored by xfdesktop
I disagree. Bug 12201 is related to the Grub bootloader and it's a new feature request. It has nothing to do with this ticket. It's not a duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063140 Title: Drag and Drop position ignored by xfdesktop To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1063140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815356] [NEW] package grub-efi-amd64-signed 1.93.11+2.02-2ubuntu8.10 failed to install/upgrade: Unterprozess installiertes grub-efi-amd64-signed-Skript des Paketes post-installation gab den Fehl
Public bug reported: error during update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64-signed 1.93.11+2.02-2ubuntu8.10 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: openssh-client:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Feb 9 18:26:58 2019 ErrorMessage: Unterprozess installiertes grub-efi-amd64-signed-Skript des Paketes post-installation gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-12-27 (44 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.8 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.93.11+2.02-2ubuntu8.10 failed to install/upgrade: Unterprozess installiertes grub-efi-amd64-signed-Skript des Paketes post-installation gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815356 Title: package grub-efi-amd64-signed 1.93.11+2.02-2ubuntu8.10 failed to install/upgrade: Unterprozess installiertes grub-efi-amd64-signed- Skript des Paketes post-installation gab den Fehler-Ausgangsstatus 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1815356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10
The mainline kernel indeed seems to fix the issue: Not a single failed suspend/resume cycle since using 4.19.1. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10
Yes the issue did not happen prior to the update to 18.04. But I don't know if there was a prior kernel in 18.04 where the issue did not occur, because it's not happening 100% of the time. Still a successful resume is rare. I'll give the mainline kernel a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209384/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209390/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209388/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209381/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209392/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209382/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209391/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209389/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209387/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209394/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209385/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209393/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209386/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209383/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10
apport information ** Tags added: apport-collected ** Description changed: After upgrading to kubuntu 18.04 resuming from suspend fails in most cases on my laptop. When trying to resume the power LED is turned on, but the screen stays black and the system does not respond at all. Switching to another virtual terminal is not possible and closing the lid again does not show any effect. The hardware is a Dell Latitude e7440 with core i7 4600U and intel graphics only. The only way to change the status is a hard shut-down by long pressing the power button. The last message in kern.log is: PM: suspend entry (deep) The described problem is similar to bug #1774950. However, the latter is considered to be fixed with kernel 4.15.0-38 while my problem persists with this kernel. Output of 'sudo lspci -vnvn' is attached, the result of 'cat /proc/version_signature' is: Ubuntu 4.15.0-38.41-generic 4.15.18 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: graeser2116 F pulseaudio + /dev/snd/controlC0: graeser2116 F pulseaudio + CurrentDesktop: KDE + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-precise-amd64-20130203-1 + DistroRelease: Ubuntu 18.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=none + InstallationDate: Installed on 2014-03-20 (1690 days ago) + InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 + MachineType: Dell Inc. Latitude E7440 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-38-generic N/A + linux-backports-modules-4.15.0-38-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-38-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 02/02/2015 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A14 + dmi.board.name: 0WK2DM + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E7440 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1801743/+attachment/5209380/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Thanks for the information. I just filed bug #1801743. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801743] [NEW] Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10
Public bug reported: After upgrading to kubuntu 18.04 resuming from suspend fails in most cases on my laptop. When trying to resume the power LED is turned on, but the screen stays black and the system does not respond at all. Switching to another virtual terminal is not possible and closing the lid again does not show any effect. The hardware is a Dell Latitude e7440 with core i7 4600U and intel graphics only. The only way to change the status is a hard shut-down by long pressing the power button. The last message in kern.log is: PM: suspend entry (deep) The described problem is similar to bug #1774950. However, the latter is considered to be fixed with kernel 4.15.0-38 while my problem persists with this kernel. Output of 'sudo lspci -vnvn' is attached, the result of 'cat /proc/version_signature' is: Ubuntu 4.15.0-38.41-generic 4.15.18 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Result of sudo lspci -vnvn" https://bugs.launchpad.net/bugs/1801743/+attachment/5209340/+files/lspci-vnvn.log ** Description changed: After upgrading to kubuntu 18.04 resuming from suspend fails in most cases on my laptop. When trying to resume the power LED is turned on, but the screen stays black and the system does not respond at all. Switching to another virtual terminal is not possible and closing the lid again does not show any effect. The hardware is a Dell Latitude e7440 with core i7 4600U and intel graphics only. The only way to change the status is a hard shut-down by long pressing the power button. The last message in kern.log is: PM: suspend entry (deep) - The described problem is similar to #1774950. However, the latter is + The described problem is similar to bug #1774950. However, the latter is considered to be fixed with kernel 4.15.0-38 while my problem persists with this kernel. Output of 'sudo lspci -vnvn' is attached, the result of 'cat /proc/version_signature' is: Ubuntu 4.15.0-38.41-generic 4.15.18 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
So should I file a new bug report or should the status of this one be changed again? Can I help by providing more information? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
My Dell Latitude e7440 (core i7 4600U, intel graphics) shows a similar behaviour after updating to 18.04: Wake-up after suspend often fails with power LED on. Hard shut down seems to be the only way to recover. Sometimes, additionally to this, suspend seems to incomplete in the sense that the laptop gets hot and the fan is running. The last entry in kern.log during the failing suspend is: PM: suspend entry (deep) While the issue shows up often, I did not figure out how to deterministically triggers it. I'm using the current kernel 4.15.0-38. Should this one contain the above discussed fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597466] Re: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file
Also Ubuntu 18.04.1 LTS here.
I tracked down the issue to the plymouth-theme-kubuntu-text.postinst
script:
Comparing /var/lib/dpkg/info/plymouth-theme-ubuntu-text.postinst and
/var/lib/dpkg/info/plymouth-theme-kubuntu-text.postinst we see that the
first has:
case "$1" in
configure|triggered)
if [ "$1" = "configure" ]; then
# We remove leftover generated file from previous plymouth
version. Can be removed on xenial+1
if dpkg --compare-versions "$2" le-nl "0.9.2-3ubuntu1~"; then
rm -f
/lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
fi
fi
while the second has:
case "$1" in
configure|triggered)
# We remove leftover generated file from previous plymouth version. Can
be removed on xenial+1
if dpkg --compare-versions "$2" le-nl "1:16.04ubuntu1~"; then
rm -f /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
fi
Notice the missing check for the "configure" argument. Also see
http://man7.org/linux/man-pages/man5/deb-postinst.5.html:
postinst configure old-version
After the package was installed.
postinst triggered trigger-name...
After the package was triggered.
The actual "bad syntax" message is then generated because
dpkg --compare-versions "$2" le-nl "1:16.04ubuntu1~"
resolves to
dpkg --compare-versions "/etc/lsb-release" le-nl "1:16.04ubuntu1~"
which is of course not what dpkg expects ("/etc/lsb-release" being the
trigger-name)
So the bug seems to be a missing check for "configure" in the kubuntu
version of the plymouth-theme postinst script.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597466
Title:
dpkg giving warning about '/etc/lsb-release' version number not
starting with a digit when there is no apparent problem in the file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1597466/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455881] Re: Global history for apt package management
Sorry it's still a problem in Ubuntu 18.04 and yes, I'm still interested in finding a solution. I think "apport-collect 1455881" is not necessary. The problem is extremely easy to reproduce. I can understand that some people consider this as enhancement or feature but I think this is a bug. It's irritating and provokes mistakes at the administrative level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455881 Title: Global history for apt package management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1455881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628862] Re: RSS & "Accept-Language" header
I can't reproduce it, because the RSS feet changed its URL structure. That means my personal problem is gone anyway. If nobody else is affected by this issue, then it's ok for me to close it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628862 Title: RSS & "Accept-Language" header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1628862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
Same with me, on two different CPUs (old 2009 macbook and an amd desktop) both running 18.04. Linux MyCPU 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Also tried the reinstall thingy as suggested in post#2 with no difference. lsusb-> Bus 008 Device 002: ID 056a:00dd Wacom Co., Ltd Bamboo Pen (CTL-470) Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ..shows the tablet, it works like a mouse but no pressure nor access through control panel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772148] Re: Mount.cifs does not work without keyutils being installed
A small clarification of the problem: The core issue is that installing
cifs-utils (and smbclient) and doing a cifs SMB3 (or SMB1) mount:
> sudo mount -t cifs //xx.yy.zz/abc t --verbose -o
vers=3,username=xx,sec=ntlmv2,uid=1000,gid=1000,iocharset=utf8,domain=DD,nounix
yields a obfuscating "-2" CIFS error code:
dmesg: [ 381.870721] CIFS VFS: cifs_mount failed w/return code = -2
error text: No such file or directory" or "CIFS VFS: cifs_mount failed
w/return code = -2"
Installing keyutils resolves the problem, and the mount command
succeeds.
Keyutils is a suggested package in cifs-utils (and libkeyutils1 is
required), but it seems that the CIFS mount is directly dependent on the
keyutils package (not just the libkeyutils1 as one would expect).
The problem is NOT new in 18.04, it was basically the same in 17.10.
A suggested solution could be 1) to check CIFS for use/dependency of
keyutils, and to put a better error message into the log ('keytuils
missing' not just -2), or 2) to make keyutils required for the cifs-
utils package.
NOTE: I still get a strange
dmesg: [ 362.752492] CIFS VFS: BAD_NETWORK_NAME: \\xx.yy.zz\abc
when the mount succeeds.
Regards
.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772148
Title:
Mount.cifs does not work without keyutils being installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1772148/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly
Yes, right - thank you! This is related to: https://wiki.ubuntu.com/MigratingToNetplan#Rationale https://askubuntu.com/questions/1005390/why-did-ubuntu-change-the- network-configuration https://github.com/hashicorp/vagrant/issues/9134 https://github.com/hashicorp/vagrant/issues/9428 As I can not upgrade to the latest Vagrant version due to other compatibility issues I'll try installing ifupdown package manually as a workaround. ** Bug watch added: github.com/hashicorp/vagrant/issues #9134 https://github.com/hashicorp/vagrant/issues/9134 ** Bug watch added: github.com/hashicorp/vagrant/issues #9428 https://github.com/hashicorp/vagrant/issues/9428 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: Vagrant bionic 64 with virtualbox image doesn't start network correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1738400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly
I've just checked v20180518.0.0 with the same result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: Vagrant bionic 64 with virtualbox image doesn't start network correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly
I have the same issue with 'ubuntu/bionic64' (v20180426.2.0) on MacOS 10.11 / Vagrant 1.9.8 / VirtualBox 5.1.30 --- The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! /sbin/ifdown 'enp0s8' || true /sbin/ip addr flush dev 'enp0s8' # Remove any previous network modifications from the interfaces file sed -e '/^#VAGRANT-BEGIN/,$ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces.pre sed -ne '/^#VAGRANT-END/,$ p' /etc/network/interfaces | tac | sed -e '/^#VAGRANT-END/,$ d' | tac > /tmp/vagrant-network-interfaces.post cat \ /tmp/vagrant-network-interfaces.pre \ /tmp/vagrant-network-entry \ /tmp/vagrant-network-interfaces.post \ > /etc/network/interfaces rm -f /tmp/vagrant-network-interfaces.pre rm -f /tmp/vagrant-network-entry rm -f /tmp/vagrant-network-interfaces.post /sbin/ifup 'enp0s8' Stdout from the command: Stderr from the command: bash: line 4: /sbin/ifdown: No such file or directory bash: line 20: /sbin/ifup: No such file or directory --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: Vagrant bionic 64 with virtualbox image doesn't start network correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749723] Re: Unable to upgrade from Ubuntu 12.04 to 14.04
To be precise: agger@dsntest:~$ sudo dpkg --configure -a agger@dsntest:~$ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749723 Title: Unable to upgrade from Ubuntu 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1749723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749723] Re: Unable to upgrade from Ubuntu 12.04 to 14.04
Hi Gustavo, I just did that. It doesn't fix it. In fact, it does nothing, reflecting the fact that the 12.04 system is already fully upgraded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749723 Title: Unable to upgrade from Ubuntu 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1749723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749723] [NEW] Unable to upgrade from Ubuntu 12.04 to 14.04
Public bug reported: Update-manager stops and informs me that something unspecified goes wrong. Apparently, this is about package conflicts which affects a lot of Python packages. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager (not installed) ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.15 Architecture: amd64 Date: Thu Feb 15 15:42:21 2018 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) MarkForUpload: True ProcEnviron: TERM=screen PATH=(custom, no user) LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: Upgraded to precise on 2018-02-15 (0 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749723 Title: Unable to upgrade from Ubuntu 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1749723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731870] Re: Failed to start Cryptography Setup for cryptswap1
@rubo77: why not as described at https://bugs.launchpad.net/ecryptfs/+bug/1670336, comments #21 and #23? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731870 Title: Failed to start Cryptography Setup for cryptswap1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1731870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740923] Re: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Problem occurs on Pentium M with PAE bug. Solved by adding forcepae to grub and grub-update. After that sudo apt-get install -f worked. Before this update forcepae was not needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740923 Title: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740923] [NEW] package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: standard system update after first install of lubuntu ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-16-generic. ApportVersion: 2.20.7-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: red 862 F pulseaudio Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with Cx20468-31 at irq 10' Mixer name : 'Conexant Cx20468-31' Components : 'AC97a:43585430' Controls : 24 Simple ctrls : 16 Date: Tue Jan 2 20:09:24 2018 DuplicateSignature: package:linux-image-4.13.0-21-generic:(not installed) Preparing to unpack .../71-linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /tmp/apt-dpkg-install-UematV/71-linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=c3bdf7d5-b131-4b28-8b11-ad45372208c2 InstallationDate: Installed on 2018-01-02 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer TravelMate 4000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=c553c403-6d68-4bee-af31-1b6dc83b7391 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2004 dmi.bios.vendor: ACER dmi.bios.version: 3A10 dmi.board.name: TravelMate 4000 dmi.board.vendor: Acer dmi.board.version: Rev 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Rev.1 dmi.modalias: dmi:bvnACER:bvr3A10:bd10/12/2004:svnAcer:pnTravelMate4000:pvrRev1:rvnAcer:rnTravelMate4000:rvrRev1.0:cvnAcer:ct10:cvrRev.1: dmi.product.name: TravelMate 4000 dmi.product.version: Rev 1 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package artful i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740923 Title: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
There is a new bios update for the ThinkPad Yoga S1 available under https://support.lenovo.com/de/de/downloads/ds038335. Could this have any relation to our bios problems? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Am i right that the fix is included in linux-image-4.13.0-21-generic? This update just arrived on my ThinkPad Yoga S1, but sadly it didn't change anything. Still bios changes disappear after booting Xubuntu 17.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734139] [NEW] Failed Installation, grub could not be installed
Public bug reported: Installation could not continue without grub installation ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.9 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 Date: Thu Nov 23 15:57:31 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=de_DE.UTF-8 PATH=(custom, no user) LANG=de_DE.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734139 Title: Failed Installation, grub could not be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1734139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734140] [NEW] Failed Installation, grub could not be installed
Public bug reported: Installation could not continue without grub installation ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.9 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 Date: Thu Nov 23 15:57:31 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=de_DE.UTF-8 PATH=(custom, no user) LANG=de_DE.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734140 Title: Failed Installation, grub could not be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1734140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722592] [NEW] package python3-jwt 1.3.0-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Error occurred during the boot process ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-jwt 1.3.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Oct 9 17:49:11 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-10-08 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: pyjwt Title: package python3-jwt 1.3.0-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pyjwt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722592 Title: package python3-jwt 1.3.0-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyjwt/+bug/1722592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708511] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die
Public bug reported: in screen there is the information for a conflict ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49 Uname: Linux 4.4.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Aug 3 21:10:17 2017 DpkgHistoryLog: Start-Date: 2017-08-03 21:10:10 Commandline: apt-get install -f Requested-By: carsten (1000) Upgrade: grub-common:amd64 (2.02~beta2-36ubuntu3.11, 2.02~beta2-36ubuntu3.12), grub2-common:amd64 (2.02~beta2-36ubuntu3.11, 2.02~beta2-36ubuntu3.12), grub-pc:amd64 (2.02~beta2-36ubuntu3.11, 2.02~beta2-36ubuntu3.12), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.11, 2.02~beta2-36ubuntu3.12) ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2017-02-11 (173 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708511 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1708511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707029] [NEW] Crashes, when installing on EFI system
Public bug reported: Tried to install on efi, but failed . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.3 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 Date: Thu Jul 27 19:53:59 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/xubuntu.seed cdrom-detect/try-usb=true persistent noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: LANGUAGE=de_DE.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.3 xenial xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707029 Title: Crashes, when installing on EFI system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1707029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705824] [NEW] package grub-pc-bin 2.02~beta2-36ubuntu3.11 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie di
Public bug reported: during booting information is displayed that there is a mistake. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-pc-bin 2.02~beta2-36ubuntu3.11 ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49 Uname: Linux 4.4.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Jul 21 18:38:05 2017 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2017-02-11 (161 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic root=UUID=e8e0b0b6-9e94-4ea5-95f0-2aa1e4345c84 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: grub2 Title: package grub-pc-bin 2.02~beta2-36ubuntu3.11 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705824 Title: package grub-pc-bin 2.02~beta2-36ubuntu3.11 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1705824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704553] [NEW] package grub-pc 2.02~beta2-36ubuntu3.11 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Public bug reported: Description:Ubuntu 16.04.2 LTS Release:16.04 Paketdateien: 100 /var/lib/dpkg/status release a=now 500 http://update.devolo.com/linux/apt stable/main i386 Packages release o=devolo,a=stable,n=stable,l=devolo,c=main,b=i386 origin update.devolo.com 500 http://update.devolo.com/linux/apt stable/main amd64 Packages release o=devolo,a=stable,n=stable,l=devolo,c=main,b=amd64 origin update.devolo.com 500 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 Packages release v=16.04,o=Ubuntu,a=xenial-security,n=xenial,l=Ubuntu,c=multiverse,b=i386 origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages release v=16.04,o=Ubuntu,a=xenial-security,n=xenial,l=Ubuntu,c=multiverse,b=amd64 origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages release v=16.04,o=Ubuntu,a=xenial-security,n=xenial,l=Ubuntu,c=universe,b=i386 origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages release v=16.04,o=Ubuntu,a=xenial-security,n=xenial,l=Ubuntu,c=universe,b=amd64 origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 Packages release v=16.04,o=Ubuntu,a=xenial-security,n=xenial,l=Ubuntu,c=restricted,b=i386 origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 Packages release v=16.04,o=Ubuntu,a=xenial-security,n=xenial,l=Ubuntu,c=restricted,b=amd64 origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages release v=16.04,o=Ubuntu,a=xenial-security,n=xenial,l=Ubuntu,c=main,b=i386 origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages release v=16.04,o=Ubuntu,a=xenial-security,n=xenial,l=Ubuntu,c=main,b=amd64 origin security.ubuntu.com 500 http://archive.canonical.com/ubuntu xenial/partner i386 Packages release v=16.04,o=Canonical,a=xenial,n=xenial,l=Partner archive,c=partner,b=i386 origin archive.canonical.com 500 http://archive.canonical.com/ubuntu xenial/partner amd64 Packages release v=16.04,o=Canonical,a=xenial,n=xenial,l=Partner archive,c=partner,b=amd64 origin archive.canonical.com 100 http://de.archive.ubuntu.com/ubuntu xenial-backports/universe i386 Packages release v=16.04,o=Ubuntu,a=xenial-backports,n=xenial,l=Ubuntu,c=universe,b=i386 origin de.archive.ubuntu.com 100 http://de.archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages release v=16.04,o=Ubuntu,a=xenial-backports,n=xenial,l=Ubuntu,c=universe,b=amd64 origin de.archive.ubuntu.com 100 http://de.archive.ubuntu.com/ubuntu xenial-backports/main i386 Packages release v=16.04,o=Ubuntu,a=xenial-backports,n=xenial,l=Ubuntu,c=main,b=i386 origin de.archive.ubuntu.com 100 http://de.archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages release v=16.04,o=Ubuntu,a=xenial-backports,n=xenial,l=Ubuntu,c=main,b=amd64 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/multiverse i386 Packages release v=16.04,o=Ubuntu,a=xenial-updates,n=xenial,l=Ubuntu,c=multiverse,b=i386 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages release v=16.04,o=Ubuntu,a=xenial-updates,n=xenial,l=Ubuntu,c=multiverse,b=amd64 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages release v=16.04,o=Ubuntu,a=xenial-updates,n=xenial,l=Ubuntu,c=universe,b=i386 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages release v=16.04,o=Ubuntu,a=xenial-updates,n=xenial,l=Ubuntu,c=universe,b=amd64 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/restricted i386 Packages release v=16.04,o=Ubuntu,a=xenial-updates,n=xenial,l=Ubuntu,c=restricted,b=i386 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages release v=16.04,o=Ubuntu,a=xenial-updates,n=xenial,l=Ubuntu,c=restricted,b=amd64 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages release v=16.04,o=Ubuntu,a=xenial-updates,n=xenial,l=Ubuntu,c=main,b=i386 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages release v=16.04,o=Ubuntu,a=xenial-updates,n=xenial,l=Ubuntu,c=main,b=amd64 origin de.archive.ubuntu.com 500 http://de.archive.ubuntu.com/ubuntu xenial/multiverse i386 Packages release v=16.04,o=Ubuntu,a=xenial,n=xenial,l=Ubuntu,c=multiverse,b=i386 origin de.archive.ubuntu.com 500
[Bug 1683037] Re: touchpad mouse not moves hoizontally in kubuntu 17.04.
Adding the file "/etx/X11/xorg.conf" like it was recommended in comment #5 solved the problem for me: Section "InputClass" Identifier "touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" EndSection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683037 Title: touchpad mouse not moves hoizontally in kubuntu 17.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1683037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683037] Re: touchpad mouse not moves hoizontally in kubuntu 17.04.
Same problem here with also with on a Lenovo ideapad 500S-13ISK. Horizontal movement stops after login - it works while still in gdm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683037 Title: touchpad mouse not moves hoizontally in kubuntu 17.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1683037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683830] [NEW] Missing geoip module in nginx-naxsi
Public bug reported: Contrary to the nginx-full package the nginx-naxsi package does not include the geoip module for unknown reasons. This makes it impossible to seamlessly switch over to nginx-naxsi if required. Seen in Ubuntu 14.04.5 LTS ** Affects: nginx (Ubuntu) Importance: Undecided Status: New ** Description changed: Contrary to the nginx-full package the nginx-naxsi package does not include the geoip module for unknown reasons. - This makes it impossible to seamlessly switch over to ngxin-naxsi if + This makes it impossible to seamlessly switch over to nginx-naxsi if required. Seen in Ubuntu 14.04.5 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683830 Title: Missing geoip module in nginx-naxsi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1683830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659257] [NEW] kde-info2html exits with error (perl compatibility problem) -> info browsing fails "Cannot Initiate the info Protocol"
Public bug reported: On can't browse info pages with konqueror on Ubuntu-Xenial. Issue is already known and fixed: https://bugs.kde.org/show_bug.cgi?id=359015 It seems the fix just haven't made it into Xenial yet (and this is perl, so it'll also affect other platforms and not just mine) Here is my version of the package: jacobi@Jacobis-G5:~$ apt-cache policy kde-runtime-data kde-runtime-data: Installiert: 4:15.12.3-0ubuntu1 Installationskandidat: 4:15.12.3-0ubuntu1 Versionstabelle: *** 4:15.12.3-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports xenial/universe powerpc Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: kde-runtime-data 4:15.12.3-0ubuntu1 [modified: usr/share/kde4/apps/kio_info/kde-info2html] ProcVersionSignature: Ubuntu 4.4.0-59.80-powerpc64-smp 4.4.35 Uname: Linux 4.4.0-59-powerpc64-smp ppc64 NonfreeKernelModules: openafs ApportVersion: 2.20.1-0ubuntu2.5 Architecture: powerpc CurrentDesktop: KDE Date: Wed Jan 25 11:46:44 2017 InstallationDate: Installed on 2016-08-05 (172 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: kde-runtime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kde-runtime (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659257 Title: kde-info2html exits with error (perl compatibility problem) -> info browsing fails "Cannot Initiate the info Protocol" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1659257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652322] [NEW] package cubemap 1.3.1-1build1 failed to install/upgrade: underproces installerede post-installation-script returnerede afslutningsstatus 1
Public bug reported: No user experience of erroneous behaviour ProblemType: Package DistroRelease: Ubuntu 16.10 Package: cubemap 1.3.1-1build1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 22 12:00:28 2016 ErrorMessage: underproces installerede post-installation-script returnerede afslutningsstatus 1 InstallationDate: Installed on 2016-11-27 (26 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: cubemap Title: package cubemap 1.3.1-1build1 failed to install/upgrade: underproces installerede post-installation-script returnerede afslutningsstatus 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cubemap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652322 Title: package cubemap 1.3.1-1build1 failed to install/upgrade: underproces installerede post-installation-script returnerede afslutningsstatus 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cubemap/+bug/1652322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628862] [NEW] RSS & "Accept-Language" header
Public bug reported:
Some RSS feeds evaluate the "Accept-Language" header of the request to
deliver the content in the correct language.
Unfortunately my German Thunderbird delivers the content in English.
I've tested the RSS-URL in Firefox and the content was German. I changed
the "Accept-Language" header with Tamper Data in Firefox to English and
the content switched to English.
I don't know a tool like Tamper Data for Thunderbird. So I can't check
the "Accept-Language" header directly. I also don't see a way to
configure this in Thunderbird.
This problem appears circa one year ago (not sure). So it worked in the
past.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: thunderbird 1:45.3.0+build1-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: holzmueller 1509 F pulseaudio
/dev/snd/controlC1: holzmueller 1509 F pulseaudio
BuildID: 20160916153542
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Sep 29 11:45:14 2016
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini
or extensions.sqlite)
InstallationDate: Installed on 2015-10-09 (355 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
IpRoute:
default via 10.20.20.1 dev eth0 proto static metric 100
10.20.20.0/24 dev eth0 proto kernel scope link src 10.20.20.72 metric 100
169.254.0.0/16 dev eth0 scope link metric 1000
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
Locales: extensions.sqlite corrupt or missing
Plugins:
Java(TM) Plug-in 11.66.2 - /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
/usr/share/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
/usr/share/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
Profiles: Profile0 (Default) - LastVersion=45.3.0/20160916153542 (In use)
RfKill:
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-04-26 (155 days ago)
dmi.bios.date: 04/14/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0XCR8D
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd04/14/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0XCR8D:rvrA03:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 9020
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628862
Title:
RSS & "Accept-Language" header
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1628862/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609419] Re: pstack is broken on amd64
Hello Thomas Preud'homme, were you able to look into this? Do you need anything else in order to analyze the issue? Best Carsten Hoffmann -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609419 Title: pstack is broken on amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pstack/+bug/1609419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609419] Re: pstack is broken on amd64
Hello Thomas, the binary I am originally trying to print the stack of is proprietary, so I cannot make it available to you. But I did try to print the pstack of an apache tomcat 8.0.26, the pstack is attached. The result looks different, but still not very helpful. (essentially the binary is java in this example) If you want me to run pstack on another binary, let me know, I could not think if a good multi threaded binary. ** Attachment added: "pstackApacheTomcat.txt" https://bugs.launchpad.net/ubuntu/+source/pstack/+bug/1609419/+attachment/4716503/+files/pstackApacheTomcat.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609419 Title: pstack is broken on amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pstack/+bug/1609419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532000] Re: no pstack for amd64
I have created a new bug, based on my experiences and the comments from Luca Clementi and Andrey: https://bugs.launchpad.net/ubuntu/+source/pstack/+bug/1609419 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/532000 Title: no pstack for amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pstack/+bug/532000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609419] [NEW] pstack is broken on amd64
Public bug reported: Using pstack 1.3.1-1 on Ubuntu 14.04.4 LTS leads to no usable results. It seems like this was already reported in a comment 2013 in the popular bug report (https://bugs.launchpad.net/ubuntu/+source/pstack/+bug/532000). I am absolutely not sure on what other information to provide, but I have attached the pstack results that I am getting for a Multi Thread application. ** Affects: pstack (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 ** Attachment added: "pstackDemo.txt" https://bugs.launchpad.net/bugs/1609419/+attachment/4713192/+files/pstackDemo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609419 Title: pstack is broken on amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pstack/+bug/1609419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607973] [NEW] Upgrade from 15.10 to 16.04 LTS is not possible
Public bug reported: when trying to upgrade to wily werewolf, I received the following error message: Ein unlösbares Problem trat beim Ermitteln der Systemaktualisierung auf. Dies kann verursacht worden sein durch: * Aktualisieren auf eine Vorabversion von Ubuntu * Verwendung der aktuellen Vorabversion von Ubuntu * Inoffizielle Softwarepakete, die nicht von Ubuntu bereitgestellt wurden I already uninstalled all packages I had installed, but still I receive this error message. Is there another way to upgrade to 16.04? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.4 ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Sat Jul 30 00:12:08 2016 InstallationDate: Installed on 2016-03-09 (142 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to wily on 2016-07-29 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607973 Title: Upgrade from 15.10 to 16.04 LTS is not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1607973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600581] [NEW] rhythmbox segfault when scanning files, on non-media file
Public bug reported: rhythmbox crashes with segfault every time shortly after startup since my upgrade from ubuntu 15.10 to 16.04. This is while importing media files. My music library is in ~/Musik, Musik is a soft link to a directory on an encrypted partition. ~/Musik is set in the preferences, yet rhythmbox still looks at my whole file system. The last file mentioned in the output of "rhythmbox -d >rb.out" is not always the same. It is however the same if I run rhythmbox several times in a row. It seems to be always outside of my music library. A few 1000 files are imported before the crash occurs. ## beginning + end of rb.out: (12:39:16) [0xf10b90] [rb_debug_init_match] rb-debug.c:240: Debugging enabled (12:39:16) [0xf10b90] [construct_db] rb-shell.c:454: creating database object (12:39:16) [0xf10b90] [impl_constructor] rb-ext-db.c:354: creating new metadata store instance album-art (12:39:16) [0xf10b90] [rb_shell_constructed] rb-shell.c:1693: Constructing shell (12:39:16) [0xf10b90] [construct_widgets] rb-shell.c:537: shell: initializing shell services (12:39:16) [0xf10b90] [impl_constructor] rb-ext-db.c:349: found existing metadata store album-art (12:39:16) [0xf10b90] [rb_podcast_manager_start_update_timer] rb-podcast-manager.c:591: last periodic update at 1468146098, interval 3600, time is now 1468147156 (12:39:16) [0xf10b90] [rb_podcast_manager_start_update_timer] rb-podcast-manager.c:598: next periodic update in 2542 seconds (12:39:16) [0xf10b90] [player_settings_changed_cb] rb-shell-player.c:923: track transition time changed (12:39:16) [0xf10b90] [player_settings_changed_cb] rb-shell-player.c:914: play order setting changed (12:39:16) [0xf10b90] [rb_shell_player_sync_buttons] rb-shell-player.c:1974: syncing with source (nil) (12:39:16) [0xf10b90] [rb_shell_player_sync_control_state] rb-shell-player.c:1468: syncing control state (12:39:16) [0xf10b90] [rb_shell_player_set_playing_source_internal] rb-shell-player.c:2055: setting playing source to (nil) (12:39:16) [0xf10b90] [rb_shell_player_sync_with_source] rb-shell-player.c:1882: playing source: (nil), active entry: (nil) (12:39:16) [0xf10b90] [rb_shell_player_sync_control_state] rb-shell-player.c:1468: syncing control state (12:39:16) [0xf10b90] [rb_display_page_model_add_page] rb-display-page-model.c:672: appending page Library with no parent (12:39:16) [0xf10b90] [rb_display_page_model_add_page] rb-display-page-model.c:672: appending page Stores with no parent (12:39:16) [0xf10b90] [rb_display_page_model_add_page] rb-display-page-model.c:672: appending page Playlists with no parent (12:39:16) [0xf10b90] [rb_display_page_model_add_page] rb-display-page-model.c:672: appending page Devices with no parent (12:39:16) [0xf10b90] [rb_display_page_model_add_page] rb-display-page-model.c:672: appending page Shared with no parent (12:39:16) [0xf10b90] [impl_constructor] rb-ext-db.c:349: found existing metadata store album-art (12:39:16) [0xf10b90] [rb_header_sync] rb-header.c:970: not playing (12:39:16) [0xf10b90] [rhythmdb_query_model_chain] rhythmdb-query-model.c:921: query model 0x13175f0 chaining to base model (nil) (12:39:16) [0xf10b90] [rhythmdb_query_model_chain] rhythmdb-query-model.c:921: query model 0x13176b0 chaining to base model (nil) (12:39:16) [0xf10b90] [rhythmdb_query_model_dispose] rhythmdb-query-model.c:731: disposing query model 0x13175f0 (12:39:16) [0xf10b90] [rhythmdb_query_model_finalize] rhythmdb-query-model.c:779: finalizing query model 0x13175f0 (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x13c7740 (title: , key: PlaylistTrack) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x13cea70 (title: Track, key: Track) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x13cece0 (title: Title, key: Title) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x13cef50 (title: Genre, key: Genre) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x14482a0 (title: Artist, key: Artist) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x1448510 (title: Composer, key: Composer) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x1448780 (title: Album, key: Album) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x1450a80 (title: Year, key: Year) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x1450cf0 (title: Time, key: Time) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom] rb-entry-view.c:1742: appending column: 0x1450f60 (title: Quality, key: Quality) (12:39:16) [0xf10b90] [rb_entry_view_insert_column_custom]
[Bug 521533]
Since I stumbled about this again: The following minor changes would increase usability of forms a lot since they make the behaviour of Okular more transparent. a) Add a menu entry "save form data" that makes Okular store the data in the file itself. b) When the user tries to close a filled in form without explicitly saving it: Warn the user that the form data is not stores in the file (but only cached somewhere else) and ask if she/he want's to save now. c) Always give precedence to data saved in the file itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/521533 Title: Okular stores form data in a different directory (possible leak of private data) To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/521533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521533]
(In reply to Yuri from comment #43) > (In reply to Carsten Gräser from comment #42) > > Yuri, this is not correct. Okular can in principle save the data to the pdf. > > But the interplay of this with saving to and loading from .kde/... is not > > very intuitive. > > What does it mean "can in principle"? Is the code saving it to the pdf there > or not there? If it is there, can you send the link (line numbers)? I gave a very detailed explanation of "in principle". just try out as described above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/521533 Title: Okular stores form data in a different directory (possible leak of private data) To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/521533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521533]
Yuri, this is not correct. Okular can in principle save the data to the pdf. But the interplay of this with saving to and loading from .kde/... is not very intuitive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/521533 Title: Okular stores form data in a different directory (possible leak of private data) To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/521533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535677] Re: Double-click does not work properly in low-level sub-directories.
I have a similar problem. I'm using a wacom intous pen and double clicking using the pen doesn't work in nautilus (it works in the mouse settings test and everywhere else). Using the touch mode of the tablet works, though (using a double tab), -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535677 Title: Double-click does not work properly in low-level sub-directories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1535677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521533]
I also stumbled about the fact that it seems to be impossible to have multiple instances of the same filled in form under the same file name and got the impression that "Save as..." does not work. After some experimenting I found out the problem with "Save as...": There's two places where form data is stored: .kde/* and the pdf-file itself. Data is always saved to .kde/* (attached to filename?). If you use "Save as" it's also stored to the file. The problem is that this is not visible to the user and that .kde/* seems to have precedence. If you want to fill the same form twice you can easily run into problems: Case a: Since form data is visible after closing, reopening, or moving the file, the user assumes that it's stored inside of the pdf. To fill a form a second time he copies the filled in form into a new location and changes the necessary data. Everything seems to work, but if he reopens the original file all it's data is changed to what he entered in the new place. Case b: The user is aware that data is stored in the file only if he used "Save as". After filling the form the first time he uses "Save as". To fill the form a second time he copies the filled in form into a new location and changes the necessary data and uses "Save as" again. Now different data is saved in both versions of the file. But if he opens version 1 again, he sees the changes he did in version 2. The reason for this is that by changing version 2, the data in .kde/* is changed and this seems to have precedence when viewing version 1. If you delete th corresponding file in .kde/* you see what's stored in the file. In both cases the user seems to have lost data. In a) this is true, in b) his data is just not visible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/521533 Title: Okular stores form data in a different directory (possible leak of private data) To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/521533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341944] Re: 32-Bit UEFI bootloader support needed
Faced the problem today on a cheap surfpad from TrekStor. It is the "TrekStor SurfTab wintron 7.0". I had to copy the right EFI loader from a debian stick to my ubuntu install stick. Wouldn't it be much easier, when Ubuntu would just provide both EFI loaders, which in turn use the same boot.cfg file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341944 Title: 32-Bit UEFI bootloader support needed To manage notifications about this bug go to: https://bugs.launchpad.net/debian-installer/+bug/1341944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450887] Re: Tooltip of nm-applet shows a part of the MATE-panel before text is displayed
My computers are really slow - a netbook with an older single-core Atom processor and a desktop PC with a socket A AMD Sempron 2600+, both with 1 GB RAM. With high CPU load the period before the tooltip correctly appears gets longer. So I guess the issue cant't be seen on a faster computer. Meanwhile I installed the MATE spin of Fedora 22 on the netbook (with GTK 3.16 and Mate 1.10). The issue is not present there. On the desktop PC, with compton and a slight tooltip fading it's nearly not noticeable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450887 Title: Tooltip of nm-applet shows a part of the MATE-panel before text is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1450887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483185] [NEW] package redmine 3.0~20140825-5 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported: the error occured within redmine after choosing the option not to configure the database part directly ProblemType: Package DistroRelease: Ubuntu 15.04 Package: redmine 3.0~20140825-5 ProcVersionSignature: Ubuntu 3.19.0-25.26-lowlatency 3.19.8-ckt2 Uname: Linux 3.19.0-25-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 Date: Mon Aug 10 11:28:47 2015 DuplicateSignature: package:redmine:3.0~20140825-5:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2015-05-02 (99 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: redmine Title: package redmine 3.0~20140825-5 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to vivid on 2015-05-03 (99 days ago) ** Affects: redmine (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483185 Title: package redmine 3.0~20140825-5 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1483185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)
I had the same problem when upgrading from 14.04 - 14.10 and then again from 14.10 - 15.04. My solution -which I found somewhere in the web- was the same both times: Simply delete(!) /etc/bluetooth/audio.conf (or rename it) and restart the bluetooth service. At least this worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181106 Title: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455872] Re: Optimize the drag drop positioning of windows
Hi, I'm not a member of the quality assurance team. I'm just a user. I've no intension to register me on all the bug tracking tools. So far I see, it's possible for the ubuntu team to reference bugs in other bug tracking systems (Example: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1455873). I would be very pleased if you do that also with this bug. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455872 Title: Optimize the drag drop positioning of windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1455872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455872] [NEW] Optimize the drag drop positioning of windows
Public bug reported: If I want to change the positions of direct neighbor windows, than I have do drop the dragged window behind the middle of the target. By direct neighbors I think it's a better usability to allow switching windows independent from the drop position. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xfce4-panel 4.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Sun May 17 10:36:21 2015 InstallationDate: Installed on 2012-10-23 (935 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-panel UpgradeStatus: Upgraded to vivid on 2015-04-30 (16 days ago) ** Affects: xfce4-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455872 Title: Optimize the drag drop positioning of windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1455872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
