Timo, Do you have an ETA when this would be released to focal-update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920096
Title:
Cursor bleeds on the platform with Mali armsoc driver
To manage
** Changed in: vitis-ai (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928714
Title:
Vitis AI 1.3.2 Release tag updated
To manage notifications about this
@Timo, any ETA for when this would land into Focal? thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920096
Title:
Cursor bleeds on the platform with Mali armsoc driver
To manage
I have confirmed that it will not crash if I have a single monitor.
In duel monitor mode, i can also reconfirm that after updating
(strangely) Chrome browser that the window manager will crash, but will
restart -- prior to the update it would crash and not restart.
--
You received this bug
Additional thought on my scenario ... I was also working in a duel
monitor mode when gnome crashed. In my case Thunderbird was on my
primary monitor, and the thunderbird dialog came up on my secondary
monitor. Interacting with this dialog is when gnome crashes.
--
You received this bug
Regarding comment #10 that this may be this user's specific issue. I
have opened bug #1850833 that is classified as a duplicate of this bug.
I have also provided in that bug a cleaner path to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi:
I had to use step 3 and the new bug report is here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850881
Now, there are a number of (IMHO) really weird things that also happened
in this round of reproductions:
After reproducing the crash, I had these crash files:
-rw-r- 1
** Description changed:
Changing text color in Thunderbird table will crash gnome desktop.
I have reproduced this multiple times.
Reproduction steps:
1) Open Thunderbird
2) New mail
3) Add Table to mail
4) Format->Table->Table or Cell background Color
+ 5) Select the color
Public bug reported:
Changing text color in Thunderbird table will crash gnome desktop.
I have reproduced this multiple times.
Reproduction steps:
1) Open Thunderbird
2) New mail
3) Add Table to mail
4) Format->Table->Table or Cell background Color
At this point the color dialog will open, and
Example error output...
admin@C031051823-00213:~$ sudo journalctl | grep observe
Sep 10 16:41:42 C031051823-00213 customer-deviceoperations.service[1765]:
time="2018-09-10T16:41:42Z" level=error msg="Error getting slot: unknown slot
core:hardware-observe\n" tag=plug
--
You received this bug
can you provide an ETA for when this will be pushed as a proposed SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634236
Title:
[SRU] Dependency on snap-confine too weak
To manage
** Tags added: cpc-current-milestone
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1403617
Title:
gce datasource does not handle instance ssh keys
To manage notifications
** Tags added: cpc-current-milestone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411582
Title:
Azure data source should auto-detect ephemeral disk location
To manage notifications about this
** Tags added: cpc-current-milestone
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1411582
Title:
Azure data source should auto-detect ephemeral disk location
To manage
** Tags added: cpc-current-milestone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403617
Title:
gce datasource does not handle instance ssh keys
To manage notifications about this bug go to:
Hi Viktor:
1) Are you testing with your new cloud? Kiril has stated your new
cloud would have this dmi info in the instances. We did explicitly
break (with agreement from Kiril) the datasource on something without
that dmi info. Our understanding is the new cloud would have
'cloudsigma' as the
Hi Viktor:
1) Are you testing with your new cloud? Kiril has stated your new
cloud would have this dmi info in the instances. We did explicitly
break (with agreement from Kiril) the datasource on something without
that dmi info. Our understanding is the new cloud would have
'cloudsigma' as the
Chris:
I spoke with Viktor today and requested his team test and provide results here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1303986
Title:
[SRU][FFe] CloudSigma
Chris:
I spoke with Viktor today and requested his team test and provide results here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303986
Title:
[SRU][FFe] CloudSigma Datasource doesn't handle
Public bug reported:
For Clouds that have support in later or development version of Cloud-init,
Canonical allows for Cloud Vendors to backport the datasource and dependencies
to under the following rules:
Only Datasources which have been submitted to upstream or are in upstream
cloud-init
** Changed in: cron (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304075
Title:
Cloud-init Datasource backporting via PPA
To manage notifications about this
When I was playing with this a hard reset (hold down on/off switch)
brought the system back to its original state.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787587
Title:
Cannot change screen
I know longer own this system, but the unit is owned by Canonical and
now resides in the Milbank offices. Chris Kenyon has this system and is
using it for demo purposes. I know he had someone install Oneiric on
the unit. but I did not hear the results of that installation or
testing.
--
You
Regarding resolution question in #10.
The sensitivity of the Duo touch screen is not close to that on a phone.
Therefore, for a decent touch experience you need a larger resolution in the
16:9 ratio spectrum. Users of the Duo have found the 1024x576 resolution to be
a good middle ground. A
I have never loaded and booted an alternative kernel image before. I
know it has something to do with placing new kernel images in /boot and
selecting at boot-up via Grub. But, that is where my understanding
stops. I will need to research how to do this.
--
You received this bug notification
I have validated that the Maverick kernel does work properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787587
Title:
Cannot change screen resolution on Dell Duo in Natty
To manage
I realized that I failed to problem exact instructions to reproduce the
problem...
The default Dell Duo resolution is a 16:9 ratio and is set to 1366x768.
This is too small. You can use another preconfigured resolution of
1024x768, but this leaves large amounts of unused screen. Therefore,
@Chris, this was a fresh install. Others on the forums expressed the
same problems after an upgrade, but I wanted to keep this completely
clean, so I went with the new installation of Natty 11.04, and then
loaded all updates.
--
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: xserver-xorg-video-intel
After upgrade (or fresh install) from 10.10 to 11.04 we can no longer
change screen resolution from the default resolution of 1366x768.
There is a large Ubuntu user community who is trying to get the Dell Duo
to work properly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787587
Title:
Cannot change screen resolution on Dell Duo in Natty
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
30 matches
Mail list logo
