Public bug reported:
The pkg-config file is no longer present. It is still available in
vivid, though.
** Affects: gflags (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gflags in
It is in the 10.3. branch but a few commits after the 10.3 tags. So it
will be in 10.3.1.
Or we cherry pick that into 10.3?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1275398
Title:
Public bug reported:
There is a bugfix in 10.3.1 that will fix dma-buf handling in i915. So
we would like to see the newest minor release of mesa, which is 10.3.1
This will fix:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275398 and
basically enable i915 devices to run mir.
[Impact]
*
needs a new mir platform patch and a one liner in 915 - so it seems
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
ht
no change needed in mir
** Changed in: mir
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1275398
Title:
i915 driver/i945 hardware: Mir GL clients are
needs a new mir platform patch and a one liner in 915 - so it seems
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1275398
Title:
i915 driver/i945 hardware: Mir GL clients are rendered a
just a mesa patch needed
** Changed in: mesa (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bug
Yes the stack trace is from the lightdm restart attempt, when I tried to
manually resolve the freeze.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1353926
Title:
Xo
I think this failure is resolved with the updated mir platform patch and
bugfixes for i915 that have been sent upstream. Waiting for those to get
applied.
But the story does not end there. Now when running unity8-dash it fails
because mesa claims it only supports OpenGL 1.4. And that because of
an
Which intel driver is meant in the spreadsheet?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1364003
Title:
[FFE] mesa 10.3
Status in “mesa” package in Ubuntu:
New
Bug description:
Had the same issue today when upgrading from utopic to vivid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/985228
Title:
[USB-Audio - Logitech USB Headset, playback] Can not set U
I doubt that the error is invalid, there seems to be an issue with
upgrading.
** Changed in: pulseaudio (Ubuntu)
Status: Invalid => New
** Summary changed:
- [USB-Audio - Logitech USB Headset, playback] Can not set USB headset as
active device for playback and recording in sound settings
The issue disappeared after removing ~/.config/pulse and rebooting
twice.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/985228
Title:
[USB-Audio - Logitech USB Headset, playback]
I can reproduce here locally, I have a fix.. cursor buffers now are
allowed to have arbitrary sizes, even when you request a different one..
** Changed in: mir
Assignee: Daniel van Vugt (vanvugt) => Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you ar
** Changed in: mir
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1391975
Title:
USC - mouse cursor on AMD graphics is drawing incorrectly
Status
https://github.com/glasen/snap-
ausweisapp2-ce/blob/master/snap/snapcraft.yaml
This is another snap that supports smart card readers. It seems to
package pcscd...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu
I recently had to switch my company card and it now uses a newer version
so it get mis-identified by pcsc-lite from debian - but works fine in
the latest release of pcsc-lite. As companies like Atos seem to
frequently roll out new versions of their cards it would be nice if we
could have opensc (I
Public bug reported:
chromium uses the Netscape Cryptographic Module to access smartcards for
authentication purposes. This stopped working when switching to the snap
version. Chromium would normally access the setup in
~/.pki/nssdb/pkcs11.txt That file would refer to a library used to
access the
** Description changed:
chromium uses the Netscape Cryptographic Module to access smartcards for
authentication purposes. This stopped working when switching to the snap
version. Chromium would normally access the setup in
~/.pki/nssdb/pkcs11.txt That file would refer to a library used to
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1845286
Title:
pdftoraster crashed with SIGSEGV in convert8to16()
Status in cup
cups error log while printing the file via evince
** Attachment added: "cups error log"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845286/+attachment/5291162/+files/error_log
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
I am printing with Defaults everything but "Color Mode" = "Device Gray".
I now discovered that using "Color Mode" Color does not trigger the error.
** Attachment added: "file that causes the issue"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845286/+attachment/5291163/+files/L
One more detail. I have two printer queues configured:
HP-Officejet-Pro-8620: HP Officejet Pro 8620, driverless, cups-filters 1.25.4
HP_Officejet_Pro_8620_794B2D_: HP Officejet Pro 8620, driverless, cups-filters
1.25.6
The crashes only happen with the second printer. Everything worked fine
whe
I recreated the backend
** Attachment added: "cups error log 2"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845286/+attachment/5291170/+files/error_log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in
** Attachment added: "ppd"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845286/+attachment/5291171/+files/hp_officejet_pro_8620_794b2d_.ppd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https:
Yes upgrading with that PPA fixes the issue for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1845286
Title:
pdftoraster crashed with SIGSEGV in convert8to16()
Status in cu
My impression was that smart card readers are pretty common and it is
the smartcards that keep changing. So USB access to the smart card
devices class should be enough there.
Being able to add custom/newer pkcs smartcard support modules sounds
like a good idea.
I wonder if that could be something
** Changed in: mir
Status: New => Invalid
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1549455
Title:
Mesa in Ubuntu has a patch for i915 that disables OpenGL 2.0 but not
GLES 2,0. Thats why all mir clients and the unity8 session starts up..
since mirserver always use GL|ES.
Regular qt clients do the EGL init in a different path and they insist
on GL 2.0.
When you recompile mesa without that patc
i915 does not have native shader support so mesa simulate that with
llvmpipe, using i915 only for blitting.. So a less demanding - (but also
not existing) fixed-function gl-1.x backend is the probably your best
chance to use that gpu with unity8.
--
You received this bug notification because you
** Bug watch added: GNOME Bug Tracker #769554
https://bugzilla.gnome.org/show_bug.cgi?id=769554
** Also affects: gtk via
https://bugzilla.gnome.org/show_bug.cgi?id=769554
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Yes those branches are not related at all. Unless we expect each client
to create a fullscreen transparent/empty surface on every output.
Do we really want to support client side decorations?
If so we could have a look at xdg-shells way of doing it. When a window
drag should be started (because t
** Bug watch added: GNOME Bug Tracker #768138
https://bugzilla.gnome.org/show_bug.cgi?id=768138
** Also affects: gtk via
https://bugzilla.gnome.org/show_bug.cgi?id=768138
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
The root cause for this problem was fixed upstream and applied in the
ubuntu packages in virtualbox and the kernel (lp:1669807)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1639745
Title
This bug cannot be fixed in mir or qtubuntu - applications like unity8
and the applications using qtdeclarative will be slow within x11 and
mir. A backend for fixed function gpus, i.e using only GL1.5 would be
required to fix that..
** Also affects: qtdeclarative (Ubuntu)
Importance: Undecided
Yes i can also remember seeing that stacktrace when toying around with
our reload hack, to get mesa to find our symbols during egl display
detection. But I dont get that anymore on xenial with lp:mir or
lp:mir/0.18
--
You received this bug notification because you are a member of Desktop
Packages
Wrt to the segmentation fault more details in
https://bugs.launchpad.net/mir/+bug/1526658
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209
Title:
[regression] Clients of nested Mir
37 matches
Mail list logo
