Public bug reported:
Changing `APT::Periodic::Update-Package-Lists` to a value not in the
data model `model_updates_interval` in `/usr/share/software-
properties/gtkbuilder/main.ui` calls an invalid method, crashing the
program.
```
$ cat /etc/apt/apt.conf.d/10periodic
Public bug reported:
Very early in the installation process.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Kernel 5.4.0-71 has finally fixed the problem. Having just installed it,
I have not run extensive test on it, but it appears to be stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Still screwed up after reinstall. At this point I'd just recommend
installing the 5.11.3 kernel from the ppa and be done with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu
While 5.10.0-1017 did fix the ir-keytable problem it introduced other
problems which I couldn't live with. After deleting my 5.11.3 kernel I
have since reinstalled it and am running it.Maybe I'll try to reinstall
the 5.10.0-1017 kernel later and see if I just got a bad install.
--
You received
I'm happy to report that the following dist kernel has fixed the problem.
wes@mythfe0:~$ uname -a
Linux mythfe0 5.10.0-1017-oem #18-Ubuntu SMP Fri Mar 5 18:33:48 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
It's in the repos.
And it also supports my nvme drive status which was why I was running later
Well, I run newer kernels from the ppa as my main kernel. Currently
running 5.11.3, so it's not a problem for me. As long as whomever does
the distribution kernels keep using old base kernels, the problem will
never be fixed. If you want to run a distribution kernel, then you
should go back to
Kernel 5.4.0-67 is still broken.
Can anyone explain this to me.
A patch that fixed it was done in Dec. 2020. And it was implemented in ppa
kernels compiled after 01/28/2021.
So why is it that this has not made it into any of the distribution kernels
yet. Kernels 5.10 has shown up in the repos,
Did I miss something? It looks like you may have referenced 3 commands
but I only see 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917771
Title:
Icon location not updating in
echo $XDG_DATA_DIRS:
/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917771
Title:
Icon location not updating in
gsettings get org.gnome.shell favorite-apps:
['chromium_chromium.desktop', 'nemo.desktop', 'org.gnome.gedit.desktop',
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop',
'libreoffice-calc.desktop', 'shotwell.desktop', 'slack_slack.desktop',
'simple-scan.desktop', 'Zoom.desktop',
This has been going on for a while. I found an article that suggested a
solution for the disappearing icon be to add the .desktop file. I would
certainly be interested in a better solution. Changing to "current"
seems to have worked but I sense you hinting there is a larger problem
in having to
I should have mentioned - I can go in and update
chromium_chromium.desktop with the new location, the icon appears and
everything works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917771
Public bug reported:
I am having to constantly edit
~/.local/share/applications/chromium_chromium.desktop and update the
location of the icon. I think this is something happening when an update
happens. For instance Icon location:
Icon=/snap/chromium/1444/chromium.png changed to Icon location:
last kernel upgrade to 5.4.0-66 is still broken.
** 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/1901089
Title:
Ubuntu kernels
Patch was added into kernel builds on 01-31-21. Working later kernels.
Linux mythfe0 5.10.13-051013-generic #202102032337 SMP Thu Feb 4 00:17:21 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After a system upgrade last night, the patched version 5.4.0-59 that
works was replaced by an older version of 5.4.0-59 dated Dec 10. So
anyone that installed the patched version will likely find their remote
not working again if they do a system upgrade.
--
You received this bug notification
Just curious how long that takes. 5.10.3 was just released today and
doesn't look like it made it into it going by the changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu
Yes! That fixed it for me. Glad someone here could compile it. I was lost.
What happens now to all the other kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels
After enabling sources and reverting to ubuntu kernel 5.4.0-58 installed
first part. Will continue tomorrow or later tonight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu
Well, that didn't work.
wes@mythfe0:~$ sudo apt-get build-dep linux linux-image-$(uname -r)
[sudo] password for wes:
Reading package lists... Done
E: You must put some 'deb-src' URIs in your sources.list
wes@mythfe0:~$ uname -r
5.10.2-051002-generic
wes@mythfe0:~$
Last time I compiled a kernel
As you can see there's no reference to ir-keytable running in that
kernel. Ran the same on good kernel 5.8.7 and here's a snippet from the
output of it.
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3:
/usr/lib/udev/rules.d/60-ir-keytable.rules:5 RUN '/usr/bin/ir-keytable -a
/etc/rc_maps.cfg
here goes.
root@mythfe0:/home/wes# journalctl -u systemd-udevd.service -f
-- Logs begin at Thu 2020-09-24 22:03:46 CDT. --
Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: value '[dmi/id]sys_vendor' is 'To
Be Filled By O.E.M.'
Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: 1-8: Device (SEQNUM=4105
Ccofigs for both kernels attached.
** Attachment added: "config-5.8.8-050808-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+attachment/5445250/+files/config-5.8.8-050808-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Oops. here's the other.
** Attachment added: "config-5.8.7-050807-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+attachment/5445251/+files/config-5.8.7-050807-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
= 125 ms
root@mythfe0:/home/wes# evtest /dev/input/event7
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x471 product 0x815 version 0x0
Input device name: "Media Center Ed. eHome Infrared Remote Transceiver
(0471:0815)"
Supported events:
Event type 0 (EV_SYN)
Ev
This is with working kernel 5.8.7.
root@mythfe0:/home/wes# ir-keytable
Found /sys/class/rc/rc3/ with:
Name: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)
Driver: mceusb
Default keymap: rc-rc6-mce
Input device: /dev/input/event19
LIRC device
this one. Don't know what evtest you mean. Nor do I
select the device. It just works after boot.
I'm not a kernel guy and don't know how to revert the commits. Here's my
ir-keytable output on kernel 5.8.7.
wes@mythfe0:~$ ir-keytable
Found /sys/class/rc/rc3/ with:
Name: Media Center Ed. eHome
I've emailed the person that commited them. With luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
To manage
I have no idea how to do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
To manage notifications about this bug go
** 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/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
To
5.8.7-050807-generic #202009051031 SMP Sat Sep 5 10:34:16 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux WORKS.
kernel 5.8.8 does not.
Looks like any kernel built after Sep 5 2020 will be bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Last ubuntu kernel that worked was 5.4.0-48. First that doesn't is 5.4.0-51.
And there isn't a 5.4.0 dir list here.
https://kernel.ubuntu.com/~kernel-ppa/mainline/
It works in some later kernels from mainline but quit working sometime after
5.4.53, and doesn't work in 5.9 or 5.10.
--
You
AFAICT, it affects all later kernels starting after 5.4.0-48 somewhere.
that includes 5.9 and 5.10 which i just installed a couple of days ago.
If you think it would help I can reboot to whichever kernel you want and
post dmesg output.Wondering if this should be posted as a kernel bug
too.
--
Interesting, but doesn't seem to be a proper fix. Been running ir-
keytable for years and was never able to use ir-krytable -t as a regular
user. had to redo keymap file going from xubuntu 18.04lts to 20.04lts.
Having to load after boot is not a viable option as this is a frontend
my wife uses
Just upgraded to -58 kernel and it broke my remote too. Going back to
-42 kernel fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break
if someone has a good contact at Slack, please reach out to them about
this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901959
Title:
Default Profile is called "default-release", programs
I'm reporting that it opens the wrong profile.
I'm not sure how Slack does this but I'm guessing Oliver is right, they
call it directly with -profile or something
Marking invalid since this is a FF/Slack issue.
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
You received this
Public bug reported:
Firefox 82.0
Ubuntu 20.04
The default profile in the Ubuntu Firefox package is called "default-
release", while the typical profile name for Firefox is "default".
Slack opens links using the default profile when Firefox is the browser,
causing links to open in a different
Sigh indeed. The ignoring of this bug report (and many other bad, bad
decisions for that matter) has now lead us to just abandon Ubuntu
entirely. Even for non-server desktop use cases. I have no idea if the
original reported issue has ever actually been dealt with, and I guess I
never will.
--
> In kernel v < 4.19 the "normal" BLE commands work.
> In kernel v > 4.19 only the BLE extended (BT 5.0) commands work.
..
> So it doesn't seem to be an issue in kernel
What? That indicates it is a problem with the kernel, doesn't it? The
desired behaviour exists in previous versions but is
memtest86+ freezes on my am4 ryzen 3 2200G and 3200G systems. Runs fine
on all my older systems. And Theirs nothing wrong with the memory on the
amd system. Multiple passes with another tester.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: tripleo
Milestone: ussuri-rc3 => victoria-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
python3 + Fedora + SSL + wsgi nova deployment, nova api returns
** Changed in: tripleo
Milestone: ussuri-3 => ussuri-rc3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
python3 + Fedora + SSL + wsgi nova deployment, nova api returns
** Changed in: tripleo
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
python3 + Fedora + SSL + wsgi nova deployment, nova api returns
Public bug reported:
* What you're doing and what's happening: launching bash from a user
whose name includes a space breaks /etc/profile.d/wsl-integration.sh
* What's wrong / what should be happening instead:
> PS C:\Users\Jack Troughton\git\dcp-jason> bash
> -bash: [: /mnt/c/Users/Jack:
** Changed in: tripleo
Milestone: ussuri-2 => ussuri-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
python3 + Fedora + SSL + wsgi nova deployment, nova api returns
Hello,
Hello and than you for the assistance and your time.
For sure I thought this was a bug because it appeared platform dependent
and only associated with nano.
The first thing I did was I checked my version of PuTTy which was .70
and then checked the PuTTy site and updated to PuTTy .73 and
Question Answers:
1. Windows 10 laptop core i7 Microsoft Windows [Version 10.0.17763.914]
2. TERM=xterm
3.
write(1,
"\33[?1049h\33[22;0;0t\33[1;47r\33(B\33[m\33[4l\33[?7h\33[39;49m\33[?1h\33=",
54) = 54
write(1, "\33[?1h\33=", 7) = 7
write(1, "\33[?1h\33=", 7) = 7
Public bug reported:
Nano 2.9.3
Ubuntu 18.04.3 LTS - Linux 4.14.157-171 armv7l
ARMv7 Processor rev 3 (v7l)
Ubuntu 18.04.3 LTS - Linux 4.9.196-63 aarch64
Amlogic S922X rev a (4 A73 + 2 A53)
This issue is repeatable on more than 6 each different machines of the above
configurations.
I am
Medium? I've had this take a few prod clusters offline at highly
inconvenient times, it effectively makes keepalived on 18.04 unfit for
purpose. We've had to build our own keepalived packages to keep things
running - I think you need to give this a bit more priority please
--
You received this
installing the HWE packages resolved the issue for Linux Mint 19.2, thank you.
Command: apt install --install-recommends xserver-xorg-hwe-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839174
Public bug reported:
Issue
xorg crashes, there doesn't seem to be any repeatable cause, it'll happen just
watching hulu or youtube, it'll happen when using citrix, or when playing steam
games.
Steps to reproduce
use xorg for a while
Expected behaviour
not crashing
Other information
issue
Same here. Reported to
https://bugzilla.kernel.org/show_bug.cgi?id=204325
Covers all 5.2.x kernels up to 5.2.5. No video, no KB response. But system
runs. Can ssh into it. Runs fine on kernels up to 5.1.21.
Ryzen 3 2200G using internal video.
** Bug watch added: Linux Kernel Bug Tracker #204325
This is not a bug only a very weird ubuntu not having a system tray issue. the
fact is that this program was intended to be used just like (example. When you
click on the Wi-Fi status icon, and then a small menu pops up. Thats it.) If
your like me and you saw a picture of the settings GUI. And
I have tested this package and it fixes the bug without causing any
regressions in my tests. To test the update I re-performed the test case
procedure to verify the updated package fixed the bug and then used the
updated package to run the unit tests for an internal application
compiled for ppc64.
When I try to edit the description I'm getting timeout errors (maybe
because I'm behind a corporate proxy?). I've written the test case
below. Please add it to the bug description.
[Test Case]
* Compile the attached source code using your host C compiler.
* Run the resulting binary.
> It
I've attached source code to use for the test case. I tested it using
the Ubuntu standard compiler (gcc package), the Ubuntu standard
powerpc64 cross compiler (gcc-powerpc64-linux-gnu package), and a custom
GCC 4.9.2 targeting PowerPC64 on an embedded board.
** Attachment added: "C source code to
Public bug reported:
QEMU erroneously fails to detect support for the timerfd_create syscall
when running user-mode emulation of PowerPC targets. QEMU supports the
timerfd_create syscall, but because the PowerPC target syscall header
has it named "timerfd" instead of "timerfd_create", support is
** Summary changed:
- vlc liblirc-client0 depends breaks kernel lirc
+ ir-keytable -c -w /etc/rc_keymaps/file
** Description changed:
- Subject pretty much says it all. Installing vlc also installs liblirc-
- client0. This hoses up kernel lirc by not allowing some key codes to be
- passed to
Problem resolved.
I changed to BIOS to allow booting from the CDROM in EFI mode. Once
that was done it worked correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783631
Title:
Dual boot
Public bug reported:
Trying a dual boot install.
/dev/sda is a Windows SSD and boots normally.
/dev/sdb is supposed to be the Ubuntu SSD, but grub will not install from the
graphical install program.
Command line install "sudo grub-install /dev/sdb" returns an error "failed to
get canonical
Has to be the right shift key on my 18.04lts system, but I've always
just used tapping the Esc key immediately after post until the grub menu
comes up. I explained earlier how to remove the .24 kernel. But don't
try to remove the one you are running at the time. Not sure what would
happen then.
Easiest thing to do is just delete the .24 kernel. During boot, start
tapping the esc key repeatedly. You should get the grub menu. Select the
advanced option, and then load the last good kernel, which should be the
.23 one if you've kept the system up to date. Once it boots and
everything is
I only had the slow boot problem on 2 out of 3 systems with the .24
kernel. Both systems that had problems had single ssd drives in them.
One was an ECS GF8200A mb and the other was a jetway GF8200 based mb.
The system that didn't have a problem was also an ECS GF8200A mb, but
does not have a ssd
I had already installed everything from the proposed mirror using
software updater, but it didn't install the new .26 kernel on the 2
affected machines. So I installed the image, headers, module-extra
packages using apt-get install /bioic-proposed. that
worked and everything worked fine afterwards
Don't know why the new kernel didn't install from the software updater,
but after manually installing it, it works fine. Now to do the same on
other machine. Funny it all installed fine with the software updater on
my main machine.
--
You received this bug notification because you are a member
After turning on developer options for pre-release upgrades and
installing a lot of stuff, I still have the same problem with the slow
boot on the 2 machines I updated. uname-a shows same as before.Is that
normal? I turned off developer stuff afterwards. Since 4.15.0-23 works
fine, should I just
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: wes1410 F pulseaudio
/dev/snd/controlC1: wes1410 F
OK, I changed one key code and then issued this command;
root@mythfe0:/home/wes# ir-keytable -c -w /etc/rc_keymaps/myremotes
Then tested that it worked like this]
root@mythfe0:/home/wes# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
555.460958: event type EV_MSC(0x04): scancode
having got ir-keytable the way I want it and all key codes working with
vlc and liblic-client0 removed, I then reinstalled vlc and all the key
codes still worked, even after a reboot. So now I'm guessing that
liblirc-client0 prevents proper setup of the key codes if it is
installed, but after it's
** Description changed:
- Subject pretty says it all. Installing vlc also installs liblirc-
+ Subject pretty much says it all. Installing vlc also installs liblirc-
client0. This hoses up kernel lirc by not allowing some key codes to be
- passed to apps. ir-table -t shows it is working fine.
Public bug reported:
Subject pretty says it all. Installing vlc also installs liblirc-
client0. This hoses up kernel lirc by not allowing some key codes to be
passed to apps. ir-table -t shows it is working fine. Removing liblirc-
client0 fixes the problem but also removes vlc.
** Affects: vlc
I compiled (from a make oldconfig) 4.13.16 w/ CONFIG_RCU_NOCB_CPU=y and
rcu_nocbs=0-15 as a boot parameter. I've been almost 60 hours, which is
a first since buying this machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
These symptoms definitely still happen to me on 18.04 w/
4.15.0-22-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
let me know, if removing files in said directory makes networkd ignore
> interfaces.
I'll test this when I have a spare minute and report back soon
Thanks,
Wes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Changed in: systemd (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/1771236
Title:
forced use of systemd-networkd interferes with ifupdown in 18.04
To
There are plenty of examples, some of them bespoke 3rd party things. An
equally large issue though are legacy technicians who aren't familiar
with systemd's way of doing things yet (I've been trying to get them up
to speed though).
But the crux is if returning to ifupdown is offered as an
Actually, it appears this installer variant won't install to LVM at all,
even if you precreate the LV.
** Package changed: debian-installer (Ubuntu) => subiquity
** Changed in: subiquity
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
This is a feature request/WISHLIST item.
It's pretty common (at least here) for us to format VM images with full-
disk ("whole disk") LVM. Normally we have to drop to a shell and
preconfigure that beforehand so I was super excited to see the new
"Whole Disk" option in the
Well I think it pertains to ubuntu's architecture in general not just
systemd but whatever.
** Package changed: ubuntu => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771236
Public bug reported:
For several reasons, we are not able to use netplan nor systemd-networkd
due to legacy applications that expect ifupdown's pre-up and post-up
script mechanism. The documentation around 18.04's (premature, I feel)
wholesale adoption of netplan claims that one can revert to
After trying to start Nautilus from Unity and failing, I tried invoking
it from the terminal.
$ nautilus .
(nautilus:20662): GLib-GIO-CRITICAL **:
g_dbus_interface_skeleton_unexport: assertion
'interface_->priv->connections != NULL' failed
(nautilus:20662): GLib-GIO-CRITICAL **:
Public bug reported:
have disabled secure boot, removed bitlocker and reformatted drive.
Also, removed Windows 10 hibernation
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic
Public bug reported:
During initial installation buntu 16.04.3 on Dell Inspiron 3000
Unable to install GRUB in /dev/sda
Executing 'grub-install /dev/sda' failed.
This is a fatal error.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721
Public bug reported:
Just said I needed to report a bug on reboot. I had just tried to run
Synaptic to install Skype and it said that it coulldn't run because apt-
get or apt something was already running.
Hans,
Thank you for following up!
Best,
Wes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673583
Title:
dar_split not included in package.
To manage notifications about this bug go to:
https
Further investigation: looks like it's as simple as a missing rule in
~/debian/dar.install for usr/bin/dar_split.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673583
Title:
dar_split not included
Public bug reported:
Neither the Ubuntu version (any release, it appears) nor the Debian
packages have dar_split in the package.
https://packages.debian.org/search?searchon=contents=dar_split=exactfilename=unstable=any
Using 16.04/AMD64 w/
ii dar
Public bug reported:
Because of the dependency "node-ansi (>= 0.3.0-2)", you cannot backport
npm to a PPA for trusty et al, as the ppa prefix is incompatible with
the depends:
The following packages have unmet dependencies:
npm : Depends: node-ansi (>= 0.3.0-2) but 0.3.0-2~ubuntu14.04.1~ppa1 is
** Changed in: juju-core
Milestone: None = 1.25.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network
** Changed in: juju-core
Milestone: None = 1.25.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network don't have
HP Pavillion 15-P214DX Notebook
intel core i7-5500U CPU @ 2.40 GHz
6.00GB
64-bit Operating System, x64-based processor
On Thu, Jun 25, 2015 at 7:48 AM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Wes, thank you for reporting this and helping make Ubuntu better.
Could you
Public bug reported:
There are missing letters, some of the background display is black, etc.
Everything only works properly when I resume boot from the recovery
mode.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu
Public bug reported:
We would like to create an exception to allow for Juju 1.23 to be
included in the package which would provide support for systemd. Our
intent is to land on 23 Mar with systemd features.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
We would like to create an exception to allow for Juju 1.23 to be
included in the package which would provide support for systemd. Our
intent is to land on 23 Mar with systemd features.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
**
I also needed to add NEWS\.Debian to VfilePattern to get ubuntu
changelogs to download.
VfilePattern =
(^|.*/)(Index|Packages(\.gz|\.bz2|\.lzma|\.xz)?|NEWS\.Debian|InRelease|Release|Release\.gpg
Public bug reported:
Bug: Changelogs fail to download in update-manager with apt-cacher-ng in
the default configuration.
Solutions:
1. Enable ForwardBtSoap in /etc/apt-cacher-ng/acng.conf and cross
fingers
# Experimental feature for apt-listbugs: pass-through SOAP requests and
# responses
Encountered this this morning when installing a fresh install of 14.10
in Virtualbox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1340923
Title:
virtualbox-guest-dkms 4.3.12-dfsg-1:
FYI Solution for Android users - use bVNC Free
It accepts this encryption type
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281250
Title:
VNC accessible from non-linux machines only with
1 - 100 of 307 matches
Mail list logo
