There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring
it to main.
** Changed in: vulkan-tools (Ubuntu)
Status: Incomplete => Invalid
** Changed in: vulkan-tools (Ubuntu Jammy)
St
** Description changed:
+ Window actions (like maximize) no more work in wayland for QEMU using
+ GTK backend once the guest UI is intialized.
+
+ This can be seen by running an installed or even a trial Ubuntu from an
+ ISO like:
+
+ $ qemu-system-x86_64 \
+ -boot d \
+ -cdrom ubuntu-22.04.
The reason for esmtp is actually bug 1895011 - but until then track it
here to show better in weekly checks.
** Also affects: esmtp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubu
Thanks for the ping on this old case Alexander!
Can you confirm that this is what you see on 22.04 with the there recent
2:11.3.5-1ubuntu4 version of open-vm-tools?
I have subscribed John Wolfe who looks after open-vm-tools from VMwares
side and might have more details.
Further I added a bug tas
Public bug reported:
Hi,
I've seen this while looking for NBS and saw
intel-opencl-icd holding in the old libigdgmm11
I checked if there was no rebuild, but there was one that would pick up
libigdgmm12 but it is an FTBFS
https://launchpad.net/ubuntu/+source/intel-compute-runtime/21.32.20609-
** Changed in: libxcvt (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcvt in Ubuntu.
https://bugs.launchpad.net/bugs/1960500
Title:
[MIR] libxcvt
To manage notifications about
While this is for CPC, Server team members work on it. Thereby I know
that while obviously we'd appreciate a faster review, this can happen
past 22.04 - but not much later. Also we have to face that the >=Focal
tasks still have some TODOs to even enter security review queue -
therefore this can't b
Thank you Alberto for clarifying that last bit.
By that we now have the MIR-team and the security-team Acks.
That should indeed be ready for promotion now \o/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.lau
Still waiting on a response on this - marking incomplete
** Changed in: egl-wayland (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1935082
T
Thanks Alberto, while this is n't perfect yet (many would still need help to
run the test as it isn't detailed enough yet for e.g. me desktop-noob) but you
outlined what it is about - thanks.
But especially for a package like this which could be lost between kernel
(owning it) and Desktop (every
@Lukas - could you in the very same context also look at src:vulkan for
Bionic please?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to vulkan in Ubuntu.
https://bugs.launchpad.net/bugs/1946359
Title:
[MIR] vulkan-tools
To manage notifications
FYI - this is meant to be eventually promoted throughout all our releases.
Since the location changed there is also bug 1947020 for <=Bionic.
While the source changed and even more the source-name, since the rational and
many other things are actually the same I'm merging them here.
** Descriptio
Hi, this was not "wrong" in any way, but since the context, rationale
and so many other things are shared I merged this with the MIR bug
1946359
** Description changed:
- [Availability]
-
- vulkaninfo tool is present up to Bionic in package vulkan-utils, as
- part of vulkan source package:
-
** Changed in: vulkan-tools (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to vulkan-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1946359
Title:
[MIR] vulkan-tools
To manage noti
Hi,
I'd expect something based on those to questions:
- can the test be automated?
- yes => "link to the scripts you run"
- no => a list of the steps & tests that you will do (think of you are run
over by a bus, the next QA person has to do them by the script)
- does this have console outpu
Hi,
now everything is complete except the QA via testing.
We have amended the MIR rules to better clarify as this is one of the cases
that is hard to autopkgtest/build-test but some QA should happen still.
The new rule is:
"The package must include a non-trivial test suite, and if there is no obv
> kernel-packages is now subscribed.
Thanks, then it has the MIR-team ACK now and waits on security to be
complete.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] eg
>From the MIR meeting.
We are ok in regard to the testing, but please be sure that you as the owning
Team should ensure to have the necesary HW to be able to test this on
merges/updates as well as on debugging.
The only concern that is left (which can be clatrified while waiting on
security rev
...
>
> Something we could discuss at next MIR mtg.
>
I totally agree and I think this also is how we handled it so far (to
discuss it in the meeting AND how you suggested handling those HW
dependent cases).
It only seems right to formally express it in the process description.
Please remind me in
Yeah that is what I thought - Thanks for confirming Von!
My search engine use on this case found a few but no really related
issues either. If you happen to stumble over one please let me know.
Since it works fine for me I have to hope for the Desktop team taking a
look from the libepoxy POV what
As I said I added a libepoxy task and subscribed ubuntu-desktop as this
might be much more their home-turf to e.g. be up to date about known
cases why that would fail to initialize GTK/EGL.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy
... I guess "qemu(5.2+dfsg-3ubuntu1)+virgl on GTK/X11" is the bad case
then?
** Also affects: libepoxy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpa
Hi didrocks/seb128 - this shows up in component mismatches.
We were wondering if ubuntu-x really still is an active team or if the
desktop-team would today be better to take this over?
Since it was approved in the past once the owner is sorted out this
could be re-promoted.
--
You received this
Hi Luke,
thanks for the bug report and your help to make Ubuntu better.
I'm unsure what ssh could/should do differently in this case.
For similar issues there was a gnome PR [1] that went into gnome that should
allow a "yes and remember" kind of use-case. Not sure if that is missing in the
gnome
FYI:
I was affected by the issue, but there must be another way to trigger than the
(re)install of console-setup and/or keyboard-configuration as those actions
were not triggering the issue for me after I rebooted.
OTOH the time it started to happen perfectly matches a background update to
those
in: mesa (Ubuntu Ee-series)
Status: New => Triaged
** Changed in: qemu (Ubuntu Ee-series)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.l
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244324/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs
Just the plain Disco kernel environment as you get it when spawning a
new guest - data provided changing state of both bug tasks back.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244322/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244320/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244321/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244319/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.la
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244323/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1818879
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244318/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244316/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244317/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1818879
T
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 7 08:12 seq
crw-rw 1 root audio 116, 33 Mar 7 08:12 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
ArecordDevices: Error: [Errno
@Daniel - on one hand it is also a change in xorg that makes the driver missing
now - so an FYI for that.
But in an IRC discussion there were two potential paths to resolve this issue
overall:
- make the cirrus.ko available in the non -extra package so that it works out
of the box using this dri
The PPA was built against -proposed so I had to enable that to install all libs.
That done the 19.0.0~rc6-1ubuntu0.1 with the set affinity change reverted works
quite nicely.
It would be great to get that into Ubuntu 19.04 until the involved
upstreams agreed how to proceed with it and we can then
Hi Timo,
I tried to test with the mesa from ppa:canonical-x/x-staging
But there is a dependency issue in that PPA - I can't install all packages from
there.
It seems most of the X* packages will need a transition for the new mesa and
those are not in this ppa right now.
Installing all that I can
** Also affects: mesa (Ubuntu Disco)
Importance: Medium
Status: Confirmed
** Also affects: qemu (Ubuntu Disco)
Importance: Undecided
Status: Triaged
** No longer affects: qemu (Ubuntu Disco)
** Changed in: mesa (Ubuntu Disco)
Status: Confirmed => Triaged
** Changed in
Thanks Daniel and MarcAndre for chiming in here.
Atfer thinking more about it I agree to Daniel that actually mesa should honor
and stick with its affinity assignment.
For documentation purpose: the solution proposed on the ML is at
https://lists.freedesktop.org/archives/mesa-dev/2019-February/2
@Ubuntu-Desktop Team (now subscribed) - is there a chance we can revert [1] in
mesa before it will be released with Disco for now. That would be needed until
an accepted solution throughout the stack of libvirt/qemu/mesa is found?
Otherwise using GL backed qemu graphics will fail as outlined in t
Hi Gannet,
the discussion of RussianNeuroMancer with upstream ended trying to tackle the
KDE resolution setting [1], but not a change in qemu/libvirt or other
components of the virst-stack. Also it was reported that newer versions were
less (or not)9 affected.
Is your case related to KDE as wel
** Also affects: spice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1719038
Title:
X Server crashes during log in VM since 16.04.2
To mana
45 matches
Mail list logo
