I just got caught up by this bug as well with Kubuntu 24.04. I think it
started happening when I replaced the firefox snap with Mozilla's apt
repo as listed here - https://support.mozilla.org/en-US/kb/install-
firefox-
linux?utm_source=www.mozilla.org_medium=referral_campaign=firefox-
Just a quick heads up (GA-790FXTA-UD5-rev-10 motherboard), adding the
...
optional: true
...
to the 50-cloud-init.yaml does indeed solve the bug.
I had exact same situation with twin ethernet port on my motherboard. It
is now solved.
OT:
Can't believe in a long time Google actually found an
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1970778/+attachment/5585155/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970778
apport information
** Tags added: apport-collected
** Description changed:
I was just installing the latest 22.04 upgrade on 21.10. While watching
the terminal output something was "not found".
Then at the end it said
"Tex-Common Package" was not working and that I should file a
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1970778/+attachment/5585154/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I was just installing the latest 22.04 upgrade on 21.10. While watching
the terminal output something was "not found".
Then at the end it said
"Tex-Common Package" was not working and that I should file a bug
report.
Then it reverted back to 21.10.
And I'm filing a bug
Installing Kubuntu 22.04 LTS with a 250 MB /boot partition resulted in this
message:
installed initramfs-tools package post-installation script
subprocess returned error exit status 1
Decent chance it's the same fundamental issue at work (14 years later?)
as it left /boot filled with some
Public bug reported:
I'm not sure of any further details. The install fails.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl
Public bug reported:
I chose "Erase Disc" with no advanced options.
Additionally got the message "Installation Complete: Installation is
complete. You need to restart the computer in order to use the new
installation."
I will attempt another clean install. This time I will try the LVM
advanced
Paul,
Thanks for responding to the bug report. Have been attempting to get
this Ricoh Aficio SG3110DN printer working on Ubuntu 20.04 for a few
days now with no success. Works fine with Windows 10, so I am stumped.
Any ideas?
Don McCormick
On 12/23/21 11:22 AM, Paul White wrote:
> ** T
Public bug reported:
Just dual booted Ubuntu 20.04 and all works well except the printer driver for
Ricoh Aficio SG3110DN provided in Add New Printer indicates that the printer is
not responding. Printer works fine on same machine using Windows 10 OS.
What is the fix?
Printing trounleshooter:
I updated the SRU Justification
** Description changed:
SRU Justification:
Impact:
-
+ Update the smartpqi driver with latest kernel.org patches from git repo:
+ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
+
+ These patches will align the Canonical smartpqi driver
Added Jeff Lane, Scott Benesh, Gerry Morong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953689
Title:
smartpqi: Update 20.04.4 to latest kernel.org patch level
To manage notifications about
Public bug reported:
Here is a list of patches that need applied to 20.04.4 to bring the
smartpqi up to date with kernel.org.
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055
*** This bug is a duplicate of bug 1849859 ***
https://bugs.launchpad.net/bugs/1849859
I realize the last post here was almost two years ago, but I am new to
Ubuntu, having recently wiped my drive to completely remove Windows from
my laptop.
Funny enough, my reason for getting rid of Windows
I wanted to add to this as well I downloaded this build as well and I
can see my DHCP offer the IP address but the Ubunutu server does not ACK
the offer or even see it from tcpdump. This is also on unRAID as well
using VirtIO network adapter.
--
You received this bug notification because you are
Completed my testing.
System Information
Manufacturer: HPE
Product Name: ProLiant DL385 Gen10
Version: Not Specified
Serial Number: 2M2935031X
UUID: 37383738-3831-4d32-3239-333530333158
Wake-up Type: Power Switch
SKU Number: 878718-B21
What you need is some verification tests?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933518
Title:
Update SmartPQI driver
To manage notifications about this bug go to:
I installed the provided kernel package and thus far performed:
1. reboot tests
2. insmod/rmmod tests
3. fio testing: no performance regressions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933518
-0ubuntu3.29
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: don2065 F pulseaudio
CurrentDmesg:
[ 36.463703] init: plymouth-upstart-bridge main process (1265) killed by
TERM signal
[ 49.032303] audit_printk_skb: 33 callbacks suppressed
Public bug reported:
After cleaning the PPA up by removing packages, I still am not able to
upgrade.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.41 [origin: unknown]
ProcVersionSignature: Ubuntu 5.4.0-56.62~18.04.1-generic 5.4.73
Uname: Linux
This should be closed. I found out that I had packages from a ppa
repository which were duplicates of standard ubuntu packages. So this
bug report should not even been submited.
Useful commands to solve this problem were:
for name in `dpkg -l | gawk -e '{print $2}'` ; do apt-cache policy $name;
This should be closed. I found out that I had packages from a ppa
repository which were duplicates of standard ubuntu packages. So this
bug report should not even been submited.
Useful commands to solve this problem were:
for name in `dpkg -l | gawk -e '{print $2}'` ; do apt-cache policy $name;
Public bug reported:
removed rc packages and it still fails . all current packages are ii
status
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
Public bug reported:
Description:Ubuntu 18.04.5 LTS
Release:18.04
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules:
Public bug reported:
This system originally had Ubuntu 16.04 LTS and now has 18.04. After
removing all PPA, the upgrade continues to fail.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic
ok, can i at least assume that shim is not required? that was my main issue.
i wanted a single unencrypted file (grub + initramfs by another name:), and, my
chain of trust.
that is the key for me, if there is a requirement to only use shim and
the microsoft keys, i'm in trouble.
if its simply
** Changed in: grub2 (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890672
Title:
secure boot fails after upgrade to grub2-common 2.04-1ubuntu26.2
To manage
I'm the author of that secure boot package.
I think you might misunderstand... what it does is put all the grub config etc
into a signed initramfs. So you cannot change the grub.cfg.
Also, to sign the binaries you need the GPG keyring and the passphrase.
The objective is to *not* use the shipped
Public bug reported:
As suggested here -
https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/691633 -
I'm putting this as a bug report, even though it's mainly a Feature
request.
Not copying user settings to /etc/skel and not configuring /etc/fstab on
the new user installed are bugs,
Observing on Focal 20.04 on ROG STRIX X470-I, same ALC1220 audio device.
Its intermittent, sometimes audacity will record properly. Sometimes it
will record slow and playback fast.
its not just audacity, e.g. chrome observes same affect
(https://mictests.com/)
bumped kernel to
Hi Erich, I was able to test this today. I completed the test case
outlined above with no problems. It does fix the issue I reported.
Thanks!
Don
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Ok, thanks! Let me know if you would like me to do some testing of the
new package. If so, also please let me know where to find it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877806
Title:
FYI, this is reproducible on a fresh install on a completely different
system. Also, this affects ALL lv2 plugins that I have tried. The
ladspa plugin presets seem to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
gmentation fault (core dumped)
AFAIK, teh preset add and save functions work for ladspa plugins.
-Don
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ardour 1:5.12.0-3ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30
Uname: Linux 5.4.0-29-lowlatency x86_64
ApportVersion: 2.20.11
Public bug reported:
This is the same problem reported about 2 hrs ago.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Public bug reported:
The install was running fine the it crashed and reported failure to
write grub to the EFI folder.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
To the second question - yes, per the askubuntu link, I executed `sudo
apt remove backport-iwlwifi-dkms`. After I did that, wifi seemed to work
normally.
I should note that the output of `lspci -nnk` is from after executing
the remove command.
Would it help to re-install the backported driver,
Hello,
It has been a number of years since I have used Ubuntu and then it was always
on an installed version.
I was using a desktop system that had a dvd drive so I could install from the
burned dvd.
Now none of my systems have dvd or cd drives, so I need to get a working copy
of
In the referenced bug, another reporter was asked to give the output of
lspci -nnk. In case it helps, here's the output of the command from my
machine:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b51]
Subsystem: Dell Device [1028:0962]
00:02.0 VGA compatible controller
Public bug reported:
Per instruction in https://bugs.launchpad.net/ubuntu/+source/backport-
iwlwifi-dkms/+bug/1869587/comments/10, I am filing a separate bug that
is probably related to #1869587.
After upgrading my Dell XPS 13 7390 Developer Edition from Kubuntu 19.10
-> 20.04, wifi performance
@You-Sheng,
Done - https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/+bug/1877217
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869587
Title:
WiFi performance is slow
To manage
In case it helps - I dug a little deeper and technically, the wifi card
in my Dell XPS 13 7390 is a Killer AX1650 card, which is apparently just
based on the Intel AX200 chipset. Not sure if it matters, but a small
detail.
--
You received this bug notification because you are a member of Ubuntu
Ended up here via https://askubuntu.com/questions/1230525/ubuntu-20-04
-network-performance-extremely-slow
I've got a Dell XPS 13 7390 Developer Edition with the AX200 wifi
chipset. Upgraded to 20.04 from 19.10. Post-upgrade, wifi speeds were so
slow webpages would not load. After removing the
18.04 still uses Snort 2.9.7.
Current community rules
(https://snort.org/downloads/community/community-rules.tar.gz) are incompatible
with this version.
** Summary changed:
- 16.04 Snort 2.9.7 is EOL at March 13!
+ 16.04 / 18.04 - Snort 2.9.7 is EOL at March 13!
--
You received this bug
To add to my earlier comment, it also happens when copying between
Ubuntu applications. In this case, a rather poor workaround is to copy
twice or even three times which usually will eventually grab the text
being copied.
--
You received this bug notification because you are a member of Ubuntu
Often cannot copy and paste between Notepad++ and Firefox or even
Terminal. If I open GEdit, I can paste there, then copy again which
seems to be a workaround though not a very good one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have this exact issue, and I have a ~200GB syslog file because of it.
I'm not experienced enough to do forensics on this, if anyone has some
idea where to look I'll help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see this, too, on two different machines (one at home, one at work),
both desktops with two monitors. Though for me the delay is usually
longer then five seconds. The duration of the delay seems to increase
with how long the machine's been up since its last reboot. This was not
present when I
Quick update--the newest BIOS update to my motherboard seems to have
fixed this issue.
I am using the MSI B450i MB and the new AMD ComboPI1.0.0.3abba seems to
make this issue go away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211955
Title:
file-roller crashed with SIGSEGV in gtk_box_pack()
To manage notifications about
Hey sorry for the lack of updates. Been busy with school... I'll
hopefully get that thing done Friday night (US time)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842785
Title:
Freeze after
Public bug reported:
My system is a newly build Ryzen 3600 based system with Vega 56
graphics.
On suspend wakeup, the entire system locks up. A workaround is booting
with linux kernel version 4.19.69.
Using newer linux versions (5.3-rc7) did not fix the issue.
The motherboard is an MSI B450I
Public bug reported:
Ran dist package upgrade, it gave error.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ntp 1:4.2.8p10+dfsg-5ubuntu7.1
ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185
Uname: Linux 4.4.0-159-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture:
Public bug reported:
I have a script that is triggered by a udev rule, and that needs to
connect to a remote host.
The example below works fine in 16.04, but fails in 18.04. It seems that
the process executing the script is somehow limited wrt. network access.
The script works fine when started
If the problem is corrected as stated by Mauricio Grueso (Above) Why has
this not been fixed? His note was dated June of LAST YEAR! This fix
might also fix the MANY other bugs of the same type I have encountered.
I am no programmer so I really don't know how to incorporate Grueso's
fix. Thank you,
Thanks!
[VERIFICATION XENIAL]
1) Used vagrant init ubuntu/xenial64 to create new instance.
2) Used vagrant ssh to login.
3) Added "session required pam_tty_audit.so enable=*" at the top of
/etc/pam.d/common-session
5) Installed 1.1.8-3.2ubuntu2.2 from xenial-proposed
6) Tried to use in with new
Public bug reported:
I can't give any useful information because I have no idea what is going
on. None of the instructions below are even remotely understandable to
me. I use computers, I do not understand them, sorry.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.12
Ubuntu 18.10 latest Wine, Safari loads no sites with https and nothing
to do with PlayOnLinux. Was just playing with it anyway so will
uninstall Safari as no desire to fight it to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[VERIFICATION COSMIC]
1) Used vagrant init ubuntu/cosmic64 to create new instance.
2) Used vagrant ssh to login.
3) Added "session required pam_tty_audit.so enable=*" at the top of
/etc/pam.d/common-session
4) Tried to use in with new vagrant ssh session (package 1.1.8-3.6ubuntu2):
DOES NOT
Sorry for the delay and thanks for the feedback and effort Eric!
Please find the new Xenial debdiff (xenial-fix-for-lp-1666203-v2.debdiff)
attached.
I tested the update and verified that it works.
I also tested the Bionic update and verified that it works as intended.
** Patch added:
Thanks Steve!
However, what is the status for Xenial and Bionic?
The bug seems closed now (status: fix released), can someone reopen it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666203
Title:
** Changed in: corosync (Ubuntu)
Assignee: (unassigned) => Don van der Haghen (donvdh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809682
Title:
"systemctl enable corosync-qdevice
Attached debdiff, based on corosync (2.4.3-0ubuntu1) for Ubuntu
18.04/bionic removes the debian/corosync-qdevice.init script from the
package. If already installed previously, it removes the /etc/init.d
/corosync-qdevice script through the corosync-qdevice.postinst script
upon package upgrade.
I
Please see attached patch for Ubuntu 16.04/Xenial.
I have tested and verified that the patch works as intended.
** Patch added: "xenial-fix-for-lp-1666203.debdiff"
https://bugs.launchpad.net/debian/+source/pam/+bug/1666203/+attachment/5236239/+files/xenial-fix-for-lp-1666203.debdiff
--
You
Thank you all very much for the responses.
I added the description, origin and bug headers to the bionical debdiff,
new debdiff is attached.
I was able to reproduce the issue on xenial using vagrant, I will create
and test a patch.
** Patch added: "bionic-fix-for-lp-1666203-v2.debdiff"
Thank you both very much for the responses.
Toru: I just tested this on another 16.04 system (now with kernel
4.4.0-142-generic) and was unable to reproduce the issue there also. I
was able to reproduce the issue on both Bionic systems I tested however.
So there seems to be a difference between
.
** Changed in: pam (Ubuntu)
Assignee: (unassigned) => Don van der Haghen (donvdh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666203
Title:
pam_tty_audit failed in pam_open_session
To man
Attached patch (which is based on pam_1.1.8-3.6ubuntu2) fixes the issue for
Ubuntu 18.04/Bionic
Following fix was implemented as mentioned by the reporter of the LP bug:
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee
I tested the patch and it indeed
Public bug reported:
root@bionic-test ~ # dpkg -l python-diamond
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
I forgot to mention, this bug report concerns:
Ubuntu 18.04
Package: corosync-qdevice
Version: 2.4.3-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809682
Title:
"systemctl enable
Public bug reported:
"systemctl enable corosync-qdevice.service" fails:
Synchronizing state of corosync-qdevice.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable corosync-qdevice
update-rc.d: error: corosync-qdevice
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200778
Title:
bamfdaemon crashed with signal 5 in _XReply()
To manage notifications about this bug
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304540
Title:
bat crashed with SIGSEGV
To manage notifications about this bug go to:
Buenas noches les cuento que hoy complimos 13 años de la existencia de esta
comunidad que tanto defendí, lamentablemente anuncio mi retiro definitivo
de la comunidad después de 9 años y 8 meses.
Como herencia les dejo un sin fin de eventos liderados:
https://wiki.ubuntu.com/ColombianTeam/Eventos
Public bug reported:
This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by
pulling the following patches from upstream kernel version 4.19-rc7.
Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date
with kernel.org and to
correct issues seen
It is now going on 5 years and this bug is still alive and well. I'm
trying to migrate off of 14.04.5, and need to use tar for creating
backups of folders and files to analyze for migration purposes. This
bug is getting in the way of my work. I copied the live folder / files
to an intermediate
It seems this regression has been introduced through
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900912
** Bug watch added: Debian Bug tracker #900912
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900912
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Bug watch added: JOSM bug tracker #1
http://josm.openstreetmap.de/ticket/1
** Also affects: josm via
http://josm.openstreetmap.de/ticket/1
Importance: Unknown
Status: Unknown
** Changed in: josm
Importance: Unknown => Critical
--
You received this bug
it "failed to build", but in the link they say it ran out of virtual
memory on their MIPS architecture build.
i would guess what happened is that gcc on their build machine ran out
of memory, on the file cgalutils.cc . It is actually pretty normal to
have memory issues when building OpenSCAD on
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594
This bug, or what I believe to be this bug and not 1735594, cropped up
for me in an update on July 24, 2018 to kernel 4.4.0-131. Have spent the
last week + searching the web and residing trying to figure
Solved! A few days ago I unplugged and reinserted it at both ends but
still couldn't print. However, after making man software changes and
still not printing, I unplugged the USB cable, flexed it at both ends,
and reinserted it and Ubuntu immediately detected the printer, warned
about drivers,
lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 005 Device 002: ID 046d:c312 Logitech, Inc. DeLuxe 250 Keyboard
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID
Done
On 07/26/2018 02:05 PM, Till Kamppeter wrote:
> Please run the following commands and post the output here:
>
> lsusb
> sudo /usr/lib/cups/backend/usb
> /usr/lib/cups/backend/hp
> ps auxwww | grep ippusbxd
>
> Also run
>
> sudo lsusb -vvv > lsusb.txt 2>&1
>
> and attach lsusb.txt to this
Public bug reported:
This printer worked great prior to Ubuntu 18.04. Days of repeated fresh ubuntu
18.04 installs and trying stock hplip, removing and reinstalling it, removing
it (all with pkg mgr), downloading and running latest HPLIP script, the printer
is not seen by USB (it is on, power
The way of configuring /etc/network/interfaces* seems to be changed.
https://github.com/openvswitch/ovs/blob/master/debian/openvswitch-switch.README.Debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
esperamos
**Mas info:**
https://t.me/ubuntucolombia
https://ubuntu-co.com/2018/07/19/gran-curso-preparatorio-lpic-1-e-introduccion-lfcs-y-rhcsa/
https://t.me/UcoClassroom
--
= Don Forigua ==
--
Al escribir recuerde observar la etiqueta (normas) de esta lista:
http://goo.gl
Version 13860 has been released:
https://josm.openstreetmap.de/wiki/Changelog#stable-release-18.05
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770391
Title:
Ubuntu 18.04 josm: No valid JVM found
*** This bug is a duplicate of bug 1770391 ***
https://bugs.launchpad.net/bugs/1770391
** This bug has been marked a duplicate of bug 1770391
Ubuntu 18.04 josm: No valid JVM found
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This has been fixed upstream in revision 13700:
https://josm.openstreetmap.de/changeset/13700/josm
And the fix is in Debian (version 13710): https://packages.debian.org/sid/josm
as well in cosmic:
https://bugs.launchpad.net/ubuntu/+source/josm/0.0.svn13710+dfsg-1
13710 must either be backported
See https://bugs.launchpad.net/ubuntu/+source/ca-certificates-
java/+bug/1769013 for merge of ca-certificates-java 20180413
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739631
Title:
Fresh
** Bug watch added: JOSM bug tracker #15851
http://josm.openstreetmap.de/ticket/15851
** Also affects: josm via
http://josm.openstreetmap.de/ticket/15851
Importance: Unknown
Status: Unknown
** Changed in: josm
Importance: Unknown => Critical
--
You received this bug
Public bug reported:
during update i get this error
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xdg-user-dirs 0.15-2ubuntu6.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
d.net/bugs/1763865
>
> Title:
> Random system freezes
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I have a lenovo T-61 with 4 GB of RAM. and a Intel® Core™2 Duo CPU
> T7300 @ 2.00GHz × 2 GNOME is v 3.26.2. I have a 70 GB IDE HD
.gl/Pu0ke
> Para cambiar su inscripción, vaya a "Cambio de opciones" en
> http://goo.gl/Nevnx
--
= Don Forigua ==
--
Al escribir recuerde observar la etiqueta (normas) de esta lista:
http://goo.gl/Pu0ke
Para cambiar su inscripción, vaya a "Cambio de opciones" en http://goo.gl/Nevnx
Public bug reported:
I have a lenovo T-61 with 4 GB of RAM. and a Intel® Core™2 Duo CPU T7300
@ 2.00GHz × 2 GNOME is v 3.26.2. I have a 70 GB IDE HDD. Running v
17.10
don@jarvis-t61:~$ ubuntu-bug linux
Using PPAPI flash.
don@jarvis-t61:~$
--ppapi-flash-path=/usr/lib/adobe-flashplugin
l grupo en Telegram de Ubuntu Colombia o
simplemente respondan este hilo
https://t.me/ubuntucolombia
Feliz noche y para los que no saben que es flisol https://flisolbogota.org
Nos vemos el 28 :)
--
===== Don Forigua ==
--
Al escribir recuerde observar la etiqueta (normas) de esta li
Public bug reported:
install failed on SATA drive on Silicon Image 3124 Raid card in PCI-X
(not E) slot in 32bit dual Xeon motherboard from year 2002.
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:
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890882
I just recompiled from upstream git repo, and same problem.
(w/ X11)
I did:
$ lxc launch images:ubuntu/bionic/amd64 b
to get a fresh system, and followed the build instructions from
https://www.freecadweb.org/wiki/CompileOnUnix
Public bug reported:
I installed from 64GB USB flash drive using the Ubuntu
16.04.3-Desktop-i386.iso using your recommended Windows flash app. I
was trying to install on my Windows 7 Pro SATA 120GB SSD which had 60+
GB free. Installer suggested partitioning this 120GB into ~90GB Windows
7 and
1 - 100 of 1743 matches
Mail list logo
