[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
This is a very annoying bug. Last morning unattended-upgrade failed on a machine, so I set APT::Periodic::Verbose to "3" and this morning I got a very verbose email showing that it succeeded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
Yurii: can you clarify how that broke unattended upgrades? I also don't see how a cron script might get different PATH values from one day to the other. I just had another instance of this bug on a third Ubuntu 14.04 LTS server (this one a physical machine, not a VPS) where unattended-upgrades worked fine before. And on that machine # cat /proc/$(pidof cron)/environ | tr '\0' '\n' | grep PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin looks fine to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730027] Re: trap divide error
Duplicate of bug 1022865? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730027 Title: trap divide error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1730027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336869] Re: mkhomedir option not working on ipa-client-install
@tjaalton do you have any references to the Debian fix? So Free IPA still needs to switch the toggle to enable it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336869 Title: mkhomedir option not working on ipa-client-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1336869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336869] Re: mkhomedir option not working on ipa-client-install
** Description changed: The option --mkhomedir of ipa-client-install script is not working (Ubuntu 14.04). As a workaround, after executing the script, the following line can be added to the file /etc/pam.d/common-session: sessionrequired pam_mkhomedir.so skel=/etc/skel/ Unless for this problem and the bug https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1309655 everything is working fine. Really nice!. + + Workaround: https://bgstack15.wordpress.com/2017/06/26/enabling- + mkhomedir-on-ubuntu-for-freeipa/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336869 Title: mkhomedir option not working on ipa-client-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1336869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637797] Re: kernel referred to by /*.old autoremoved
The nightly unattended-upgrade (which I've configured to Unattended- Upgrade::Remove-Unused-Dependencies "true";) removed the .old kernel on two different 14.04 LTS servers last night, leaving both with no backup kernel at all. In fact now that I'm paying attention again, I have quite a number of servers without a /vmlinuz.old. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637797 Title: kernel referred to by /*.old autoremoved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1637797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750387] Re: xinetd fails to restart during unattended upgrades
Yes, etckeeper shows that xinetd was installed in a separate apt transaction, after cups-bsd. Both happened in 2009. I suspect I don't need lpd compatibility -- I expect any users who use the print queue access it over IPP. I think I'll remove xinetd entirely and forget about this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750387 Title: xinetd fails to restart during unattended upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/1750387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750387] Re: xinetd fails to restart during unattended upgrades
Yes, this system has been continuously upgraded from older Ubuntu
versions (starting with 9.04). It acts as a print server for the
office. I've no memory of manually setting up xinetd for cups-lpd. I
always assumed it was pulled in automatically as a dependency.
/etc/xinetd.d/printer looks like this:
service printer
{
socket_type = stream
protocol = tcp
wait = no
user = lp
server = /usr/lib/cups/daemon/cups-lpd
}
It took some digging through my changelogs and etckeeper history, but
now I'm certain that this file was generated by update-inetd calls from
/var/lib/dpkg/info/cups-bsd.postinst:
update-inetd --add 'printer stream tcp nowait lp
/usr/lib/cups/daemon/cups-lpd cups-lpd'
IIRC the only reason I have cups-bsd installed is that I was used to
typing 'lpq' to see if there are any jobs stuck in the print queue.
For the record, I don't see any cups-lpd processes actually running, so I don't
think things like the printers configured in my cups configuration should
affect xinetd's shutdown times.
Attempts to strace -f service xinetd restart show two things:
- the bug is not 100% reproducible for me
- systemctl restart talks to systemd over a socket, so I can't see any of the
interesting bits with strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750387
Title:
xinetd fails to restart during unattended upgrades
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/1750387/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750387] Re: xinetd fails to restart during unattended upgrades
The last line of the log excerpt has a suspiciously low PID number Feb 16 07:03:30 fridge xinetd[2756]: Exiting... I took that to be a clue that this is the old instance of xinetd, that was supposed to be stopped by the two lines above: Feb 16 07:03:29 fridge xinetd[24720]: * Stopping internet superserver xinetd Feb 16 07:03:29 fridge xinetd[24720]: ...done. (They have the same process name, but I think one's actually /usr/sbin/xinetd, and the other is /etc/init.d/xinetd.) Let me see if I can reproduce the issue. 1. 'service xinetd status' shows it's active (running) with pid 2776 2. 'service xinetd restart' says nothing because systemd 3. 'service xinetd status' shows it's active (exited) with a log excerpt Let me just paste the entire status output: ● xinetd.service - LSB: Starts or stops the xinetd daemon. Loaded: loaded (/etc/init.d/xinetd; bad; vendor preset: enabled) Active: active (exited) since Sat 2018-02-24 11:21:56 EET; 2s ago Docs: man:systemd-sysv-generator(8) Process: 6507 ExecStop=/etc/init.d/xinetd stop (code=exited, status=0/SUCCESS) Process: 6517 ExecStart=/etc/init.d/xinetd start (code=exited, status=0/SUCCESS) Feb 24 11:21:56 fridge systemd[1]: Starting LSB: Starts or stops the xinetd daemon Feb 24 11:21:56 fridge xinetd[6517]: * Starting internet superserver xinetd Feb 24 11:21:56 fridge systemd[1]: Started LSB: Starts or stops the xinetd daemon.. Feb 24 11:21:56 fridge xinetd[6517]:...fail! Feb 24 11:21:56 fridge xinetd[2776]: Exiting... As you can see, it's trying (and failing) to start the new instance before the old one (pid 2776) exits. ** Changed in: xinetd (Ubuntu) Status: Incomplete => New ** Description changed: + STEPS TO REPRODUCE: + + 1. make sure xinetd is running + 2. 'service xinetd restart' + 3. pgrep xinetd + + Expeced behavior: + + - xinetd is running (with a different PID) + + Actual behavior + + - xinetd is not running + - service xinetd status shows it as "active (exited)", and shows a failure message from startup before the old instance finished exitting + + + ORIGINAL DESCRIPTION: + This has happened twice now: xinetd dies during an unattended-upgrade process and I have to restart it manually. /var/log/syslog contains - Feb 16 07:03:28 fridge systemd[1]: Reloading. - Feb 16 07:03:28 fridge systemd[1]: Started ACPI event daemon. - Feb 16 07:03:28 fridge systemd[1]: Started CUPS Scheduler. - Feb 16 07:03:28 fridge systemd[1]: Stopping LSB: Starts or stops the xinetd daemon - Feb 16 07:03:29 fridge xinetd[24720]: * Stopping internet superserver xinetd - Feb 16 07:03:29 fridge xinetd[24720]:...done. - Feb 16 07:03:29 fridge systemd[1]: Stopped LSB: Starts or stops the xinetd daemon.. - Feb 16 07:03:29 fridge systemd[1]: Starting LSB: Starts or stops the xinetd daemon - Feb 16 07:03:29 fridge xinetd[24731]: * Starting internet superserver xinetd - Feb 16 07:03:29 fridge xinetd[24731]:...fail! - Feb 16 07:03:29 fridge systemd[1]: Started LSB: Starts or stops the xinetd daemon.. - Feb 16 07:03:30 fridge xinetd[2756]: Exiting... + Feb 16 07:03:28 fridge systemd[1]: Reloading. + Feb 16 07:03:28 fridge systemd[1]: Started ACPI event daemon. + Feb 16 07:03:28 fridge systemd[1]: Started CUPS Scheduler. + Feb 16 07:03:28 fridge systemd[1]: Stopping LSB: Starts or stops the xinetd daemon + Feb 16 07:03:29 fridge xinetd[24720]: * Stopping internet superserver xinetd + Feb 16 07:03:29 fridge xinetd[24720]:...done. + Feb 16 07:03:29 fridge systemd[1]: Stopped LSB: Starts or stops the xinetd daemon.. + Feb 16 07:03:29 fridge systemd[1]: Starting LSB: Starts or stops the xinetd daemon + Feb 16 07:03:29 fridge xinetd[24731]: * Starting internet superserver xinetd + Feb 16 07:03:29 fridge xinetd[24731]:...fail! + Feb 16 07:03:29 fridge systemd[1]: Started LSB: Starts or stops the xinetd daemon.. + Feb 16 07:03:30 fridge xinetd[2756]: Exiting... so it looks like systemd is trying to start the new process before the old one finishes exiting. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xinetd 1:2.3.15-6 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Feb 19 16:45:06 2018 ProcEnviron: - LC_CTYPE=lt_LT.UTF-8 - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LC_CTYPE=lt_LT.UTF-8 + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: xinetd UpgradeStatus: Upgraded to xenial on 2016-11-07 (469 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750387 Title: xinetd fails to restart d
[Bug 1750387] Re: xinetd fails to restart during unattended upgrades
In case this might be relevant: the only service xinetd is serving on this machine is /usr/lib/cups/daemon/cups-lpd (via /etc/xinetd.d/printer). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750387 Title: xinetd fails to restart during unattended upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/1750387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial
Tested the scilab 5.5.2 for ubuntu which works great. However, I did not test it before applying the jogl2 patch :-o. Had a look at the source and it seems that the Ubuntu version is patched to use the generic version of jogl2. I would like to try and get this patch integrated in the Scilab source tree. Probably a difficult and slow process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742894 Title: Scilab does not start after some upgrades on Ubuntu Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1742894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial
I tested the proposed package on Lubuntu 17.10. I tested some example programs they use either: GLProfile glp = GLProfile.getDefault(); Or they use the GLCanvas default constructor. Before this version all these examples emitted the typical error found in the previous version of jogl2. The new package RESOLVED this problem. I noticed after some experimenting that replacing getDefault with get(GLProfile.GL2); also solved the problem. Then I found this thread. I build scilab from source using the git repository. This is the master and future 6.1 version it has the same problem. However, scilab 6 and higher have the jogl2 library prebuild and distributed as a thirdparty library. Removing this library doesn't work. The problem is that the scirender module and the gui modules depend on the old syntax. The Java path in the past was javax.media. In newer version of jogl2 this changed to com.jogamp. This means that besides removing the faulty library from scilab the modules scirender and gui need to be patched. I did just this in the last days. The git master branch version 6.1 build and works with the new jogl2 version. I noticed however one regression bug the cursor selection in the plot window work kind of inverted. This is an old bug which I have seen before. So, yes this fixes the jogl2 bug. But, no likely not the scilab bug. Depends how you get scilab and which version probably. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742894 Title: Scilab does not start after some upgrades on Ubuntu Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1742894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750387] [NEW] xinetd fails to restart during unattended upgrades
Public bug reported: This has happened twice now: xinetd dies during an unattended-upgrade process and I have to restart it manually. /var/log/syslog contains Feb 16 07:03:28 fridge systemd[1]: Reloading. Feb 16 07:03:28 fridge systemd[1]: Started ACPI event daemon. Feb 16 07:03:28 fridge systemd[1]: Started CUPS Scheduler. Feb 16 07:03:28 fridge systemd[1]: Stopping LSB: Starts or stops the xinetd daemon Feb 16 07:03:29 fridge xinetd[24720]: * Stopping internet superserver xinetd Feb 16 07:03:29 fridge xinetd[24720]:...done. Feb 16 07:03:29 fridge systemd[1]: Stopped LSB: Starts or stops the xinetd daemon.. Feb 16 07:03:29 fridge systemd[1]: Starting LSB: Starts or stops the xinetd daemon Feb 16 07:03:29 fridge xinetd[24731]: * Starting internet superserver xinetd Feb 16 07:03:29 fridge xinetd[24731]:...fail! Feb 16 07:03:29 fridge systemd[1]: Started LSB: Starts or stops the xinetd daemon.. Feb 16 07:03:30 fridge xinetd[2756]: Exiting... so it looks like systemd is trying to start the new process before the old one finishes exiting. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xinetd 1:2.3.15-6 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Feb 19 16:45:06 2018 ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xinetd UpgradeStatus: Upgraded to xenial on 2016-11-07 (469 days ago) ** Affects: xinetd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750387 Title: xinetd fails to restart during unattended upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/1750387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
Well, I got the debug output this time (a whole megabyte of it, split in two different emails), but unattended-upgrades succeeded, so I still don't know what the original problem was. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
The good news is the problem is reproducible. The bad news is APT::Periodic::Verbose "1" doesn't make unattended- upgrade produce any more output in its failure email: Unattended upgrade returned: False Packages that attempted to upgrade: dh-apparmor libapparmor1 python3-update-manager update-manager-core Package installation log: Error in function: Unattended-upgrades log: Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=trusty-security', 'o=UbuntuESM,a=trusty', 'o=Ubuntu,a=trusty-security', 'o=Ubuntu,a=trusty-updates', 'origin=LP-PPA-pov,suite=trusty'] Packages that will be upgraded: dh-apparmor libapparmor1 python3-update-manager update-manager-core Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2018-02-13_03:07:51.796037.log' Installing the upgrades failed! error message: 'installArchives() failed' dpkg returned a error! See '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2018-02-13_03:07:51.796037.log' for details Packages that are auto removed: '' Packages auto-removed Which is exactly the same thing I saw yesterday. I think I see my mistake: I should've set APT::Periodic::Verbose to "3" to have the cron script pass -d to unattended-upgrade! D'oh! On the other hand I got an extra email from cron.daily saying /etc/cron.daily/apt: verbose level 1 sleeping for 280 seconds check_stamp: interval=86400, now=1518559200, stamp=1518472800, delta=86400 (sec) apt-key net-update (failure) download updated metadata (success). send dbus signal (success) check_stamp: interval=0 download upgradable (not run) check_stamp: interval=86400, now=1518559200, stamp=1518472800, delta=86400 (sec) unattended-upgrade (success) check_stamp: interval=0 autoclean (not run) aged: ctime <30 and mtime <30 and ctime>2 and mtime>2 end remove by archive size: size=24256 < 512000 The "apt-key net-update (failure)" line is intriguing, but seems to be unrelated. I've bumped APT::Periodic::Verbose to "3" now and will see what happens next morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
(By reading that script I've discovered the existence of APT::Periodic::Verbose. We'll see what happens next morning with this set to "1"!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
The thing is, whenever I run it interactively over ssh, unattended- upgrade succeeds. It's only the cron job that fails. If there's no separate config file, I'll edit /etc/cron.daily/apt directly. (This server is still on Ubuntu 14.04 LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
This happened again. Can I tweak some config file to enable verbose mode for unattended-upgrades and see if it'll fail when run from cron tomorrow night? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747910] Re: Crashes on DP hotplug (wl_registry@2: error 0: invalid global wl_output (29))
*** This bug is a duplicate of bug 1731911 *** https://bugs.launchpad.net/bugs/1731911 This is probably a duplicate of 1728588 (which itself is marked as a duplicate of 1731911). apport-retrace gives me this Xwayland stack trace: (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7fce6a322f5d in __GI_abort () at abort.c:90 #2 0x558934f5713a in OsAbort () at ../../../../os/utils.c:1361 #3 0x558934f5cc53 in AbortServer () at ../../../../os/log.c:877 #4 0x558934f5da75 in FatalError (f=f@entry=0x558934f66fa6 "%s") at ../../../../os/log.c:1015 #5 0x558934de2e6c in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:885 #6 0x7fce6c7728ca in wl_log (fmt=) at ../src/wayland-util.c:406 #7 0x7fce6c76e2d8 in display_handle_error (data=, display=0x558935d07e30, object=0x558935d0c300, code=0, message=) at ../src/wayland-client.c:810 #8 0x7fce69c60e18 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #9 0x7fce69c6087a in ffi_call (cif=cif@entry=0x7ffd318ba470, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffd318ba540) at ../src/x86/ffi64.c:525 #10 0x7fce6c771a1b in wl_closure_invoke (closure=, flags=, target=, opcode=0, data=) at ../src/connection.c:935 #11 0x7fce6c76e5b8 in dispatch_event (display=display@entry=0x558935d07e30, queue=) at ../src/wayland-client.c:1310 #12 0x7fce6c76f847 in dispatch_queue (queue=0x558935d07ef8, display=0x558935d07e30) at ../src/wayland-client.c:1449 #13 wl_display_dispatch_queue_pending (display=0x558935d07e30, queue=0x558935d07ef8) at ../src/wayland-client.c:1698 #14 0x7fce6c76f8cc in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1761 #15 0x558934de341b in xwl_read_events (xwl_screen=0x558935cffa40) at ../../../../../hw/xwayland/xwayland.c:598 #16 0x558934f54cb1 in ospoll_wait (ospoll=0x558935cf4a20, timeout=) at ../../../../os/ospoll.c:412 #17 0x558934f4dcbb in WaitForSomething (are_ready=) at ../../../../os/WaitFor.c:226 #18 0x558934f199f3 in Dispatch () at ../../../../dix/dispatch.c:422 #19 0x558934f1dc90 in dix_main (argc=11, argv=0x7ffd318bb4f8, envp=) at ../../../../dix/main.c:287 #20 0x7fce6a30b1c1 in __libc_start_main (main=0x558934de2a60 , argc=11, argv=0x7ffd318bb4f8, init=, fini=, rtld_fini=, stack_end=0x7ffd318bb4e8) at ../csu/libc-start.c:308 #21 0x558934de2a9a in _start () ** This bug has been marked a duplicate of bug 1731911 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747910 Title: Crashes on DP hotplug (wl_registry@2: error 0: invalid global wl_output (29)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747910] [NEW] Crashes on DP hotplug (wl_registry@2: error 0: invalid global wl_output (29))
Public bug reported: I switched to a new external monitor at work today. I cannot reproduce the exact sequence of events, but it was basically: plug in external monitor (via DisplayPort), suspend laptop, unplug that monitor and plug in another one, resume laptop. At that point I was staring at the GDM login screen because gnome-shell had crashed on me. (It's hard to understand what happened exactly, from the journal, but it may've been Xwayland that crashed -- I've an Xwayland crash file in /var/crash with a matching timestamp -- but the entire GNOME session died soon afterwards.) Highlights from journalctl: Vas 07 15:04:27 platonas gtimelog[27075]: Error 71 (Protokolo klaida) dispatching to Wayland display. Vas 07 15:04:27 platonas gsd-color[3440]: no xrandr-Goldstar Company Ltd-LG ULTRAWIDE-316961 device found: Failed to find output xrandr-Goldstar Company Ltd-LG ULTRAWIDE-316961 Vas 07 15:04:27 platonas evolution-alarm[4513]: Error 71 (Protokolo klaida) dispatching to Wayland display. Vas 07 15:04:27 platonas update-notifier[5165]: Error 71 (Protokolo klaida) dispatching to Wayland display. Vas 07 15:04:27 platonas xdg-desktop-por[5317]: Error 71 (Protokolo klaida) dispatching to Wayland display. Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: Fatal server error: Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) wl_registry@2: error 0: invalid global wl_output (29) Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) Vas 07 15:04:27 platonas systemd[4065]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Vas 07 15:04:27 platonas systemd[4065]: xdg-desktop-portal-gtk.service: Unit entered failed state. Vas 07 15:04:27 platonas systemd[4065]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. ... Vas 07 15:04:34 platonas org.gnome.Shell.desktop[4166]: xcb_connection_has_error() grąžino reikšmę "true" ... Vas 07 15:04:34 platonas gnome-shell[4166]: Connection to xwayland lost Vas 07 15:04:34 platonas org.gnome.Shell.desktop[4166]: == Stack trace for context 0x564a010d2000 == ... Vas 07 15:04:35 platonas gnome-session[4081]: gnome-session-binary[4081]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Vas 07 15:04:35 platonas gnome-session-binary[4081]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Vas 07 15:04:35 platonas gnome-session-binary[4081]: Unrecoverable failure in required component org.gnome.Shell.desktop ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Feb 7 15:20:24 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-10 (515 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (110 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Description changed: I switched to a new external monitor at work today. I cannot reproduce the exact sequence of events, but it was basically: plug in external monitor (via DisplayPort), suspend laptop, unplug that monitor and plug - in another one, resume laptop. At that point I was starting at the GDM + in another one, resume laptop. At that point I was staring at the GDM login screen because gnome-shell had crashed on me. (It's hard to understand what happened exactly, from the journal, but it may've been Xwayland that crashed -- I've an Xwayland crash file in /var/crash with a matching timestamp -- but the entire GNOME session died soon afterwards.) Highlights from journalctl: - Vas 07 15:04:27 platonas gtimelog[27075]: Error 71 (Protokolo klaida) dispatching to Wayland display. - Vas 07 15:04:27 platonas gsd-color[3440]: no xrandr-Goldstar Company Ltd-LG ULTRAWIDE-316961 device found: Failed to find output xrandr-Goldstar Company Ltd-LG ULTRAWIDE-316961 - Vas 07 15:04:27 platonas evolution-alarm[4513]: Error 71 (Protokolo klaida) dispatching to Wayland display. - Vas 07 15:04:27 platonas update-notifier[5165]: Error 71 (Protokolo klaida) dispatching to Wayland display. - Vas 07 15:04:27 platonas xdg-desktop-por[5317]: Error 71 (Protokolo klaida) dispatching to Wayland display. - Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) - Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: Fatal server error: - Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) wl_registry@2: error 0: invalid global wl_output (
[Bug 1637797] Re: kernel referred to by /*.old autoremoved
One interesting thing is that this bug didn't manifest on other Ubuntu 14.04 LTS servers. I've a couple of sibling servers that are supposed to be exact copies (one is a hot standby for the other). One of them is now down to just one kernel, with two kernels listed in /etc/apt/apt.conf.d/01autoremove- kernels. The other has two kernels left, but it has *three* kernels listed in /etc/apt/apt.conf.d/01autoremove-kernels. In both cases some of the kernels listed in APT::NeverAutoRemove did get removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637797 Title: kernel referred to by /*.old autoremoved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1637797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637797] Re: kernel referred to by /*.old autoremoved
FWIW I can reinstall linux-image-3.13.0-139-generic, mark it as autoremovable with apt-mark auto linux-image-3.13.0-139-generic, and at that point apt-get autoremove doesn't try to remove it any more. (But the apt-get install didn't restore /vmlinuz.old or /initrd.img.old symlinks.) I'm not sure how to reproduce the original bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637797 Title: kernel referred to by /*.old autoremoved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1637797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637797] Re: kernel referred to by /*.old autoremoved
I accidentally ran apt-get autoremove twice on a couple of Ubuntu 14.04
LTS servers, and it removed the stale kernel (on 1st run) and the old
kernel (on 2nd run), leaving the latest kernel the only one available in
/boot.
The .old kernel was linux-headers-3.13.0-139-generic, and if I look at
/etc/apt/apt.conf.d/01autoremove-kernels, I see that it should've been
kept:
// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
"^linux-image-3\.13\.0-139-generic$";
"^linux-image-3\.13\.0-141-generic$";
"^linux-headers-3\.13\.0-139-generic$";
"^linux-headers-3\.13\.0-141-generic$";
"^linux-image-extra-3\.13\.0-139-generic$";
"^linux-image-extra-3\.13\.0-141-generic$";
"^linux-signed-image-3\.13\.0-139-generic$";
"^linux-signed-image-3\.13\.0-141-generic$";
"^kfreebsd-image-3\.13\.0-139-generic$";
"^kfreebsd-image-3\.13\.0-141-generic$";
"^kfreebsd-headers-3\.13\.0-139-generic$";
"^kfreebsd-headers-3\.13\.0-141-generic$";
"^gnumach-image-3\.13\.0-139-generic$";
"^gnumach-image-3\.13\.0-141-generic$";
"^.*-modules-3\.13\.0-139-generic$";
"^.*-modules-3\.13\.0-141-generic$";
"^.*-kernel-3\.13\.0-139-generic$";
"^.*-kernel-3\.13\.0-141-generic$";
"^linux-backports-modules-.*-3\.13\.0-139-generic$";
"^linux-backports-modules-.*-3\.13\.0-141-generic$";
"^linux-tools-3\.13\.0-139-generic$";
"^linux-tools-3\.13\.0-141-generic$";
};
The timestamp of /etc/kernel/postinst.d/apt-auto-removal is very recent,
so I cannot guarantee that it had the same contents at the time of my
second apt-get autoremove run.
(Thankfully, running apt-get autoremove for the third time does not try
to remove my current--and only--kernel.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637797
Title:
kernel referred to by /*.old autoremoved
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1637797/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743886] [NEW] TypeError: unsupported operand type(s) for -=: 'Retry' and 'int'
Public bug reported:
I'm trying to build a Debian package that uses dh-python, pybuild, and
tox.
debuild -i runs dpkg-buildpackage, which runs debian/rules build, which
runs dh build --with python2,python3 --buildsystem=pybuild, which runs
dh_auto_test -O--buildsystem=pybuild, which runs tox -c .../tox.ini -e
py27, which runs /usr/bin/python3 -m virtualenv --python
/usr/bin/python2.7 py27, which fails with a traceback in .../pthurllib3:
Installing setuptools, pkg_resources, pip, wheel...
Complete output from command /home/mg/src/pov-ser...x/py27/bin/python2.7 -
setuptools pkg_resources pip wheel:
Collecting setuptools
Exception:
Traceback (most recent call last):
File
"/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/basecommand.py",
line 215, in main
status = self.run(options, args)
File
"/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/commands/install.py",
line 353, in run
wb.build(autobuilding=True)
File "/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/wheel.py",
line 749, in build
self.requirement_set.prepare_files(self.finder)
File
"/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/req/req_set.py",
line 380, in prepare_files
ignore_dependencies=self.ignore_dependencies))
File
"/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/req/req_set.py",
line 554, in _prepare_file
require_hashes
File
"/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/req/req_install.py",
line 278, in populate_link
self.link = finder.find_requirement(self, upgrade)
File "/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/index.py",
line 465, in find_requirement
all_candidates = self.find_all_candidates(req.name)
File "/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/index.py",
line 423, in find_all_candidates
for page in self._get_pages(url_locations, project_name):
File "/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/index.py",
line 568, in _get_pages
page = self._get_page(location)
File "/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/index.py",
line 683, in _get_page
return HTMLPage.get_page(link, session=self.session)
File "/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/index.py",
line 792, in get_page
"Cache-Control": "max-age=600",
File
"/home/mg/src/pov-server-page/pkgbuild/pov-server-page/.tox/py27/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py",
line 501, in get
return self.request('GET', url, **kwargs)
File
"/usr/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/download.py", line
386, in request
return super(PipSession, self).request(method, url, *args, **kwargs)
File
"/home/mg/src/pov-server-page/pkgbuild/pov-server-page/.tox/py27/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py",
line 488, in request
resp = self.send(prep, **send_kwargs)
File
"/home/mg/src/pov-server-page/pkgbuild/pov-server-page/.tox/py27/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py",
line 609, in send
r = adapter.send(request, **kwargs)
File
"/home/mg/src/pov-server-page/pkgbuild/pov-server-page/.tox/py27/share/python-wheels/CacheControl-0.11.7-py2.py3-none-any.whl/cachecontrol/adapter.py",
line 47, in send
resp = super(CacheControlAdapter, self).send(request, **kw)
File
"/home/mg/src/pov-server-page/pkgbuild/pov-server-page/.tox/py27/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/adapters.py",
line 423, in send
timeout=timeout
File
"/home/mg/src/pov-server-page/pkgbuild/pov-server-page/.tox/py27/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py",
line 643, in urlopen
_stacktrace=sys.exc_info()[2])
File
"/home/mg/src/pov-server-page/pkgbuild/pov-server-page/.tox/py27/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/util/retry.py",
line 315, in increment
total -= 1
TypeError: unsupported operand type(s) for -=: 'Retry' and 'int'
...Installing setuptools, pkg_resources, pip, wheel...done.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/virtualenv.py", line 2375, in
main()
File "/usr/lib/python3/dist-packages/virtualenv.py", line 724, in main
symlink=options.symlink)
File "/usr/lib/python3/dist-packages/virtualenv.py", line 992, in
create_environment
download=download,
File "/usr/lib/python3/dist-packages/virtualenv.py", line 922, in
install_wheel
call_subprocess(cmd, show_stdout=False, extra_env=env, stdin=SCRIPT)
File "/usr/lib/python3/dist-packages/virtualenv.py", line 817, in
call_subprocess
% (cmd_desc, proc.returncode))
OSError: Command /home/mg/src/pov-ser...x/py27/bin/python2.7 - setuptools
pkg_resources pip wheel failed with error code 2
Running virtualenv with interpreter /usr/bin/python2.7
ERROR: InvocationEr
[Bug 1743886] Re: TypeError: unsupported operand type(s) for -=: 'Retry' and 'int'
To clarify: this is a bug in urllib3 as bundled in python-pip, that shows up only when PyPI is unavailable. Pybuild sets https_proxy=https://127.0.0.1:9/ to forcefully make PyPI unavailable during the package build. (There's probably a sibling bug lurking around: why is python3-virtualenv attempting to pip install stuff from PyPI instead of using the bundled python-setuptools wheels?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743886 Title: TypeError: unsupported operand type(s) for -=: 'Retry' and 'int' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1743886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742903] [NEW] Microcode updates require a reboot to apply, but package postinst doesn't touch /run/reboot-required
Public bug reported: The intel-microcode postinst script prints this text to standard error intel-microcode: microcode will be updated at next boot but tools like unattended-upgrades don't parse stderr, they expect a /run/reboot-required to exist to tell them that a reboot is needed to complete the update. Can you fix the postinst script to touch /run/reboot-required? ** Affects: intel-microcode (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742903 Title: Microcode updates require a reboot to apply, but package postinst doesn't touch /run/reboot-required To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1742903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742483] Re: Kernel 4.4.0-108-generic fails to boot on this machine
*** This bug is a duplicate of bug 1741934 *** https://bugs.launchpad.net/bugs/1741934 The 4.4.0-109-generic kernel boots fine! Thank you. ** This bug has been marked a duplicate of bug 1741934 Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742483 Title: Kernel 4.4.0-108-generic fails to boot on this machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742483] [NEW] Kernel 4.4.0-108-generic fails to boot on this machine
Public bug reported: Kernel 4.4.0-108-generic fails to boot on one particular x86-64 machine I have here. The screen goes blank (backlight is on), no cursor visible, no reaction to keyboard (CapsLock/NumLock/Ctrl+Alt+Del/Alt- SysRq-S,U,B all do nothing), no reaction to power button (unless I hold it down for like 10 seconds, which turns off the machine). If I choose rescue mode in GRUB, I see a truncated call trace (attached). Shift+PageUp does not work, so I can't see the beginning. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jan 10 17:57:56 2018 HibernationDevice: RESUME=UUID=f697408a-0779-4641-b284-ab40bad8f24c MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/hostname-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-17 (511 days ago) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742483 Title: Kernel 4.4.0-108-generic fails to boot on this machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742483] Re: Kernel 4.4.0-108-generic fails to boot on this machine
** Attachment added: "screenshot of the kernel call trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742483/+attachment/5034541/+files/IMG_20180110_181235.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742483 Title: Kernel 4.4.0-108-generic fails to boot on this machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I can confirm that the #294 fix worked on Lenovo Yoga 2 11". I have installed kernel 4.14.9 via ukuu and it unlocked BIOS. I can save BIOS settings, dual boot into Windows and I can boot from USB memory sticks. In the end I have removed kernel 4.14.9 and now using the latest 4.13.0-21-generic. I would like to thank everyone who spent time investigating and fixing this. I didn't think this would be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738644] [NEW] pkg-create-dbgsym removes debhelper 10
Public bug reported: When trying to install pkg-create-dbgsym it removed debhelper 10 on artful ** Affects: pkg-create-dbgsym (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738644 Title: pkg-create-dbgsym removes debhelper 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkg-create-dbgsym/+bug/1738644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1737589] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Please how to ga back to python?? Cordialement *Marius NGADOM* Web & Mobile developer, Marketer, Community Manager Tel : (237) 699 120 192 - 243 199 566 Mail : marius.nga...@gmail.com Site : http://www.lecamerounaisinfo.com *Si vous voulez aller vite: allez-y seul, si vous voulez aller loin: allez-y ensemble ...* 2017-12-11 19:48 GMT+01:00 Mattia Rizzolo : > indeed, having the `python` in the path being a python3 is not supported. > Don't do it. > > ** Changed in: libxml2 (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1737589 > > Title: > package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to > install/upgrade: subprocess new pre-removal script returned error exit > status 1 > > Status in libxml2 package in Ubuntu: > Invalid > > Bug description: > i have problem to update my Ubuntu > > i have use some code line on internet to make my Ubuntu see my Iphone > i think i have alias python 2 to 3 form installation i have made > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3 > Uname: Linux 4.10.10-041010-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.12 > Architecture: amd64 > Date: Mon Dec 11 19:20:39 2017 > ErrorMessage: subprocess new pre-removal script returned error exit > status 1 > InstallationDate: Installed on 2016-12-30 (346 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.3 >apt 1.2.24 > SourcePackage: libxml2 > Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to > install/upgrade: subprocess new pre-removal script returned error exit > status 1 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/ > 1737589/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737589 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1737589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737589] [NEW] package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: i have problem to update my Ubuntu i have use some code line on internet to make my Ubuntu see my Iphone i think i have alias python 2 to 3 form installation i have made ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3 Uname: Linux 4.10.10-041010-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 Date: Mon Dec 11 19:20:39 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-12-30 (346 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737589 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1737589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I see Tobia already submitted apport-collect 1734147. Would you like a second set from me as well or is one set of data enough? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Regarding UEFI vs Legacy mode. If I understand it correctly it happened in UEFI and not Legacy mode. I am not sure but I think my Lenovo Yoga 2 doesn't have Legacy "old school" BIOS and it only has UEFI. It has "BIOS backport" feature but I don't know if that's what you mean. In either case BIOS backport was disable by default on the laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I can confirm the same problem on Lenovo Yoga 2 11". Model Name: 20332. TL;DR: Bios does not save any changes, i.e. Secure Boot cannot be switched back on USB boot devices are not detected I wanted to install Ubuntu along Windows 10 (dual boot). It was clean an simple install of Ubuntu 17.04. When I installed 17.04 version I found out that I need to disable Secure Boot in Bios in order for WiFi module to work with included proprietary drivers. Which I did and Wifi worked fine.Then I upgraded to 17.10, the upgrade process was simple and no errors shown. After playing with 17.10 for a bit I wanted to boot back into Windows and was greeted by black screen and no disk activity after selecting Windows Boot Manager. I thought that the problem may be because Secure boot was still disabled in Bios. I went into Bios and tried to enable it. Obviously it had no effect since after several attempts I went into Bios and realised that any changes I make in Bios are not saved anymore like for almost everyone on this thread. Then I tried to boot from Ubuntu Live 17.04, thinking that may be I would be able to debug better in the previous Ubuntu version. Then I realised that I can't boot with the very same bootable flash disk I used to install Ubuntu 17.04. This leaves me with a (currently still) working version of Ubuntu 17.10, no ability to boot into Windows Safe/Recovery Mode and no option to boot from bootable USB disks. When I install/upgrade an OS I am prepared to lose the data on the HDD, in the worst case scenario... But not to brick the motherboard/system!!! :-O What year is this? 1985? Any help appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
This happened again, while trying to upgrade libpq-dev libpq5 postgresql-9.3 postgresql-client-9.3. Running `unattended-upgrade -v` over an interactive SSH session succeeded. I'm not sure what's different. Locale? The successful installation log contains some non-ASCII characters, specifically dpkg's (Skaitoma duomenų bazė ... 53857 files and directories currently installed.) But if that were the problem, then every upgrade would fail, not just some of them. (Besides, if the locale were missing from the cron environment, dpkg wouldn't be using translations.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721577] Re: switch monitor configurations crash-freezes desktop
Upstream bugs that look similar to this one: - https://bugzilla.gnome.org/show_bug.cgi?id=787637 - https://bugzilla.gnome.org/show_bug.cgi?id=788764 ** Bug watch added: GNOME Bug Tracker #787637 https://bugzilla.gnome.org/show_bug.cgi?id=787637 ** Bug watch added: GNOME Bug Tracker #788764 https://bugzilla.gnome.org/show_bug.cgi?id=788764 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721577 Title: switch monitor configurations crash-freezes desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728062] [NEW] MIRC color code stripping too greedy
Public bug reported: I'm trying to use Polari as my IRC client. I've discovered that telepathy-idle is stripping parts of messages it shouldn't be stripping, if you have a sequence of digits (like a git commit hash) right after a mIRC color code (\x03nn). This is upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=761957 and it's already been fixed by https://bugs.freedesktop.org/show_bug.cgi?id=94189. Upstream commit that fixes this: https://cgit.freedesktop.org/telepathy /telepathy-idle/commit/src/idle- ctcp.c?id=cf646c5c0d8a47ae15e4ecbea015b75c56eea4a0. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: telepathy-idle 0.2.0-2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 27 17:08:10 2017 InstallationDate: Installed on 2016-09-10 (412 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: telepathy-idle UpgradeStatus: Upgraded to artful on 2017-10-19 (7 days ago) ** Affects: telepathy-idle (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728062 Title: MIRC color code stripping too greedy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-idle/+bug/1728062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721049] Re: "Got unknown content type text/html" error viewing flatpack packages
** Bug watch added: GNOME Bug Tracker #789352 https://bugzilla.gnome.org/show_bug.cgi?id=789352 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=789352 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721049 Title: "Got unknown content type text/html" error viewing flatpack packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1721049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288655] Re: terminal gets smaller when maximized and then restored
** Bug watch added: GNOME Bug Tracker #751064 https://bugzilla.gnome.org/show_bug.cgi?id=751064 ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=751064 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: terminal gets smaller when maximized and then restored To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 ** This bug has been marked a duplicate of bug 1288655 terminal gets smaller when maximized and then restored -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723368] Re: terminal window shrinks by 1 column and 1 row each time it is unmaximised
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 This looks like a duplicate of bug 1288655. ** This bug has been marked a duplicate of bug 1288655 terminal gets smaller when maximized and then restored -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723368 Title: terminal window shrinks by 1 column and 1 row each time it is unmaximised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1723368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
Duplicate of bug 1288655? BTW I cannot confirm that not using colors fixes the issue; even if I set PS1='$ ', I still get shrinkage after repeated maximizing/restoring or fullscreening/restoring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key
This doesn't look like a terminal problem. It looks like a kernel problem -- some input device is spamming fake key press events. It would be useful if you could determine which device is sending these events. I would run `sudo evemu-record`, pick each device in turn, to see if it sees repeating events or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722298 Title: keyboard autorepeat not happening when I hold down any key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688528] Re: gnome-terminal with screen interprets mouse wheel events as up/down
I've been using this in my ~/.screenrc to tell screen not to switch to the alternate screen, so I can use my scrollback: termcapinfo xterm|xterm-256color ti=\E7\E[?47l:te=\E[H\E[2J\E[?47l This also enables mouse wheel scrolling of the scrollback (as long as you don't turn on 'mousetrack' in your .screenrc). ** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688528 Title: gnome-terminal with screen interprets mouse wheel events as up/down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1688528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=780622 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688391] Re: Highlight of links in terminal is not very smart
** Summary changed: - Highlight of links in terminal is retarded + Highlight of links in terminal is not very smart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688391 Title: Highlight of links in terminal is not very smart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1688391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609009] Re: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)
** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion ** Changed in: vte2.91 (Ubuntu) Status: New => Opinion ** Changed in: ubuntu-gnome Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609009 Title: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1609009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535169] Re: specify error
What are the steps to reproduce this? When I run gnome-terminal in a terminal window in 17.10 all I get is Warning: DESKTOP_STARTUP_ID not set and no fallback available. This doesn't change if I export PYTHONWARNINGS=all beforehand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535169 Title: specify error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1535169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605397] Re: gnome-terminal doesn't return to its original size when unsnapping from the side of the screen
I'm unable to reproduce on 17.10 with gnome-shell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605397 Title: gnome-terminal doesn't return to its original size when unsnapping from the side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1605397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637688] Re: Terminal and file manager scrolls inverted
The old way of mouse wheel scrolling was mice would emit discrete button 4 and 5 events, and scrolling was jumpy. The new way of mouse wheel scrolling is via XInput2, you get two additional axes (vertical and horizontal scroll events) that give you more fine-grained positions. This way you can get smooth scrolling with a touchpad. When you remap mouse buttons, this can only affect older applications that do not support smooth mouse wheel scrolling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637688 Title: Terminal and file manager scrolls inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1637688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496829] Re: when the set command is passed without any parameters it throws some sort of source code on the screen
`set` is a bash builtin command that displays the names values of all shell variables when invoked without any arguments. Shell functions are implemented as variables, technically (although you cannot see the body of the function with echo $functionname). This is working as designed and has noting to do with gnome-terminal. ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496829 Title: when the set command is passed without any parameters it throws some sort of source code on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1496829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525579] Re: terminal freezes when I use : run-mozilla.sh
** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525579 Title: terminal freezes when I use : run-mozilla.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1525579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429584] Re: gnome-terminal doesn't set $COLORTERM from 3.14 onwards
** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429584 Title: gnome-terminal doesn't set $COLORTERM from 3.14 onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1429584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406980] Re: /etc/profile does not get sourced when logging into a terminal window
(Although TBH you're right when you say /etc/profile isn't sourced on Ubuntu -- that's because the default gnome-terminal profile doesn't run the shell as a login shell. There's a checkbox in the profile preferences dialog you can toggle to enable that.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406980 Title: /etc/profile does not get sourced when logging into a terminal window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1406980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288655] Re: terminal gets smaller when maximized and then restored
Bug 1233205 was a bug in Unity and/or Compiz. Ubuntu 17.10 uses gnome- shell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: terminal gets smaller when maximized and then restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341667] Re: Ctrl+Backspace should send ^W instead of doing the same thing as Backspace
** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341667 Title: Ctrl+Backspace should send ^W instead of doing the same thing as Backspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1341667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406980] Re: /etc/profile does not get sourced when logging into a terminal window
Ubuntu's default ~/.bashrc (copied over from /etc/skel/.bashrc when you create new user accounts) overrides PS1 when $TERM is xterm*. When you open new terminal windows or tabs, bash sources /etc/bash.bashrc and then ~/.bashrc, and thus your global PS1 setting is overwritten. Do the change in ~/.bashrc instead of in /etc and you'll be fine. ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406980 Title: /etc/profile does not get sourced when logging into a terminal window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1406980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1356433] Re: detached tabs can not be reattached
Current versions of gnome-terminal (3.24 in Ubuntu 17.10) no longer allow you to detach and reattach tabs via drag and drop. Instead there's a context menu option that lets you detach tabs, but AFAICS there's no way to reattach them back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1356433 Title: detached tabs can not be reattached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1356433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978173] Re: $PATH not being honored
** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/978173 Title: $PATH not being honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/978173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932940] Re: gnome-terminal intercepts ctrl-f1 making it unusable for applications running within
This seems fixed? I can open gnome-terminal, run cat, hit Ctrl+F1 and see ^[[1;5P ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932940 Title: gnome-terminal intercepts ctrl-f1 making it unusable for applications running within To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/932940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288655] Re: terminal gets smaller when maximized and then restored
The bug is still present in 17.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: terminal gets smaller when maximized and then restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989611] Re: terminal not working properly problem inside usr/bin
** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989611 Title: terminal not working properly problem inside usr/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/989611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792341] Re: gnome-terminal is sometimes not adding trailing slash when [Tab] used
Tab-completion is implemented by your shell (bash, most likely), not by gnome-terminal. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792341 Title: gnome-terminal is sometimes not adding trailing slash when [Tab] used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/792341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 885148] Re: Spurious blank lines in gnome-terminal
I've seen this kind of problem when my disk was full. Since gnome- terminal stores the scrollback buffer in a (deleted) file in /tmp, when the disk fills up, scrollback gets lost. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/885148 Title: Spurious blank lines in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/885148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263637] Re: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab
I've just noticed that Debian carries a patch for reading the working directory from /proc if OSC 7 was not in use. This patch doesn't have the "let's look for $PWD in the environment" logic that was supposed to fix this bug. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712628 ** Bug watch added: Debian Bug tracker #712628 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712628 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263637 Title: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/263637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 902679] Re: Alt 1,2,etc does not change terminal page
** Summary changed: - Alt 1,2,etc does to change terminal page + Alt 1,2,etc does not change terminal page -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/902679 Title: Alt 1,2,etc does not change terminal page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/902679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282688] Re: patch adds ubuntu specific pref in global namespace
2017 update: - there's no gconf - there's no alternate_screel_scroll preference added by ubuntu patches - but there are some new transparency-related preferences added to the gsettings schema The current patch at https://patches.ubuntu.com/g/gnome-terminal/gnome- terminal_3.24.2-0ubuntu4.patch adds these preferences - use-transparent-background - use-theme-transparency - background-transparency-percent However I believe the same transparency patch is also shipped by Debian and Fedora, so an ubuntu prefix would not be appropriate. Perhaps this bug ought to be closed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/282688 Title: patch adds ubuntu specific pref in global namespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/282688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263637] Re: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab
This is still a problem in Ubuntu 17.10, if your shell doesn't use OSC 7 to inform gnome-terminal about the current working directory. In theory /etc/profile.d/vte-2.91.sh should set it up automatically, but for some reason that doesn't happen for me. I think that reason is because in Ubuntu gnome-terminal doesn't launch login shells by default, and thus /etc/profile is ignored. I don't know why the commits from 2012 that are supposed to check $PWD do not work any more. Perhaps a newer version removed them, when the OSC 7 was deemed to be the correct solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263637 Title: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/263637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] Re: Unattended upgrade fails with "Error in function"
This happened again this morning, on a different VPS, while trying to upgrade curl libcurl3 libcurl3-gnutls linux-libc-dev. My guess that this had something to do with ca-certificates upgade printing non-ASCII strings to the output was proven wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721294] [NEW] Unattended upgrade fails with "Error in function"
Public bug reported: This is the cron email I received today: From: root To: r...@pov.lt Subject: unattended-upgrades result for 'iv-4.pov.lt': 'False' Date: Wed, 4 Oct 2017 03:40:19 +0300 (EEST) Unattended upgrade returned: False Packages that attempted to upgrade: ca-certificates libidn11 libnss3 libnss3-nssdb Package installation log: Error in function: Unattended-upgrades log: Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=trusty-security', 'o=UbuntuESM,a=trusty', 'o=Ubuntu,a=trusty-security', 'o=Ubuntu,a=trusty-updates', 'origin=LP-PPA-pov,suite=trusty'] Packages that will be upgraded: ca-certificates libidn11 libnss3 libnss3-nssdb Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log' Installing the upgrades failed! error message: 'installArchives() failed' dpkg returned a error! See '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log' for details Packages that are auto removed: '' Packages auto-removed The named log file, var/log/unattended-upgrades/unattended-upgrades- dpkg_2017-10-04_03:40:17.411277.log contains only this: Error in function: That's it. Now given that ca-certificates is involved, I suspect this may be related to non-ASCII filenames (see bug 1554365), but unlike that bug, here the upgrade fails instead of succeeding, and the actual error is not shown anywhere. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.5 Uname: Linux 2.6.32-042stab124.2 x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 Date: Wed Oct 4 18:54:54 2017 PackageArchitecture: all ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=lt_LT.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721294 Title: Unattended upgrade fails with "Error in function" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)
It looks like the unattended upgrade itself was successful, it's just that instead of the usual email showing me the upgrade log I get this traceback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554365 Title: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)
Last night's update gave me two more of these errors, both in OpenVZ containers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554365 Title: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719159] [NEW] 'service procps start' does nothing
Public bug reported: /etc/sysctl.d/README says After making any changes, please run "service procps start" (or, from a Debian package maintainer script "invoke-rc.d procps start"). however running this command does absolutely nothing on Ubuntu 17.04 (and, presumably, any other Ubuntu version since systemd became the main init system). To actually get your changes written into /proc/sys, you have to do service procps reload Can you please update the README? (This is similar to bug 1332362, but I think that one was Upstart's fault.) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: procps 2:3.3.12-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 24 11:26:45 2017 InstallationDate: Installed on 2016-09-10 (379 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: procps UpgradeStatus: Upgraded to zesty on 2017-04-14 (163 days ago) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719159 Title: 'service procps start' does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1719159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718371] Re: Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out"
Here's the full journal log of the shutdown process. ** Attachment added: "Journal of the shutdown process" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718371/+attachment/4953370/+files/reboot-hangs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718371 Title: Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718371] [NEW] Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out"
Public bug reported: This morning unattended-upgrades had a reboot scheduled for 6:30 AM. The reboot process succeeded in turning off all network access but failed to actually reboot. As far as I can tell, this is because Sep 20 06:50:44 fridge systemd[1]: Starting Reboot... Sep 20 06:51:09 fridge systemctl[3886]: Failed to execute operation: Connection timed out Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Main process exited, code=exited, status=1/FAILURE Sep 20 06:53:54 fridge systemd[1]: Failed to start Reboot. Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Unit entered failed state. Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Failed with result 'exit-code'. (Don't ask me why it took 20 minutes to get to this point. Most everything was already shut down by 06:35.) After this the journal shows a few other random-looking service messages Sep 20 07:13:44 fridge systemd[1]: Stopping LVM2 metadata daemon... Sep 20 07:13:44 fridge systemd[1]: Stopped LVM2 metadata daemon. Sep 20 07:51:48 fridge systemd[1]: Started LVM2 metadata daemon. Sep 20 07:51:48 fridge systemd[1]: Stopped target Shutdown. and the end of a cron session that initiated the unattended-upgrade shutdown -r 06:30 call, presumably Sep 20 07:52:54 fridge CRON[1176]: pam_unix(cron:session): session closed for user root and then the machine sat idle waiting for keyboard input, which I provided in the form of Alt+SysRq+S,U,B a few hours later. This has never happened before on this server, which is running Ubuntu 16.04 LTS since November 2016. I haven't tried to reproduce this (yet). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Sep 20 11:10:34 2017 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic root=/dev/mapper/hostname-root ro nomdmonddf nomdmonisw SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-11-07 (316 days ago) dmi.bios.date: 10/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG33TL dmi.board.vendor: Intel Corporation dmi.board.version: AAD89517-803 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33TL:rvrAAD89517-803:cvn:ct2:cvr: ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718371 Title: Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648183] Re: Crackling and popping sound when using headphones
I confirm Robert Joynt's fix is working on HP Pavilion x360 Convertible 13-u103nq. Thanks Erikas for the systemd workaround, but let's hope it will be fixed soon upstream, especially that there's already a patch [1] in place. [1] https://patchwork.kernel.org/patch/9142225/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716653] [NEW] update-apt-xapian-index burning 100% CPU for two weeks
Public bug reported: I accidentally noticed that one of my Ubuntu 14.04 LTS servers hasn't been applying unattended updates for a while. Some digging shows that this is because update-apt-xapian-index started on August 27 is still running (and eating 100% CPU, for over two weeks)!, which blocks all other /etc/cron.daily/ scripts from running. Every night cron starts a new run, which gets blocked by a new instance of update-apt-xapian- index: $ pstree ... |-cron-+-16*[cron---sh---run-parts---apt---update-apt-xapi] | |-2*[cron---sh---run-parts---apt-xapian-inde---update-apt-xapi] | |-cron---sh---run-parts---apt-xapian-inde---update-apt-xapi---cat | `-cron---sh---python strace shows that it's repeatedly reading and writing the same locations in /var/cache/apt-xapian-index/index.2/postlist.DB: pread64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pwrite64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pread64(83, "\0\0\0\3\0\10F\10F\0\21\30\34\10W\0209\20%\20\t\17\365\17\334\17\251\17\223\17~\17"..., 8192, 8871936) = 8192 pwrite64(83, "\0\0\0\3\0\10F\10F\0\21\30\34\10W\0209\20%\20\t\17\365\17\334\17\251\17\223\17~\17"..., 8192, 8871936) = 8192 pread64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pwrite64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pread64(83, "\0\0\0\3\0\10F\10F\0\21\30\34\10W\0209\20%\20\t\17\365\17\334\17\251\17\223\17~\17"..., 8192, 8871936) = 8192 pwrite64(83, "\0\0\0\3\0\10F\10F\0\21\30\34\10W\0209\20%\20\t\17\365\17\334\17\251\17\223\17~\17"..., 8192, 8871936) = 8192 pread64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pwrite64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pread64(83, "\0\0\0\3\0\10F\10F\0\21\30\34\10W\0209\20%\20\t\17\365\17\334\17\251\17\223\17~\17"..., 8192, 8871936) = 8192 pwrite64(83, "\0\0\0\3\0\10F\10F\0\21\30\34\10W\0209\20%\20\t\17\365\17\334\17\251\17\223\17~\17"..., 8192, 8871936) = 8192 pread64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pwrite64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pread64(83, "\0\0\0\3\0\10F\10F\0\21\30\34\10W\0209\20%\20\t\17\365\17\334\17\251\17\223\17~\17"..., 8192, 8871936) = 8192 pwrite64(83, "\0\0\0\3\0\10F\10F\0\21\30\34\10W\0209\20%\20\t\17\365\17\334\17\251\17\223\17~\17"..., 8192, 8871936) = 8192 pread64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 pwrite64(83, "\0\0\0\3\0\rH\rH\0=\30\25\r\205\30\1\27\345\27\321\27\270\27\205\27o\27Z\27\21\26"..., 8192, 8880128) = 8192 I poked around a bit with gdb and dumped the C and Python stack frames, but I'm not sure what to look for. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt-xapian-index 0.45ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-128.177-generic 3.13.11-ckt39 Uname: Linux 3.13.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: i386 Date: Tue Sep 12 13:21:42 2017 PackageArchitecture: all SourcePackage: apt-xapian-index UpgradeStatus: Upgraded to trusty on 2016-03-31 (530 days ago) ** Affects: apt-xapian-index (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716653 Title: update-apt-xapian-index burning 100% CPU for two weeks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1716653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706313] Re: Error creating pool: local variable 'srcname' referenced before assignment
I agree completely. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706313 Title: Error creating pool: local variable 'srcname' referenced before assignment To manage notifications about this bug go to: https://bugs.launchpad.net/virt-manager/+bug/1706313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706313] Re: Error creating pool: local variable 'srcname' referenced before assignment
Forwarded to https://bugzilla.redhat.com/show_bug.cgi?id=1474766 ** Bug watch added: Red Hat Bugzilla #1474766 https://bugzilla.redhat.com/show_bug.cgi?id=1474766 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706313 Title: Error creating pool: local variable 'srcname' referenced before assignment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1706313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706313] [NEW] Error creating pool: local variable 'srcname' referenced before assignment
Public bug reported: I was trying to add an existing LVM volume group as a storage pool in virt-manager. I filled in the volume group name, then got to the dialog with source and target path entries, didn't know what to put there[*], so left them blank and hit Finish. I then got a popup with this Python traceback in it: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createpool.py", line 446, in _async_pool_create poolobj = self._pool.install(create=True, meter=meter, build=build) File "/usr/share/virt-manager/virtinst/storage.py", line 496, in install xml = self.get_xml_config() File "/usr/share/virt-manager/virtinst/xmlbuilder.py", line 834, in get_xml_config return self._do_get_xml_config() File "/usr/share/virt-manager/virtinst/xmlbuilder.py", line 1043, in _do_get_xml_config self._add_parse_bits(node) File "/usr/share/virt-manager/virtinst/xmlbuilder.py", line 1066, in _add_parse_bits return self._do_add_parse_bits(node) File "/usr/share/virt-manager/virtinst/xmlbuilder.py", line 1077, in _do_add_parse_bits prop._set_default(self) File "/usr/share/virt-manager/virtinst/xmlbuilder.py", line 506, in _set_default candefault, val = self._default_get_value(xmlbuilder) File "/usr/share/virt-manager/virtinst/xmlbuilder.py", line 494, in _default_get_value return (True, self._default_cb(xmlbuilder)) File "/usr/share/virt-manager/virtinst/storage.py", line 366, in _default_source_name return srcname UnboundLocalError: local variable 'srcname' referenced before assignment -- [*] eventually I figured out I was supposed to put /dev/vgname in the target path field, which worked fine. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: virt-manager 1:1.3.2-3ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 25 13:51:39 2017 InstallationDate: Installed on 2016-09-10 (318 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: Upgraded to zesty on 2017-04-14 (102 days ago) ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706313 Title: Error creating pool: local variable 'srcname' referenced before assignment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1706313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705433] [NEW] package samba 2:4.4.5+dfsg-2ubuntu5.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: I don't know Ubuntu has just notify me that i send to developer's team the bug rapport ProblemType: Package DistroRelease: Ubuntu 16.10 Package: samba 2:4.4.5+dfsg-2ubuntu5.8 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.7 Architecture: amd64 Date: Thu Jul 20 00:07:50 2017 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2017-02-01 (168 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NmbdLog: Packet send failed to 172.17.1.255(138) ERRNO=Aucun processus enfant Packet send failed to 172.17.1.255(138) ERRNO=Argument invalide RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package samba 2:4.4.5+dfsg-2ubuntu5.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to yakkety on 2017-06-28 (21 days ago) WindowsFailedConnect: Yes ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705433 Title: package samba 2:4.4.5+dfsg-2ubuntu5.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1705433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704094] [NEW] ubuntu-bug xorg
Public bug reported: Wine is stuck on install ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 13 10:59:03 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2017-07-12 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Gigabyte Technology Co., Ltd. H55M-USB3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: H55M-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd11/01/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81+git1707071830.ac2140~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 17.2~git1707130730.c3b5c2~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2~git1707130730.c3b5c2~gd~x version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jul 13 10:23:26 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704094 Title: ubuntu-bug xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632575] Re: systemd starts two copies of ntp at boot time
No, I never saw this again. The very next day after filing this bug I had another monitoring warning about a stale ntpd pidfile, but this time there was no second ntpd process running, and journalctl showed a simple conflict with ntpdate during startup. I apt-get removed ntpdate and never saw any more ntpd problems again on this machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632575 Title: systemd starts two copies of ntp at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1632575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648077] Re: Support for Mozilla Location Service (A-GPS)
** Also affects: ubports-meta Importance: Undecided Status: New ** Changed in: ubports-meta Status: New => Fix Released ** Changed in: ubports-meta Assignee: (unassigned) => Ricardo (ing-mendoza-ricardo) ** Changed in: location-service (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648077 Title: Support for Mozilla Location Service (A-GPS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubports-meta/+bug/1648077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637519] Re: gnome-shell segfaults on resume, leaving my session unlocked
My notes indicate I saw this crash-leaving-helpfully-unlocked-session- after-resume at least 10 times in 16.10, but I don't remember seeing this (and my notes record no crashes) in 17.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637519 Title: gnome-shell segfaults on resume, leaving my session unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1637519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687005] [NEW] Polari shows wrong port number in connection settings
Public bug reported: I'm connecting to my ZNC instance, reachable via an SSH tunnel through localhost:. If I open Polari's connection preferences, it shows me Server address: [ localhost:6697 ] I can try to change it to localhost:, hit apply, close the dialog, and when I open it again, the port is, once again, shown incorrectly as 6697. (If I check Online Accounts in System Preferences, I see that the port is actually .) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: polari 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 28 14:53:48 2017 InstallationDate: Installed on 2016-09-10 (230 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: polari UpgradeStatus: Upgraded to zesty on 2017-04-14 (14 days ago) ** Affects: polari (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687005 Title: Polari shows wrong port number in connection settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/polari/+bug/1687005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687001] Re: Polari won't connect to IRC after an upgrade to 17.04
For the record the problem was that the IRC server password got lost somehow, and went I went to System Preferences -> Online Accounts and entered it again, Polari started working. The bug is that Polari doesn't show a password prompt after getting am AUTHENTICATION_FAILED error from Telepathy. ** Summary changed: - Polari won't connect to IRC after an upgrade to 17.04 + Polari tries forever to connect to IRC with the wrong password, without indicating failure or asking for the correct password -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687001 Title: Polari tries forever to connect to IRC with the wrong password, without indicating failure or asking for the correct password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/polari/+bug/1687001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687001] [NEW] Polari won't connect to IRC after an upgrade to 17.04
Public bug reported: I've upgraded my Ubuntu to 17.04 and now Polari fails to connect to IRC. It just shows the spinner forever. In journalctl I can see Bal 28 14:19:36 platonas org.gnome.Polari[7654]: Account GNOME (ZNC) disconnected with reason AUTHENTICATION_FAILED Bal 28 14:19:36 platonas org.gnome.Polari[7654]: Account FreeNode (ZNC) disconnected with reason AUTHENTICATION_FAILED repeated every couple of minutes, but the Polari UI doesn't indicate that anything's wrong and doesn't ask me for the correct password. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: polari 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 28 14:15:50 2017 InstallationDate: Installed on 2016-09-10 (230 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: polari UpgradeStatus: Upgraded to zesty on 2017-04-14 (14 days ago) ** Affects: polari (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687001 Title: Polari won't connect to IRC after an upgrade to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/polari/+bug/1687001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686759] [NEW] apparmor denies sendmsg to /run/systemd/journal/socket
Public bug reported: While debugging why Polari can no longer connect to IRC servers after an upgrade to Ubuntu 17.04, I noticed the following errors in my journal: Bal 27 18:05:56 platonas audit[4869]: AVC apparmor="DENIED" operation="sendmsg" profile="/usr/lib/telepathy/mission-control-5" name="/run/systemd/journal/socket" pid=4869 comm="mission-control" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 (repeated many times) I also see Bal 27 18:05:56 platonas mission-control-5[4869]: (process:4869): mcd-WARNING **: got error: Account idle/irc/mgedmin0 disconnected with reason 3 so somehow log messages from mission-control-5 still make it, despite the denied journal connection (via syslog maybe?). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: telepathy-mission-control-5 1:5.16.3-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 27 18:16:08 2017 InstallationDate: Installed on 2016-09-10 (229 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: telepathy-mission-control-5 UpgradeStatus: Upgraded to zesty on 2017-04-14 (13 days ago) ** Affects: telepathy-mission-control-5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug wayland-session zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686759 Title: apparmor denies sendmsg to /run/systemd/journal/socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1686759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509183] Re: xl2tpd-1.3.6+dfsg-2build1 periodically crashes if compiled with USE_KERNEL
Bug still present on Ubuntu 16.10. I get these crashes every time I disconnect from my VPN. The Debian bug mentioned in the original description has a link to an upstream commit with the fix, which means the error should already be fixed in xl2tpd 1.3.7. Ubuntu 17.04 is going to have xl2tpd 1.3.8, so this bug should be gone once everyone upgrades. Anyone who wants the fix to be backported to 16.04 LTS or 16.10 could probably help by preparing a SRU (https://wiki.ubuntu.com/StableReleaseUpdates). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509183 Title: xl2tpd-1.3.6+dfsg-2build1 periodically crashes if compiled with USE_KERNEL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1509183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665001] [NEW] In fullscreen mode, the top-center toolbar is not visible.
Public bug reported: In fullscreen mode (VNC), when I move the mouse to the top-center, the hidden toolbar doesn't show up. But I cant blindly click the buttons. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: vinagre 3.22.0-1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Feb 15 15:56:08 2017 InstallationDate: Installed on 2017-02-02 (12 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170126) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: vinagre UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vinagre (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665001 Title: In fullscreen mode, the top-center toolbar is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1665001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662592] [NEW] [20F5S1A600, Intel Skylake HDMI, Digital Out, HDMI] Playback problem
Public bug reported: Hi, I encountered an audio bug on my new ThinkPad X260. Since I was not able to find a fix online I will try to explain my bug and hopefully get it fixed. I'm using Ubuntu 16.04.1 LTS on my X260 with i5-6200. I want to use HDMI with my Samsung TV to watch videos eg. So I connect the HDMI cable, I get my desktop on my TV and in sound settings I can see HDMI Output. When I select HDMI Output I hear a cracking noise from my TV speakers. When I play a test tone, it looks like the TV needs a 1 or 2 seconds to get the tone so I can only hear the end of the tone. When I repeat this test everything works. But when I open a music player eg. or Chrome with YouTube I hear the cracking noise again and I get no sound on my TV. When I close all applications and start the test tone again, I get the same results. To sum it up. Only test tone works with HDMI, i can select the output but dont get any sound. I attach the alsa-info-alsa-info.sh to this report. As this is my first report, feel free to ask for further outputs eg. Kind regards! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marius 2072 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 7 17:42:14 2017 InstallationDate: Installed on 2017-02-06 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Internes Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20F5S1A600, Intel Skylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET50W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S1A600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR02ET50W(1.23):bd09/20/2016:svnLENOVO:pn20F5S1A600:pvrThinkPadX260:rvnLENOVO:rn20F5S1A600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20F5S1A600 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-07T07:13:02.858136 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "alsa-info-alsa-info.sh" https://bugs.launchpad.net/bugs/1662592/+attachment/4814844/+files/alsa-info-alsa-info.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662592 Title: [20F5S1A600, Intel Skylake HDMI, Digital Out, HDMI] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1662592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659517] Re: media keys stopped working: "Could not find accelerator for accel id 123"
I restarted gnome-shell with Alt-F2 r and media keys started working. This is probably a duplicate of one of the other "media keys randomly stop working sometimes" bugs. I was searching for the particular error message and found none -- probably because the error message itself was only added relatively recently (in gnome-settings-daemon 3.20), while upstream tries to figure out what causes this bug. I haven't located the upstream bug report yet. ** Bug watch added: GNOME Bug Tracker #758302 https://bugzilla.gnome.org/show_bug.cgi?id=758302 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659517 Title: media keys stopped working: "Could not find accelerator for accel id 123" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1659517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659517] Re: media keys stopped working: "Could not find accelerator for accel id 123"
The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=758302 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=758302 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659517 Title: media keys stopped working: "Could not find accelerator for accel id 123" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1659517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659517] Re: media keys stopped working: "Could not find accelerator for accel id 123"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839958 looks like a similar bug, except my custom shortcuts (e.g. t to launch gnome- terminal) continue to work fine. ** Bug watch added: Debian Bug tracker #839958 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839958 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659517 Title: media keys stopped working: "Could not find accelerator for accel id 123" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1659517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659517] [NEW] media keys stopped working: "Could not find accelerator for accel id 123"
Public bug reported: Today after an involuntary reboot (laptop battery ran down) I can no longer use media keys like Mute, Volume Up/Down, PrintScreen. Every time I hit one of those keys I see messages like this in journalctl: Sau 26 11:53:30 platonas gnome-settings-[4972]: Could not find accelerator for accel id 123 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-settings-daemon 3.22.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 26 11:56:17 2017 InstallationDate: Installed on 2016-09-10 (138 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to yakkety on 2016-10-15 (102 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659517 Title: media keys stopped working: "Could not find accelerator for accel id 123" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1659517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656776] Re: should depend on apt-transport-https (was: fails to download andale32.exe, spams my cron every night)
This is a libvirt virtual machine that I've installed with ubuntu-vm- builder on a 16.04 LTS host. The full command, if you're interested, was ubuntu-vm-builder kvm xenial \ --libvirt qemu:///system \ --tmpfs=2048 \ --rootsize 20480 \ --ssh-key=/root/.ssh/authorized_keys \ --ssh-user-key=/root/.ssh/authorized_keys\ --lock-user \ --suite xenial \ --components main,restricted,universe,multiverse \ --addpkg openssh-server \ --addpkg avahi-daemon\ --addpkg vim \ --addpkg git \ --addpkg acpid \ --addpkg unattended-upgrades \ --addpkg command-not-found \ --addpkg software-properties-common \ --addpkg openjdk-8-jre-headless \ --addpkg htop\ --addpkg strace \ --addpkg linux-image-generic \ --hostname xenial64 \ --domain lan \ --bridge br0 \ --mem 1024 --cpus 2 etckeeper tells me I've installed ttf-mscorefonts-installer on Aug 18, 2016. At that time I was getting nightly cron errors that looked like this: /etc/cron.daily/update-notifier-common: Err:1 http://downloads.sourceforge.net/corefonts/andale32.exe 403 Forbidden W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/andale32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) E: Failed to fetch http://downloads.sourceforge.net/corefonts/andale32.exe 403 Forbidden E: Download Failed ttf-mscorefonts-installer: downloading http://downloads.sourceforge.net/corefonts/andale32.exe because my local apt proxy was denying sourceforge downloads. When I eventually figured that out and added the right domains to /etc/squid- deb-proxy/mirror-dstdomain.acl on the proxy host, the cron script succeeded downloading and extracting the font files. This was on Aug 23, 2016. Then I have an unattended-upgrades log from 2016-11-04 that upgraded update-notifier-common, which also ran the downloads successfully. And then I have an unattended-upgrades log from 2017-01-06 that upgraded update-notifier-common again, and this one failed with E: The method driver /usr/lib/apt/methods/https could not be found. N: Is the package apt-transport-https installed? and since then every night the cron script with the original message. (I was mistaken about the dates in my original report -- I thought I left all of the cron errors in my inbox, but apparently I'd already saved the errors from Jan 6 through 11 in my mail archive.) I'm fine with this bug being closed as wontfix, since I used a non-standard Ubuntu installation method. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656776 Title: should depend on apt-transport-https (was: fails to download andale32.exe, spams my cron every night) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1656776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656776] Re: should depend on apt-transport-https (was: fails to download andale32.exe, spams my cron every night)
Yep, installing apt-transport-https changes the nightly cron error from the above to a 404 because of a space in the URL. ** Summary changed: - fails to download andale32.exe, spams my cron every night + should depend on apt-transport-https (was: fails to download andale32.exe, spams my cron every night) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656776 Title: should depend on apt-transport-https (was: fails to download andale32.exe, spams my cron every night) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1656776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
