[Bug 1687577] Re: "Browse" button for Pictures location freezes the UI
Here's the output when I re-run wallch from a terminal. The Glib messages appear when I click Browse: Error: The message '--focus' could not be sent to Wallch. Assuming that the previous Wallch instance crashed and starting a new one now. Sorry for this :) libpng warning: iCCP: known incorrect sRGB profile (wallch:8282): GLib-GObject-WARNING **: cannot register existing type 'GdkWindow' (wallch:8282): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed (wallch:8282): Gdk-CRITICAL **: gdk_window_ensure_native: assertion 'GDK_IS_WINDOW (window)' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687577 Title: "Browse" button for Pictures location freezes the UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallch/+bug/1687577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687577] [NEW] "Browse" button for Pictures location freezes the UI
Public bug reported: When I start up Wallch (never having run it before on this system), I click the "Browse" button for the "Pictures location." Nothing happens, no dialogue appears, and the UI becomes unresponsive. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: wallch 4.0-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue May 2 11:14:37 2017 InstallationDate: Installed on 2017-02-06 (85 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: wallch UpgradeStatus: Upgraded to zesty on 2017-04-18 (14 days ago) ** Affects: wallch (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/1687577 Title: "Browse" button for Pictures location freezes the UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallch/+bug/1687577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Hello? Any corrections for that revisions range you wanted me to bisect? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481184] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: Automatically reported crash. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: nvidia-331-updates-uvm 340.76-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 DKMSBuildLog: DKMS make.log for nvidia-331-updates-uvm-331.113 for kernel 3.19.0-25-generic (i686) Tue Aug 4 12:54:23 ICT 2015 Makefile:216: /var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk: No such file or directory make: *** No rule to make target '/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk'. Stop. DKMSKernelVersion: 3.19.0-25-generic Date: Tue Aug 4 12:54:31 2015 InstallationDate: Installed on 2012-11-27 (979 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) PackageVersion: 331.113-0ubuntu0.1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: nvidia-graphics-drivers-340-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: Upgraded to vivid on 2015-08-01 (2 days ago) ** Affects: nvidia-graphics-drivers-340-updates (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481184 Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1481184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481178] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: Laptop insisted on upgrade from 14.10 to 15.04 on the day before travel. Took hours, so I let it upgrade overnight. Partway through it got stuck on some pointless press-OK-to-acknowledge dialog, so it wasn't done the following morning; there was no way to stop the upgrade and suspend didn't work, so I had to turn the machine off while it was installing. After that, things were of course broken to the point where they need hours more of work in the shell to fix up and complete the upgrade. This is one of several crashes which occurred while completing the upgrade. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 DKMSBuildLog: DKMS make.log for nvidia-331-updates-uvm-331.113 for kernel 3.19.0-25-generic (i686) Tue Aug 4 12:50:38 ICT 2015 Makefile:216: /var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk: No such file or directory make: *** No rule to make target '/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk'. Stop. DKMSKernelVersion: 3.19.0-25-generic Date: Tue Aug 4 12:50:46 2015 InstallationDate: Installed on 2012-11-27 (979 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) PackageVersion: 331.113-0ubuntu0.1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: Upgraded to vivid on 2015-08-01 (2 days ago) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481178 Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1481178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
This last weird effect was transient; it went away after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
It just got a bit weirder. I've got my custom xrandr-defined 2560×1440 resolution going. But for purposes like window placement, resizing windows, and maximising windows, the UI seems to think it's 1920×1080 or thereabouts. So if I open a whole bunch of editor windows from the shell, they all appear in (and eventually fill up) the upper-left part of the screen that looks like it's about 1920×1080 pixels large. I can move a window out of that zone, but I can't resize its lower or right-hand edges outside of it. If I move a window over the edge and then try to resize the window, the edge(s) I'm resizing immediately jump back to fall within that zone. When I move a window completely outside the zone and try to resize it, really strange things happen. A terminal window outside the zone immediately disappears when I try to resize its right-hand edge, as if it's been closed. I can get it back by clicking on the terminal icon in Unity's icon bar, but it's very narrow, and it looks to be dead! It's got a piece of my desktop background in it, and nothing I do convinces it to repaint itself. When I widen it, I just get to see more background, or whatever else was in its path, plus some pollution from the resizing UI. I can still close it with ctrl-d though. I can still type commands into the shell I guess, but "clear" doesn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
This is getting awkward. The upper-bound version you wanted me to bisect is also missing from the Ubuntu/upstream version mapping. So even if I want to bisect upstream versions I still have the same problem. Are you sure you gave me the correct versions for bisection? Maybe you meant 3.13.0-20.42 instead of 3.13.0.20.24? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Thanks. Could you also update that section? It says that it applies in two situations, but it never actually lists those two situations. I *think* (but without already knowing of course I can't be sure) that it's meant to refer to a list of three headings, “BISECTING: A MERGE BASE MUST BE TESTED” etc. I don't see any mention of the situation I ran into, so it may be worth adding that too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Thanks for following up. I read most of that document, but it's difficult in places. My understanding is that what you're asking me to do is what's described under “Commit bisecting Ubuntu kernel versions,” correct? That's the only part of the main page (excluding the FAQ below) that seems to apply. But I don't see anything on the page addressing the question of “what if you want to bisect revisions that are not tagged in the branch.” Are you saying you don't want me to bisect Ubuntu kernels in that case, and go to the upstream kernels instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
If you don't have time to read what I wrote, or if something I wrote is not clear, just say so and I will understand. Let's not get caught in the endless Confirmed/Incomplete circle. I'll summarise what I said before, to make it easier to digest: You asked me to bisect between 3.13.0.18.38 and 3.13.0.20.24. That latter revision is not tagged in any of the Ubuntu kernel branches I could still find. I tried all branches from Precise to Vivid, but many of them are no longer available. The closest I could find was 3.13.0-19.40. The problem started sometime *after* that version. And then we were stuck at the point where I asked for suggestions on where to find the missing version(s) so I can bisect further. Any ideas? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Read back and it will become clear. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Once again: with the given instructions I can't bisect kernel commits any further. Is there another way to obtain the kernel source versions we need? Marking as Confirmed again until then, to avoid this bug timing out. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Oh, one other thing: with the older kernels I can play AssaultCube again! I couldn't really do that with the current Vivid kernels because the frame rate was too low. Reported frame rate would be around 60 fps, but it looks more like 10 fps. With these old kernels it plays smoothly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Nope, the Utopic kernel branch only has 3.13.0-19.40 and 3.13.0-20.41, nothing inbetween. So, all I know is up to and including 3.13.0-19.40 it still works OK. The problem must have been introduced later than that. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
The Precise kernel repository finished downloading, but it doesn't have 3.13.0-20.24. It has 3.13.0-19.39 and 3.13.0-20.41, nothing inbetween. Pinning my hopes on the Utopic branch... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
3.13.0-19.40 also works OK! So it broke sometime after that. I'm now trying to find 3.13.0-20.24 in one of the kernel branches from before Vivid. It's not in the Trusty branch. I can't get the Quantal, Raring, or Saucy ones, presumably because those releases are no longer supported. Downloading the Precise and Utopic ones, but it'll take a few more hours so I'll have to get back to it tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Using the ubuntu-vivid kernel branch, 3.13.0-18.38 works OK. That branch has no tag Ubuntu-3.13.0.20.24 or Ubuntu-3.13.0-20.24. The closest tags I see are Ubuntu-3.13.0-19.40 and Ubuntu-3.13.0-20.41. I'll try 3.13.0-19.40 next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Tried 4.1-rc8 as well for good measure. Still no improvement. Highest resolution offered in the System Settings is 1920×1200. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
No Tried 4.1-rc7. No change. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Marking this bug as "Confirmed" to avoid timeout. It was marked Incomplete pending testing against Saucy, but as of a few months ago the results are shown above. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437765] Re: No desktop after upgrade to 14.10
Saw a bunch of at-spi2 errors in .xsession-errors. Reinstalled at- spi2-core, and those errors went away. Still no desktop. Deleting .config/dconf/user did the trick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
After another reboot this effect seems to have gone away. So I still don't have my native resolution available by default, but at least I can get it back by defining it with xrandr. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Correction: that last upgrade was *from* 3.19.0-14.14, not *to* it. It was the upgrade to 3.19.0-15.15. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Hurray, the problem just got a little worse! After the upgrade to kernel 3.19.0-14.14, when I define my monitor's native resolution using xrandr, I get the right *resolution* but still not the right number of *pixels*. So I'm getting (as far as I can see) one logical pixel per physical pixel on the monitor — but the right-hand and lower edges stay black. It's not just the background picture; I can't move the mouse pointer there or make windows extend into it. However, after changing the resolution in the System Settings UI and then canceling the change, I finally get a full screen in native resolution like I used to with the previous kernel version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437765] Re: No desktop after upgrade to 14.10
After some searching, I found a comment suggesting that resetting my ATI graphics driver using "aticonfig --initial" might help. I did that, and now I get slightly further. Now when I log in I get the basic file management functionality on the desktop: icons and a context menu. But no Unity buttons on the left- hand side of the screen, no Super key, and no terminal when I press ctrl-alt-T. Also, no window decorations with drag bars, close button and so on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437765] Re: No desktop after upgrade to 14.10
So to be clear: my desktop is still utterly broken, but the one on an installer disc for the same version is not. Hopefully there is a simple configuration problem. I haven't done anything very special, I thought. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437765] Re: No desktop after upgrade to 14.10
A piece of good news: I did get a working desktop when booting from the 14.10 installer, for the same architecture. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437765] Re: No desktop after upgrade to 14.10
While the system is in this state, "ps" does show a compiz process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437765] [NEW] No desktop after upgrade to 14.10
Public bug reported: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-F, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run "top," it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Well, I did some bisecting but the results are disappointing. Actually I ended up trisecting. On Saucy, kernel... 3.11.0-12 was OK. Recognised my full native resolution and enabled it by default. Wonderful. 3.11.0-13 to 3.11.0.24 inclusive were completely messed up. They booted in some ultra-low resolution and were not responsive to my mouse and keyboard. 3.11.0-25 wasn't available in the archive. 3.11.0-26 gives me a maximum resolution of 1920 by 1200, which is the same behaviour I observed with 14.04, 14.10, and the daily 15.04 test versions. So it looks like between 3.11.0-12 and 3.11.0-13 something broke, and it took until 3.11.0-26 to get it more or less working again, but the old functionality was never completely regained. I guess that means there are no easy answers for this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
I could temporarily swap out the hard drive and install Saucy on the spare. More after the weekend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Okay, I got a seemingly successful install of the last Saucy kernel. But it's not working very well: I get a super-low-res login screen, and the system doesn't respond to keyboard or mouse. (It does notice the power button, so it's not frozen). This happens both with the default boot on that kernel version, and with the Upstart boot. So I can't say for certain whether things would still work correctly with a Saucy kernel. It wasn't this broken at the time! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Trying 13.11.0-17. There was a problem while installing linux-headers though... "fwts-efi-runtime-dkmis 15.03.00-0ubuntu1: fwts-efi-runtime- dkms kernel module failed to build." Somewhere along the way it said: run-parts: executing /etc/kernel/postinst.d/dkms 3.11.0-17-generic /boot/vmlinuz-3.11.0-17-generic ERROR (dkms apport): kernel package linux-headers-3.11.0-17-generic is not supported Error! Bad return status for module build on kernel: 3.11.0-17-generic (x86_64) Consult /var/lib/dkms/fwts-efi-runtime-dkms/15.03.00/build/make.log for more information. That's being reported separately. Meanwhile I'll see if I can get it to run... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436784] [NEW] fwts-efi-runtime-dkms 15.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build
Public bug reported: Trying to install this on a 15.04 system, together with the generic kernel image, in order to see if it makes a regression since 14.04 go away (bug 1300557). ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fwts-efi-runtime-dkms 15.03.00-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 DKMSKernelVersion: 3.11.0-17-generic Date: Thu Mar 26 17:23:23 2015 InstallationDate: Installed on 2013-08-03 (599 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageVersion: 15.03.00-0ubuntu1 RelatedPackageVersions: dpkg 1.17.24ubuntu1 apt 1.0.9.7ubuntu3 SourcePackage: fwts Title: fwts-efi-runtime-dkms 15.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build UpgradeStatus: Upgraded to vivid on 2015-03-11 (14 days ago) ** Affects: fwts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436784 Title: fwts-efi-runtime-dkms 15.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1436784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
The latest upstream version I found there was v4.0-rc4-vivid. It boots, but it doesn't fix the problem. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.0-rc4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
The version that was installed on March 31 was 3.13.0.20.24. The version I uninstalled right after that was 3.13.0.18.38. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
According to the dpkg.log for that date, quite a lot: libc-bin for amd64. Also gcc-4.8, gcc-4.9, along with g++, cpp, libgcc1, libstdc++6 etc, for amd64 and i386; and libitm1, libgomp1, libgfortran3, libasan0, libatomic1, libtsan0, libquadmath0, libthumbnailer0, apport, apport-gtk, python3-problem-report, python3-apport, binfmt-support, dh-apport, libgtk2-perl, python-boto, python-lxml, python3-lxml, unity-webapps-qml, mobile-broadband-provider-info, python-keystoneclient, The day before I upgraded among other things libffi6 (for i386 and amd64) and libffi-dev, dconf-gsettings-backend, dconf-service, libdconf1, various dconf tools and frontends, libglib2.0-*, libunity- control-center1 and unity-control-center, libido3-0.1-0, lxc and related packages, libapparmor1 and apparmor, libqt5positioning5, libunity-gtk3-parser0, openjdk-7 and icedtea-7, ubuntu-release-upgrader and update-manager, libcompizconfig0, compiz-gnome, compiz-plugins- default, libdecoration0, compiz-core, compiz, im-config, kerneloops- daemon, indicator-*, unity-scope-*, libreoffice, unity, libunity- core-6.0.9, unity-services, ubuntu-mono, libvirt, the kernel, and dh- apparmor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
No change in 15.04. I can add the resolution with xrandr, and after that I can use it. But after reboot, I have to do it again. The upgrade got stuck with a black screen and no networking, but I eventually got out of it with the "apt-get dist-upgrade" dance from the console. I hope that hasn't messed things up. It may matter that I've got the monitor's DVI port hooked up to my computer's HDMI port. It was the only way to get things working: the monitor doesn't support its full native resolution on HDMI, and the Haswell builtin graphics only supports the resolution on HDMI. But, the hardware can do it and it used to work from the settings GUI without hackery. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
I first upgraded to 14.10; that didn't change anything. Trying 15.04 now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Something happened to this bug's conversation: the message asking me to upgrade the BIOS has been removed/hidden. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
Okay, I got out of that situation with the help of the flashrom people. My BIOS is now updated. It helped a bit in that I can now define and add my resolution again using xrandr. It won't stay added though: I need to define and add it every time I boot. Otherwise, the resolution is not in the Displays settings dropdown. The dmidecode output is: F7 08/12/2014 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
I'm trying the BIOS upgrade as per those instructions. The only applicable option was the flashrom one, which seems to have hosed my BIOS. It's still on now, but I won't be able to boot it again. Kindly mark this bug New again to give me time to recover and retry! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373261] Re: pserv.yaml rewrite breaks when previous generator URL uses IPv6 address
** Changed in: maas Status: In Progress => Fix Committed ** Changed in: maas (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373261 Title: pserv.yaml rewrite breaks when previous generator URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373261] Re: pserv.yaml rewrite breaks when previous generator URL uses IPv6 address
** Changed in: maas (Ubuntu) Assignee: (unassigned) => Jeroen T. Vermeulen (jtv) ** Changed in: maas (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373261 Title: pserv.yaml rewrite breaks when previous generator URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373261] Re: pserv.yaml rewrite breaks when previous generator URL uses IPv6 address
** Changed in: maas Assignee: (unassigned) => Jeroen T. Vermeulen (jtv) ** Changed in: maas Status: Triaged => In Progress ** Branch linked: lp:~jtv/maas/bug-1373261 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373261 Title: pserv.yaml rewrite breaks when previous generator URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
** Description changed:
- Reconfiguring between an IPv4-based and an IPv6-based MAAS_URL broke the
- ‘generator’ setting in my pserv.yaml: it ended up being the full IPv4
- netloc, with most of the IPv6 netloc tacked onto it.
+ Reconfiguring when the existing MAAS_URL used an IPv6 host address broke
+ the ‘generator’ setting in my pserv.yaml: it ended up being the full
+ newly configured netloc, with most of the previous IPv6 netloc tacked
+ onto it.
I think that's because the regex in maas-cluster-controller.postinst
mistakes the first colon in an IPv6 address for the beginning of a port
specifier:
- sed -i "s|MAAS_URL=.*|MAAS_URL=\"$RET\"|" /etc/maas/maas_cluster.conf
- # Extract the hostname part.
- HOSTPART=$(echo $RET|awk '{ split($0,array,"/")} END{print array[3]
}')
- # And substitute it in-place in pserv.yaml on an indented,
non-commented
- # line.
- sed -ri
"s|^([[:space:]]+)(#+[[:space:]]*)?(generator:[[:space:]]+https?://)[^:/]+|\1\3$HOSTPART|"
/etc/maas/pserv.yaml
+ sed -i "s|MAAS_URL=.*|MAAS_URL=\"$RET\"|" /etc/maas/maas_cluster.conf
+ # Extract the hostname part.
+ HOSTPART=$(echo $RET|awk '{ split($0,array,"/")} END{print array[3]
}')
+ # And substitute it in-place in pserv.yaml on an indented,
non-commented
+ # line.
+ sed -ri
"s|^([[:space:]]+)(#+[[:space:]]*)?(generator:[[:space:]]+https?://)[^:/]+|\1\3$HOSTPART|"
/etc/maas/pserv.yaml
These things are still best done in Python I suppose.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373261
Title:
pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
The problem is still there. Example: My pserv.yaml contains... generator: http://[fdd1:caf5:2922:8b1f::1]/MAAS/api/1.0/pxeconfig/ Now, realising that this doesn't work, I run ‘dpkg-reconfigure maas- cluster-controller’ and set the MAAS URL to “http://10.9.9.1/MAAS”. The resulting pserv.yaml now contains... generator: http://10.9.9.1:caf5:2922:8b1f::1]/MAAS/api/1.0/pxeconfig/ Note how the first part of the netloc, up to the first colon, is replaced with the new address — but the rest of the netloc is still there. ** Changed in: maas Assignee: Jeroen T. Vermeulen (jtv) => (unassigned) ** Changed in: maas Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382774] Re: MAAS can't connect to postgresql
There doesn't seem to be any need to install with the C locale; en_US.UTF-8 works just as well. As does installing the language pack(s) to match the session's locale settings. The real problem is that we have no hook for doing either before apt installs our dependencies: it installs the dependencies first, and only then do we get a say. As Julian pointed out on the bug that was merged into this one, it's arguably a bug in the postgres packaging for neither failing nor falling back on unicode when the system does not support the session's locale, or openssh for keeping a locally unsupported locale in the session. Maybe sudo is to blame even for neglicence in sanitising the environment. Addressing the problem there would have wider consequences. Personally I think we should create our own postgres cluster during installation, with settings we dictate, instead of relying on the default one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382774 Title: MAAS can't connect to postgresql To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
I agree: this is a clear-cut case for the request-an-address API, but we still lack a request-a-hostname API. Out of curiosity, how did the existing setup(s) obtain these generated hostnames in the first place? To my knowledge they were neither exposed nor documented. MAAS never had much control over which non-node client got which address from DHCP, and that's why we had to re-work DHCP management. These old generated hostnames were no more stable than the IP addresses were: if the container moved to a different IP address, it would also move to a different hostname. So if at all possible, I would address the problem in two discrete steps: 1. Use the container's IP address, not its hostname. It should be about as stable as the hostname was. 2. Request a static IP through the MAAs API, and configure it statically on the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
Ah, I see that using the IP address is not an option in this case. So we'll have to add a way to manage DNS entries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251257] Re: [SRU] avahi fails in containers
MAAS trunk no longer includes Avahi, so closing this bug there. ** Changed in: maas Status: Triaged => 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/1251257 Title: [SRU] avahi fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1251257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379624] [NEW] Can't build package: 01-fix-database-settings.patch no longer applies
Public bug reported: When I “make package” (with trunk r3227 and packaging r317) I get this error: « patching file contrib/maas_local_settings.py Hunk #2 FAILED at 81. 1 out of 2 hunks FAILED dpkg-source: info: fuzz is not allowed when applying patches dpkg-source: info: if patch '01-fix-database-settings.patch' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/01-fix-database-settings.patch/ --reject-file=- < maas-1.7.0~beta4+bzr3127.orig.yN3AJm/debian/patches/01-fix-database-settings.patch gave error exit status 1 » (This bug may of course need retargeting to the package). ** Affects: maas (Ubuntu) Importance: Undecided Assignee: Julian Edwards (julian-edwards) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379624 Title: Can't build package: 01-fix-database-settings.patch no longer applies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1379624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184914] Re: dhcpd sometimes says "Can't create new lease file: Permission denied"
Could this be bug 1186662? The main packaging branch has a workaround for that which is worth a try. It's a matter of adding this line to /etc/apparmor.d/dhcpd.d/maas: capability dac_override, ...and then reloading the apparmor config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184914 Title: dhcpd sometimes says "Can't create new lease file: Permission denied" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1184914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596637] Re: "Writing data to" DVD being ejected
I'm sure after all this time the problem no longer exists. Nor does the system it happened on. ** Changed in: libburn (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/596637 Title: "Writing data to" DVD being ejected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libburn/+bug/596637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308069] Re: test_prepare_holds_startup_lock() fails spuriously
New hypothesis: the code in DatabaseLock opens, and closes, a cursor for each locking/unlocking command. Do we actually know that these cursors will be in the same database session? If the command failed, do we know that we would see an error? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308069 Title: test_prepare_holds_startup_lock() fails spuriously To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1308069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308069] Re: test_prepare_holds_startup_lock() fails spuriously
No, my hypothesis doesn't look correct. We don't see anything that would make prepare() jump into the reactor thread. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308069 Title: test_prepare_holds_startup_lock() fails spuriously To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1308069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308069] Re: test_prepare_holds_startup_lock() fails spuriously
It happened again. I suspect that it may be a matter of ordering of decorators: RegionAdvertisingService.prepare is decorated as @synchronous, and *then* as taking two locks. Given decorators' "wrapping" behaviour, which reverses the order of entrance, I understand that to mean: "grab these two locks, then run this function synchronously." Which would mean that if the lock weren't available at the time of the call, or if either attempt to grab a lock yielded to the reactor for whatever reason, the function could still run asynchronously from the caller's perspective. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308069 Title: test_prepare_holds_startup_lock() fails spuriously To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1308069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318361] [NEW] package libclang1-3.5 1:3.5~svn201651-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/lib/llvm-3.5/lib/libclang.so.1', which is different from other instances
Public bug reported: Breakage during installation, on a fresh (near-pristine) amd64 14.04 system. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libclang1-3.5 1:3.5~svn201651-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun May 11 17:49:58 2014 DuplicateSignature: package:libclang1-3.5:1:3.5~svn201651-1ubuntu1:trying to overwrite shared '/usr/lib/llvm-3.5/lib/libclang.so.1', which is different from other instances of package libclang1-3.5:i386 ErrorMessage: trying to overwrite shared '/usr/lib/llvm-3.5/lib/libclang.so.1', which is different from other instances of package libclang1-3.5:i386 InstallationDate: Installed on 2014-05-11 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: llvm-toolchain-snapshot Title: package libclang1-3.5 1:3.5~svn201651-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/lib/llvm-3.5/lib/libclang.so.1', which is different from other instances of package libclang1-3.5:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: llvm-toolchain-snapshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318361 Title: package libclang1-3.5 1:3.5~svn201651-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/lib/llvm-3.5/lib/libclang.so.1', which is different from other instances of package libclang1-3.5:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/+bug/1318361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311433] Re: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__'
** Branch linked: lp:~jtv/maas/1.5-revert-bug-1311433 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311433 Title: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__' To manage notifications about this bug go to: https://bugs.launchpad.net/django/+bug/1311433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311433] Re: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__'
** Branch linked: lp:~jtv/maas/revert-bug-1311433 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311433 Title: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__' To manage notifications about this bug go to: https://bugs.launchpad.net/django/+bug/1311433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308069] Re: test_prepare_holds_startup_lock() fails spuriously
** Description changed: + [Test Case] + No test case; the code that's being patched is only a test and does not actually appear in the package. + + + [Description of the problem] + This happened when trying to land a documentation-only branch: == FAIL: maasserver.rpc.tests.test_regionservice.TestRegionAdvertisingService.test_prepare_holds_startup_lock -- _StringException: Traceback (most recent call last): - File "/tmp/tarmac/branch.wNIVV5/src/maasserver/rpc/tests/test_regionservice.py", line 667, in test_prepare_holds_startup_lock - self.assertFalse(locks.eventloop.is_locked()) - File "/usr/lib/python2.7/unittest/case.py", line 418, in assertFalse - raise self.failureException(msg) + File "/tmp/tarmac/branch.wNIVV5/src/maasserver/rpc/tests/test_regionservice.py", line 667, in test_prepare_holds_startup_lock + self.assertFalse(locks.eventloop.is_locked()) + File "/usr/lib/python2.7/unittest/case.py", line 418, in assertFalse + raise self.failureException(msg) AssertionError: True is not false I've disabled the test and added an XXX. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308069 Title: test_prepare_holds_startup_lock() fails spuriously To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1308069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315135] Re: xorg.conf deleted during upgrade; native resolution no longer works
It's beginning to look like an nvidia driver problem. I tried switching to Noveau; that left me with a resolution of 640×480, with no other options. (In case you're wondering: it looks great but isn't very practical). Switching back to the proprietary driver deleted my xorg.conf again. After a few times back and forth between the two drivers, and restoring xorg.conf, I now suddenly find that most of the fuzzy pixels are gone, the GUI fonts look good again, the menu bars are back to the Unity style, and looking at the screen no longer hurts my eyes! No idea what happened, or why making the same changes earlier didn't produce the same effects. Let's just hope it stays the way it looks now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315135 Title: xorg.conf deleted during upgrade; native resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1315135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315135] Re: xorg.conf deleted during upgrade; native resolution no longer works
Also, I don't know if these are related, but window menus now appear not only at the top of the screen or in the window's title bar (depending on the new configuration setting in 14.04), but also in the classic pre- Unity location: right below the window's title bar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315135 Title: xorg.conf deleted during upgrade; native resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1315135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315135] [NEW] xorg.conf deleted during upgrade; native resolution no longer works
Public bug reported: I just upgraded a desktop system from 13.10 to 14.04, and to my horror found that the monitor's native resolution was no longer supported: the best setting offered was 1024×768 or somesuch. Turns out the upgrade deleted xorg.conf. There were two backups: one with the date as a suffix (.01052014) and one with just ".backup" as a suffix. The one with the date didn't look like what I had before, so I restored xorg.conf from xorg.conf.backup instead. Now I think I'm back in the resolution I had before (after going to the Display settings), but there's something wrong. The resolution isn't quite the native one so many pixels are fuzzy, causing my eyes to ache, and the font inside menus looks a few sizes too small. It's hard to read and leaves a lot of horizontal space in the menus unused. It also makes kerning look irregular. The monitor is an Iiyama ProLite E2407HDSV. It's supposed to do 1920×1080, but the best I can get working properly in the Display settings is 1680×1050. The next step up, 1920×1080, won't show the entire screen — large swathes of the desktop fall outside the physical display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.117 Tue Nov 26 21:36:39 PST 2013 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 1 21:47:44 2014 DistUpgraded: 2014-05-01 21:23:35,494 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304-updates, 304.117, 3.11.0-20-generic, i686: installed nvidia-304-updates, 304.117, 3.13.0-24-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:1401] InstallationDate: Installed on 2011-02-17 (1168 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=5e1d12d5-4c62-426b-aa1a-ab9e6aac90b7 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-01 (0 days ago) dmi.bios.date: 06/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO 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.:bvr2102:bd06/17/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu May 1 21:45:41 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315135 Title: xorg.conf deleted during upgrade; native resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/
[Bug 1311433] Re: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__'
** Changed in: maas Assignee: (unassigned) => Jeroen T. Vermeulen (jtv) ** Changed in: maas/1.5 Assignee: (unassigned) => Jeroen T. Vermeulen (jtv) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311433 Title: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__' To manage notifications about this bug go to: https://bugs.launchpad.net/django/+bug/1311433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310082] Re: d-i with precise+hwe-s stops at "Architecture not supported"
** Branch linked: lp:~jtv/maas/1.5-use-main-archive-for-intel-arches -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310082 Title: d-i with precise+hwe-s stops at "Architecture not supported" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1310082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310076] Re: lost connectivity to a node when using fastpath-installer with precise+hwe-s
** Branch linked: lp:~jtv/maas/1.5-use-main-archive-for-intel-arches -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310076 Title: lost connectivity to a node when using fastpath-installer with precise+hwe-s To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1310076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311433] Re: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__'
Upstream bug seems to be https://code.djangoproject.com/ticket/22486 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311433 Title: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__' To manage notifications about this bug go to: https://bugs.launchpad.net/django/+bug/1311433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310082] Re: d-i with precise+hwe-s stops at "Architecture not supported"
** Branch linked: lp:~jtv/maas/use-main-archive-for-intel-arches -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310082 Title: d-i with precise+hwe-s stops at "Architecture not supported" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1310082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310076] Re: lost connectivity to a node when using fastpath-installer with precise+hwe-s
I am attaching a fix for the part of the problem that's in maas/preseeds/curtin_userdata, in the maas source tree. This won't be enough to fix the whole problem, so I am not marking the branch as “fixing” this bug. ** Branch linked: lp:~jtv/maas/use-main-archive-for-intel-arches -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310076 Title: lost connectivity to a node when using fastpath-installer with precise+hwe-s To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1310076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
** Changed in: maas Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
The latest build in ppa:maas-maintainers/dailybuilds should have the fix. Could you try again, but with that package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
** Changed in: maas/1.5 Milestone: None => 14.04 ** Changed in: maas Milestone: None => 14.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300026] Re: Enlistment/commissioning boot no longer works
That sounds as if it's probably just bug 1300548, which is already fixed. Definitely not the same thing that this bug is about. ** Changed in: maas 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/1300026 Title: Enlistment/commissioning boot no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1300026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] Re: Screen resolution no longer works
** Description changed: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. - Again, the Display preferences list that as the highest possible - resolution. But this time, attempts to ‘xrandr --admode’ my native + Again, the Display preferences list that resolution as the highest + possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.14-0ubuntu1 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 CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] + Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 16510 - vendor DEL + product id 16510 + vendor DEL xserver.version: 2:1.15.0-1ubuntu7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300026] Re: Enlistment/commissioning boot no longer works
Yay! A fresh import solved it. ** Changed in: maas Status: Incomplete => Invalid ** Changed in: maas (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300026 Title: Enlistment/commissioning boot no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1300026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300557] [NEW] Screen resolution no longer works
Public bug reported: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that as the highest possible resolution. But this time, attempts to ‘xrandr --admode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 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 CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 resolution trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300026] Re: Enlistment/commissioning boot no longer works
I wasn't getting any new files from the import script. Am now re- running the entire import from scratch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300026 Title: Enlistment/commissioning boot no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1300026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300026] [NEW] Enlistment/commissioning boot no longer works
Public bug reported: In my MAAS test setup, nodes now fail to enlist or commission. They used to work, I think before we changed to the new import script. Both for enlistment and commissioning the nodes netboot properly, as far as I can see, but they fail to do what they booted for. They never contact the region controller API, and don't rsyslog. Here's what I see on the console: « Begin: loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: running /scripts/local-top ... [ 16.420144] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready IP-Config: eth0 hardware address 00:1e:0b:a2:c9:c7 mtu 1500 DHCP RARP IP-Config: no response after 2 secs - giving up [ 18.548882] e1000e: eth0 NIC Link is up 1000 Mbps Full Duplex. Flow Control: Rx/Tx [ 18.549039] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready IP-Config: eth0 hardware address 00:1e:0b:a2:c9:c7 mtu 1500 DHCP RARP hostname maas-enlist hostname maas-enlist IP-Config: eth0 complete (dhcp from 10.99.99.1): address: 10.99.99.100 broadcast: 10.99.99.255 netmask: 255.255.255.0 gateway: 10.99.99.1 dns0 : 10.99.99.1 dns: 0.0.0.0 domain: maas rootserver: 10.99.99.1 rootpath: filename: : [ 19.637333] Loading iSCSI transport class v2.0-870. [ 19.644738] iscsi: registered transport (tcp) iscsistart: Logging into iqn.2004.05.com.ubuntu:maas:ephemeral-amd64-generic-trusty-daily 10.99.99.1:3260,1 iscsistart: version 2.0-873 [ 19.899127] scsi6 : iSCSI Initiator over TCP/IP [ 37.100041] random: nonblocking pool is initialized [ 169.948039] session1: session recovery timed out after 120 secs iscsistart: Connection1:0 to [target: iqn.2004-05.com.ubuntu:maas:ephemeral-amd64-generic-trusty-daily, portal: 10.99.99.1,3260] through [iface: default] is shutdown. iscsistart: initiator reported error(11 - iSCSI PDU timed out) iscsistart: Logging into iqn.2004-05.com.ubuntu:maas:ephemeral-amd64-generic-trusty-daily 10.99.99.1:3260,1 iscsistart: version 2.0-873 [ 921.584828] scsi7 : iSCSI Initiator over TCP/IP [ 1072.348035] session2: session recovery timed out after 120 secs » Eventually it drops me into a busybox-style shell. There's some lspci- style output, followed by: « Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-path/ip-10.99.99.1:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-amd64-generic-trusty-daily-lun-1 does not exist. Dropping to a shell! » Here's what I get from /proc/cmdline: « (initramfs) cat /proc/cmdline nomodeset iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-amd64-generic-trusty-daily iscsi_target_ip=10.99.99.1 iscsi_target_port=3260 iscsi_initiator=maas-enlist ip=maas-enlist:BOOTIF ro root=/dev/disk/by-path/ip-10.99.99.1:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-amd64-generic-trusty-daily-lun-1 overlayroot=tmpfs cloud-config-url=http://10.99.99.1/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed log_host=10.99.99.1 log_port=514 initrd=amd64/generic/trusty/daily/boot-initrd BOOT_IMAGE=amd64/generic/trusty/daily/boot-kernel BOOTIF=01-00-1e-0b-a2-c9-c7 » ** Affects: maas (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/1300026 Title: Enlistment/commissioning boot no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1300026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299989] Re: maas-dns fails to install without python-seamicroclient
** Project changed: maas => maas (Ubuntu) ** Changed in: maas (Ubuntu) Milestone: 14.04 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299989 Title: maas-dns fails to install without python-seamicroclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1299989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081660] Re: If maas-enlist fails to reach a DNS server, the node will be named "; ; connection timed out; no servers could be reached"
See bug 1284964 for a possible explanation: the enlist_userdata calls "dig" to look up a hostname, but does not check for errors — and "dig" prints the error message to stdout, not stderr, so it ends up in the hostname field. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081660 Title: If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1081660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278190] Re: File sync error. (auth failed(AUTH_FAILED))
To be exact, the email said that the change would log me out but also that the change had already happened. The logical conclusion as I read it now would have been "if I am not logged out already, I do not need to do anything." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278190 Title: File sync error. (auth failed(AUTH_FAILED)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-client/+bug/1278190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278190] Re: File sync error. (auth failed(AUTH_FAILED))
I did get such an email, but it did not ask me to remove and re-add my devices. It asked me to remove and re-add my account. Not sure what that means exactly. It also said that the change might log me out, and this change would be needed to get it working again. Reading this back I can only conclude that if I didn't get logged out at that point, I would have ignored the email because the problem it remedied wasn't happening. The email points to the FAQ, but isn't very specific about what to look for. An earlier search for "auth failed" got me to a different entry, but I'm now going with this one: https://one.ubuntu.com/help/faq/what- should-i-do-if-authentication-fails-auth_failed-state/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278190 Title: File sync error. (auth failed(AUTH_FAILED)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-client/+bug/1278190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278190] Re: File sync error. (auth failed(AUTH_FAILED))
Ah, found the logs back. Always a bit confusing under ~/.cache!
Here's a log entry for the failure in the UI, while trying to remove the
local device:
2014-02-11 21:12:23,994 - ubuntuone.controlpanel.qt.device - ERROR - Error
while invoking with
args (,)
and kwargs {}:
Traceback (most recent call last):
File
"/usr/lib/python2.7/dist-packages/ubuntuone-control-panel/ubuntuone/controlpanel/gui/qt/__init__.py",
line 196, in inner
res = yield f(*args, **kwargs)
AttributeError: 'QGroupBox' object has no attribute 'startswith'
As for the auth problem, the syncdaemon-exceptions logs have entries
like:
2014-02-10 11:17:03,598 - twisted - ERROR - Unhandled error in Deferred:
2014-02-10 11:17:03,599 - twisted - ERROR - Unhandled Error
Traceback (most recent call last):
Failure: twisted.internet.error.ConnectionLost: Connection to the other side
was lost in a non-clean fashion: Connection lost.
Nothing very helpful in the other logs either, that I can see. The
syncdaemon.log ends with:
2014-02-11 21:12:06,815 - ubuntuone.SyncDaemon.sync - INFO - T:LOCAL:F
6d8a369e-afad-44a7-bb7c-9027dbc6e2f3
['root'::marker:6d8a369e-afad-44a7-bb7c-9027dbc6e2f3] ''Ubuntu One/my-file'' |
Called put_file (In: T:NONE:F)
2014-02-11 21:12:06,894 - ubuntuone.SyncDaemon.Main - INFO - hash queue empty.
We are ready!
2014-02-11 21:12:07,268 - ubuntuone.SyncDaemon.ActionQueue - INFO - Connection
started to host fs-1.one.ubuntu.com, port 443.
2014-02-11 21:12:07,801 - ubuntuone.SyncDaemon.ActionQueue - INFO - Connection
made.
2014-02-11 21:12:07,803 - ubuntuone.SyncDaemon.StorageClient - INFO -
Connection made.
2014-02-11 21:12:08,900 - ubuntuone.SyncDaemon.ActionQueue - INFO - The request
'protocol_version' finished OK.
2014-02-11 21:12:09,219 - ubuntuone.SyncDaemon.ActionQueue - INFO - The request
'caps_raising_if_not_accepted' finished OK.
2014-02-11 21:12:09,708 - ubuntuone.SyncDaemon.ActionQueue - INFO - The request
'caps_raising_if_not_accepted' finished OK.
2014-02-11 21:12:10,932 - ubuntuone.SyncDaemon.ActionQueue - INFO - The request
'oauth_authenticate' failed with the error: AUTHENTICATION_FAILED and was
handled with the event: SYS_AUTH_ERROR
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278190
Title:
File sync error. (auth failed(AUTH_FAILED))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-client/+bug/1278190/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278190] Re: File sync error. (auth failed(AUTH_FAILED))
I'm seeing this too, on all my Ubuntu devices. Restarting doesn't help,
nor does reinstalling the CA certificates, nor does re-authenticating
with Ubuntu SSO.
Looking at the web UI, it looks as if the server has forgotten about all
my devices! On the website I only see my web session as a logged-in
device. Each of my devices only shows itself ("local device") and the
web session.
Figuring it was a matter of deleting my devices and re-registering them,
I tried removing the “Local device” from the U1 settings on an Ubuntu
system. But that fails with an AttributeError: "'QGroupBox' object has
no attribute 'startswith'"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278190
Title:
File sync error. (auth failed(AUTH_FAILED))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-client/+bug/1278190/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553400] Re: No keyboard with init=/bin/bash
As far as I'm concerned we can just close this bug. It's been more than 3½ years, and I think I've seen it working in the meantime (if probably on different hardware). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553400 Title: No keyboard with init=/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/553400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243917] Re: 'maas createsuperuser' errors out if no email address is entered.
For the historical record: * createsuperuser is a Django built-in command, not our code. * We have our own MAAS-tailored version, createadmin. * The email field must be unique and non-null, but can be empty. * MAAS already creates a system user with empty email address. * A null email address would be the right way to do this, but Django's supports null values more or less as an afterthought. The simple fix is to update the documentation, so it always points users to createadmin, not createsuperuser. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243917 Title: 'maas createsuperuser' errors out if no email address is entered. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1243917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243917] Re: 'maas createsuperuser' errors out if no email address is entered.
** Changed in: maas Milestone: None => 14.04 ** Changed in: maas Assignee: (unassigned) => Jeroen T. Vermeulen (jtv) ** Changed in: maas Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243917 Title: 'maas createsuperuser' errors out if no email address is entered. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1243917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237615] Re: python-bson-ext does not encode binary in Apache with mod_wsgi
Don't know if this matters, but...
The blog article suggests WSGIProcessGroup %{GLOBAL}. We have
WSGIApplicationGroup %{GLOBAL}, but WSGIProcessGroup maas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237615
Title:
python-bson-ext does not encode binary in Apache with mod_wsgi
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1237615/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236361] Re: need new simple streams based maas-import-ephemerals
** Changed in: maas Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236361 Title: need new simple streams based maas-import-ephemerals To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1236361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236361] Re: need new simple streams based maas-import-ephemerals
** Changed in: maas Milestone: None => 13.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236361 Title: need new simple streams based maas-import-ephemerals To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1236361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218731] [NEW] package unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is als
Public bug reported: Automatically reported crash. I think it happened while upgrading. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.12.1-0ubuntu2 Architecture: i386 Date: Fri Aug 30 11:45:29 2013 DuplicateSignature: package:unity-webapps-common:2.4.16+13.10.20130715-0ubuntu1:trying to overwrite '/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1 InstallationDate: Installed on 2012-11-25 (277 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all SourcePackage: webapps-applications Title: package unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1 UpgradeStatus: Upgraded to saucy on 2013-08-21 (8 days ago) ** Affects: webapps-applications (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-conflict saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218731 Title: package unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1218731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215425] Re: update-manager crashed with Package linux-headers-3.11.0-2 isn't available in _show_transaction()
I don't know — update-manager launched automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215425 Title: update-manager crashed with Package linux-headers-3.11.0-2 isn't available in _show_transaction() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1215425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1134036] Re: Package install hangs if LC_ALL is not set
Looks like this was caused by a missing en_US entry in Julian's /usr/share/locale. I'm seeing another, but possibly related failure where the error is that the database is not running; filed as bug 1171696. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Package install hangs if LC_ALL is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1134036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168299] Re: Can't upgrade to raring: libvisio download fails with Forbidden
That worked around it, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168299 Title: Can't upgrade to raring: libvisio download fails with Forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1168299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168299] Re: Can't upgrade to raring: libvisio download fails with Forbidden
There, hope that did it (apport did say “dpkg-query: no packages found matching ubuntu-release-upgrader” but it seems to be okay). I took this bug back to New status, because I've sometimes had bugs remain in Incomplete at this stage, and just expire in the end. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168299 Title: Can't upgrade to raring: libvisio download fails with Forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1168299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168299] VarLogDistupgradeMainlog.txt
apport information ** Attachment added: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/bugs/1168299/+attachment/3645211/+files/VarLogDistupgradeMainlog.txt ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168299 Title: Can't upgrade to raring: libvisio download fails with Forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1168299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168299] VarLogDistupgradeLspcitxt.txt
apport information ** Attachment added: "VarLogDistupgradeLspcitxt.txt" https://bugs.launchpad.net/bugs/1168299/+attachment/3645210/+files/VarLogDistupgradeLspcitxt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168299 Title: Can't upgrade to raring: libvisio download fails with Forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1168299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168299] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/bugs/1168299/+attachment/3645209/+files/VarLogDistupgradeAptlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168299 Title: Can't upgrade to raring: libvisio download fails with Forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1168299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
