[Touch-packages] [Bug 1988870] Re: apport-autoreport.service fails: whoopsie.path is not enabled
reopening as per comment #8. @Sebastian, I suggest you disable whoopsie-path instead "systemctl disable whoopsie-path" and then reboot to get a clean "systemctl --failed" for those who are like me looking for the "Privacy" GUI control panel mentioned in comment #5, make sure you have the "activity-log-manager" package installed ** Changed in: apport (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1988870 Title: apport-autoreport.service fails: whoopsie.path is not enabled Status in apport package in Ubuntu: Confirmed Bug description: This is what the service reports. Aside from crash reports no longer uploading automatically, I'm having trouble pointing ubuntu-bug to crash reports in /var/crash - a window opens, but then a browser never opens. ubuntu-bug program-name does open the browser though. × apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static) Active: failed (Result: exit-code) since Tue 2022-09-06 14:27:48 EDT; 2min 33s ago TriggeredBy: ● apport-autoreport.path ● apport-autoreport.timer Process: 24994 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 (code=exited, status=1/FAILURE) Main PID: 24994 (code=exited, status=1/FAILURE) CPU: 115ms Sep 06 14:27:48 mbp113 systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 06 14:27:48 mbp113 whoopsie-upload-all[24994]: ERROR: whoopsie.path is not enabled Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. Sep 06 14:27:48 mbp113 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.23.0-0ubuntu1 Uname: Linux 6.0.0-rc4 x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportLog: ERROR: apport (pid 20795) Tue Sep 6 14:26:35 2022: called for pid 3732, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 20795) Tue Sep 6 14:26:35 2022: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 20795) Tue Sep 6 14:26:36 2022: debug: session gdbus call: (true,) ERROR: apport (pid 20795) Tue Sep 6 14:26:46 2022: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:123:43075180:2022-09-06 14:26:45.388720512 -0400:2022-09-06 14:27:48.608538333 -0400:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:123:8681261:2022-08-29 22:32:29.231918756 -0400:2022-08-29 20:57:41.939131333 -0400:/var/crash/_usr_libexec_goa-daemon.1000.crash 640:1000:123:44557691:2022-08-30 08:01:54.998418753 -0400:2022-08-30 08:01:50.202489325 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 14:29:03 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1988870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1205394] Re: distupgrade fails in saucy because whoopsie-preferences _0.8_amd64.deb is trying to overwrite '/usr/bin/whoopsie-preferences', which is also in package activity-log-
Is still an issue in 2024? ** Changed in: whoopsie-preferences (Ubuntu) Assignee: Evan (ev) => (unassigned) ** Changed in: whoopsie-preferences (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie-preferences in Ubuntu. https://bugs.launchpad.net/bugs/1205394 Title: distupgrade fails in saucy because whoopsie-preferences _0.8_amd64.deb is trying to overwrite '/usr/bin/whoopsie-preferences', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu6.1 Status in whoopsie-preferences package in Ubuntu: Incomplete Bug description: Description: distupgrade fails in saucy because whoopsie-preferences _0.8_amd64.deb is trying to overwrite '/usr/bin/whoopsie-preferences', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu6.1 Steps: 1. install iso from 6/27 2. do apt-get dist-upgrade expected results: dist-upgrade passes actual results: dist-upgrade fails logs: ... Selecting previously unselected package whoopsie-preferences. Unpacking whoopsie-preferences (from .../whoopsie-preferences_0.8_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/whoopsie-preferences_0.8_amd64.deb (--unpack): trying to overwrite '/usr/bin/whoopsie-preferences', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu6.1 Preparing to replace activity-log-manager-control-center 0.9.4-0ubuntu6.1 (using .../activity-log-manager-control-center_0.9.7-0ubuntu4_all.deb) ... Unpacking replacement activity-log-manager-control-center ... Processing triggers for ureadahead ... Processing triggers for man-db ... debconf: unable to initialize frontend: Dialog debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype Processing triggers for doc-base ... Processing 1 changed doc-base file... Processing triggers for gconf2 ... Processing triggers for gnome-menus ... Processing triggers for desktop-file-utils ... Processing triggers for mime-support ... Errors were encountered while processing: /var/cache/apt/archives/whoopsie-preferences_0.8_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1205394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
@lolo, comment #19 applies to you as well ** Changed in: sudo (Ubuntu Xenial) Assignee: lolo (lolo2020) => (unassigned) ** Changed in: sudo (Ubuntu Bionic) Assignee: lolo (lolo2020) => (unassigned) ** Changed in: sudo (Ubuntu Xenial) Status: In Progress => Invalid ** Changed in: sudo (Ubuntu Bionic) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in Release Notes for Ubuntu: Incomplete Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: Invalid Status in sudo source package in Bionic: Invalid Status in sudo source package in Cosmic: Won't Fix Status in sudo source package in Disco: Won't Fix Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
@mhodson: why did you remove six from this ticket? The affect I described is very much present for python3-six. readding six task @racb: thank you for having a thorough look. you are spot on in #10, the problem is present only focal2jammy, not impish2jammy. Thus, one possibility to deal with this situation is instead of completely dropping the breaks is to erlax them to exclude the python version from focal. Let me know if this is preferrable and I'll happily provide a debdiff. ** Also affects: six (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Incomplete Status in six package in Ubuntu: New Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 346912] Re: Tracker index corruption (was Tracker does not stop indexing)
is this still a problem in focal or later? ** Changed in: tracker (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/346912 Title: Tracker index corruption (was Tracker does not stop indexing) Status in Tracker: Expired Status in tracker package in Ubuntu: Incomplete Status in tracker source package in Jaunty: Won't Fix Bug description: I recently realized that tracker does not always give me the search results I expected, meaning that it does not find documents containing certain words. A quick look through the indexer preferences, I doubled the "maximal amount of text to index" and "maximum number of unique words to index". After doing so, the tracker does not stop indexing. The information message when I hover over the tracker icons says: Tracker: Indexing Done: 883 of 22296 Estimated: 33 minutes ... Elapsed: 01 minute ... This message hasn't changed for about a day, and the indexing continues. One of my log files is continuously flooded with the following messages: nasko@serre:~/.local/share/tracker$ tail -n20 tracker-indexer.log 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'previous': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'troubl': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'preprocessor': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'ac_abs_top_builddir': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'detail': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'call': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'paramet': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'offshoot': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'with_gcc': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'honor': with fatal error I would like to have tracker index my files more fully, and yet have it do that in a normal manner. Is there a way to prevent this problem? To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/346912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 352441] Re: file index is too big - discontinuing index
closing as per #8 ** Changed in: tracker (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/352441 Title: file index is too big - discontinuing index Status in Tracker: Fix Committed Status in tracker package in Ubuntu: Fix Released Bug description: Binary package hint: tracker Tracker started behaving strangely, not returning full results, etc. So I killed it and ran from the command line. Here's what I get file index is too big - discontinuing index I restarted Tracker using verbose 3 and have attached details. Here's some more below: Index stats Files: 55514 Folders: 5699 Documents: 3455 Images: 19839 Music: 2524 Videos: 1714 Text: 5486 Development: 5323 Other: 11474 Notable lines from attached file: Opening index /home/paul/.cache/tracker/file-index.db Bucket count (max is 524288) is 589811 and Record Count is 373234 Opening index /home/paul/.cache/tracker/file-update-index.db Bucket count (max is 524288) is 589811 and Record Count is 16605 Opening index /home/paul/.cache/tracker/email-index.db Bucket count (max is 524288) is 589811 and Record Count is 0 Where are the settings for the max bucket count above? Also, are they set at this limit for a reason and have I genuinely gone above the max, or is that the bug? A reindex may solve, but I feel like this problem will likely reoccur. So maybe a more permanent solution is needed. Ubuntu 8.10. Up to date as of today. Installed: 0.6.6-1ubuntu5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/352441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 132448] Re: search-tool: deleted files are counted in filetype count
I'm not able to reproduce this in jammy still an issue? ** Changed in: tracker (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/132448 Title: search-tool: deleted files are counted in filetype count Status in tracker package in Ubuntu: Incomplete Bug description: Binary package hint: tracker Steps to reproduce: - create a file - search for this file - delete this file - search again for this file and notice that the file is not shown in the result window, but it is counted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/132448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 158665] Re: tracker-extract manpage should be improved
essentially unchanged for jammy: "man tracker3-extract " ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/158665 Title: tracker-extract manpage should be improved Status in tracker package in Ubuntu: Triaged Bug description: The tracker-extract(1) manpage actually says: SYNOPSYS tracker-extract file That's actually wrong. It should say something like: tracker-extract /path/to/file mimetype To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/158665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 130937] Re: tracker-search-tool gets no response
Is this still a problem in focal or later? ** Changed in: tracker (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/130937 Title: tracker-search-tool gets no response Status in tracker package in Ubuntu: Incomplete Bug description: Binary package hint: tracker Trackerd is still indexing my drive. I started tracker-search-tool and performed a search. It provided a number of results. Clicking on the emails and text categories worked, but when I clicked on "All Files" I got the following in the console: META_TILE_ERROR : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. META_TILE_ERROR : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ** (tracker-search-tool:26050): CRITICAL **: set_snippet: assertion `error == NULL' failed and a dialogue box saying Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/130937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 346575] Re: tracker-extract crashed with SIGSEGV in g_utf8_validate()
still an issue in focal or later? ** Changed in: tracker (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/346575 Title: tracker-extract crashed with SIGSEGV in g_utf8_validate() Status in tracker package in Ubuntu: Incomplete Bug description: Binary package hint: tracker same bug title reported fixed, but this is jaunty post-alpha6 so we can't handle utf8, or apparently 90% of my documents or media without crashing. google desktop is sadly much more reliable. ProblemType: Crash Architecture: amd64 CrashCounter: 1 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-extract Package: tracker 0.6.91-1ubuntu1 ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 Signal: 11 SourcePackage: tracker StacktraceTop: g_utf8_validate () from /usr/lib/libglib-2.0.so.0 tracker_escape_metadata () ?? () ?? () tracker_extract_get_metadata () Title: tracker-extract crashed with SIGSEGV in g_utf8_validate() Uname: Linux 2.6.28-11-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/346575/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 351334] Re: tracker-indexer crashed with SIGSEGV in IA__g_utf8_validate()
closing as per #5 and #6 ** Changed in: tracker (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/351334 Title: tracker-indexer crashed with SIGSEGV in IA__g_utf8_validate() Status in Tracker: Fix Committed Status in tracker package in Ubuntu: Fix Released Bug description: Binary package hint: tracker Using the intrepid beta release. ProblemType: Crash Architecture: i386 CrashCounter: 1 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-indexer NonfreeKernelModules: nvidia Package: tracker 0.6.91-1ubuntu1 ProcCmdline: /usr/lib/tracker/tracker-indexer ProcEnviron: SHELL=/bin/tcsh PATH=(custom, no user) LANG=fr_CA.UTF-8 Signal: 11 SourcePackage: tracker StacktraceTop: IA__g_utf8_validate (str=0x0, max_len=-1, end=0x0) strdup_len (string=0x0, len=-1, bytes_written=0x0, IA__g_filename_to_utf8 (opsysstring=0x0, len=-1, tracker_module_metadata_utils_get_data () ?? () Title: tracker-indexer crashed with SIGSEGV in IA__g_utf8_validate() Uname: Linux 2.6.28-11-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/351334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528416] Re: With Trash bookmarked, gedit deadlocks on opening Open or Save As dialog
ping @jmmorlan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1528416 Title: With Trash bookmarked, gedit deadlocks on opening Open or Save As dialog Status in Ubuntu GNOME: New Status in tracker package in Ubuntu: Incomplete Bug description: On Ubuntu 15.10, gedit randomly (about half the time) hangs when either the Open or the Save As dialog is opened. The cause appears to be a deadlock: Thread 1 is in a GCancellable::cancelled signal handler, and indirectly calls g_dbus_connection_signal_subscribe which tries to acquire a GDBusConnection's mutex Thread 3 is in on_worker_message_received, which holds the GDBusConnection's mutex and indirectly calls g_cancellable_disconnect which waits for the GCancellable's signal handler to complete. Thread 1 (Thread 0x77f27a00 (LWP 10630)): #0 0x748c45a9 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7514102c in g_mutex_lock_slowpath (mutex=mutex@entry=0x6e55a8) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gthread-posix.c:1315 #2 0x75141872 in g_mutex_lock (mutex=mutex@entry=0x6e55a8) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gthread-posix.c:1339 #3 0x7591cdb9 in g_dbus_connection_signal_subscribe (connection=0x6e5590 [GDBusConnection], sender=0x0, interface_name=interface_name@entry=0x75969d10 "org.freedesktop.DBus.Properties", member=member@entry=0x759681f0 "PropertiesChanged", object_path=0xd7a210 "/org/gtk/vfs/Daemon", arg0=0xc09880 "org.gtk.vfs.Daemon", flags=G_DBUS_SIGNAL_FLAGS_NONE, callback=0x75925da0 , user_data=0x8be350, user_data_free_func=0x75925cf0 ) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gdbusconnection.c:3445 #4 0x759263c2 in async_initable_init_first (initable=initable@entry=0x7fffd4010780) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gdbusproxy.c:1740 #5 0x75927238 in async_initable_init_async (initable=0x7fffd4010780, io_priority=0, cancellable=0x0, callback=, user_data=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gdbusproxy.c:1862 #6 0x7587fb51 in g_async_initable_new_valist_async (object_type=, first_property_name=0x7fffe8c83b40 "g-flags", var_args=0x7fffd360, io_priority=0, cancellable=0x0, callback=0x7fffe8eb0780 , user_data=0x2) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gasyncinitable.c:426 #7 0x7587fc08 in g_async_initable_new_async (object_type=, io_priority=io_priority@entry=0, cancellable=cancellable@entry=0x0, callback=callback@entry=0x7fffe8eb0780 , user_data=user_data@entry=0x2, first_property_name=first_property_name@entry=0x7fffe8c83b40 "g-flags") at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gasyncinitable.c:339 #8 0x7fffe8c74df8 in gvfs_dbus_daemon_proxy_new (connection=0x6e5590 [GDBusConnection], flags=flags@entry=G_DBUS_PROXY_FLAGS_NONE, name=name@entry=0x0, object_path=object_path@entry=0x7fffe8ebbb95 "/org/gtk/vfs/Daemon", cancellable=cancellable@entry=0x0, callback=callback@entry=0x7fffe8eb0780 , user_data=0x2) at gvfsdbus.c:1201 #9 0x7fffe8eb0528 in async_call_cancelled_cb (cancellable=, _data=) at gvfsdaemondbus.c:376 #13 0x753ed12f in (instance=instance@entry=0xd57450, signal_id=, detail=detail@entry=0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gsignal.c:3439 #10 0x753d2015 in g_closure_invoke (closure=0xd792f0, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0x7fffd6b0, invocation_hint=invocation_hint@entry=0x7fffd630) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gclosure.c:801 #11 0x753e4061 in signal_emit_unlocked_R (node=node@entry=0x6efa40, detail=detail@entry=0, instance=instance@entry=0xd57450, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd6b0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gsignal.c:3627 #12 0x753ecdfc in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffd860) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gsignal.c:3383 #14 0x758833b8 in g_cancellable_cancel (cancellable=0xd57450 [GCancellable]) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gcancellable.c:508 #15 0x76fe6ba4 in update_places (sidebar=0xd92460 [GtkPlacesSidebar]) at /build/gtk+3.0-pIzeMy/gtk+3.0-3.16.7/./gtk/gtkplacessidebar.c:941 #16 0x753d2244 in _g_closure_invoke_va (closure=closure@entry=0xa9c9d0, return_value=return_value@entry=0x0, instance=instance@entry=0xce7690, args=args@entry=0x7fffdc80, n_params=, param_types=0x0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gclosure.c:864 #17 0x753eca46 in g_signal_emit_valist (instance=0xce7690, signal_id=, detail=0,
[Touch-packages] [Bug 339027] Re: tracker-extract crashed with signal 7 in tracker_extract_get_metadata()
closing as obsolete, please open a new ticket if this can be reproduced in focal or later ** Changed in: tracker (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/339027 Title: tracker-extract crashed with signal 7 in tracker_extract_get_metadata() Status in tracker package in Ubuntu: Invalid Bug description: Binary package hint: tracker I think it was when I pulled a USB key out (after unmounting) ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-extract NonfreeKernelModules: nvidia Package: tracker 0.6.90-1ubuntu2 ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 Signal: 7 SourcePackage: tracker StacktraceTop: ?? () ?? () tracker_extract_get_metadata () ?? () from /usr/lib/libdbus-glib-1.so.2 ?? () from /lib/libdbus-1.so.3 Title: tracker-extract crashed with signal 7 in tracker_extract_get_metadata() Uname: Linux 2.6.28-8-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/339027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 355499] Re: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data()
@funkyhat, do you still experience this issue in focal or later or can this be closed? ** Changed in: tracker (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/355499 Title: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() Status in tracker package in Ubuntu: Incomplete Bug description: Binary package hint: tracker Description: Ubuntu jaunty (development branch) Release: 9.04 tracker: Installiert: 0.6.92-1ubuntu1 Kandidat: 0.6.92-1ubuntu1 Versions-Tabelle: *** 0.6.92-1ubuntu1 0 500 http://archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-indexer Package: tracker 0.6.92-1ubuntu1 ProcCmdline: /usr/lib/tracker/tracker-indexer ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 Signal: 11 SourcePackage: tracker StacktraceTop: tracker_module_metadata_utils_get_data () ?? () tracker_module_file_get_metadata () ?? () ?? () Title: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() Uname: Linux 2.6.28-11-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev pulse-rt sambashare scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/355499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 359886] Re: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data()
*** This bug is a duplicate of bug 355499 *** https://bugs.launchpad.net/bugs/355499 ** This bug has been marked a duplicate of bug 355499 tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/359886 Title: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() Status in tracker package in Ubuntu: Triaged Bug description: Binary package hint: tracker Tracker crashed while using emacs & auctex. ProblemType: Crash Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-indexer Package: tracker 0.6.92-1ubuntu2 ProcCmdline: /usr/lib/tracker/tracker-indexer ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_US.UTF-8:en LANG=en_US.UTF-8 Signal: 11 SourcePackage: tracker StacktraceTop: tracker_module_metadata_utils_get_data () tracker_module_file_get_metadata () ?? () ?? () g_main_context_dispatch () Title: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() Uname: Linux 2.6.28-11-generic x86_64 UserGroups: adm admin audio cdrom dialout dip floppy libvirtd lpadmin netdev plugdev powerdev sambashare scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/359886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 360167] Re: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data()
*** This bug is a duplicate of bug 355499 *** https://bugs.launchpad.net/bugs/355499 ** This bug is no longer a duplicate of bug 359886 tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() ** This bug has been marked a duplicate of bug 355499 tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/360167 Title: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() Status in tracker package in Ubuntu: New Bug description: Binary package hint: tracker Tracker crashed while using emacs & auctex. ProblemType: Crash Architecture: amd64 CrashCounter: 1 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-indexer Package: tracker 0.6.92-1ubuntu2 ProcCmdline: /usr/lib/tracker/tracker-indexer ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_US.UTF-8:en LANG=en_US.UTF-8 Signal: 11 SourcePackage: tracker StacktraceTop: tracker_module_metadata_utils_get_data () tracker_module_file_get_metadata () ?? () ?? () g_main_context_dispatch () Title: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() Uname: Linux 2.6.28-11-generic x86_64 UserGroups: adm admin audio cdrom dialout dip floppy libvirtd lpadmin netdev plugdev powerdev sambashare scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/360167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 361598] Re: tracker-extract crashed with SIGSEGV in tracker_albumart_copy_to_local()
does this ever occur in focal or later? ** Changed in: tracker (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/361598 Title: tracker-extract crashed with SIGSEGV in tracker_albumart_copy_to_local() Status in tracker package in Ubuntu: Incomplete Bug description: Binary package hint: tracker Tracker crashed on indexing. ProblemType: Crash Architecture: amd64 CrashCounter: 1 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-extract NonfreeKernelModules: nvidia Package: tracker 0.6.93-0ubuntu1 ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 Signal: 11 SourcePackage: tracker StacktraceTop: tracker_albumart_copy_to_local () tracker_process_albumart () ?? () ?? () tracker_extract_get_metadata () Title: tracker-extract crashed with SIGSEGV in tracker_albumart_copy_to_local() Uname: Linux 2.6.28-11-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev pulse pulse-access pulse-rt sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/361598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598814] Re: tracker-miner-fs syslog spam: Could not execute sparql
** Tags added: focal xenial zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1598814 Title: tracker-miner-fs syslog spam: Could not execute sparql Status in tracker package in Ubuntu: Confirmed Bug description: I noticed tracker-miner-fs spamming syslog on every reboot. Because there are too many messages i created a github gist at https://gist.github.com/CrazyLemon/14a54c58efcd0839a4e990a49da9b303 As you can see thats a lot of messages. I'm on Ubuntu 16.04 with latest updates. ii tracker-miner-fs 1.6.2-0ubuntu1amd64 metadata database, indexer and search tool - filesystem indexer This kind of syslog spamming has been happening at least since june 27th '16. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1598814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1126537] Re: gnome-Tracker fills up my root with 27GB after kernel update
Yeah, unfortunately, that tracker thing is a pretty badly behaved piece of software. Did you ever run into in focal or later? ** Changed in: tracker (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1126537 Title: gnome-Tracker fills up my root with 27GB after kernel update Status in tracker package in Ubuntu: Incomplete Bug description: Top shows 814:44.76 tracker-miner-f process now been running for 800 mins. after software-update installed a new kernal. This is the second time this has happened. This is poorly documented software, no description of the metadata anywhere or any justification for why this softare runs or is needed. For all I know it could e malicious. I do not like any software that keeps my disk continually busy for three days without expaination. I am going to find the line in the init scripts that kicks this off and comment it out. $ ubuntu_release LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux brucesalem-FQ582AA-ABA-SR5710F 3.0.0-31-generic #48-Ubuntu SMP Mon Feb 4 13:25:59 UTC 2013 i686 athlon i386 GNU/Linux I challenge anyone to explain why this process should be running. I am ssurely tempted to hange my window manager and possibly dump Ubuntu and not use Gnome on any other Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1126537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 336422] Re: [jaunty] tracker-extract prevents unmounting of USB storage devices, crashed with signal 7 in tracker_extract_get_metadata() when media forcibly removed
Is this still reproducible in focal or later? ** Changed in: tracker (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/336422 Title: [jaunty] tracker-extract prevents unmounting of USB storage devices, crashed with signal 7 in tracker_extract_get_metadata() when media forcibly removed Status in tracker package in Ubuntu: Incomplete Bug description: Binary package hint: tracker tracker-extract is being run against the files on removable storage, preventing timely removal of storage devices. When the devices are removed without unmounting, tracker-extract crashes. ProblemType: Crash Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-extract NonfreeKernelModules: nvidia Package: tracker 0.6.90-1ubuntu2 ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_AU.UTF-8 Signal: 7 SourcePackage: tracker StacktraceTop: ?? () ?? () ?? () tracker_extract_get_metadata () ?? () from /usr/lib/libdbus-glib-1.so.2 Title: tracker-extract crashed with signal 7 in tracker_extract_get_metadata() Uname: Linux 2.6.28-8-generic x86_64 UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare scanner vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/336422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 353008] Re: tracker indexes all the time even though only "one" folder with "one" file configured for indexing
@mandoz18, please open a new ticket if you still experience this issue in focal or later @grider-4, yours is a different issue, please open a new ticket or tag onto one of the existing "high CPU"-tickets -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/353008 Title: tracker indexes all the time even though only "one" folder with "one" file configured for indexing Status in Tracker: Fix Committed Status in tracker package in Ubuntu: Fix Released Bug description: Binary package hint: tracker I only have enabled one folder for indexing, which only contains one file. Still tracker is always indexing. Please fix this if tracker wants to become anything useful. My config: [General] # Log Verbosity - Valid values are 0 (displays/logs only errors), 1 (minimal), 2 (detailed), and 3 (debug) Verbosity=0 # Set the initial sleeping time, in seconds InitialSleep=45 # Minimizes the use of memory but may slow indexing down LowMemoryMode=false # Set to TRUE when the home directory is in a NFS filesystem NFSLocking=false [Watches] # List of directory roots to index and watch seperated by semicolons WatchDirectoryRoots=/home/asac/test; # List of directory roots to index but not watch (no live updates but are refreshed when trackerd is next restarted) seperated by semicolons CrawlDirectory= # List of directory roots to not index and not watch seperated by semicolons NoWatchDirectory= # Set to false to prevent watching of any kind EnableWatching=true [Indexing] # Throttles the indexing process. Allowable values are 0-20. higher values decrease indexing speed Throttle=0 # Disables the indexing process EnableIndexing=true # Enables indexing of a file's text contents EnableFileContentIndexing=true # Enables generation of thumbnails EnableThumbnails=true # List of partial file patterns (glob) seperated by semicolons that specify files to not index (basic stat info is only indexed for files that match these patterns) NoIndexFileTypes= # Sets minimum length of words to index MinWordLength=3 # Sets maximum length of words to index (words are cropped if bigger than this) MaxWordLength=30 # Sets the language specific stemmer and stopword list to use # Valid values are 'en' (english), 'da' (danish), 'nl' (dutch), 'fi' (finnish), 'fr' (french), 'de' (german), 'it' (italien), 'nb' (norwegian), 'pt' (portugese), 'ru' (russian), 'es' (spanish), 'sv' (swedish) Language=en # Enables use of language-specific stemmer EnableStemmer=true # List of disabled modules (separator=;) # The modules that are indexed are kept in $prefix/lib/tracker/indexer-modules DisabledModules= # Set to false to NOT hog the disk for extended periods FastMerges=false # Set the minimum length of words to index (0->30, default=3) MinWorldLength=3 # Set the maximum length of words to index (0->200, default=30) MaxWorldLength=30 # Set to true to disable indexing when running on battery BatteryIndex=true # Set to true to disable initial indexing when running on battery BatteryIndexInitial=false # Pause indexer when disk space is <= this value # (0->100, value is in % of $HOME file system, -1=disable pausing) LowDiskSpaceLimit=1 # Set to true to enable traversing mounted directories on other file systems # (this excludes removable devices) IndexMountedDirectories=false # Set to true to enable traversing mounted directories for removable devices IndexRemovableMedia=true [Emails] IndexEvolutionEmails=true [Performance] # Maximum size of text in bytes to index from a file's text contents MaxTextToIndex=1048576 # Maximum number of unique words to index from a file's text contents MaxWordsToIndex=1 # Specifies the no of entities to index before determining whether to perform index optimization OptimizationSweepCount=1 # Sets the maximum bucket count for the indexer MaxBucketCount=524288 # Sets the minimum bucket count MinBucketCount=65536 # Sets no. of divisions of the index file Dvisions=4 # Selects the desired ratio of used records to buckets to be used when optimizing index (should be a value between 0 and 4) BucketRatio=1 # Alters how much padding is used to prevent index relocations. Higher values improve indexing speed but waste more disk space. Value should be in range (1..8) Padding=2 To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/353008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 353008] Re: tracker indexes all the time even though only "one" folder with "one" file configured for indexing
going by #4, this was fixed in 0.7.0 ** Changed in: tracker (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/353008 Title: tracker indexes all the time even though only "one" folder with "one" file configured for indexing Status in Tracker: Fix Committed Status in tracker package in Ubuntu: Fix Released Bug description: Binary package hint: tracker I only have enabled one folder for indexing, which only contains one file. Still tracker is always indexing. Please fix this if tracker wants to become anything useful. My config: [General] # Log Verbosity - Valid values are 0 (displays/logs only errors), 1 (minimal), 2 (detailed), and 3 (debug) Verbosity=0 # Set the initial sleeping time, in seconds InitialSleep=45 # Minimizes the use of memory but may slow indexing down LowMemoryMode=false # Set to TRUE when the home directory is in a NFS filesystem NFSLocking=false [Watches] # List of directory roots to index and watch seperated by semicolons WatchDirectoryRoots=/home/asac/test; # List of directory roots to index but not watch (no live updates but are refreshed when trackerd is next restarted) seperated by semicolons CrawlDirectory= # List of directory roots to not index and not watch seperated by semicolons NoWatchDirectory= # Set to false to prevent watching of any kind EnableWatching=true [Indexing] # Throttles the indexing process. Allowable values are 0-20. higher values decrease indexing speed Throttle=0 # Disables the indexing process EnableIndexing=true # Enables indexing of a file's text contents EnableFileContentIndexing=true # Enables generation of thumbnails EnableThumbnails=true # List of partial file patterns (glob) seperated by semicolons that specify files to not index (basic stat info is only indexed for files that match these patterns) NoIndexFileTypes= # Sets minimum length of words to index MinWordLength=3 # Sets maximum length of words to index (words are cropped if bigger than this) MaxWordLength=30 # Sets the language specific stemmer and stopword list to use # Valid values are 'en' (english), 'da' (danish), 'nl' (dutch), 'fi' (finnish), 'fr' (french), 'de' (german), 'it' (italien), 'nb' (norwegian), 'pt' (portugese), 'ru' (russian), 'es' (spanish), 'sv' (swedish) Language=en # Enables use of language-specific stemmer EnableStemmer=true # List of disabled modules (separator=;) # The modules that are indexed are kept in $prefix/lib/tracker/indexer-modules DisabledModules= # Set to false to NOT hog the disk for extended periods FastMerges=false # Set the minimum length of words to index (0->30, default=3) MinWorldLength=3 # Set the maximum length of words to index (0->200, default=30) MaxWorldLength=30 # Set to true to disable indexing when running on battery BatteryIndex=true # Set to true to disable initial indexing when running on battery BatteryIndexInitial=false # Pause indexer when disk space is <= this value # (0->100, value is in % of $HOME file system, -1=disable pausing) LowDiskSpaceLimit=1 # Set to true to enable traversing mounted directories on other file systems # (this excludes removable devices) IndexMountedDirectories=false # Set to true to enable traversing mounted directories for removable devices IndexRemovableMedia=true [Emails] IndexEvolutionEmails=true [Performance] # Maximum size of text in bytes to index from a file's text contents MaxTextToIndex=1048576 # Maximum number of unique words to index from a file's text contents MaxWordsToIndex=1 # Specifies the no of entities to index before determining whether to perform index optimization OptimizationSweepCount=1 # Sets the maximum bucket count for the indexer MaxBucketCount=524288 # Sets the minimum bucket count MinBucketCount=65536 # Sets no. of divisions of the index file Dvisions=4 # Selects the desired ratio of used records to buckets to be used when optimizing index (should be a value between 0 and 4) BucketRatio=1 # Alters how much padding is used to prevent index relocations. Higher values improve indexing speed but waste more disk space. Value should be in range (1..8) Padding=2 To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/353008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 163544] Re: tracker search tool shows no results
Is this still an issue in focal or later? "tracker3 search png" works fine for me on jammy ** Changed in: tracker (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/163544 Title: tracker search tool shows no results Status in tracker package in Ubuntu: Incomplete Bug description: See the attached screenshots. Same with any query string. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/163544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525628] Re: tracker needs to be killed on every boot
I see this in high CPU usage after going from Focal (where I did not see it) to Jammy (where it consumes about 2 to 3 cores) ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1525628 Title: tracker needs to be killed on every boot Status in tracker package in Ubuntu: Confirmed Bug description: At every boot, tacker-miner-fs and tracker-extract uses all of the processor and needs to be killed manually for computer to work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker 1.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 13 13:02:58 2015 InstallationDate: Installed on 2015-04-24 (232 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1525628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
** Changed in: six (Ubuntu) Status: New => Confirmed ** Patch added: "debdiff for six in jammy" https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+attachment/5560382/+files/LP1958720.six.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Confirmed Status in six package in Ubuntu: Confirmed Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
** Changed in: six (Ubuntu) Status: Invalid => Confirmed ** Changed in: six (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Confirmed Status in six package in Ubuntu: New Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
OK, so it's an obsolete package. I don't see a reason here to intentionally break it. As far as I can see it continues to work just fine as an obsolete package in jammy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Confirmed Status in six package in Ubuntu: Invalid Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
** Changed in: pyyaml (Ubuntu) Assignee: Rolf Leggewie (r0lf) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: In Progress Status in six package in Ubuntu: New Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 725709] Re: package language-pack-en-base 1:10.04 20100714 failed to install/upgrade: unable to create `/var/lib/locales/supported.d/en.dpkg-new' (while processing `./var/lib/loc
Yes, I am aware of the age. I still felt it courteous to give you a chance to keep the ticket open if you so desired. No need for the aggressive tone, really. ** Changed in: language-pack-en-base (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/725709 Title: package language-pack-en-base 1:10.04 20100714 failed to install/upgrade: unable to create `/var/lib/locales/supported.d/en.dpkg-new' (while processing `./var/lib/locales/supported.d/en'): Invalid argument Status in language-pack-en-base package in Ubuntu: Invalid Bug description: Binary package hint: language-pack-en-base during update ProblemType: Package DistroRelease: Ubuntu 10.04 Package: language-pack-en-base 1:10.04+20100714 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 Architecture: i386 Date: Sat Feb 26 20:09:32 2011 DpkgTerminalLog: ErrorMessage: unable to create `/var/lib/locales/supported.d/en.dpkg-new' (while processing `./var/lib/locales/supported.d/en'): Invalid argument InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) PackageArchitecture: all SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:10.04+20100714 failed to install/upgrade: unable to create `/var/lib/locales/supported.d/en.dpkg-new' (while processing `./var/lib/locales/supported.d/en'): Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/725709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 648652] Re: package language-pack-en-base 1:10.04 20100421 failed to install/upgrade: ErrorMessage: paquets en conflit - language-pack-en-base non installé
do you have a way to reproduce this issue? does it ever occur in focal or later? Francais OK ** Changed in: language-pack-en-base (Ubuntu) Status: New => Incomplete ** Changed in: language-pack-en-base (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/648652 Title: package language-pack-en-base 1:10.04 20100421 failed to install/upgrade: ErrorMessage: paquets en conflit - language-pack-en- base non installé Status in language-pack-en-base package in Ubuntu: Incomplete Bug description: Binary package hint: language-pack-en-base no english spoken !! sorry ProblemType: Package DistroRelease: Ubuntu 10.04 Package: language-pack-en-base 1:10.04+20100421 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Mon Sep 27 11:13:21 2010 ErrorMessage: ErrorMessage: paquets en conflit - language-pack-en-base non installé InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) PackageArchitecture: all SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:10.04+20100421 failed to install/upgrade: ErrorMessage: paquets en conflit - language-pack-en-base non installé To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/648652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 662209] Re: package language-pack-en-base 1:10.10 20100930 failed to install/upgrade: trying to overwrite '/usr/share/locale-langpack/en_GB/LC_MESSAGES/transmission.mo', which is
closing as obsolete please file a new report if you encounter this in focal or later thank you for your original report, our apologies we couldn't deal with it in a timely manner ** Changed in: language-pack-en-base (Ubuntu) Status: New => Invalid ** Changed in: language-pack-en-base (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/662209 Title: package language-pack-en-base 1:10.10 20100930 failed to install/upgrade: trying to overwrite '/usr/share/locale- langpack/en_GB/LC_MESSAGES/transmission.mo', which is also in package language-pack-gnome-en 1:10.10 20100720 Status in language-pack-en-base package in Ubuntu: Invalid Bug description: Binary package hint: language-pack-en-base unknown error ProblemType: Package DistroRelease: Ubuntu 10.10 Package: language-pack-en-base 1:10.10+20100930 ProcVersionSignature: Ubuntu 2.6.35-10.15-generic 2.6.35-rc5 Uname: Linux 2.6.35-10-generic i686 Architecture: i386 Date: Sun Oct 17 15:30:33 2010 ErrorMessage: trying to overwrite '/usr/share/locale-langpack/en_GB/LC_MESSAGES/transmission.mo', which is also in package language-pack-gnome-en 1:10.10+20100720 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100702) PackageArchitecture: all SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:10.10+20100930 failed to install/upgrade: trying to overwrite '/usr/share/locale-langpack/en_GB/LC_MESSAGES/transmission.mo', which is also in package language-pack-gnome-en 1:10.10+20100720 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/662209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 623150] Re: package language-pack-en-base 1:10.04 20100421 failed to install/upgrade: ErrorMessage: conflicting packages - not installing language-pack-en-base
do you have a way to reproduce this issue? does it ever occur in focal or later? ** Changed in: language-pack-en-base (Ubuntu) Status: New => Incomplete ** Changed in: language-pack-en-base (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/623150 Title: package language-pack-en-base 1:10.04 20100421 failed to install/upgrade: ErrorMessage: conflicting packages - not installing language-pack-en-base Status in language-pack-en-base package in Ubuntu: Incomplete Bug description: Binary package hint: language-pack-en-base this is as much as i knowplease help asap ProblemType: Package DistroRelease: Ubuntu 10.04 Package: language-pack-en-base 1:10.04+20100421 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Tue Aug 24 10:38:59 2010 ErrorMessage: ErrorMessage: conflicting packages - not installing language-pack-en-base InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4) PackageArchitecture: all SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:10.04+20100421 failed to install/upgrade: ErrorMessage: conflicting packages - not installing language-pack-en-base To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/623150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 725709] Re: package language-pack-en-base 1:10.04 20100714 failed to install/upgrade: unable to create `/var/lib/locales/supported.d/en.dpkg-new' (while processing `./var/lib/loc
do you have a way to reproduce this issue? does it ever occur in focal or later? ** Changed in: language-pack-en-base (Ubuntu) Status: New => Incomplete ** Changed in: language-pack-en-base (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/725709 Title: package language-pack-en-base 1:10.04 20100714 failed to install/upgrade: unable to create `/var/lib/locales/supported.d/en.dpkg-new' (while processing `./var/lib/locales/supported.d/en'): Invalid argument Status in language-pack-en-base package in Ubuntu: Incomplete Bug description: Binary package hint: language-pack-en-base during update ProblemType: Package DistroRelease: Ubuntu 10.04 Package: language-pack-en-base 1:10.04+20100714 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 Architecture: i386 Date: Sat Feb 26 20:09:32 2011 DpkgTerminalLog: ErrorMessage: unable to create `/var/lib/locales/supported.d/en.dpkg-new' (while processing `./var/lib/locales/supported.d/en'): Invalid argument InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) PackageArchitecture: all SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:10.04+20100714 failed to install/upgrade: unable to create `/var/lib/locales/supported.d/en.dpkg-new' (while processing `./var/lib/locales/supported.d/en'): Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/725709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692361] Re: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current stat
do you have a way to reproduce this issue? does it ever occur in focal or later? ** Changed in: language-pack-en-base (Ubuntu) Status: New => Incomplete ** Changed in: language-pack-en-base (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/1692361 Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') Status in language-pack-en-base package in Ubuntu: Incomplete Bug description: al iniciar ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun May 21 00:02:11 2017 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package language-pack-en-base (--configure): package language-pack-en-base is not ready for configuration ErrorMessage: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-04-23 (393 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1692361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 816258] Re: package language-pack-en-base 1:11.04 20110421 failed to install/upgrade: ErrorMessage: unable to stat `./usr/share/locale-langpack/en_CA/LC_MESSAGES/apt.mo' (which I
looks like a hardware issue closing since it was never confirmed by anybody else. thank you for reporting. ** Changed in: language-pack-en-base (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/816258 Title: package language-pack-en-base 1:11.04 20110421 failed to install/upgrade: ErrorMessage: unable to stat `./usr/share/locale- langpack/en_CA/LC_MESSAGES/apt.mo' (which I was about to install): Input/output error Status in language-pack-en-base package in Ubuntu: Invalid Bug description: I have xubuntu installed onto a 4gb transcend usb drive mounted at root and a 2gb drive mounted at /usr. The boot loader is installed onto a 100mb partition on a third sony 2gb usb stick the rest of which is formatted as swap space. I've had some problems getting xubuntu installed. I originally tried using LVM however the booter would not recognize the logical volume. I finally tried repartitioning the drives and finally got it installed but now every time I update that is the error that I receive. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: language-pack-en-base 1:11.04+20110421 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 Architecture: amd64 Date: Mon Jul 25 23:05:50 2011 ErrorMessage: ErrorMessage: unable to stat `./usr/share/locale-langpack/en_CA/LC_MESSAGES/apt.mo' (which I was about to install): Input/output error InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) PackageArchitecture: all SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:11.04+20110421 failed to install/upgrade: ErrorMessage: unable to stat `./usr/share/locale-langpack/en_CA/LC_MESSAGES/apt.mo' (which I was about to install): Input/output error UpgradeStatus: Upgraded to natty on 2011-07-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/816258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758734] Re: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory
do you have a way to reproduce this issue? does it ever occur in focal or later? ** Changed in: language-pack-en-base (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/1758734 Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory Status in language-pack-en-base package in Ubuntu: Incomplete Bug description: error in libc-bin stops update, auto-remove, remove, etc. No packages can be installed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Mar 25 20:24:44 2018 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Removing language-pack-en-base (1:16.04+20160627) ... dpkg: error processing package language-pack-en-base (--remove): unable to securely remove '/var/lib/locales/supported.d/en': Not a directory ErrorMessage: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory InstallationDate: Installed on 2015-11-12 (863 days ago) InstallationMedia: /etc/systemd/system/multi-user.target.wants/unattended- PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory UpgradeStatus: Upgraded to xenial on 2016-04-22 (701 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1758734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782986] Re: package language-pack-en-base 1:18.04+20180712 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
closing since there is no way to figure out what went wrong thank you for reporting and sorry we couldn't be of more help ** Changed in: language-pack-en-base (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/1782986 Title: package language-pack-en-base 1:18.04+20180712 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in language-pack-en-base package in Ubuntu: Invalid Bug description: During my latest apt upgrade this package is no longer functional: Do you want to continue? [Y/n] y dpkg: error processing package language-pack-en-base (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: language-pack-en-base E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: language-pack-en-base 1:18.04+20180712 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Jul 21 19:58:27 2018 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-11-27 (602 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:18.04+20180712 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to bionic on 2018-06-11 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1782986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 163686] Re: There is no way to install only needed English translations - language-pack-en installs all translations of english variants (en_GB, en_AU, en_CA, etc)
*** This bug is a duplicate of bug 152945 *** https://bugs.launchpad.net/bugs/152945 the requested solution in bug 152945 is how this should be done ** Summary changed: - There are no way to install only needed English translations - language-pack-en installs all translations of english variants (en_GB, en_AU, en_CA, etc) + There is no way to install only needed English translations - language-pack-en installs all translations of english variants (en_GB, en_AU, en_CA, etc) ** This bug has been marked a duplicate of bug 152945 /var/lib/locales/supported.d should reside in /etc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/163686 Title: There is no way to install only needed English translations - language-pack-en installs all translations of english variants (en_GB, en_AU, en_CA, etc) Status in language-pack-en-base package in Ubuntu: Confirmed Status in language-pack-en-base package in Baltix: New Bug description: Binary package hint: language-pack-en-base There are no way to install only needed English translations (for example just British English) - language-pack-en installs all the translations of English variants (en_GB, en_AU, en_CA, etc). This is an annoying problem, because too many unneeded locales appear in login prompt (gdm login screen) and users are confused by this - they don't know which English variant to choose from about 15 (en_HK, en_DK, en_IN, en_ZW, en_NZ, en_PH, en_US, en_GB, en_AU, en_SG, en_BW, en_ZA, en_CA, en_IE) ! :( I think this situation is not correct - almost no one will need English British, English Australian, English South African, English Singapore and all other 10 translations (look above) *at* *the* *same* *time*. Users will need only one of them at the majority of cases. Some other translations variants of the same language are already in separate language packs, for example Greek: language-pack-el-base (translations for language Greek, Modern) language-pack-grc-base (translations for language Greek, Ancient) I think language-pack-en should be split at least to several language packs according to geographical regions, for example for en_AU (Australian) and en_NZ (New Zealand) translations same language pack could be used, because Australia and New Zealand are neighbor countries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/163686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 657254] Re: Lucid German: Disk-check screen during log-on contains typos
** Changed in: language-pack-de-base (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-de-base in Ubuntu. https://bugs.launchpad.net/bugs/657254 Title: Lucid German: Disk-check screen during log-on contains typos Status in language-pack-de-base package in Ubuntu: Incomplete Bug description: Festplatte wir überprüft. Should read Festplatte wird überprüft. cf: http://forum.ubuntuusers.de/post/2645092/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-de-base/+bug/657254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-sixx are not co-installable with python-is-python2 in jammy
** Summary changed: - python3-yaml and python-is-python2 are not co-installable in jammy + python3-yaml and python3-sixx are not co-installable with python-is-python2 in jammy ** Also affects: six (Ubuntu) Importance: Undecided Status: New ** Summary changed: - python3-yaml and python3-sixx are not co-installable with python-is-python2 in jammy + python3-yaml and python3-six are not co-installable with python-is-python2 in jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: In Progress Status in six package in Ubuntu: New Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10
** Changed in: what-is-python (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1899288 Title: Python3 can't co-exist with Oracle's VirtualBox on 20.10 Status in dh-python package in Ubuntu: Fix Released Status in what-is-python package in Ubuntu: Invalid Bug description: Sorry I couldn't file this bug against the correct packages. The form told me there are no such packages as python-is-python3 and dh-python in Ubuntu... Release: Groovy Gorilla (Ubuntu 20.10). Package versions: python-is-python3 3.8.2-4 dh-python 4.20200925 The release of Ubuntu 20.10 is less than two weeks out, so I'd like to draw attention to a problem I've run into. It seems that 20.10 defaults to python3 and wants to install python-is-python3, which pulls in the latest version of dh-python, which in turn can't co-exist with Oracle's Virtualbox-6.1 and wants to uninstall it. I don't mind having _both_ python2 (apparently a requirement of VirtualBox) and python3 installed. But as of right now I can have either python-is-python3, and not be able to do a complete upgrade since virtualbox-6.1 will be uninstalled, or python-is-python2, in which case I cripple 20.10's python3 install, since I won't get dh- python and python-six. Ia there something the python packagers do about this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1899288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915910] Re: evince does not print
** Tags added: apparmor hirsute ** Summary changed: - evince does not print + evince does not print (apparmor, pxgsettings) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
** Tags added: focal2jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: In Progress Status in libsignon-glib source package in Impish: In Progress Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
https://packages.ubuntu.com/search?keywords=gir1.2-signon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: In Progress Status in libsignon-glib source package in Impish: In Progress Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
Oh, Robie, come on now. You already asked that question and an answer was given in #3 and #4. Too bad that was so long ago, but it's not my fault. "In this case, in essence the package name is already the versioning." and "IOW, gir1.2-signon-1.0 isn't going to see any further upstream work and Debian won't reintroduce it either. That line ends with Debian stable." You know guys, it's really frustrating to do all the work and then have to do it over and over again and again. Sometimes for years without getting an inch closer to getting a fix uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: In Progress Status in libsignon-glib source package in Impish: In Progress Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
@kibitih, please don't change the bug status without at least providing an upload or some kind of explanation ** Changed in: ubuntu-release-notes Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in Release Notes for Ubuntu: Confirmed Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: Won't Fix Status in sudo source package in Disco: Won't Fix Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
There is no need for an SRU. The problem does not affect focal as such. This is only an issue when moving from gir1.2-signon-1.0 to gir1.2-signon-2.0 which will only occur in groovy2hirsute and focal2jammy. The Replaces-line can be dropped in jammy+1. ** Changed in: libsignon-glib (Ubuntu) Status: Incomplete => In Progress ** Summary changed: - gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) + gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: In Progress Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505670] Re: "uncaptured python exception"
Christian, thank you for stepping in. It seems you finally got the ball
rolling here where I was unsuccessful in a good half dozen attempts in
#ubuntu-devel and other venues. That's the good news I suppose.
I maintain my assessment of the situation of Ubuntu as stated in #16.
I've been with Ubuntu since breezy or so. I've been very active in bug
triage, I know the processes. I'm happy to back up my rant with facts,
if you want to hear.
I also maintain that this bug ticket and the problem was clearly
described including a test case in #7 and a clear analysis of where the
problem is IN THE CODE right in #1. You don't need more bug triage at
that point. You need a dev to look at the code and that did not happen,
no matter the effort, here and elsewhere. I believe I even tried to get
the patch sponsored but nobody dared touching mvo's stuff without an
ACK.
I'm not sure, but it seems that both you and Miriam mistakenly assume
that this bug can be triggered by some configuration on the computer
where squid-deb-proxy-CLIENT is installed. As stated in #7 "this
problem occurs whenever there is more than one host/IP discovered via
avahi." in other words, a certain state of affairs with regards to the
LAN (plus VPNs) is needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
"uncaptured python exception"
Status in python2.7 package in Ubuntu:
New
Status in squid-deb-proxy package in Ubuntu:
Confirmed
Status in python2.7 source package in Bionic:
New
Status in squid-deb-proxy source package in Bionic:
New
Status in python2.7 source package in Focal:
New
Status in squid-deb-proxy source package in Focal:
New
Bug description:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('172.24.74.129', 3142): 2147483647 (:[Errno 111]
Connection refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
http://172.24.74.145:3142/
The last line still returns the proper proxy URI so as far as I can
tell things are still working. The IP 10.1.2.3 is for an n2n VPN.
This is on trusty with version 0.8.6ubuntu1.
To trigger the bug the environment setup needs to be in a specific way.
It seems for the problem to occur it need more than one host/IP discovered
via avahi. This can be probed via $ avahi-browse -kprtf _apt_proxy._tcp
and e.g. the common LXD setup of IPv4 + ipv6 is NOT enough to trigger it.
TODO: a sample output of the above command in an affected environment
could be helpful.
TODO: if possible outlining how the environment can be configured to
have this multi host/IP reply in avahi would be helpful as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
still unfixed - sigh! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) Status in libsignon-glib package in Ubuntu: New Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505670] Re: "uncaptured python exception"
@Miriam, actually, all that I've written has been mentioned before in
the bug ticket. Have you actually read the ticket? Why is it that
people who get paid by Canonical to work on Ubuntu can't even be
bothered to read the tickets where volunteers who don't get paid have
already done their work (you are not the first and not the second
employee where I noticed this)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
"uncaptured python exception"
Status in python2.7 package in Ubuntu:
New
Status in squid-deb-proxy package in Ubuntu:
Confirmed
Status in python2.7 source package in Bionic:
New
Status in squid-deb-proxy source package in Bionic:
New
Status in python2.7 source package in Focal:
New
Status in squid-deb-proxy source package in Focal:
New
Bug description:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('172.24.74.129', 3142): 2147483647 (:[Errno 111]
Connection refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
http://172.24.74.145:3142/
The last line still returns the proper proxy URI so as far as I can
tell things are still working. The IP 10.1.2.3 is for an n2n VPN.
This is on trusty with version 0.8.6ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505670] Re: "uncaptured python exception"
Thank, Miriam, for having a look. I only became aware of your response
now by accident.
I'm not sure I understand what you did and what your results were. It
appears that you got the issue of an "uncaptured python exception" at
least once "when you removed squid-deb-proxy"? I really don't know what
you mean there. Then you list the output of /usr/share/squid-deb-proxy-
client/apt-avahi-discover twice, unchanged, but apparently get an IPv4
result once and an IPv6 result on the next, identical invocation.
The problem with squid-deb-proxy is easy to trigger. All it needs is
two or more responses to the avahi discovery in your LAN. See the
initial report where it shows three different IP numbers. These days, I
believe an IPv4 and IPv6 response from the same server is actually
enough.
Frankly, we don't need more bug triage here, it's all been laid out
forever, we've had a working patch for years. The patch is as far as I
can tell correct in that it is not simply a workaround. I assume you
haven't looked at the code. What needs to be done here is for @mvo to
finally comment on whether or not this is the correct way to fix it or
reject the patch (and come up with an alternative patch).
Truth be told, the state of this bug is disgusting and demotivating.
Ubuntu used to be about making Debian polished and usable. How come we
dropped the ball so badly on this awesome USP?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
"uncaptured python exception"
Status in python2.7 package in Ubuntu:
New
Status in squid-deb-proxy package in Ubuntu:
Confirmed
Status in python2.7 source package in Bionic:
New
Status in squid-deb-proxy source package in Bionic:
New
Status in python2.7 source package in Focal:
New
Status in squid-deb-proxy source package in Focal:
New
Bug description:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('172.24.74.129', 3142): 2147483647 (:[Errno 111]
Connection refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
http://172.24.74.145:3142/
The last line still returns the proper proxy URI so as far as I can
tell things are still working. The IP 10.1.2.3 is for an n2n VPN.
This is on trusty with version 0.8.6ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.
https://github.com/google/fscrypt/issues/270 ** Bug watch added: github.com/google/fscrypt/issues #270 https://github.com/google/fscrypt/issues/270 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in fscrypt package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in fscrypt package in Debian: Unknown Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.
** Bug watch added: Debian Bug tracker #964951 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964951 ** Also affects: fscrypt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964951 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in fscrypt package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in fscrypt package in Debian: Unknown Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.
not a bug in pulseaudio, but confirmed and fixed upstream in fscrypt ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in fscrypt package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in fscrypt package in Debian: Unknown Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505670] Re: "uncaptured python exception"
Thanks, Lucas.
As far as I'm aware, this was never addressed upstream and thus still
affects ubuntu+1 (ping @mvo). So, before SRU this needs to be fixed in
ubuntu+1. The patch from #4 is what I've been using for the last few
years without a hitch. It would certainly be nice for it to land before
a decade is up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
"uncaptured python exception"
Status in python2.7 package in Ubuntu:
New
Status in squid-deb-proxy package in Ubuntu:
Confirmed
Status in python2.7 source package in Bionic:
New
Status in squid-deb-proxy source package in Bionic:
New
Status in python2.7 source package in Focal:
New
Status in squid-deb-proxy source package in Focal:
New
Bug description:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('172.24.74.129', 3142): 2147483647 (:[Errno 111]
Connection refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
http://172.24.74.145:3142/
The last line still returns the proper proxy URI so as far as I can
tell things are still working. The IP 10.1.2.3 is for an n2n VPN.
This is on trusty with version 0.8.6ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915910] Re: evince does not print
$ evince ~/Documents/fullblack.pdf sh: 1: /usr/lib/x86_64-linux-gnu/libproxy/0.4.15/pxgsettings: Permission denied Above excerpt from my terminal lends me to believe this is a problem in the libproxy package, after all, with permissions on the /usr/lib/x86_64-linux-gnu/libproxy/0.4.15/pxgsettings file or another file it calls. ** Also affects: libproxy (Ubuntu) Importance: Undecided Status: New ** Changed in: libproxy (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
** Patch added: "debdiff for hirsute - in line with comment #4" https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+attachment/5484745/+files/libsignon-glib_2.1-3_2.1-3ubuntu1.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) Status in libsignon-glib package in Ubuntu: New Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
I follow LTS-to-LTS normally and upgraded a btrfs subvolume copy all the way up to Hirsute now. I suspect that this is cruft from bionic or even earlier. I will look into it more as I find time. I usually don't boot into this hirsute system much. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Incomplete Status in fam package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in ipfm package in Ubuntu: Incomplete Status in n2n package in Ubuntu: Incomplete Status in pfm package in Ubuntu: Incomplete Status in shadowsocks package in Ubuntu: Incomplete Status in sysfsutils package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in virtualbox package in Ubuntu: Incomplete Status in xl2tpd package in Ubuntu: Incomplete Status in systemd package in Debian: Unknown Bug description: systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file.
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
IOW, gir1.2-signon-1.0 isn't going to see any further upstream work and Debian won't reintroduce it either. That line ends with Debian stable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) Status in libsignon-glib package in Ubuntu: New Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
Thank you for your comment, Robie. I agree about Conflicts most likely not being required here. I felt it was conservative to add so as not to introduce a regression if both packages are installed. After some further looking into it, a regression is unlikely. The file in question is identical in both packages, unchanged upstream for 8 years, so it's safe to "overwrite" with the "newer" version: https://gitlab.com/accounts-sso/libsignon- glib/-/tree/master/pygobject So, in the end, the conservative thing to do is to allow anyone with the need to install both packages at the same time and do a Replaces only. About the versioning, I also agree that in general it is a good idea to be more permissive and limit restrictions by versioning them. In this case, in essence the package name is already the versioning. Bottom line: Can you drop the Conflicts line in the patch but otherwise upload as proposed here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) Status in libsignon-glib package in Ubuntu: New Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
** Summary changed: - gir1.2-signon-2.0 needs to declare replace on older releases + gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) ** Description changed: + gir1.2-signon-1.0 from groovy + gir1.2-signon-2.0 from hirsute + + above two packages ship the same file /usr/lib/python3/dist- + packages/gi/overrides/Signon.py without specifying how to resolve the + conflict. + Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) Status in libsignon-glib package in Ubuntu: New Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases
debdiff is in my PPA https://launchpadlibrarian.net/523915756/libsignon- glib_2.1-3_2.1-3ubuntu1.diff.gz bugfixed package currently building. I verified the fixed package to deal with the issue reported here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) Status in libsignon-glib package in Ubuntu: New Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases
** Tags removed: groovy-hirsute ** Tags added: groovy2hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases Status in libsignon-glib package in Ubuntu: New Bug description: Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] [NEW] gir1.2-signon-2.0 needs to declare replace on older releases
Public bug reported: Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. ** Affects: libsignon-glib (Ubuntu) Importance: Undecided Status: New ** Tags: groovy-hirsute hirsute ** Description changed: Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): - trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 + trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: - /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb + /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) + + Probably needs a conflicts/replaces dependency added to the newer + hirsute package. ** Tags added: groovy-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases Status in libsignon-glib package in Ubuntu: New Bug description: Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505670] Re: "uncaptured python exception"
I've long been using the patch from this ticket successfully and have
now published a bionic package in my LTS ppa
https://launchpad.net/~r0lf/+archive/ubuntu/stable Other release
pockets to follow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
"uncaptured python exception"
Status in python2.7 package in Ubuntu:
New
Status in squid-deb-proxy package in Ubuntu:
Confirmed
Bug description:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('172.24.74.129', 3142): 2147483647 (:[Errno 111]
Connection refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
http://172.24.74.145:3142/
The last line still returns the proper proxy URI so as far as I can
tell things are still working. The IP 10.1.2.3 is for an n2n VPN.
This is on trusty with version 0.8.6ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915887] [NEW] systemd spams the syslog about lack of native systemd unit file
Public bug reported: systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Affects: fam (Ubuntu) Importance: Undecided Status: New ** Affects: freeradius (Ubuntu) Importance: Undecided Status: New ** Affects: ipfm (Ubuntu) Importance: Undecided Status: New ** Affects: n2n (Ubuntu) Importance: Undecided Status: New ** Affects: pfm (Ubuntu) Importance: Undecided Status: New ** Affects: shadowsocks (Ubuntu) Importance: Undecided Status: New ** Affects: sysfsutils (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Affects: xl2tpd (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
This discussion should be continued in the following places in a civil (!) manner. Uncivilized language, no matter how angry you are, is likely only to have the effect of alienating the people in charge. It's in your own interest to stay civil if you want to get the old behaviour restored. No need for any comments, really, just upvote as "being affected" in the two below tickets if you'd like to see this problem fixed. bug 1914962: replace nautilus with alternative default file manager bug 1751069: restore type-ahead find in nautilus itself -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: Upgrades to 18.04 fail due to systemd-shim
** Changed in: systemd (Ubuntu Bionic) Assignee: Jim Denny (bluedanser) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: Upgrades to 18.04 fail due to systemd-shim Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891338] Re: apparmor misconfigured for evince
** Summary changed: - apparmor misconfigured for envice + apparmor misconfigured for evince -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1891338 Title: apparmor misconfigured for evince Status in apparmor package in Ubuntu: In Progress Status in evince package in Ubuntu: Triaged Bug description: On a fully up to date xubuntu 20-04 system, when i run evince and click on a link, it fails to follow that link in my browser. This kind of thing happens when you are reading a technical paper and want to follow one of the references and click on the doi or url. When i click on the link i get a box that i cannot copy from that says: Failed to launch preferred application for category "WebBrowser". Failed to execute child process "/usr/lib/x86_64-linux-gnu/xfce4/exo-2 /exo-helper-2"(Permission denied). Did I say that it is annoying that i could not copy the text in this box!! The output of the ldd command you asked for is attached. I should also point out that this worked fine under xubuntu 18.04. I had originally posted this as an additional comment on https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159?comments=all but https://launchpad.net/~seb128 said that I should submit this as a separate bug because this is likely an apparmor configuration problem that is similar to the ancient bug https://bugs.launchpad.net/bugs/987578. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1891338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895664] [NEW] problem in apparmor configuration of evince
Public bug reported: evince 3.28.4-0ubuntu1.2 running on bionic. I cannot call the vivaldi- browser by clicking on a link. Instead an error is shown "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission denied)". Some lines from syslog: Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 audit(1600172908.761:241): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 audit(1600172909.393:242): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 audit(1600172909.585:243): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 audit(1600172909.617:244): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 audit(1600172933.841:256): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Also affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895664 Title: problem in apparmor configuration of evince Status in apparmor package in Ubuntu: New Status in evince package in Ubuntu: New Bug description: evince 3.28.4-0ubuntu1.2 running on bionic. I cannot call the vivaldi-browser by clicking on a link. Instead an error is shown "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission denied)". Some lines from syslog: Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 audit(1600172908.761:241): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 audit(1600172909.393:242): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 audit(1600172909.585:243): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 audit(1600172909.617:244): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 audit(1600172933.841:256): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain
while you can certainly argue that the obsolete key was a configuration issue, I'd find it surprising to see the missing warning about this while silently pretending to be working just fine not to be considered a bug. ** Changed in: openssh (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1764044 Title: ssh-add asks about passphrases for keys already unlocked in the keychain Status in openssh package in Ubuntu: New Bug description: In the below example, on the second invocation of ssh-add I should not be prompted to enter the passphrase again after I successfully entered it on the first instance. This used to work fine in trusty i386 setup. $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Starting ssh-agent... Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Found existing ssh-agent: 25744 Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) gnome-keyring is running: $ ps -ax|grep key 2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components ssh 2078 ?Ssl0:01 /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service --use-gtk 6987 ?S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh 17832 pts/2S+ 0:00 grep --color=auto key ssh-agent is running: $ ps aux | grep ssh-agent leggewie 1928 0.0 0.0 15548 340 ?Ss 02:38 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 /usr/lib/gnome-session/run-systemd-session unity-session.target leggewie 6987 0.0 0.0 11304 1484 ?S02:50 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh leggewie 9952 0.0 0.0 11304 320 ?Ss 04:11 0:00 ssh-agent bash leggewie 17850 0.0 0.0 14492 1160 pts/2S+ 06:06 0:00 grep --color=auto ssh-agent $ env|grep SSH SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992 SSH_AGENT_PID=9952 SSH_AGENT_LAUNCHER=gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain
I finally was able to solve this. It turns out, my key was too old and thus kind of disabled as a security measure, I suppose. After creating a new key based off ED25519 and adding the corresponding public key to ~/.ssh/authorized_keys on the server, things are now working again. Can we please do better and inform the user what's wrong instead of silently pretending to be working but dropping the unlocked key? FWIW, even now with the process working again "keychain -l" still lists nothing. I'm not 100% sure but that looks like a bug of its own. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1764044 Title: ssh-add asks about passphrases for keys already unlocked in the keychain Status in openssh package in Ubuntu: New Bug description: In the below example, on the second invocation of ssh-add I should not be prompted to enter the passphrase again after I successfully entered it on the first instance. This used to work fine in trusty i386 setup. $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Starting ssh-agent... Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Found existing ssh-agent: 25744 Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) gnome-keyring is running: $ ps -ax|grep key 2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components ssh 2078 ?Ssl0:01 /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service --use-gtk 6987 ?S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh 17832 pts/2S+ 0:00 grep --color=auto key ssh-agent is running: $ ps aux | grep ssh-agent leggewie 1928 0.0 0.0 15548 340 ?Ss 02:38 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 /usr/lib/gnome-session/run-systemd-session unity-session.target leggewie 6987 0.0 0.0 11304 1484 ?S02:50 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh leggewie 9952 0.0 0.0 11304 320 ?Ss 04:11 0:00 ssh-agent bash leggewie 17850 0.0 0.0 14492 1160 pts/2S+ 06:06 0:00 grep --color=auto ssh-agent $ env|grep SSH SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992 SSH_AGENT_PID=9952 SSH_AGENT_LAUNCHER=gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807514] Re: installed systemd-shim package post-removal script subprocess returned error exit status 2
systemd-shim is a xenial package. Your distro information is bionic. Am I right to assume that this happened while you were trying to upgrade a xenial system to bionic? I have to admit I just ran into this myself. ** Changed in: systemd-shim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1807514 Title: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd-shim package in Ubuntu: Incomplete Bug description: installed systemd-shim package post-removal script subprocess returned error exit status 2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Dec 8 17:13:53 2018 DistUpgraded: 2018-12-08 17:07:42,953 DEBUG /openCache(), new cache size 61306 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1682:3030] InstallationDate: Installed on 2014-02-15 (1757 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: Dell Inc. Dell DXP051 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=e3337e9d-4116-4f99-b96f-8019182e5c07 ro Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-08 (0 days ago) dmi.bios.date: 01/08/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0YC523 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0YC523:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell DXP051 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Nov 4 10:33:25 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1807514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752635] Re: [patch] Please add command-not-found hints
has this landed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1752635 Title: [patch] Please add command-not-found hints Status in python2.7 package in Ubuntu: New Bug description: The new command-not-found extractor uses hints from the binary packages. The attached fix adds renaming for python2.7-minimal -> python2.7. We probably want the same for python3.6,3.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1752635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 809302] Re: pydoc -k launches kwallet
For me on bionic, that command tries to launch gourmet, a totally unrelated application. $ pydoc -k "hello" boto.pyami.helloworld usage: gourmet [-h] [--version] [--database-url DB_URL] [--plugin-directory HTML_PLUGIN_DIR] [--use-threads] [--disable-threads] [--gourmet-directory GOURMETDIR] [--debug-threading-interval THREAD_DEBUG_INTERVAL] [--debug-threading] [--debug-file DEBUG_FILE] [--showtimes] [--disable-psyco] [-q | -v] gourmet: error: unrecognized arguments: -k hello ** Changed in: python2.7 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/809302 Title: pydoc -k launches kwallet Status in python2.7 package in Ubuntu: Confirmed Bug description: steps to reproduce 1) run pydoc -k "hello" It seems to begin to operate correctly, but always includes the following details, and opens kwallet (?) [... Package names - descriptions...] Usage: pydoc2.7 [options] A simple dialog based tool for basic configuration of Speech Dispatcher and problem diagnostics. pydoc2.7: error: no such option: -k """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/809302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853525] Re: no python 2.7.17 in LTS version
The requested version is in the repos and the changelog suggests that at the time of filing the reporter's installation was not uptodate. http://changelogs.ubuntu.com/changelogs/pool/main/p/python2.7/python2.7_2.7.17-1~18.04ubuntu1/changelog ** Changed in: python2.7 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1853525 Title: no python 2.7.17 in LTS version Status in python2.7 package in Ubuntu: Invalid Bug description: Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version this version broke my scripts and get me segmentation fault each time I trying to do something. IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so why I have .15 and in RC1 version. Who is maintainer of this package that sleeps so long. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1853525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505670] Re: "uncaptured python exception"
filing against python2.7 as well based on comment #4
** Also affects: python2.7 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
"uncaptured python exception"
Status in python2.7 package in Ubuntu:
New
Status in squid-deb-proxy package in Ubuntu:
Confirmed
Bug description:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('172.24.74.129', 3142): 2147483647 (:[Errno 111]
Connection refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
http://172.24.74.145:3142/
The last line still returns the proper proxy URI so as far as I can
tell things are still working. The IP 10.1.2.3 is for an n2n VPN.
This is on trusty with version 0.8.6ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804444] Re: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: installed python2.7 package post-installation script subprocess returned error exit status 127
from DpkgTerminalLog.txt: Setting up python2.7 (2.7.15~rc1-1ubuntu0.1) ... /var/lib/dpkg/info/python2.7.postinst: 9: /var/lib/dpkg/info/python2.7.postinst: /usr/bin/python2.7: not found [1mdpkg:[0m error processing package python2.7 (--configure): installed python2.7 package post-installation script subprocess returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/180 Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: installed python2.7 package post-installation script subprocess returned error exit status 127 Status in python2.7 package in Ubuntu: New Bug description: I uninstalled python2.7 using apt purge python-minimal and later installed it again ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python2.7 2.7.15~rc1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Nov 21 09:19:33 2018 ErrorMessage: installed python2.7 package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2017-05-04 (566 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: python2.7 Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: installed python2.7 package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-10-02 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586771] Re: unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04.
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586771 Title: unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04. Status in network-manager package in Ubuntu: Incomplete Bug description: Previously Wifi was in working condition By adding extra packages from software updates -> Additional Drivers. But now I can not able to connect with wifi. It only shows in Air Plane mode. I am using Laptop Thinkpad T520 OS = ubuntu gnome 16.04 Network card = Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (Centrino Advanced-N 6205 AGN) Kernel version = 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 29 18:26:15 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-16 (42 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.1.1 dev enp0s25 proto static metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.105 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected/org/freedesktop/NetworkManager/Devices/1 enp0s25 dacd31ad-8949-42a6-8115-142800960f1c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1586771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1274857] Re: wi-fi continually fails to connect (after previous success)
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1274857 Title: wi-fi continually fails to connect (after previous success) Status in network-manager package in Ubuntu: Incomplete Bug description: Wi-fi had been working fine, but this morning, nothing doing. syslog shows many instances of: Activation (wlan0/wireless): association took too long, failing activation. Some info which may or may not be relevant: Removing the network and adding it made no difference. Deactivating, then reactivating the hardware wi-fi network switch made no difference. This was happening on two independent wi-fi networks (my hotel and the bluefin office) Rebooting fixed the issue. Closing the laptop did not reliably send it to sleep last night. Two competent Canonical engineers were unable to diagnose the problem. % lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 % uname -a Linux rog-ThinkPad-X220 3.13.0-2-generic #17-Ubuntu SMP Fri Jan 10 12:14:30 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux % lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] 0d:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 07) % I have attached my syslog starting just before the most recent successful connection until just before I rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1274857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368147] Re: Lenovo Thinkpad Twist: Mobile Broadbad not working any more
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1368147 Title: Lenovo Thinkpad Twist: Mobile Broadbad not working any more Status in network-manager package in Ubuntu: Incomplete Bug description: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click "Enable Mobile Broadband" in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying "Connection activation failed, (32) The connection was not supportedby oFono". I am using Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867496] [NEW] Thinkpad X220 internal ethernet identified as T520
Public bug reported: This is a very minor bug, only cosmetic in nature, but likely easy to fix. The internal ethernet adapter on my Thinkpad X220 is identified as from the T520 by network-manager. See attached screenshot. This is on an up-to-date bionic system. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "screenshot demonstrating the problem" https://bugs.launchpad.net/bugs/1867496/+attachment/5337120/+files/misidentified-ethernet.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1867496 Title: Thinkpad X220 internal ethernet identified as T520 Status in network-manager package in Ubuntu: New Bug description: This is a very minor bug, only cosmetic in nature, but likely easy to fix. The internal ethernet adapter on my Thinkpad X220 is identified as from the T520 by network-manager. See attached screenshot. This is on an up-to-date bionic system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1867496/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1068304] Re: ssh not using gnome-ssh-askpass
closing as unreproducible ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1068304 Title: ssh not using gnome-ssh-askpass Status in openssh package in Ubuntu: Invalid Bug description: When I run ssh, it prompts me for my private key's passphrase on the terminal, not in a separate window. If I run ssh again, it prompts again at the terminal. (By "terminal" I really mean an instance of gnome-terminal.) I expected the following behavior: When I run ssh the first time for this particular host, it should prompt for my passphrase in a new window. When I run ssh again after that, it should succeed without prompting at all. If I run "env" in the terminal, I see values for SSH_AGENT_PID and SSH_AUTH_SOCK as well as GNOME_KEYRING_CONTROL. If I run "ps -ax" I see both ssh-agent and gnome-keyring-daemon running. Finally, /etc/alternatives/ssh-askpass is linked to /usr/lib/openssh/gnome-ssh- askpass. If I run "ssh-add" explicitly to add the key, it also prompts me for my password at the terminal, but after that, ssh uses the unlocked key (that is, it no longer prompts for that key's passphrase). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ssh-askpass-gnome 1:6.0p1-3ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Thu Oct 18 15:21:15 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1068304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1130191] Re: config IdentityFile entries ignored with agent
closing as unreproducible ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1130191 Title: config IdentityFile entries ignored with agent Status in openssh package in Ubuntu: Invalid Bug description: I have a pair of ssh config entires which look like: Host host1 User serge Identityfile host1key ProxyCommand none Host cloud-* User ubuntu StrictHostKeyChecking no IdentityFile ~/some/path/cloudkey ProxyCommand ssh host1 nc -q0 %h.cloud %p If I'm logged in through unity, ssh -vvv cloud-* shows that it tries all of the ssh keys under ~/.ssh instead of the named IdentityFile. I assume ssh would eventually get to trying host1key, but the remote end (host1) refuses the login before getting to that. It should try the listed IdentityFile first. Note: I had a set of password-less keys under ~/.ssh for testing purposes. gnome-keyring-daemon auto-loads those, so that doing 'ssh-add -D' doesn't help. When not running gnome-keyring-daemon, you can avoid this by only loading the needed keys into the ssh-agent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1130191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 666706] Re: Multiple notifications aren't displayed
I can confirm the described behaviour. A dev will have to decide whether or not this is working as designed and intended. FWIW, I would like to point out that my understanding of bug 725435 hints at this possibly being a conscious choice NOT to display more than 1 bubble at the same time. It might also have been done so as not to overload the screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/666706 Title: Multiple notifications aren't displayed Status in libnotify package in Ubuntu: Confirmed Bug description: in libnotify if there are multiple notifications at the same time they arent visible together ...it would be helpful when a new notification is triggered before the old one vanishes...the new notification should be displayed below the old notification. Right now new notification is not displayed until the old notification vanishes...which is quite some time later i would also like a feature by which we can adjust time for which a notification bubble is displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/666706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 725435] Re: notify-osd a memory hog (memory leak?)
** Also affects: libnotify (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/725435 Title: notify-osd a memory hog (memory leak?) Status in libnotify package in Ubuntu: New Status in notify-osd package in Ubuntu: Triaged Bug description: Binary package hint: notify-osd Noticed this today on my lucid box in top: 2647 myaccount 20 0 1196m 595m 3528 S0 29.7 1:09.68 notify-osd I don't think a simple notifcation daemon should suck up more than a Gig of memory of which half is real memory. It's the first time I noticed this. I don't have too much information at this point. $ dpkg -l notify-osd* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== ii notify-osd0.9.29-0ubuntu2 daemon that displays passive pop-up notifications ii notify-osd-icons 0.6 Notify-OSD icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/725435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1266492] Re: ld:i386 crashes with -static -fPIE -pie
closing task for trusty
** Changed in: evolution-data-server (Ubuntu Trusty)
Status: Triaged => Invalid
** Changed in: binutils (Ubuntu Trusty)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1266492
Title:
ld:i386 crashes with -static -fPIE -pie
Status in GLibC:
Incomplete
Status in binutils package in Ubuntu:
Confirmed
Status in eglibc package in Ubuntu:
Fix Released
Status in evolution-data-server package in Ubuntu:
Fix Released
Status in xorg-server package in Ubuntu:
Fix Released
Status in binutils source package in Trusty:
Invalid
Status in eglibc source package in Trusty:
Fix Released
Status in evolution-data-server source package in Trusty:
Invalid
Status in xorg-server source package in Trusty:
Fix Released
Status in eglibc package in Debian:
Fix Released
Bug description:
Making a simple file conftest.c with the following contents:
int main() { return 0; }
And then compiling it on i386 with gcc -fPIE -pie -static conftest.c
returns:
*** Error in `/usr/bin/ld': corrupted double-linked list: 0x08dddb38
***
This breaks compilation xorg-server on i386. I believe that -static
-fPIE -pie is probably invalid, and it fails on amd64 too.
$ gcc -fPIE -pie -static conftest.c
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: relocation
R_X86_64_32 against `__TMC_END__' can not be used when making a shared object;
recompile with -fPIC
/usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
But autoconf hangs on the corrupted double-linked list, which times
out the xorg-server build.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1266492/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856547] Re: focal live ISO fails to boot in VirtualBox (initramfs write error)
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856547 Title: focal live ISO fails to boot in VirtualBox (initramfs write error) Status in initramfs-tools package in Ubuntu: New Bug description: Please see the attached screenshot for a description of the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1856547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices
Here is my status. The hidd binary seems to be gone. The bluetooth-wizard binary worked fine for me in bionic just now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1059185 Title: bluetooth-wizard doesn't find any devices Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: I have just upgrade to Quantal from Precise. I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and mouse. They worked without problems before the upgrade, but now they don't. I removed them and tried to add them again, but the bluetooth-wizard is stuck searching for devices, and doesn't find any. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 11:45:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830945] Re: DNS settings from interfaces file are ignored
Thank you for reporting back. I will close this ticket as invalid, then. ** Changed in: resolvconf (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1830945 Title: DNS settings from interfaces file are ignored Status in resolvconf package in Ubuntu: Invalid Bug description: Since a recent reboot (00:00 CEST on tuesday to be precise), DNS settings from the interfaces file are no longer present in resolvconf. A file /run/resolvconf/interface/eth0.inet exists but is empty. This is happening on a xenial system. I have since rebooted once more, with the same result. These are the contents of /etc/network/interfaces: iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.200.52 netmask 255.255.255.0 gateway 192.168.200.5 dns-nameserver 192.168.200.5 dns-nameserver 8.8.8.8 # second address iface eth0 inet static address 192.168.200.67 netmask 255.255.255.0 I'm running dnsmasq as a local DNS server on this system, which expects to get the "upstream" dns servers from resolvconf and thus can no longer resolve external addresses. Until this recent reboot, this configuration has worked without issue for many months, I have the etckeeper log to prove it :-). Here are some relevant excerpts from the logs: systemd[1]: Starting Clean up any mess left by 0dns-up... systemd[1]: Reached target Remote File Systems. systemd[1]: Started Clean up any mess left by 0dns-up. systemd[1]: Starting Nameserver information manager... systemd[1]: Started Nameserver information manager. systemd[1]: Reached target Sockets. systemd[1]: Reached target Basic System. systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server... systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down... systemd[1]: Starting Raise network interfaces... systemd[1]: Started ifup for eth0. systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down. ifup[624]: /sbin/ifup: waiting for lock on /run/network/ifstate.eth0 systemd[1]: Started Raise network interfaces. systemd[1]: Reached target Network. dnsmasq[583]: dnsmasq: syntax check OK. systemd[1]: Reached target Network is Online. ntpdate[840]: name server cannot be used: Temporary failure in name resolution (-3) dnsmasq[975]: started, version 2.75 cachesize 150 dnsmasq[975]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dnsmasq[975]: DNS service limited to local subnets dnsmasq-dhcp[975]: DHCP, IP range 192.168.200.100 -- 192.168.200.200, lease time 1h dnsmasq[975]: using local addresses only for domain myname.local dnsmasq[975]: no servers found in /var/run/dnsmasq/resolv.conf, will retry dnsmasq[975]: read /etc/hosts - 14 addresses ntpd[1060]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3) systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. systemd[1]: Reached target Host and Network Name Lookups. ntpd[1060]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1830945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1070006] Re: Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1070006
Title:
Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)
Status in gnome-control-center package in Ubuntu:
Invalid
Status in gnome-shell package in Ubuntu:
Invalid
Status in modemmanager package in Ubuntu:
Invalid
Status in network-manager package in Fedora:
Fix Released
Bug description:
The modem (ZTE MF622) is recognised and 'Mobile Broadband' can be
enabled. The network is shown ('3' in the UK) and has signal strength
bars (2 for me). However, the modem doesn't connect.
Ubuntu Desktop displays a Mobile Broadband Connection dialog/wiz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070006/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 438520] Re: Right Alt key is always selected under "key to choose 3rd level"
what is the status here? Anything left to be done for bionic or later? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/438520 Title: Right Alt key is always selected under "key to choose 3rd level" Status in console-setup package in Ubuntu: Expired Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-control-center On a fresh install of Karmic, under the keyboard layout options, the right Alt key is selected under "Key to Choose 3rd Level". I'm not even sure what the 3rd level is, as I've never needed this setting before. On Jaunty, there is nothing set under this option. As a result on Karmic, this breaks the right Alt key. For example right Alt+F2 doesn't do anything. But when you try to uncheck this option, it doesn't remember the setting. The next time you open the layout options, it's checked again. There seems to be no way to uncheck this option. What should happen 1. Open System > Preferences > Keyboard 2. Go to the Layouts tab 3. Click Layout Options 4. Expand Key to Choose 3rd Level 5. Uncheck Right Alt 5. Close the Layout Options window 6. Reopen Layout Options 7. Nothing should be checked under Key to Choose 3rd Level What happens instead Right Alt is still selected after unchecking it, closing the Layout Options window and reopening it. ProblemType: Bug Architecture: i386 Date: Tue Sep 29 00:08:29 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-control-center 1:2.28.0-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: gnome-control-center Uname: Linux 2.6.31-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/438520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Could this be an incompatibility between i386 and amd64 packages? I have trouble adding my keys via ssh-add and after reading some comments here and elsewhere gave removing dbus-user-session a try. My computer is amd64 with i386 foreign arch. dbus-user-session was replaced with dbus-user-session:i386 and a few other :386 packages. After the installation, the situation was much worse, with ssh-add completely hanging now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 377356] Re: ssh-askpass has no Option to save the Passphrase to a keyring
closing as obsolete ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/377356 Title: ssh-askpass has no Option to save the Passphrase to a keyring Status in openssh package in Ubuntu: Invalid Bug description: Binary package hint: ssh-askpass-gnome When Ssh-askpass asks for a pass phrase to a ssh-key on previews releases, there was a checkbox for saving the pass phrase in the keyring and lock it up when logging in. Under Jaunty (with ssh- askpass-gnome version 1:5.1p1-5ubuntu1) this Option is no longer available, so there is no possibility to get new pass phrases into the keyring. For clarification see this screenshot of working window in Hardy: http://launchpadlibrarian.net/26627518/ubuntu-8.10-default-ssh-add- behaviour.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/377356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain
** Description changed: In the below example, on the second invocation of ssh-add I should not be prompted to enter the passphrase again after I successfully entered - it on the first instance. + it on the first instance. This used to work fine in trusty i386 setup. $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Starting ssh-agent... Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Found existing ssh-agent: 25744 Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) + + gnome-keyring is running: + $ ps -ax|grep key + 2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components ssh + 2078 ?Ssl0:01 /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service --use-gtk + 6987 ?S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh + 17832 pts/2S+ 0:00 grep --color=auto key + + ssh-agent is running: + $ ps aux | grep ssh-agent + leggewie 1928 0.0 0.0 15548 340 ?Ss 02:38 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 /usr/lib/gnome-session/run-systemd-session unity-session.target + leggewie 6987 0.0 0.0 11304 1484 ?S02:50 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh + leggewie 9952 0.0 0.0 11304 320 ?Ss 04:11 0:00 ssh-agent bash + leggewie 17850 0.0 0.0 14492 1160 pts/2S+ 06:06 0:00 grep --color=auto ssh-agent + + $ env|grep SSH + SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992 + SSH_AGENT_PID=9952 + SSH_AGENT_LAUNCHER=gnome-keyring -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1764044 Title: ssh-add asks about passphrases for keys already unlocked in the keychain Status in openssh package in Ubuntu: New Bug description: In the below example, on the second invocation of ssh-add I should not be prompted to enter the passphrase again after I successfully entered it on the first instance. This used to work fine in trusty i386 setup. $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Starting ssh-agent... Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Found existing ssh-agent: 25744 Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) gnome-keyring is running: $ ps -ax|grep key 2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components ssh 2078 ?Ssl0:01 /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service --use-gtk 6987 ?S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh 17832 pts/2S+ 0:00 grep --color=auto key ssh-agent is running: $ ps aux | grep ssh-agent leggewie 1928 0.0 0.0 15548 340 ?Ss 02:38 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 /usr/lib/gnome-session/run-systemd-session unity-session.target leggewie 6987 0.0 0.0 11304 1484 ?S02:50 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh leggewie 9952 0.0 0.0 11304 320 ?Ss 04:11 0:00 ssh-agent bash leggewie 17850 0.0 0.0 14492 1160 pts/2S+ 06:06 0:00 grep --color=auto ssh-agent $ env|grep SSH SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992 SSH_AGENT_PID=9952 SSH_AGENT_LAUNCHER=gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1068304] Re: ssh not using gnome-ssh-askpass
Still an issue on bionic or later? ** Changed in: openssh (Ubuntu) Status: Confirmed => Incomplete ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1068304 Title: ssh not using gnome-ssh-askpass Status in openssh package in Ubuntu: Incomplete Bug description: When I run ssh, it prompts me for my private key's passphrase on the terminal, not in a separate window. If I run ssh again, it prompts again at the terminal. (By "terminal" I really mean an instance of gnome-terminal.) I expected the following behavior: When I run ssh the first time for this particular host, it should prompt for my passphrase in a new window. When I run ssh again after that, it should succeed without prompting at all. If I run "env" in the terminal, I see values for SSH_AGENT_PID and SSH_AUTH_SOCK as well as GNOME_KEYRING_CONTROL. If I run "ps -ax" I see both ssh-agent and gnome-keyring-daemon running. Finally, /etc/alternatives/ssh-askpass is linked to /usr/lib/openssh/gnome-ssh- askpass. If I run "ssh-add" explicitly to add the key, it also prompts me for my password at the terminal, but after that, ssh uses the unlocked key (that is, it no longer prompts for that key's passphrase). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ssh-askpass-gnome 1:6.0p1-3ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Thu Oct 18 15:21:15 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1068304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1130191] Re: config IdentityFile entries ignored with agent
Still an issue in bionic or later? ** Changed in: openssh (Ubuntu) Status: New => Incomplete ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1130191 Title: config IdentityFile entries ignored with agent Status in openssh package in Ubuntu: Incomplete Bug description: I have a pair of ssh config entires which look like: Host host1 User serge Identityfile host1key ProxyCommand none Host cloud-* User ubuntu StrictHostKeyChecking no IdentityFile ~/some/path/cloudkey ProxyCommand ssh host1 nc -q0 %h.cloud %p If I'm logged in through unity, ssh -vvv cloud-* shows that it tries all of the ssh keys under ~/.ssh instead of the named IdentityFile. I assume ssh would eventually get to trying host1key, but the remote end (host1) refuses the login before getting to that. It should try the listed IdentityFile first. Note: I had a set of password-less keys under ~/.ssh for testing purposes. gnome-keyring-daemon auto-loads those, so that doing 'ssh-add -D' doesn't help. When not running gnome-keyring-daemon, you can avoid this by only loading the needed keys into the ssh-agent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1130191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661199] Re: Apt-cacher-ng fails on https repo
Reopening against acng for further consideration and possible discussion. ** Changed in: apt-cacher-ng (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1661199 Title: Apt-cacher-ng fails on https repo Status in apt package in Ubuntu: Won't Fix Status in apt-cacher-ng package in Ubuntu: New Bug description: Following the instructions to add the docker repo here: https://docs.docker.com/engine/installation/linux/ubuntu/ /etc/apt/sources.list contains the repo: deb https://apt.dockerproject.org/repo/ ubuntu-xenial main When running through apt-cacher-ng, apt-get update returns: $ sudo apt-get update Ign:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 https://apt.dockerproject.org/repo ubuntu-xenial Release Ign:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages.diff/Index Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Err:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Received HTTP code 403 from proxy after CONNECT Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:9 http://dl.google.com/linux/chrome/deb stable InRelease Hit:10 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:11 http://dl.google.com/linux/chrome/deb stable Release Hit:13 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:14 http://archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages Received HTTP code 403 from proxy after CONNECT E: Some index files failed to download. They have been ignored, or old ones used instead. When apt is set to disable the proxy, using the following /etc/apt/apt.conf: Acquire::http::Proxy "http://127.0.0.1:/;; Acquire::https::Proxy "DIRECT"; (note that the port has been changed from the default) The response is: $ sudo apt-get update Hit:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease Hit:3 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable Release Hit:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:7 http://archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done
[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher
bug 1674765 and https://askubuntu.com/questions/92349/how-do-i-hide-a -particular-user-from-the-login-screen have information how to deal with this -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in accountsservice: Confirmed Status in accountsservice package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher
Why am I seeing this in a bionic fresh install when I did not see this in trusty? How can I workaround this very annoying and very old bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in accountsservice: Confirmed Status in accountsservice package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
