Hi Sam,
Canonical will take a look at this issue and get back to you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/2044664
Title:
HDMI plugin after boot, but disp
Hi Sam,
Could you update the kernel to the latest version[1] and then try it
again? Thanks~
---
[1] linux-mtk (5.15.0-1033.38), https://launchpad.net/ubuntu/+source/linux-mtk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to w
** Attachment added: "mediatek.conf"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+attachment/5708343/+files/mediatek.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu
@Marjan
I set time by BIOS settings.
--
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/1905688
Title:
systemd-timesyncd.service: Timed out waiting for reply from NTP server
** Attachment added: "ntp_systemd-timesyncd.pcapng"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+attachment/5438201/+files/ntp_systemd-timesyncd.pcapng
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sys
Based on the wireshark log in comment#1, system received the package from NTP
server.
But, the log showed "Timed out waiting for reply from NTP server"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
Public bug reported:
systemd-timesyncd.service fails to correct time if the system time is
later than February 7, 2036.
Image: ubuntu-20.10-desktop-amd64.iso
systemd: 246.6-1ubuntu1
$ timedatectl status
Local time: Fri 2038-11-26 07:58:16 UTC
Universal time: Fri 2038-11
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1727401
Title:
Corruption on windowed 3D apps running on dGPU (Intel/AMD)
Status in Me
@Timo
Here is the test result of mesa (xenial-proposed)
A. Test Result:
1. DRI_PRIME=1 glxgear: Pass
2. DRI_PRIME=1 glxgear -fulscreen: Pass
3. glxgear: Pass
4. glxgear -fulscreen: Pass
5. Unigine_Heaven-4.0.run (5mins): Pass
6. Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass
7. DRI_PRIME=1 Unig
@Timo
Here is the test result for mesa (17.2.4-0ubuntu1~16.04.3~1)
A. Test Result:
1. DRI_PRIME=1 glxgear: Pass
2. DRI_PRIME=1 glxgear -fulscreen: Pass
3. glxgear: Pass
4. glxgear -fulscreen: Pass
5. Change Resolution: Pass
6. Scale for menu and title bars: Pass
7. Unigine_Heaven-4.0.run (5mins):
Cannot reproudce the issue on xenial.
A. Test Result:
1. DRI_PRIME=1 glxgear -info: Pass
2. Change Resolution: Pass
3. Scale for menu and title bars: Pass
4. Unigine_Heaven-4.0.run (5mins): Pass
B. Test Environment:
1. Ubuntu: Xenial 16.04
2. Graphic Card:
a. AMD [1002:9874] (rev e2)
b. Intel [
mesa 17.2.4 works well on my two devices. Here is the test result:
1) AMD [1002:9874] (rev e2)
glxgear -info: Pass
Unigine_Heaven-4.0 (5mins): Pass
2) Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff)
glxgear -info: Pass
DRI_PRIME=1 glxgear -info: Pass
Unigine_Heaven-4.0 (5mins): Pass
DRI_PRI
typo... u-u in #73 should be 0.97ubuntu1~16.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1690980
Title:
unattended-upgrades does not block shutdown of system, as it is
@Balint
Here is test result for InstallOnShutdown:false
Timestamp:
1. 13:25:10~13:40:32: 15mins
2. reboot system
3. 14:59:17~16:44:18: 1hr45mins
Total: 2hr
Comparing to the test result in #69, 0.97ubuntu1~16.04.1 saves 4~5
hours.
Log: Please check full log as attached.
Installed packages:
apt
@Balint
Here is test result for InstallOnShutdown:true
"Errors were encountered while processing: apport"
u-u still has packages to upgrade after this issue happens.
So, when I reboot system every time, u-u still tries to upgrade package.
We expect that there are 30 mins to do the update.
But, de
@Balint
Here is another test result for InstallOnShutdown:false
Log: 2017-09-14 17:20:14 ~ 2017-09-15 00:00:03
It took 6~7 hours to finish online update. (Packages: around 700mb)
unattended-upgrades.log
// Online update was triggered.
2017-09-14 17:15:03,561 INFO Allowed origins are: ['o=Ubun
@Balint
Here is my test result: (InstallOnShutdown:true)
Packages will be installed when rebooting system.
I rebooted system five times, but system still didn't finish the update.
It took too long to finish online update.
Timestamp: (reboot system)
1. 2017-09-14 13:57:00,998
2. 2017-09-14 14:32:
@Balint
I tried three times, and 0.95-16.04.0rbalint1 didn't work well.
Please refer to attached file for detailed log.
1) Reboot system when unattended upgrades starts to download packages.
//unattended-upgrades.log
2017-08-08 15:34:07,782 INFO Starting unattended upgrades script
2017-08-08 15:
@Balint
unattended-upgrades didn't finish online-update.
https://launchpad.net/~rbalint/+archive/ubuntu/scratch/+packages
unattended-upgrades: (0.93.2~16.04.0+rbalint2）
apt:（1.2.25~rbalint2）
Here are logs:
/var/log/unattended-upgrades/unattended-upgrades.log
2017-07-26 15:58:59,769 INFO Initial
@Balint
Something wrong happens when installing deb package apport.
(Please check full log as attached)
unattended-upgrades-dpkg.log
Unpacking python3-apport (2.20.1-0ubuntu2.10) over (2.20.1-0ubuntu2) ...
Preparing to unpack .../apport_2.20.1-0ubuntu2.10_all.deb ...
unattended-upgrades-shutdown.
@Brian
My test result with Balint's patch is in #22.
According to the previous test in #18, the behavior of my test script is
different from apt-daily timer. If you want to reproduce this issue, creating
override.conf would be a better way.
---
sudo cat << EOF > /etc/systemd/system/apt-daily.tim
@Balint
The attached patch can fix the communication between u-u and u-u-shutdown.
However, without workaround 1 or 2 in #19, u-u will be killed when users
reboot/shutdown the device.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
In xenial and yakkety, unattended-upgrade can finish security updates
after applying workaround 1&2.
workaround 3: If users reboot/shutdown by UI, there will be a pop-up window
which asks users for root password.
If users reboot/shutdown by command (sudo reboot), unattended-upgrade will be
kille
New test result:
1. unattended-upgrades is triggered by apt-daily.timer.
yakkety (triggered by apt-daily.timer): Failed
xenial (triggered by apt-daily.timer): Failed
2. unattended-upgrades is triggered by cmdline (sudo unattended-upgrade)
yakkety (triggered by cmdline): Pass
xenial (triggered by cm
I added more debug messages (ps -aef | grep unatteded-upgrade) to
unattended-upgrades-shutdown.
In xenial, it looks like unattended-upgrade is killed before
unattended-upgrades-shutdown is running.
That is why unattended-upgrades-shutdown can get lock.
Log:
1. xenial (unattended-upgrades-0.90ubu
I added more debug messages and reproduced the issue again.
Here are logs:
lock_file: /var/run/unattended-upgrades.lock
1. xenial (unattended-upgrades-0.90ubuntu0.6):
a. /var/log/unattended-upgrades/unattended-upgrades-shutdown.log
2017-06-22 03:43:09,028 WARNING - get_lock returned...
2017-06-22
** Changed in: oem-priority
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1690980
Title:
No pop-up window to warn users
@Brian Murray
It seems to me that Yakkety (16.10) deals better with a reboot while
unattended-upgrades is running.
After I shutdowned system by GUI, I saw the following message.
"Unattended-upgrade in progress during shutdown, sleeping for 5s
Progress: 67.5656 % .."
(Please check logs as atta
@Brian Murray
Still can reproduce this issue if I reboot system by GUI.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1690980
Title:
No pop-up window to warn
@Brian Murray
I still can reproduce this issue with 0.90ubuntu0.6
$ apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: 0.90ubuntu0.6
Candidate: 0.90ubuntu0.6
Please check full log as attached.
Here are reproduction steps:
1. sudo /usr/bin/unattended-upgrade
2. Run the follo
** Changed in: oem-priority
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1690980
Title:
No pop-up window to warn users
@Brian Murray
Here is the log which I uploaded in #1
//dpkg.log
2017-05-12 08:22:24 status unpacked linux-headers-4.4.0-75:all 4.4.0-75.96
2017-05-12 08:22:24 install linux-headers-4.4.0-75-generic:amd64
4.4.0-75.96
2017-05-12 08:22:24 status half-installed linux-headers-4.4.0-75-generic:amd64
@Brian Murray
When I saw this issue first time, unattended-upgrades was triggered
automatically.
I tried to reproduce this issue, so I executed the python script manually.
I filed the bug because users don't know security updates is ongoing
when unattended-upgrades is triggered automatically. If
** Project changed: unattended-upgrades => unattended-upgrades (Ubuntu)
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Assignee: (unassigned) => ethan.hsieh (et
Public bug reported:
Title: No pop-up window to warn users that system should not reboot or
shutdown while installing security updates
Summary:
No pop-up window to warn users that system should not reboot or shutdown while
installing security updates
Steps:
1. trigger unattended-upgrades
2. reb
I have verified xserver-xorg-video-amdgpu (1.1.2) and mesa (12.0.6)
Test result:
1. glxgears: Pass
2. glmark2: Pass
3. S3 Test: Pass
(sudo fwts s3 --s3-multiple=30 --s3-min-delay=30 --s3-max-delay=30)
Test Environment
1. Kernel: 4.4.0-49-generic
2. VGA compatible controller [AMD/ATI] Device [1002
** Changed in: bluez (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1589889
Title:
Bluetooth search gets nothing on Dell XPS
** Changed in: bluez (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1589889
Title:
Bluetooth search gets nothing on Dell XPS
38 matches
Mail list logo
