also output to show that netplan did set parameters:
root@mike-desktop:~# brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.b8aeed760abf no enp0s25
veth6F9QVF
Public bug reported:
Running netplay try give me the following error but reboot the system
everything works:
root@mike-desktop:~# netplan try
br0: reverting custom parameters for bridges and bonds is not supported
Please carefully review the configuration and use 'netplan apply' directly.
This might have the same root cause but 1865503 is using LXD where I had the
problem using
lxc (lxc-start).
Once fixed need to make sure the fix work under lxc (lxc-start) also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
when trying to install chromium in 20.04 in a lxc container to fails to install
with the following:
root@python:~# apt-get install chromium-browser
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional
*** This bug is a duplicate of bug 1532508 ***
https://bugs.launchpad.net/bugs/1532508
I do not think this is the same problem.
1532508 is supsend issue.
This does not require supsend.
Just do nothing for the amount of time it takes to cause the screen to lock
because of being idle.
then
The pinning is holding me back for moving from current version to 20.04.
So far the only option I see is to use the beta you pointed me to or switch
to google-chrome which looks like there still create debs.
Not being able to pin things and not being able to choose when the snap upgrade
is a
that fixes the --no-sandbox but still needs the
QT_X11_NO_MITSHM=1
also the --no-xshm works now.
This whole bug report shows my big problem with snaps.
In production I have a pin a version of chromium that works so that I can use
webdriver to access a number of site that I need to submit data
it need the no-sandbox to work.
On 6/11/20 10:57 AM, Olivier Tilloy wrote:
> Thanks for the upstream report Mike. I see it has been marked as a
> duplicate of
> https://bugs.chromium.org/p/chromium/issues/detail?id=1035803, and
> comment #19 there suggests the following:
>
> tldr; manually turn
I have reported the bug.
Here is the url.
https://bugs.chromium.org/p/chromium/issues/detail?id=1085136
On 5/20/20 8:24 AM, Olivier Tilloy wrote:
> Indeed, it appears to be the same problem. I think an actual bug report
> (as opposed to a support thread) would be useful if we want upstream
>
It look like
https://support.google.com/chrome/thread/41722791?hl=en
On 5/19/20 8:48 AM, Olivier Tilloy wrote:
> Ack, thanks Mike. In light of this information, I have removed the
> duplicate status.
>
> Is there an upstream bug report for the crash? If not, would you mind
> filing one at
*** This bug is a duplicate of bug 1857252 ***
https://bugs.launchpad.net/bugs/1857252
Sorry about last comment. (ignore last comment)
The workaround in bug 18752 fixes the blank screen. (This is also my bug report)
export QT_X11_NO_MITSHM=1
export _X11_NO_MITSHM=1
export _MITSHM=0
This
*** This bug is a duplicate of bug 1857252 ***
https://bugs.launchpad.net/bugs/1857252
Can no long test this bug as chromium has moved on to 81.0.4044.132 and
now has a different set of problems.
Thing crash on on gpu problems.
Look at Bug 1877173.
On 5/15/20 7:58 AM, Olivier Tilloy wrote:
*** This bug is a duplicate of bug 1857252 ***
https://bugs.launchpad.net/bugs/1857252
This is not the same problem.
The --use-gl=swiftshader work for chrome before 81.0.4044.138. Without the
--use-gl option it only had a blank (gray) screen but did not crash.
On 81.0.4044.138 it crashes
Public bug reported:
I just upgraded from 19.10 to 20.04.
I am getting email from smart about errors on the nvme ssds.
If I look in the syslog I see for all nvme devices:
Device: /dev/nvme0, number of Error Log entries increased from 485 to 48
nvme nvme0: missing or invalid SUBNQN field.
nvme
That did work for both 18.04 and 16.04
Any idea what i lose by not having the sandbox ?
On 5/7/20 4:38 AM, Sebastien Bacher wrote:
> Seems similar to https://support.google.com/chrome/thread/41722791?hl=en
> , does it work if you use --no-sandbox ?
>
--
You received this bug notification
Public bug reported:
Chromium crash on a ssh x forwarding connection
It crashes on both 18.04 and 16.04 with the same message.
The X forwarding is working for other programs just fine.
It was working until last update.
Here is the message from the console on the crash
1 hit the 3 dots in upper conner
2 Hit the Privcay and Security
3 hit authorities tab
4 hit the import button
Then I get:
Could Not read the contents of void
Error opening directory '/var/lib/snap/void': Permission denied
I just try the import now and it worked.
I assume the problem was fixed
Public bug reported:
When I try to add Server Cert to chromium-browser I get the following message
Could Not read the contents of void
Error opening directory '/var/lib/snap/void': Permission denied
This worked on 18.04 but not 19.10.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package:
Public bug reported:
root@ltcd-mike:~# do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,242 kB]
Fetched 1,243 kB in 0s (0 B/s)
Public bug reported:
Using any vnc viewer it takes 30 seconds before the display comes up. I have
tried with remmina and
vinagre as the viewer.
The only thing in syslog is the following:
Dec 22 15:18:58 mike-desktop dbus-daemon[10399]: [session uid=0 pid=10397]
Activating service
Public bug reported:
Chromium 78 worked and things broke in version 79.
With chromium 79 when using the remote display (ssh for x forward) I get
the display forward but only a blank (white) window. Chromiumn does not
render anything into the window.
If I am at the console then every thing work
Public bug reported:
When running lxc-top as root it flashes the following error messages for every
container:
Unable to read cgroup item memory.memsw.usage_in_bytes
Unable to read cgroup item memory.memsw.limit_in_bytes
Here output showing bad blkio write
Container CPU
Public bug reported:
This system work without problem on 4.13.0-45-generic but under
4.15.0-43-generic the system
hangs hard that event the keyboard cap-lock does not work.
This lockup is caused by do a number of zfs send/receive which is being using
to backup a number
of zfs data sets. All of
It look like there was a patch added to fix this
https://github.com/torvalds/linux/commit/7fee72d5e8f1e7b8d8212e28291b1a0243ecf2f1
/* All Seagate disk enclosures have broken ATA pass-through support */
if (le16_to_cpu(udev->descriptor.idVendor) == 0x0bc2)
flags |=
Public bug reported:
smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15.
Here is data from 16.04
root@server:~# uname -a
Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
root@server:~# lsb_release -a
No LSB modules
There is 02proxy
Acquire::http { Proxy "http://cache:3142;; };
It is apt-cacher-ng running 16.04.
I found something on the net that talk about adding
passThroughPattern: ^changelogs.ubuntu.com:443$
This fixed the problem for me.
--
You received this bug notification because you are a member
Public bug reported:
mike@mike-think:~$ do-release-upgrade -c
Checking for a new Ubuntu release
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your
Internet connection or proxy settings
No new release found.
This machine does not need a proxy to get to the internet.
The 7.5 and 4.15 kernel was causing a crash under load when only zfs io was
happening and then
did something to cause ext4 root file system i/o. The system locked up so hard
that the console
keyboard cap lock did not even work.
I have downgraded to 4.13 which solves the system lockup and the
Public bug reported:
In both the subject line and list of emails when there is a graphic displayed
it is too large
and in the case of panel with the list of emails it cover a a number of email
before and after
the email with the problem.
This problem start just after upgraded from 16.04 to
Public bug reported:
ZED should be sending email when scrub finishes but I do not get any email. I
did update modify
the zed.rc file to end the email by setting the following
ZED_EMAIL_ADDR="root"
ZED_EMAIL_PROG="mail"
ZED_NOTIFY_VERBOSE=1
I tested to verify mail work. I did the following:
Public bug reported:
I have 16.04 installed with HWE and did a dist-upgrade. This installed a
new kernel 4.15 with zfs version 7.5 but did not upgrade the zfsutils-
linux package.
I now have a mismatch zfsutils and zfs module.
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
The problem still exists
I needed to patch saned.c:
I needed to change SANE_TRUE to SANE_FALSE
at line 1830:
reply.status =
sane_get_devices ((const SANE_Device ***) _list,
SANE_FALSE);
** Attachment added: "Here is the patch I need to get saned
Fix missing for 16.04.
Any chance of getting this fixed in 16.04. Since 16.04 is an LTS it
would be good to also fix the problem in the LTS.
At a min could we get the GeneralInfo.pm fix. This would at least fix
the RRD graph.
The patch also fixed the problem for me on 16.04
--
You received
Public bug reported:
I had a working squirrel mail in 14.04.
I upgrade to 16.04 and had problem with login. so I moved back to 14.04 and
created a free
install of 16.04 and then install squirrelmail. I then copied the config file
over to the
new install and got the same problem.
When I try to
** Attachment added: "Config file in use on both 14.04 and 16.04"
https://bugs.launchpad.net/ubuntu/+source/squirrelmail/+bug/1653530/+attachment/4799104/+files/config.php
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When running scanimage -L on a remove system no scanner are found.
when running scanimage -L on local system (where saned is run) finds the
scanners.
when running scaned in deubg mode I can see the remote system request a list of
scanner
but no list is returned to scanimge
I am have the same problem with puppet in a container on 14.04 using hwe kernel
version 3.16.0-31.
Package install for kernel is linux-image-generic-lts-utopic
Switch back to kernel 3.13.0-46 fixed the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Why is this marked Incomplete ?
Is there anything you need from me ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261255
Title:
[ThinkPad T530, Realtek ALC269VC, Speaker, Internal] No sound at
send email to the author if sound not working on your T530
who is should I be sending a email to about the sound not working ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261255
Title:
Public bug reported:
The sound did work for a while on 13.10.
It stop working after a reboot and have not had sound comming from the
speakers. I hear a poping nose comming from
the right speaker and can mute the poping nose only by pressing the speak mute
button on the laptop.
I have looked
This T530 only has 2 speakers that I known about.
I do not have the dock for the t530.
Are you asking me to rebuild the sound driver ?
Is there something I can try and see if that is the problem without
having to rebuild stuff ?
I do not have kernel bugtrack account to look at the first url.
This problem also exists on 13.04
jmike@mike-think:~$ lsb_release -a
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description:Ubuntu 13.04
Public bug reported:
hgview will not install.
Here is the output from apt-get:
batch@eggs:~$ sudo apt-get install hgview
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an
This is a security problem because it stop an package which has security
problems from being updated.
Package: slapd (2.4.15-1ubuntu3.1) [security]
from package changelog:
openldap (2.4.15-1ubuntu3.1) jaunty-security; urgency=low
* SECURITY UPDATE: null ptr deref, free uninitialized data in
ba...@work-isp:~$ sudo sh -c ls -l /etc/ldap/slapd.d/cn=config/olcDatabase*
ls: cannot access /etc/ldap/slapd.d/cn=config/olcDatabase*: No such file or
directory
ba...@work-isp:~$ sudo sh -c grep olcSuffix:
/etc/ldap/slapd.d/cn=config/olcDatabase*
grep: /etc/ldap/slapd.d/cn=config/olcDatabase*:
changing suffix dc=domain to suffix dc=domain fixed the problem.
Not sure why nothing in ldap/slapd thinks this is a problem but thing look
to be working.
--
slapd dist-upgrade chown: invalid argument: `'
https://bugs.launchpad.net/bugs/632051
You received this bug notification because you are
This is a security problem because it stop an package which has security
problems from being updated.
Package: slapd (2.4.15-1ubuntu3.1) [security]
from package changelog:
openldap (2.4.15-1ubuntu3.1) jaunty-security; urgency=low
* SECURITY UPDATE: null ptr deref, free uninitialized data in
ba...@work-isp:~$ sudo sh -c ls -l /etc/ldap/slapd.d/cn=config/olcDatabase*
ls: cannot access /etc/ldap/slapd.d/cn=config/olcDatabase*: No such file or
directory
ba...@work-isp:~$ sudo sh -c grep olcSuffix:
/etc/ldap/slapd.d/cn=config/olcDatabase*
grep: /etc/ldap/slapd.d/cn=config/olcDatabase*:
changing suffix dc=domain to suffix dc=domain fixed the problem.
Not sure why nothing in ldap/slapd thinks this is a problem but thing look
to be working.
--
slapd dist-upgrade chown: invalid argument: `'
https://bugs.launchpad.net/bugs/632051
You received this bug notification because you are
*** This bug is a security vulnerability ***
Public security bug reported:
When doing a apt-get dist-upgrade going from slapd_2.4.15-1ubuntu3_amd64.deb
to slapd_2.4.15-1ubuntu3.1_amd64.deb
I get the following output:
ba...@work-isp:/tmp$ sudo apt-get dist-upgrade
[sudo] password for batch:
*** This bug is a security vulnerability ***
Public security bug reported:
When doing a apt-get dist-upgrade going from slapd_2.4.15-1ubuntu3_amd64.deb
to slapd_2.4.15-1ubuntu3.1_amd64.deb
I get the following output:
ba...@work-isp:/tmp$ sudo apt-get dist-upgrade
[sudo] password for batch:
Public bug reported:
Binary package hint: fail2ban
I am runnig ubuntu 9.04 server 64 bit.
r...@work-isp:/etc/fail2ban# uname -a
Linux work-isp.ltcd.com 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12
UTC 2009 x86_64 GNU/Linux
Want start fail2ban a jail using iptables some or all of the
I am also seeing the same problem.
The machine is a laptop Thinkpad T61p.
When remote desktop is enable the cpu goes to 25-35% turn off the remote
desktop drop the cpu normal level (1%-3%).
This did not cause a problem on 8.10.
The problem exists with both nvida 180 driver and free driver. It
apt-cache show of python-xml
Package: python-xml
Priority: optional
Section: universe/python
Installed-Size: 2452
Maintainer: Ubuntu MOTU Developers [EMAIL PROTECTED]
Original-Maintainer: Debian/Ubuntu Zope Team [EMAIL PROTECTED]
Architecture: amd64
Version: 0.8.4-10ubuntu2
Replaces:
Public bug reported:
Binary package hint: python-zsi
System in 8.04 amd64 and is up to date.
ZSI depends on PyXML.
This is not listed in the depends for zsi package.
From the readme for the ZSI package
ZSI is built on top of DOM. It requires Python 2.3 or later, and PyXML
0.8.3 or later.
Public bug reported:
Binary package hint: gnome-power-manager
the power history is just a flat line when on running battery.
The machine is a T61P.
The Device information does not show the correct information:
Device Information:
current Charge 69.0 Wh
[EMAIL
** Attachment added: power-bug.tar
http://launchpadlibrarian.net/12330786/power-bug.tar
--
g-p-m power history is wrong
https://bugs.launchpad.net/bugs/197101
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I am attach a output of the commands you requested.
The voltage history looks ok (match now is not flat)
With the power history off I can tell if the charge history is correct but it
is not flat and down but is at 79% which is not real.
The system is hardy and was updated at 1:30pm today.
hover over the battery icon give wrong info
battery at 80% time left 17 plus hours
left clicking on the battery icon give correct info
precentage charge 20% and 52 mins.
--
g-p-m power history is wrong
https://bugs.launchpad.net/bugs/197101
You received this bug notification because you are a
I also get a blank screen instead of usplash screen. It is blank till
login screen.
I have a Thinkpad T61P.
video:
01:00.0 VGA compatible controller: nVidia Corporation Quadro FX 570M (rev a1)
uname -a
Linux mike-laptop 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64
GNU/Linux
60 matches
Mail list logo
