[Bug 1738398] [NEW] Installer crashed
Public bug reported: I got a crash report prompt during installation of 17.10 from USB stick. I have no idea what was going on when it crashed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 15 12:27:49 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=sv_SE.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738398 Title: Installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733322] Re: Unable to enable file or screen sharing with unmanaged network connection
Sebastien, thanks for the quick response. I found an existing upstream bug (https://bugzilla.gnome.org/show_bug.cgi?id=788097) which, while lacking detail, seemed to match. I linked it to this issue. ** Bug watch added: GNOME Bug Tracker #788097 https://bugzilla.gnome.org/show_bug.cgi?id=788097 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=788097 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/1733322 Title: Unable to enable file or screen sharing with unmanaged network connection To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1733322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733322] [NEW] Unable to enable file or screen sharing with unmanaged network connection
Public bug reported: I have installed Ubuntu Server 17.10. At request from a colleague I then tried to install ubuntu-desktop and enable screen sharing. However, this did not work as expected. When trying to enable screen sharing (same goes for file sharing), the enable button just jumps straight back to disabled when toggling it. I assumed this had something to do with the fact that the "networks" list at the bottom of the sharing dialog was empty. This appears in the syslog when trying to toggle: Nov 20 11:31:06 bcubuntu3 gnome-control-c[1054]: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing cannot be enabled on this network, status is '0' This computer has only a single wired network connection (no wifi). This connection shows in the system menu as "Wired unmanaged" which seems to be the reason that it doesn't show up in the sharing dialogs. As a workaround, I tried the following things: 1. Change "managed=false" to "managed=true" in /etc/NetworkManager/NetworkManager.conf as suggested in https://askubuntu.com/a/2905 2. Touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf as suggested in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547 3. Change renderer to NetworkManager in /etc/netplan/01-netcfg.yaml 1 and 2 was not enough to get NetworkManager to manage the wired interface, but 3, possibly together with one or both of the previous steps did the trick. When I finally got NetworkManager to manage the wired connection, it did show up in the sharing dialogs, and I was able to enable screen sharing. However, it would seem reasonable to be able to enable sharing even on unmanaged interfaces by some mechanism, especially since unmanaged interfaces seem to be the norm these days. ~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 gnome-control-center: Installed: 1:3.26.1-0ubuntu5 Candidate: 1:3.26.1-0ubuntu5 Version table: *** 1:3.26.1-0ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.1-0ubuntu4 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages ** Affects: gnome-control-center (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/1733322 Title: Unable to enable file or screen sharing with unmanaged network connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1733322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778578] Re: Problem with window focus when switching virtual desktops
I can confirm this. I am *not* using focus follows mouse. Steps to reproduce (not 100%, it seems to come and go): * Start Firefox on desktop 1, make sure unity launcher is visible * Ctrl+alt+right to desktop 2 * Start Qt Creator * Maximize window or move it so that it makes the launcher auto-hide * Select the editor, typing works. * Ctrl+alt+left to desktop 1 - Firefox gets focus * Ctrl+alt+right to desktop 2 - launcher starts to hide. Qt Creator cursor blinks briefly,, suggesting keyboard focus, but when launcher is done hiding the cursor disappears and keyboard input does not register. Clicking the window does not help, but switching to another app and then back does. It seems related to dock hide/unhide - if I move the QtC window so that it doesn't make the launcher hide (i.e. switching desktops keeps the launcher on the screen), the problem has never occured. Ubuntu 11.10 ii libunity-core-4.0-44.22.0-0ubuntu3 ii libunity-misc4 4.0.4-0ubuntu2 ii libunity6 4.0.6-0ubuntu2 ii unity 4.22.0-0ubuntu3 Qt Creator 2.2.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778578 Title: Problem with window focus when switching virtual desktops To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/778578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771716] Re: middle click emulation not working
Workaround: xinput set-prop device id 257 1. Device id can be obtained with xinput list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771716 Title: middle click emulation not working -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771716] Re: middle click emulation not working
This should be configurable in gnome-mouse-properties I guess - emulation is required to get usable copy/paste with a two-button mouse, so having to hack config files is not really acceptable. Can this bug be moved to that package or should a new one be created? Or are there other options to get this working in a user-friendly fashion? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771716 Title: middle click emulation not working -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771716] Re: middle click emulation not working
This also affects me, using a Logitech Trackman Marble, attaching the output of xinput list ** Attachment added: xinput-list.txt https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/771716/+attachment/2092514/+files/xinput-list.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771716 Title: middle click emulation not working -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410
@Mike: 9.04 worked during the install for me, but then I got random graphics freezes during normal usage (might not be related to this bug). Another workaround that works for me is to use an external display (with 10.04). -- [i915] blank screen on Latitude E6410 https://bugs.launchpad.net/bugs/561802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410
I can also report success with linux-image-2.6.35-20-generic-pae 2.6.35-20.29~lucid1 (from kernel-ppa) on E5410, i3. Screen lights up during boot, suspend/resume works and no crash when connecting/disconnecting external monitor. -- [i915] blank screen on Latitude E6410 https://bugs.launchpad.net/bugs/561802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
I can't even verify the fix - on my E5410 core i3, the screen doesn't even turn on during boot using 2.6.32-25.42 (however, the boot seems to go fine otherwise). I, like dragilla, use the PAE kernel, I also tried the normal one, but then there was some trouble detecting my hard drive and I couldn't boot at all. Passing i915.modeset=0 gives me the boot graphics, but I get a kernel panic at some point during boot (flashing keyboard leds). With the maverick backport from kernel-ppa (2.6.35) I can boot, but after suspend/resume the screen is black (with backlight) until power management kills the backlight. At that point I get back graphics when I touch the keyboard or mouse. -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
@Carlos: that kernel is a pre-proposed one, and as far as I can tell not the one referred to in #106. Thus, I still have the same question as Paulo. -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
I have this issue, but on E5410 (core i3+arrandale). Resume works apart from the screen being blank, i.e. I can ssh into the box and reboot it. However, the backported kernel in #103 does not work for me. I think there is some improvement, because now the backlight turns on, but still no image. If it helps, I can post the kernel log from the resume attempt. -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
Update: When the display backlight is shut down by power management, after a failed resume, everything goes back to normal again (i.e. pressing any key turns on the screen and shows the screen lock prompt). -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
