[Bug 1795024] Re: setting release-upgrades Prompt to never can cause confusing behavior

2021-01-24 Thread Pietro Gagliardi (andlabs/pietro10)
Ah no it was [allow-insecure=yes] that was throwing it off, because when I did it there were certificate issues. My original question still stands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795024

[Bug 1795024] Re: setting release-upgrades Prompt to never can cause confusing behavior

2021-01-24 Thread Pietro Gagliardi (andlabs/pietro10)
Oh, it seems do-release-upgrade doesn't recognize old-releases in a sources.list, so that won't quite work either... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795024 Title: setting release-upgr

[Bug 1795024] Re: setting release-upgrades Prompt to never can cause confusing behavior

2021-01-24 Thread Pietro Gagliardi (andlabs/pietro10)
Is there a way I can have both prompt=never and to be able to run do- release-upgrade? I'd like to decide on my own terms when to do an upgrade, and to fully disable the update/upgrade UI entirely. I know I could temporarily change prompt back, but that's inconvenient in the long term. -- You rec

[Bug 1725099] Re: “Vanilla GNOME desktop” task doesn't work

2018-05-12 Thread Pietro Gagliardi (andlabs/pietro10)
Update: sudo apt-get install vanilla-gnome-desktop does install everything. However, regardless of whether I also tasksel'd it, I do get an errors encountered while configuring for both vanilla-gnome-default- settings and vanilla-gnome-desktop; dpkg --audit says to dpkg --configure both to resolve

[Bug 1725099] Re: “Vanilla GNOME desktop” task doesn't work

2018-05-11 Thread Pietro Gagliardi (andlabs/pietro10)
Affects me with both the i386 and x86_64 netinstall images of 18.04 — the installation process completes unusually quickly, and upon rebooting, I get dropped to a terminal login. startx is not found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribe

[Bug 970638] Re: killall can't kill processes with names >15 bytes long (Ubuntu 12.04)

2015-11-27 Thread Pietro Gagliardi (andlabs/pietro10)
Several years on, this is still present in wily. I'm not sure if it's the same root cause, but pgrep plugin-container doesn't work. Annoying, as I typically do kill -9 `pgrep xxx`, and killing Nightly doesn't kill plugin-container (it will die some time later, causing apport to complain). -- You

[Bug 1409366] Re: missing /usr/lib/libGL.so, pkg-config gl.pc file causes programs to fail to build

2015-02-17 Thread Pietro Gagliardi (andlabs/pietro10)
And it isn't saying which packages are held or conflict...? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409366 Title: missing /usr/lib/libGL.so, pkg-config gl.pc file causes programs to fail to

[Bug 1409366] Re: missing /usr/lib/libGL.so, pkg-config gl.pc file causes programs to fail to build

2015-02-11 Thread Pietro Gagliardi (andlabs/pietro10)
That's a different issue from the one in this bug report but I'll try to diagnose it: what packages conflict? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409366 Title: missing /usr/lib/libGL.so,

[Bug 1409366] Re: missing /usr/lib/libGL.so, pkg-config gl.pc file causes programs to fail to build

2015-01-28 Thread Pietro Gagliardi (andlabs/pietro10)
bigdavesr: what issue are you having specifically? Are you saying installing fglrx itself fails for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409366 Title: missing /usr/lib/libGL.so, pkg-c

[Bug 1385572] Re: gnome-session not shutting down cleanly

2015-01-21 Thread Pietro Gagliardi (andlabs/pietro10)
I don't know how much this comment would contribute to this bug but I can at least confirm that the behavior described here is a possible reason why this is going on, as judged by my comment to bug 1236749 here: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1236749/comments/77 Specifi

[Bug 1236749] Re: Gnome shell extensions disabled at every startup

2015-01-21 Thread Pietro Gagliardi (andlabs/pietro10)
The problem with this bug is that it doesn't exhibit itself consistently or predictably. On my previous laptop's Ubuntu GNOME 14.10 setup, reboots worked fine until some point (a month after installing?), at which point this behavior started happening... but only on a clean reboot. If I killed pow

[Bug 1409366] [NEW] missing /usr/lib/libGL.so, pkg-config gl.pc file causes programs to fail to build

2015-01-10 Thread Pietro Gagliardi (andlabs/pietro10)
Public bug reported: I test the software I write against GTK+ master, and for that I build cairo and pango master as part of the build process with jhbuild. After getting a new laptop with AMD graphics, mesa kept freezing so I switched to fglrx. The two libraries now fail to build. cairo fails to

[Bug 1291169] Re: bash-completion behaves oddly under specific circumstances

2014-03-22 Thread Pietro Gagliardi (andlabs/pietro10)
The VAR= part isn't as important as the not being able to tab complete files, which is now fixed mysteriously, so I suppose I'll let this one rest as well. Thanks anyway! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.lau

[Bug 1291169] Re: bash-completion behaves oddly under specific circumstances

2014-03-13 Thread Pietro Gagliardi (andlabs/pietro10)
Something in the most recent set of updates (as of an hour ago) fixed the filename completion issues (but not the VAR= -l issue). I'm not sure what it is, and I've had to reboot since... is there a way I can get a log of what packages were updated so I could spot the culprit? -- You received this

[Bug 1291169] [NEW] bash-completion behaves oddly under specific circumstances

2014-03-11 Thread Pietro Gagliardi (andlabs/pietro10)
Public bug reported: After some unknown update in the past at least week and a half or so, my bash completion has acted strangely: - if I begin a filename to complete with ~/ I cannot complete filenames, only directory names, and the suggested names (if I press tab twice) show only directo