Public bug reported:
Occured during Ubuntu upgrade
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: firefox 130.0+build2-0ubuntu0.22.04.1~mt1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.28.1
Thanks for asking, but a year later? Some sort of anniversary
celebration? I don't even remember what that bug was about. The new
problem is that Firefox just fails to show up... But I'm pretty sure it
isn't the firefox package, but one of the lower-level display packages.
When I "upgraded" to Num
Not an Aaeon issue. This board has 2 separate Ethernet chips - one
supports TSN, one does not.
TSN tests will have to properly detect all interfaces that support TSN
so they can be tested separately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
This might be an Aaeon issue; maybe only 1 port supports TSN?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943587
Title:
[Ethtool][TSN] Support frame preemption
To manage notifications about this
I was able to install the snap onto my Aaeon EHL board.
This board has 2 ehternet ports, and I enabled TSN for both of them.
However, only 1 port seems to support frame preemption. Is this
correct?
u@u:~$ sudo ethtool-intel-tsn.ethtools --show-frame-preemption enp1s0
Cannot get frame preemption
Public bug reported:
This is a dual boot. I was trying to reinstall ubuntu over a previous
installation because I was having major issues after moving my
filesystem partition using gparted.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.15 [modified:
lib/partman/automati
Verified with 5.13.0-1007.
** Tags added: cqa-verified
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938298
Title:
[EHL][Graphic]Removing force probe protection from EHL platform
To manage notifi
Verified fixed with 5.13.0-1007.
** Tags added: cqa-verified
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938413
Title:
[ehl] Shutdown hangs on board
To manage notifications about this bug go to
TGL-Aaeon:
20.04LTS Desktop: Detects both interfaces and allows them to get an IP#
when you plug in a cable.
IOTG Desktop (Oct. 13 build): Detects both interfaces and allows them to
get an IP# when you plug in a cable. (Desktop Manual network tests
pass.)
IOTG Core (Oct. 14 build): If you perfor
I see this same behavior on the TGL-Aaeon running Core.
I even tried to manually edit /etc/netplan/00-snapd-config.yaml but I
could not make it bring the interface up.
When the cable is plugged in the link lights are on but the system
doesn't seem to acknowledge the connection.
The other port wo
Public bug reported:
Running cdts.odm-certification
It will ask if specific HW features are available, such as TPM,
Thunderbolt, WWAN, Bluetooth, etc.
While this allows Checkbox to skip that feature area, the respective
tests in Suspend still get run.
This means even if I tell Checkbox that the
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936899
Title:
[IoTG] [TGL-H] TPM tests fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/int
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936903
Title:
CDTS Network (Ethernet) failures
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Public bug reported:
Laptop: Dell XPS-15-9500
OS: Ubuntu Desktop 20.04.3
I plugged in the headphones while watching a video in Firefox.
I expected Ubuntu to detect the headphones and use them for audio
output.
Instead the laptop's built-in speakers continued to be used.
Audio settings did not
That is what I was told to do in the past.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678
Title:
[intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
TGL-H
To manage notifica
Actually I made a mistake. I filed these with iotg-focal-
desktop-20210706.img
This is the only image I've used on the EHL board. I got confused with
the TGL-H board which I've used both Desktop and Core.
So, What is the old kernel you want me to use?
--
You received this bug notification beca
Which is the Old Kernel you want me to try?
All these bugs were filed using
iotg-focal-core-20210722.img (5.11.0-1011-intel)
I then used the patch you gave me on this kernel and retested.
I have managed to have the system hang on booting after a shutdown
twice, but after another 10 shutdowns, it
I spoke too soon.
If you continually shutdown/boot the system, it will hang, about 20% of
the time, at the splash screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938413
Title:
Shutdown hangs
System shuts down properly after this workaround. Fan stops, board LEDs
remain on (system has no LED power indicator.) System boots properly
upon unplugging/plugging back in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Applied the patch as instructed in
https://bugs.launchpad.net/bugs/1938413:
Hi @Doug,
Please use this test kernel to verify this issue.
version: 5.11.0-1011-intel #12+lp1938408~lp1938413
[Installation steps]
1. tar -zxvf revert.tgz
2. cd revert
3. sudo dpkg -i *.deb
After the patch was appli
Me too. After the recent thunderbird update, every time I send an email
results in an extra “point” that I can seemingly get rid of only by
logging out and back in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I rebooted my VM a few times, and was able to remove chromium from Snap.
Not sure why it took more than one reboot but something eventually got
unstuck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
Public bug reported:
Related to bug #1886414
Ubuntu 20.04 LTE desktop VirtualBox VM
Tried installing chromium-browser.
Seemed to hang at "installing chromium snap".
Terminal and desktop were no longer responsive, so I had to reboot the VM,
which apparently left the package manager in an incons
solution of hui wang works for me!
thx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862831
Title:
hciattach on rpi4 times out on first attempt
To manage notifications about this bug go to:
https:
I installed version 5.55-0ubuntu2
did not make a difference.
in journalctl is this :
bluetoothd[40120]: src/main.c:parse_controller_config() Key file does not have
group “Controller”
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Tried the suggestion in comment #9 and that produced the error message
"Invalid client RPC password. Try reinstalling BOINC."
I already did a reinstall using aptitude.
I also found a version of the file at a higher level, but messing with
that one didn't help, either.
--
You received this bug n
The minimal solution of comment #4 did not work for me. I also tried
manually changing the permissions of the file to make it "Read and
write", but I didn't look for the BOINC group, so I'm going to try that
next...
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Not sure why it's marked incomplete at this late date, but if I remember
correctly the problem was fixed not long after I reported it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/492995
Title:
How
Public bug reported:
19.10
Eoan Ermine
A clean install
It failed
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVe
Debian apparently has a separate repository for debug packages. I found and
installed nemo-dbgsym and nemo-fileroller-dbgsym, and re-ran gdb.
(terminal output for gdb without dbgsym is shown in comment #6, above)
No crash.
Ran without gdb.
Crash.
I will attach the no-crash terminal output for
** Attachment added: "nemo_gdb_with_dbgsym.txt"
https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1804978/+attachment/5304903/+files/nemo_gdb_with_dbgsym.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
As of version 4.2.3-2 from https://deb.debian.org/debian testing/main amd64
Packages
bug is still present.
(bring` up external drive in second tab, eject: nemo window disappears)
scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
(2019-0
As of version 4.0.6-1 from https://deb.debian.org/debian testing/main amd64
Packages
bug is still present.
(bring` up external drive in second tab, eject: nemo window disappears)
scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
(2019-01
Well, this was a LONG time ago, and I must have figured out how to get around
the bug, or the bug was fixed, but...
It seems to me that reporting not being able to get Wi-Fi to work, when it had
worked perfectly well in all [L]Ubuntu versions I had used previous to 16.04
(with no fiddling at all
As of Nemo 3.8.5, bug still present.
scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
(2019-01-17) x86_64 GNU/Linux
scott@ASUS-PRIME-B350M-A-CSM:~$ lsb_release -dsc
Debian GNU/Linux buster/sid
buster
scott@ASUS-PRIME-B350M-A-CSM:~$ echo
Hello Kai-Heng,
I see how the fix I provided is included in the 4.4.0, however I don't
see it (yet) in 4.15.0. Is there something I need to do to get this fix
into 4.15.0, or will it eventually percolate through by itself?
Thanks!
--
You received this bug notification because you are a member o
Hello Rafael,
In response to your question. I upgraded my server from Trusty to Xenial
and then found out my NFS services weren't running right. After some
digging I came across this this bug, and I applied the work-around
manually, as I mentioned in my comment #73.
A week or two later I realized
As it turns out, I'd not subscribed to this bug so I didn't get comments
after I posted mine. I had to refer back to my own comment to figure out
the solution since my NFS server apparently broke earlier this week.
An update to nfs-common (I think that's the package that installs the
service files
Not a bug in snapd. Nevermind.
** Changed in: snapd (Ubuntu)
Status: New => Invalid
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Adam Jacobs (bllfr0g)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Laptop is a Lenovo X240.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828828
Title:
Hang on "Started Wait until snapd is fully seeded" during boot
To manage notifications about this bug go to:
ht
Public bug reported:
About 50% of the time, when I boot my laptop, the boot hangs on "Started
Wait until snapd is fully seeded." I *do* have haveged installed.
This started fairly recently. I don't think it existed right after I
upgraded to 19.04, but some additional update after that (I don't
Reported upstream.
It's a shame, it sure seems like moving to the desktop-icons extension
gives up a lot of functionality that was available when nautilus
rendered the desktop. vmware-tools drag-and-drop is gone, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
Recently upgraded from 18.10 to 19.04. Under Preferences/Behavior I
have "Show action to permanently delete files and folders" checked, but
when I right-click a file or folder on the desktop only "Move to Trash"
is offered. This was working previously in 18.10.
jeremiah:~$
This issue just popped up for me after upgrading from 14.04 to 16.04.6.
Per comments #20 and #25, I changed nfs-mountd.service to include
rpcbind.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
This issue just popped up for me after upgrading from 14.04 to 16.04.6.
Per comments #20 and #25, I changed nfs-mountd.service to include
rpcbind.service to the Wants and After statements:
Wants=nfs-config.service rpcbind.service
After=nfs-config.service rpcbind.service
I also added BindsTo and
After I had tested the crash from the terminal, I went back and finished the
install.
This I also invoked from the terminal.
In case the terminal output from a successful install would be useful to
you, I will now attach it here also.
The output appears to be identical prior to where the SegFaul
Public bug reported:
I have tested this a couple of times, and will attach a text file of
terminal output.
I was installing the beta of Lubuntu 19.04 (03/26), and manually editing
partitions.
I had edited a partition, and either hit "Enter" from the partition name
field, or clicked on "OK" (depe
As of the Beta release (03/26) of Lubuntu 19.04, the same thing occurs.
calamares 3.2.4-0ubuntu1
calamares-settings-lubuntu 1:19.04.3
calamares-settings-ubuntu-common1:19.04.3
partitionmanager3.3.1-5
--
You received this bug notification because you are a member of Ubu
As of the Beta release (03/26) of Lubuntu 19.04, the same thing occurs.
calamares 3.2.4-0ubuntu1
calamares-settings-lubuntu 1:19.04.3
calamares-settings-ubuntu-common1:19.04.3
partitionmanager3.3.1-5
--
You received this bug notification because you are a member of Ubu
Yes, confirmed. On my Lenovo x240, kernel 4.18.0-15-generic, I removed
i2c_i801 from the blacklist and no longer can reproduce the hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802689
Title:
Public bug reported:
I just did a Catfish search, and it found the two files for which I was looking
(one a copy of the other, in a different location).
I opened the context menu, to see what it contained.
I saw "Show in File Manager"
Since I do not use the default File Manager for Lubuntu (PCMan
I take it that you found the problem?
Boy - that was fast!
I am curious what it was...
Also,
If it has been fixed, please let me know where and when I can access the
fixed version for "artful", so I can help verify that it now works.
--
You received this bug notification because you are a memb
** Attachment added: "Stitching log file"
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5239910/+files/TKDC9713-28_4_Cyl.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
OK. I have done the SSR recording of the process, and will attach it,
and the .log file (to which I added the terminal output), and the
stitching log and the .pto file.
The logs are from a run later than the one in the video, but it looked
and achieved exactly the same thing (I had somehow messed
** Attachment added: "Hugin .log file, with terminal output appended"
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5239909/+files/Hugin.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Attachment added: ".pto file of same run as hugin.log, and the stitching
.log file"
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5239911/+files/TKDC9713-28_4_Cyl.pto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
No. I was able to reproduce it several times.
When I get a minute, I will Simple Screen Recorder a video showing the
process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815854
Title:
Hugin (et
Here is the .pto file requested.
** Attachment added: "TKDC9713-28-2_Cyl.pto"
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5239392/+files/TKDC9713-28-2_Cyl.pto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
The attached screenshot shows what the desktop with the empty window and empty
Error box looks like, after going away to a different desktop (to file this
bug) and then returning to it.
Part of the window gets erased, but not redrawn with anything, and hence
remains blank, and the rest doesn't e
Public bug reported:
I just tried to do another long (14 picture) panorama (also with a
tripod).
This one had a wide brightness range, which was eventually going to cause a
problem, but I told it to go ahead and align it anyway.
In two different runs-through, I got two slightly different results
** Attachment added: "Screenshot showing enlarged lower bound of crop box
during stitch."
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5238511/+files/Hugin_Squeeze_Bug_2.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
I have a long horizontal panorama (16 photos), that I took with a
tripod.
I opened the images, and told Hugin to align them
I used the Move/Drag tab to slightly rotate the image to be more
horizontal.
I used the Crop tab to approximately match the top/bottom/right/left
edge
Okay, after the latest update (from the 0-13 kernel) it now seems to be
booting normally. I hope that means the problem has been corrected and
this bug can be closed. Perhaps some kind of regression bug?
If anyone over there wants me to collect any additional information
about what was going on, p
I am unable to run that command under the afflicted kernel because the
machine cannot boot under that kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815258
Title:
4.18.0-14-generic unbootabl
The robotic message tells me to change the status to confirmed after
adding the previous comment, but the instructions there say that the
confirmed status is supposed to be done by someone else.
By the way, my current theory (based on weak understanding) is that
there might be some logs of the boo
Oops! Sorry!
I think I actually did check this, but somehow never reported...
In any event, I have just tried it again. NO persistence, on new
computer.
Same result: I actually did a screenshot (which looked just as the previous did)
but of course, without persistence, I could not save it on th
** Description changed:
After the update for the 4.18.0-14-generic kernel the machine freezes on
booting. Machine still books under the 0-13 kernel. Booting in Recovery
Mode seems go normally to the Recovery Menu. At that point it reports
- "Starting Avahi mDNS-SD Stack" and gets and OK. Tha
Public bug reported:
After the update for the 4.18.0-14-generic kernel the machine freezes on
booting. Machine still books under the 0-13 kernel. Booting in Recovery
Mode seems go normally to the Recovery Menu. At that point it reports
"Starting Avahi mDNS-SD Stack" and gets and OK. That is repeat
"LXDE will now use the titlebar layout by default."
Well, time marches on, and Lubuntu now has LXQt.
Should I assume that the comment also applies to LXQt as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
>>> Surprise! <<<
(...sorry...)
I just booted up the live-USB for another purpose (prepping a new SSD to
be used in a new computer, once I have them put it together) and ran the
installer (only as far as the problem window), and it still almost
doesn't show the buttons.
I will attach screenshots
Here is the monitor settings window.
** Attachment added: "MonitorSettings.jpg"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1801441/+attachment/5220766/+files/MonitorSettings.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
The patch was picked up in the stable kernel
(https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/), and
added to 4.19.5, 4.14.84, 4.9.141, 4.4.165, and 4.20-rc4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
I can fairly reliably cause Nemo to crash.
I have to say "fairly", as after multiple crashes, nemo now does something
different.
(More on that later)
To induce the crash, I would mount a USB stick with files on it, and open it in
a second tab.
I then clicked on "Eject", an
Oddly enough, this problem started for me after I mounted a NFS volume
using autofs.
Not quite sure how that relates to samba - but it may mean something.
In response to David Spoelstra's comment. I meant to follow his
direction but accidentally installed samba-common (rather then samba-
common-b
Tested 7.7p1-4ubuntu0.1. Works perfectly.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801128
Title:
OpenSSH 7
My kernel patch was accepted this morning (very quick!!). Per the
notification received:
"The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel
Hello Joseph,
To keep things in sync here (and to make sure the bug doesn't expire due
to inactivity):
1. I worked my way through the process for submitting a kernel patch. (Not for
the faint hearted I might add ;))
2. The patch has been submitted - now I have to wait and see if there's anybody
kmod 25-1ubuntu1.2 looks good on cosmic
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802689
Title:
Upgrade to k
The change I applied to cdc-acm.c is as follows:
--- cdc-acm.orig.c 2018-11-11 11:31:18.754382981 -0500
+++ cdc-acm.c 2018-11-10 17:32:29.802278377 -0500
@@ -1713,6 +1713,9 @@
{ USB_DEVICE(0x0572, 0x1324), /* Conexant USB MODEM RD02-D400 */
.driver_info = NO_UNION_NORMAL, /*
Public bug reported:
I procured a USB modem manufactured by Hiro (model number H50228). This
is in fact a Conexant modem, and while some conexant models are
supported in cdc_adm, this particular type is not.
Hence, when I connect the modem to my system, cdc_adm does not
initialize the modem prope
Another regression: bug 1802689
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786574
Title:
remove i2c-i801 from blacklist
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Public bug reported:
After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
on boot.
After blacklisting i2c_i801 everything works great again.
I realize that this was a fix for bug 1786574, and that helps some other
folks out. I'm not sure what the right fix is but there's got
I was able to boot without persistence (I had been afraid that I would
have to re-"burn" the USB drive without persistence, in order to test
this, but found the 3rd GRUB menu option did the trick).
Lo and behold, the "Trust this executable" was checked.
I have NO IDEA how it could have become un-
/etc/apt/sources.list :
--
deb cdrom:[Lubuntu 18.10 _Cosmic Cuttlefish_ - Release amd64 (20181017.2)]/
cosmic main multiverse restricted universe
deb http://archive.ubuntu.com/ubuntu/ cosmic main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ cosmic-s
I have booted from the install USB drive again.
The icon still exhibits the same behaviour (see screenshot).
regarding libfm-qt5 / casper :
lubuntu@lubuntu:~$ apt-cache policy libfm-qt5
libfm-qt5:
Installed: 0.13.1-5ubuntu7
Candidate:
For simplicity, here's the patch that fixes this bug (and is included in
openssh 7.8):
diff --git a/openbsd-compat/port-net.c b/openbsd-compat/port-net.c
index 7050629c..bb535626 100644
--- a/openbsd-compat/port-net.c
+++ b/openbsd-compat/port-net.c
@@ -185,7 +185,7 @@ sys_tun_open(int tun, int mo
Thanks++
> On Nov 5, 2018, at 02:06, Christian Ehrhardt <1770...@bugs.launchpad.net>
> wrote:
>
> Thanks Thomas!
>
> ** Tags removed: verification-needed verification-needed-bionic
> ** Tags added: verification-done verification-done-bionic
>
> --
> You received this bug notification beca
I don't know if it was a YouTube video, or a website photo, but I later
noticed that a British user's install showed UnitedKingdom, also as one
word...
Perhaps, for some reason, the required text cannot contain white-
space...
--
You received this bug notification because you are a member of Ubu
scott@scott-Asus-M2N68-AM-PLUS:~$ sha256sum
/data/scott/Downloads/lubuntu-18.10-desktop-amd64.iso
99408e73e5ff11727be6987d9b2f8ee3b6a3b672c9da540a63c8b462a0cf63c4
/data/scott/Downloads/lubuntu-18.10-desktop-amd64.iso
I always do a md5sum on my .iso downloads, before burning to USB.
Is this sha
Here is the second of the two screen images.
Note that more time has passed and more notifications have displayed in
the panel.
Seeing this, and that at first nothing seems to happen at all, a first-
time user might be getting worried that maybe something is wrong.
I have a dual-core 3.1 Mhz. sy
Public bug reported:
First, when logging in from the boot screen, there is no indication that the
password entered was accepted.
The image remains on the screen what seems a long time.
So long, that eventually, the boot screen image ends up sharing the
screen with the panel as it is displayed, o
Unfortunately I don't have a bionic server available any more, but I did
upgrade to cosmic and the fix is there, and has been working perfectly.
On 11/2/18 6:29 PM, Steve Langasek wrote:
> Hello Adam, or anyone else affected,
>
> Accepted amavisd-new into bionic-proposed. The package will build
Calamares is apparently NOT present ("dpkg-query: no packages found
matching calamares") on the installed release version of Lubuntu 18.10
(as I had suspected), so I am reporting the 5 separate issues from the
live session. Fortunately, ubuntu-bug seems to work from a live
session...
--
You rece
Public bug reported:
I don't use my Windows partition, except once in a while, when I need files
from it, so I do
not boot from it. When I saw "boot" checked, amongst various other flags, I
unchecked it
(I probably didn't need to - I don't know what all those flags do, anyway...)
On the overview
Public bug reported:
After manually selecting partitions for installation, the overview summary
window is so tall that only the top of the buttons "Back", "Install", and
"Cancel" are visible.
I had to click on the window's Maximize button to see the whole button.
(I think I remember a later wind
Public bug reported:
During the install, when the "System Language" and "...Locale" are displayed,
"UnitedStates" contains no space between "United" and "States".
This is after one selects the language and locale... I don't remember if it is
also true just as one is entering the information i
Public bug reported:
Double-clicking on the "Install Lubuntu 18.10" icon on the desktop in the
live-session results in
the Window "Execute File" appearing, and it asks what we want to do with
"...what seems to be a desktop entry". The options "Open", "Execute", and
"Cancel" appear (with "Execut
Public bug reported:
Upon booting with a USB live system of the release version of Lubuntu 18.10,
the system menu contains two entries that appear to be able to install the new
version.
One is labelled "Install Lubuntu 18.10" and the other is labelled "Install
System".
I don't imagine that we ne
>In particular, #2 makes me question what image you're using. Sounds
like an old one.
I just today downloaded the released Lubuntu 18.10, placed it on a USB
thumb drive, and booted from it. There on the desktop was the install
icon, which when double-clicked upon, yielded the stated window...
I
Public bug reported:
In doing testing for other bugs related to this package, I have noted
that this file manager defaults to displaying files/directories in
reverse order (Z->A, 9->1, etc.)
I don't know if this is a bug, or a design decision, but it seems
counter-intuitive to me...
I just inst
1 - 100 of 908 matches
Mail list logo
