22.04 . Other old bluetooth gadgets attached without issue.
The end result at the very bottom of this page indicates ‘requestor
exited before bonding was completed’ .
root@bill:~# bluetoothctl --version
bluetoothctl: 5.64
root@bill:~# hciconfig -a
hci0: Type: Primary Bus: USB
BD
result at the very bottom of this page indicates ‘requestor
exited before bonding was completed’ .
root@bill:~# bluetoothctl --version
bluetoothctl: 5.64
root@bill:~# hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12
UP RUNNING PSCAN
RX bytes:11627
I see it now within `/usr/share/doc/tzdata/changelog.Debian.gz`, that's
a file I did not check. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2058249
Title:
US
Thank you, that certainly resolves the missing files.
While I understand the reason behind the switch, I can't find where the
"intentional change" is communicated. There is no `apt changelog
tzdata`, and nothing else I see gives me a hint that the package was
split in that way. While it may not
Public bug reported:
On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we
have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata
version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal?
I don't follow the IANA mailing lists, but I had
I have installed the proposed release and the file
/usr/share/zoneinfo/leap-seconds.list expiry date is '28 June 2024'. A
future update should be schedule for May. Thanks for the update.
Test regressions may be related to this change in 2023a data set. If so
test should be updated accordingly.
Public bug reported:
It appears the tzdata package has not been updated with the 2023d
timezone data. Current distribution is 2023c.
leap-seconds.list is expiring Dec 28th 2023,
My fix was to download and extract https://data.iana.org/time-
zones/releases/tzdata2023d.tar.gz. Then copy the
PID ACCESS COMMAND
/dev/snd/controlC0: bill 1876 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Oct 14 08:38:00 2023
InstallationDate: Installed on 2019-11-18 (1425 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
.
Bill
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1916931
Title:
omshell returns inconsistent results or segfaults
Status in isc-dhcp package in Ubuntu:
Expired
Bug
> Bill, Lukas asked a question in comment #10 and set the bug to 'incomplete',
> hoping
> to get feedback from someone who could reproduce the problem. If you can
> provide an
> answer, please do set the bug back to 'confirmed' when answering.
I don't agree with Lukas' a
Hmm, why would an unresolved bug be expired? The problem has been
confirmed by more than one of us. I just finished tested with 22.04 and
can report that the problem persists.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
When using 'gsettings set org.gnome.desktop.interface text-scaling-
factor' command to set the scaling factor to something greater than 1,
the text gets misaligned in the search bar, which seems to be too small
(shown in an attachment here).
ProblemType: Bug
DistroRelease:
Public bug reported:
When I use a desktop interface text scaling factor of 1.5, the alignment
text in the applications menu search bar is not set properly
I have attached a screenshot showing the issue.
1)
Description:Ubuntu 22.04.1 LTS
Release:22.04
2) xorg:
Installed:
The `journalctl -xb` output is attached. The error is noted at time
"Aug 29 11:12:19". I had to press Ctrl-D at the right moment during
boot so that I could get this output. For clarity, I removed the
"nofail" to get this error again, and it is reproducible by
adding/removing "nofail".
**
I tried to use ubuntu-bug to report the lock up of chrome during the
ubuntu-bug reporting process but ubuntu-bug won't allow a report on
ubuntu-bug itself.
bill@bill ~$ ubuntu-bug ubuntu-bug
dpkg-query: no packages found matching ubuntu-bug
FYI - When I attempted to report the bug this page
ance' option
Status in ubuntu-settings package in Ubuntu:
New
Bug description:
In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine.
Ubuntu Forum users report they have an Appearance option in their
Settings app; I don't.
bill@bill ~$ apt show ubuntu-settings
Pack
Public bug reported:
In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine.
Ubuntu Forum users report they have an Appearance option in their
Settings app; I don't.
bill@bill ~$ apt show ubuntu-settings
Package: ubuntu-settings
Version: 22.04.6
Priority: optional
Section: x11
Origin
One more note: While booting, my external (USB) monitor was
disconnected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1981849
Title:
Xorg freeze
Status in xorg package
Public bug reported:
Although I filed this against X11, this might be a kernel issue.
I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't
noted the "reboot required pop-up).
After reboot, the screen was blank/black and unresponsive. Looking at
indicator lights, I believe that
@Robie and @Lukas
Sorry for pushing. May I have your comments on this. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1955997
Title:
The airplane hotkey has
Hi Robie and Lukas,
From our understanding, the concern is only related to Jammy, not focal.
Is that OK to change to fix released on focal.
This is one of the blocking issue for Stella Magneta platform.
We need your help to comment on this. Thank you.
--
You received this bug notification
Hi Robie,
May we have your comment on this. Since we would like to have this
solution in the latest kernel, need you help to check on this. Thank
you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Ok, but the standalone clock indicator works. The clock in "indicator
applet complete" doesn't. See https://i.stack.imgur.com/x11A4.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
This happens for me on 20.04 LTS when the file being copied has a colon
(:) in its name. The error doesn't pop up until the very end of the
file copy process, and in the end, the file is not copied to the
destination.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
This command should non-interactively obliterate whatever partition
table is on /dev/sde, and create a new table with a linux partition that
spans the whole disk:
- $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label
+ $ sfdisk --label gpt
Public bug reported:
This command should non-interactively obliterate whatever partition
table is on /dev/sde, and create a new table with a linux partition that
spans the whole disk:
$ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label
gpt -T | awk '{IGNORECASE = 1;} /linux
Public bug reported:
This command should theoretically fetch all PDFs on a page:
$ wget -v -d -r --level 1 --adjust-extension --no-clobber --no-directories\
--accept-regex 'administrative-orders/.*/administrative-order-matter-'\
--accept-regex 'administrative-orders.*.pdf'\
Public bug reported:
This code should in principle (per the docs) fetch a few *.pdf files:
$ wget -r --level 1 --adjust-extension --relative --no-clobber --no-directories\
--domains=ncua.gov --accept-regex 'administrative-orders/.*.pdf'\
Public bug reported:
There is no good reason for this command to fail:
$ wget --quiet -O -
https://web.archive.org/web/20210721004028/freefontsdownload.net/download/76451/lucida_fax.zip
| gunzip -
The output is:
[InternetShortcut]
URL=HOMESITEfree-lucida_fax-font-76451.htmgzip: stdin has more
** Changed in: maas
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1918970
Title:
Unable to netboot Ubuntu 18.04 and older on an IBM
** Description changed:
SSL2 and SSL3 have been hastily removed, apparently by developers who
are unaware that these protocols serve purposes other than encryption.
SSL2/3 is *still used* on onion sites. Why? For verification. An
onion site has inherent encryption, so it matters not
Public bug reported:
cURL supports a -ssl3 option (and rightly so), but openssl removed it
prematurely (see
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1934040). The
fallout:
torsocks curl --insecure --ssl-allow-beast -ssl3 -vvI
https://xhfheq5i37waj6qb.onion:110 2>&1
* Trying
Public bug reported:
SSL2 and SSL3 have been hastily removed, apparently by developers who
are unaware that these protocols serve purposes other than encryption.
SSL2/3 is *still used* on onion sites. Why? For verification. An
onion site has inherent encryption, so it matters not how weak the
Public bug reported:
With x11 not running, this was executed: "Xorg -configure". It should
simply build a configuration file. The output below appears in the
terminal with an error. It manages to create a config file anyway, but
what it creates causes "startx" to fall over. So I am forced to
The socks.c code shows that cURL does not even attempt DNS resolution on
SOCKS4a. Strictly speaking, the SOCKS4a spec expects apps to /attempt/
DNS resolution before contacting the socks server. I won't complain on
this point though because the status quo is favorable to Tor users (as
it
According to the SOCKS4a spec:
https://www.openssh.com/txt/socks4.protocol
https://www.openssh.com/txt/socks4a.protocol
With SOCKS4 cURL *must* do DNS resolution and pass the selected IP to
the SOCKS server. OTOH, SOCKS4a gives cURL the option to resolve. If
cURL fails at DNS resolution,
Public bug reported:
This is how a Tor user would use cURL to grab a header, and also expect
to be told which IP address was contacted:
curl --ssl --socks4a 127.0.0.1:9050 -L --head -w '(effective URL =>
"%{url_effective} @ %{remote_ip}")' "$target_url"
It's broken because the "remote_ip" is
This is actually a security issue and it's surprising it's gone unfixed
for 9 years. It's inconsistent for apt to check the hash on deb files
that it downloads, but then neglect to do so on user-supplied deb files.
The status quo is a recipe for disaster. To exacerbate the problem, the
man page
Public bug reported:
man page shows:
-nd
--no-directories
Do not create a hierarchy of directories when retrieving
recursively. With this option turned on, all files will get saved
to the current directory, without clobbering (if a name shows up
more than
A secondary bug manifests from this, whereby sfdisk chokes on its own
output and therefore cannot restore its own backup. E.g. suppose
another tool is used to put a BIOS boot partition from sector 34 to
2047, as follows:
$ sgdisk --clear -a 1 --new=1:34:2047 -c 1:"BIOS boot"
Public bug reported:
According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's
both legal and interesting to place the BIOS BOOT partition from sector
34 to sector 2047, as follows:
$ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF
start= 34, size=2013,
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1925973
Title:
Nvidia driver 450.119 crashes lxpanel on Ubuntu
Public bug reported:
Running Ubuntu 18.04 with the LXDE desktop.
After installing the Nvidia driver version 450.119 and rebooting, the
LXDE desktop crashes, specifically lxpanel.
Reloaded clonezilla clone of / with Nvidia driver 450.102, all is well
again.
ProblemType: Bug
DistroRelease:
For me the fact that the upstream repo moved from bugzilla.samba.org to
github.com is sufficient to diverge from upstream. But to each his own.
My contempt for github is in fact why I reported the bug downstream. I
will not use github but I still intended to make a public record of the
bug, hence
** Description changed:
Rsync has an astonishing and dangerous bug:
The dry run feature (-n / --dry-run) fails to report file deletions when
--remove-source-files is used. This is quite serious. People use --dry-
run to see if an outcome will work as expected before a live run. When
Public bug reported:
Rsync has an astonishing and dangerous bug:
The dry run feature (-n / --dry-run) fails to report file deletions when
--remove-source-files is used. This is quite serious. People use --dry-
run to see if an outcome will work as expected before a live run. When
the simulated
I imported version 4.4.2 from upstream and built for focal. The problem
persists. OMAPI failover queries work sometimes and fail most of the
time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Changed in: fonts-noto-color-emoji (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1917183
Title:
Font spacing and rendering
Public bug reported:
I have just built a Ubuntu 20.04 server and installed isc-dhcp-server
4.4.1 on it and I am seeing inconsistent returns from omshell.
Initially omshell returns data as expected, but when I exit and re-enter
omshell connections fail.
Here is the initial, working, session:
#
Public bug reported:
When running:
$ pdfimages -list grayscale-document.pdf
the output is:
```
page num type width height color comp bpc enc interp object ID x-ppi
y-ppi size ratio
Some follow-up with users from the Ubuntu MATE Community forums show
that this is occurring on Focal and Groovy; with 5.4, 5.8, and 5.10
kernels.
Following is a list of hardware and graphics information from affected users:
System:
Host: huppyryzen Kernel: 5.4.0-54-generic x86_64 bits: 64
*** This bug is a duplicate of bug 1890394 ***
https://bugs.launchpad.net/bugs/1890394
Sounds right, thanks! I was morally certain it would have been reported
previously, but I couldn't find it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
After installing routine updates including systemd version
237-3ubuntu10.43 this 32 bit Lubuntu 18.04 booted to a black screen with
a blinking cursor.
I booted to recovery mode and removed the systemd update. This gave me a
normal boot.
ProblemType: Bug
DistroRelease:
This is confirmed working correctly on Ubuntu MATE with 20201022 re-
spin.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1897934
Title:
[SRU][Intel HDA] The initial
This breaks Screen Reader installs for Visually impaired users and
breaks testcase #1305
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1897934
Title:
[HP 14-ac100na
This is occurring on 20.10 Ubuntu MATE 20201021.2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1897934
Title:
[HP 14-ac100na N9S73EA#ABU] The initial sound level is
Same problem for me. I have an old parallel-only printer. It has been
working with a dedicated printer server, but the printer server died and
the PC has no parallel port. So I connected a USB-to-LPT cable. As I
attach the cable /var/log/syslog shows:
parport0: fix this legacy no-device port
rule read but "RUN" command is not executed
Status in systemd package in Ubuntu:
Invalid
Bug description:
The following was introduced as
"/etc/udev/rules.d/99-harvest_camera.rules":
ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C3
Public bug reported:
I wrote a udev rule that would not trigger when expected. I spent 2
days working on it, trying to understand what the problem was. I
finally figured it out -- it was a matching problem:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836
The most verbose output
PEBKAC
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Bill Yikes (yik3s)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
TION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D",
RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh"
When the device is attached, it gets mounted but the harvest_camera.sh
script does not execute. The udev_log=debug pa
UUID_ENC}=="C355-A42D",
RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh"
When the device is attached, it gets mounted but the harvest_camera.sh
script does not execute. The udev_log=debug parameter is set in
/etc/udev/udev.conf. Verbosity was also
Public bug reported:
The following was introduced as
"/etc/udev/rules.d/99-harvest_camera.rules":
ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D",
RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh&q
Notice also there is a serious transparency problem. The output only
shows files for which removal failed. This acutely heightens the
destruction because it potentially destroyed *thousands* of files as I
sat there and let it run. The tool gives no idea how what's being
destroyed. The admin
Public bug reported:
The man page for udevadm neglects to mention options which seem to only
be documented in stackexchange. E.g.
udevadm monitor --environment
udevadm control --reload-rules
>From the man page, it's unclear what the difference is between /udevadm
trigger/ and /udevadm test/.
Sorry, i mean to say /var/log/syslog (not /var/log/system) shows the
device was attached.
The verbosity in /var/log/syslog increases when udev_log=debug, but
still no /var/log/udev.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1844426
Title:
*** This bug is a duplicate of bug 1873895 ***
https://bugs.launchpad.net/bugs/1873895
** This bug has been marked a duplicate of bug 1873895
Regression: block staircase display with side-by-side monitors of different
pixel widths
--
You received this bug notification because you are a
Public bug reported:
My laptop (Lenovo ThinkPad P51) has 2 display interfaces. One mini-dp
and one HDMI. But none of them is shown in xrandr, and my external
display connected through mini-dp is not detected also.
When I used LiveCD, the external monitor works normally. The above
situation
Link to crash report from step #2:
https://errors.ubuntu.com/oops/88d785d4-80ba-11ea-a860-fa163ee63de6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1873386
Public bug reported:
Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on
20200416.
Upon reboot system should error and error for nmcli.
Crash file located in /var/crash
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature:
Public bug reported:
Ubuntu MATE 20.04 updated 03312020
Hesitation on login to system
Login successful
System reports error and crash file located in /var/crash
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic
Tested with latest packages in proposed Ubuntu MATE and able to install
and use balena-etcher-electron.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1869716
Title:
*** This bug is a duplicate of bug 1869716 ***
https://bugs.launchpad.net/bugs/1869716
https://packages.ubuntu.com/bionic/libpango1.0-0
** Package changed: ubuntu => pango1.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Still stuck on version 7.5 3 months later.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1856054
Title:
pulseaudio now depends on libsnapd-glib1 which recommends
Using 20.04 current build still see:
$ python
Command 'python' not found, but can be installed with:
If I run sudo apt install python
Package python is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from
Public bug reported:
Run sudo apt dist-upgrade on 20.04 install.
Expected result:
python3 is updated without issue
Actual result:
After this operation, 1,114 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu focal/main amd64
@seb128 this is working correctly now after the grilo update.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1856927
Title:
totem crashed with SIGSEGV in
nVidia driver 340.107 is available, however switching to that in
Software & Updates has resulted in some issues.
After Apply Changes, I am kicked to the Nouveau driver.
And I get an ErrorBrokenCount > 0
Trying to resolve with sudo apt --fix-broken install as recommended by
apt gives me:
The
Public bug reported:
System is Ubuntu MATE 18.04.3 T430 with nVidia
On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no
issues.
On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no
issues.
System was rebooted today.
Expected outcome:
System
I have an Nvidia based video card that has 2 DVI outputs, an HDMI
output, a DisplayPort output. I have 2 monitors that are plugged in to
the DVI outputs, and nothing plugged in to the HDMI or DP outputs. And
still, XUbuntu insists on switching audio to the HDMI outputs that have
nothing plugged
I'd prefer that the message be suppressed when the packages in question
are pinned. In this case, not updating them is the desired action, and
errors/warnings are not appropriate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
A recent update to unattended-upgrades causes messages to be displayed
at login similar to this: "1 updates could not be installed
automatically. For more details,see /var/log/unattended-upgrades
/unattended-upgrades.log"
However, when the user has pinned/held a package,
*** This bug is a duplicate of bug 1441460 ***
https://bugs.launchpad.net/bugs/1441460
I'm using Mint 19.2 XFCE. I went with chrisc1073 setup and things seem
to be working fine. Thanks for the help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks for the quick response.
Yesterday to fix the issue, I uninstalled the resolvconf package. I
reinstalled it today, and now it is working with the correct "search"
domain.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
When I rebooted my system after an update, `/etc/resolv.conf` was
symlinked to `/run/resolvconf/resolv.conf`. That file did not have my
local domain name in the search even though it is supplied by the dhcp
server. The systemd resolv.conf file (in
Public bug reported:
crashes on start up of gui
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.6
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
udev:amd64:
I see the messages (starting with "Could not find key with description")
on a fresh install of Linux Mint 19 Cinnamon.
Second line of kern.log says: "Linux version 4.15.0-36-generic
(buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
#39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
Hi is not merged on 4.16 / 4.17 / 4.18 / 4.19 for what ?
https://forum.manjaro.org/t/asus-e200ha-no-sound/44205/17
marcin19883 say : Kernel 4.19 RC1 Audio not working. No codec include. :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
ly a Manjaro problem, not an upstream
> problem.
>
> On Sat, Jul 14, 2018 at 4:15 AM,
> wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=115531
> >
> > liberodark (bill@live.fr) changed:
> >
> >
No problem. I really forgot about it.
Bill
On Sun, Aug 5, 2018 at 2:32 PM, gf <533...@bugs.launchpad.net> wrote:
> Thanks for the update, Bill. I am just trying to clear up these old
> tickets. I will close the report now.
> Have a great day!
> :)
> G
>
> Clo
I have no idea if this was resolved. It's at least 10 years since I had an
HP-5400 I quit using Ubuntu when it became too much like Windoze. Other
distros work fine.
On Sun, Aug 5, 2018 at 10:19 AM, gf <533...@bugs.launchpad.net> wrote:
> Hello Bill,
> Thank you for submitt
For anyone that's interested ---
I added the following to root's crontab:
@reboot sleep 120 && /bin/systemctl restart sshd
That works for me to get sshd up AND listening
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Robie: If the service offers a mechanism to set a specific NIC to listen
on, then the service should make good on that offer when it's requested.
Doesn't that make sense to you?
All services that require a NIC to function should wait for that NIC to
come alive. Having a service start or attempt
I created Bug 1774788 which is for rsyncd not starting at boot and was
provided with a fix by Andreas Hasenack that works. I tried using that
fix for ssh and it does not work.
Both services fail when an attempt is made to specify a particular NIC
via their respective config files. In the case of
Public bug reported:
Description: Ubuntu 18.04 LTS
Release: 18.04
ubuntu-keyring: Installed: 2018.02.28
apport: Installed: 2.20.9-0ubuntu7.2
cowbuilder: Installed: 0.86
On a bionic system when attempting to report what I suspect is a bug in
ubuntu-keying I got the
I'm a recent convert to Ubuntu, having been on Fedora from FC2 through
F26; quite a long time. Over the last few years, their support became
nonexistent. Bugs reported would not even be acknowledged, much less
worked on. To have someone actually respond to a bug report is so
unusual in my
I'm impressed!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1774788
Title:
Daemon won't start at boot up (18LTS fully patched)
Status in rsync:
Unknown
Status in
Public bug reported:
By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon
fails at boot.
Once the NIC(s) is/are up, it will start fine when executed via
systemctl start rsync
● rsync.service - fast remote file copy program daemon
Loaded: loaded
I installed version 16LTS recently and just upgraded the box to 18LTS
and both display the error.
I have 2 NICs (Private / Public) with an sshd config file set to only
listen to the private side. It appears sshd attempt to start after the
Public NIC is up, but before the private NIC is available.
1 - 100 of 2491 matches
Mail list logo
