[Bug 1918035] Re: ld-2.31.so is not correctly packaged in libc6-dbg

2021-08-05 Thread Mario Sánchez Prada
Hi, thanks for reporting and for fixing this! Unfortunately, I'm on
Ubuntu 21.04 where the fix hasn't arrived yet as we're still on
2.33-0ubuntu5 [1], and I was wondering if it could be possible to
release at least the update to 2.33-0ubuntu6 in there as well, so that
we can have sane stack traces again without waiting for the 21.10
release (which I see already have 2.33-0ubuntu9 [2]).

WDYT? Would that be possible?

Thanks in advance!

[1] https://packages.ubuntu.com/source/hirsute/glibc
[2] https://packages.ubuntu.com/source/impish/glibc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918035

Title:
  ld-2.31.so is not correctly packaged in libc6-dbg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1918035/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

2020-05-04 Thread Mario Sánchez Prada
Same problem here, with a DisplayLink dock station and a Thinkpad P1
(1st gen) with the NVIDIA (Quadro P2000) card disabled, running only on
the iGPU that comes with my Xeon E-2176M CPU.

It's so unusable that I basically had to move back to using an NVIDIA-
only mode and plug the screen directly over the laptop's HDMI port,
which makes now the dock station a "glorified pots hub" :-).

This said, I believe this is in general a known issue of the DisplayLink
drivers for Linux, and not necessarily related to Ubuntu or the Linux
kernel. Reporting anyway in case I'm wrong and there's a chance to make
this work properly, which would be awesome for many reasons (e.g. I
could go back to the iGPU-only mode).

Hope this helps, and thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875015

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1875015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)

2018-10-23 Thread Mario Sánchez Prada
I can confirm this very same problem in my laptop, which is a Thinkpad
P1 with a Xeon E-2176M and hybrid Intel / NVIDIA card working in
"Discreet" mode (that is, only the NVIDIA card is enabled) using the
proprietary NVIDIA driver installed via the nvidia-driver-390 package
(390.87-0ubuntu1).

The NVIDIA card is a Quadro P2000 Mobile according to lspci:

  01:00.0 VGA compatible controller: NVIDIA Corporation GP107GLM [Quadro
P2000 Mobile] (rev a1)

I'm currently in Ubuntu 18.10 Cosmic Cuttlefish with kernel 4.18.0-10:

$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.10"
VERSION_ID="18.10"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic

$ uname -ar
Linux rosmon 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

And just to confirm, what I'm seeing is this:

1. Pressing the media keys for brightness cause not visible effect (no
brightness change), with errors showing up in the journal:

  oct 23 11:37:47 rosmon gsd-media-keys[2532]: Failed to set new screen 
percentage: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_5fpower_5fmanager_5ferror.Code0:
 Screen backlight not available
  oct 23 11:37:47 rosmon gsd-media-keys[2532]: Failed to set new screen 
percentage: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_5fpower_5fmanager_5ferror.Code0:
 Screen backlight not available

2. Installing xbacklight allows me to effectively change the brightness
from the command line (e.g. `xbacklight -set 50`, `xbacklight -inc
10`...)

3. The /sys/class/backlight directory is empty, suggesting that the ACPI
interface was not initialize, which I believe is why the media keys
don't work and throw that error in the journal (media keys -> gsd-media-
keys -> gsd-power-manager -> GUDev -> /sys/class/backlight ACPI
interface):

  $ ls -l /sys/class/backlight/
  total 0

4. Booting with acpi_osi= or acpi_osi=Linux causes the
/sys/class/backlight directory to be populated with a thinkpad_backlight
directory, and the media keys to respond showing the OSD for the
brightness, but does not change brightness at all when used:

  a. The brightness bar is always shown at "random" values between 0 and ~20%
  b. /sys/class/backlight/thinkpad_backlight/actual_brightness is always 0

Also, in this setup where /sys/class/backlight/ is not empty, xbacklight
does NOT work.


I hope this is helpful, as it's kind of annoying to have to use xbacklight to 
change brithgness. I was myself looking into a fix for this, but I can't figure 
out whether this should be fixed in the NVIDIA driver, some kernel module or 
somewhere else, so I figured I'd comment here and hope for the best.

PS: I can do more tests if needed. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775065

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775065/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776912] Re: chromium-browser package does NOT install an AppData file

2018-08-14 Thread Mario Sánchez Prada
Hi Olivier, sorry for the late reply but I'm in the middle of an
overseas relocation (UK > Spain) + holidays and I'm a bit off the grid
these days...

Thanks for your comment, and sorry for reporting it against the wrong
branch. Hopefully this will help having a better chromium package for
future releases, though.

Let me know if you need anything else from me and I'll try to help when
I get some time with my computer (will be a bit off the grid for a while
still, but on September things should get back to normal).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776912

Title:
  chromium-browser package does NOT install an AppData file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1776912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776912] Re: chromium-browser package does NOT install an AppData file

2018-06-14 Thread Mario Sánchez Prada
Note that the Fedora package is installing this file into the deprecated
path /usr/share/appdata, instead of using the one specified by AppStream
since a while ago: /usr/share/metainfo.

I've filed a bug for Fedora in
https://bugzilla.redhat.com/show_bug.cgi?id=1591306, but I'm commenting
this explicitly here to prevent confusion, and to be clear on that
/usr/share/metainfo should be the right place to install this file into.

** Bug watch added: Red Hat Bugzilla #1591306
   https://bugzilla.redhat.com/show_bug.cgi?id=1591306

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776912

Title:
  chromium-browser package does NOT install an AppData file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1776912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776912] [NEW] chromium-browser package does NOT install an AppData file

2018-06-14 Thread Mario Sánchez Prada
Public bug reported:

In order for Chromium Browser to integrate properly with software
centers (e.g. GNOME Software), an additional XML file with metadata
needs to be installed under /usr/share/metainfo, in the form of an
"AppData file", containing the relevant bits according to the AppStream
specification:

  https://www.freedesktop.org/software/appstream/docs

Fortunately, upstream has included that file in the chromium repository
for a while (since [1]) and, as far as I can see, Fedora is already
installing that file in its place, see
https://src.fedoraproject.org/rpms/chromium/blob/9cdea2b9/f/chromium.spec#_1462

I have quickly looked into the .install and rules files in of the
chromium-browser package for Ubuntu [2][3] and I could not find any
trace of this happening, so I guess all that would remain here would be
to adapt the debian packaging files to make sure that it gets installed
too for Ubuntu, similar to what Fedora and other distros do already.

[1] 
https://chromium.googlesource.com/chromium/src.git/+/d6807b9a7da70dae9191b93d4ec6157187515078%5E%21
[2] 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/chromium-browser.install
[3] 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/rules


https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#sect-Quickstart-DesktopApps

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776912

Title:
  chromium-browser package does NOT install an AppData file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1776912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742653] Re: chromium-browser 63+ packages 50+ MB of binaries only needed at build time

2018-01-11 Thread Mario Sánchez Prada
No problem, happy to see the report and the patch are useful.

After all, shaving 50MB out of 260MB is quite something! :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742653

Title:
  chromium-browser 63+ packages 50+ MB of binaries only needed at build
  time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2018-01-11 Thread Mario Sánchez Prada
Sorry for dropping the ball on this one, for some reason I completely
missed all notifications and I only happened to find this bug today
almost by chance :-)

Anyway, if you don't mind me asking... I understand that my workaround
of passing --with-system-groups='lpadmin root' to configure when
building CUPS would no longer be needed with the patches for cups-pk-
helper 0.2.6-1ubuntu2 and 0.2.6-1ubuntu3?

If so, one more question: would this be proposed to Debian? I can't see
them in https://packages.debian.org/sid/cups-pk-helper, but comments in
this thread seem to suggest the intention is to have them there as well.

Many thanks in any case

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934291

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742653] Re: chromium-browser 63+ packages 51+ MB of binaries only needed at build time

2018-01-11 Thread Mario Sánchez Prada
** Summary changed:

- chromium-browser 63+ package includes a 44MB binary only needed at build time
+ chromium-browser 63+ packages 51+ MB of binaries only needed at build time

** Summary changed:

- chromium-browser 63+ packages 51+ MB of binaries only needed at build time
+ chromium-browser 63+ packages 50+ MB of binaries only needed at build time

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742653

Title:
  chromium-browser 63+ packages 50+ MB of binaries only needed at build
  time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742653] Re: chromium-browser 63+ package includes a 44MB binary only needed at build time

2018-01-11 Thread Mario Sánchez Prada
I believe all it's needed is to patch the debian/rules file to add 
`v8_context_snapshot_generator` to the TRASH list of files:
```
--- a/debian/rules  2017-12-07 08:40:06.0 +
+++ b/debian/rules  2018-01-11 10:59:39.168190995 +
@@ -219,7 +219,7 @@
 override_dh_install-arch: T := verify-install-integrity-dep
 override_dh_install-arch: SPACE := $(eval) $(eval)
 override_dh_install-arch: S_CR_PATH := apps/chromium/current
-override_dh_install-arch: TRASH := .deps gen obj obj.host obj.target \*.lock 
build.\* .landmines mksnapshot\* protoc pyproto re2c resources yasm \*.TOC 
product_logo_\*png gen\* lib/\* lib libvpx_obj_int_extract .ninja\* 
chrome-wrapper \*.breakpad.\* java_mojo dump_syms browser_test_resources 
ar_sample_test_driver unittests app_streaming/dev locales remoting_locales
+override_dh_install-arch: TRASH := .deps gen obj obj.host obj.target \*.lock 
build.\* .landmines mksnapshot\* protoc pyproto re2c resources yasm \*.TOC 
product_logo_\*png gen\* lib/\* lib libvpx_obj_int_extract .ninja\* 
chrome-wrapper \*.breakpad.\* java_mojo dump_syms browser_test_resources 
ar_sample_test_driver unittests app_streaming/dev locales remoting_locales 
v8_context_snapshot_generator
 override_dh_install-arch: debian/chromium-browser.sh
 override_dh_install-arch:
# Two stages: Install out of source tree. Copy to packaging.
```

That said, if we're to update that TRASH list, I'd recommend adding a
few more files to that list that we (Endless) found useful to reduce the
size of the resulting package even more, since those are only used for
building as well, and take up quite some space too (e.g. toolchain.ninja
is 5 MB, gn binary is 2.5 MB...).

Thus, the full list of targets I'm proposing to add to TRASH is this:
  - v8_build_config.json 
  - v8_context_snapshot_generator
  - args.gn
  - gn
  - *.ninja

This would reduce the size of the installed binary in a bit over 51MB in
total, not bad :-). FWIW, we had those additional targets added to TRASH
in our chromium-browser package for a while already, not sure why we
didn't reported that before, sorry about that.

See attached the patch implementing this proposal

** Patch added: "Save 50+ MB by avoiding packaging build only files"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+attachment/5035029/+files/avoid-packaging-build-only-files.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742653

Title:
  chromium-browser 63+ packages 50+ MB of binaries only needed at build
  time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742653] [NEW] chromium-browser 63+ package includes a 44MB binary only needed at build time

2018-01-11 Thread Mario Sánchez Prada
Public bug reported:

As mentioned in [1], it seems like the chromium-browser package might
be, since Chromium 63, packaging a new and pretty big (44MB) binary that
is not needed at run time, just at build time.

This binary is `/usr/lib/chromium-browser/v8_context_snapshot_generator`, which 
is at the moment being packaged (see file list for bionic in [2]) in the 
chromium-browser package along with the 1MB related binary that is the only one 
that should be included in the package:
```
$ ls -ltrh /usr/lib/chromium-browser/v8_context_snapshot*
-rwxr-xr-x 1 root root  44M Jan  9 18:21 
/usr/lib/chromium-browser/v8_context_snapshot_generator
-rw-r--r-- 1 root root 1.6M Jan  9 18:21 
/usr/lib/chromium-browser/v8_context_snapshot.bin
```

This can become a big deal in space-constrained installations, of
course, but considering that the installed size of the package is
~260MB, this binary alone accounts for ~16% of the package's size, so it
would be good to clean that up from the package if possible.

[1] 
https://askubuntu.com/questions/986031/why-is-chromium-browser-63-so-much-bigger-than-62/986132
[2] https://packages.ubuntu.com/bionic/amd64/chromium-browser/filelist
[3] 
https://docs.google.com/document/d/1jpQQX0piaxcHJPWakp_Kr_03g5Gnma5h5-Kdlqu7jVQ/edit#heading=h.k6iklq6rvd30

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742653

Title:
  chromium-browser 63+ package includes a 44MB binary only needed at
  build time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1253638] Re: dynamic linker does not use DT_RUNPATH for transitive dependencies

2017-07-14 Thread Mario Sánchez Prada
> I don't know if this is expected behavior, but it's certainly annoying
behavior. I'm writing an app that depends on libtcodxx.so, which in turn
depends on libtcod.so. I want to ship them both in the lib directory
next to my app. With RUNPATH as "$ORIGIN/lib", it finds the direct
dependency (libtcodxx.so) and then doesn't look in the same directory
for its dependency. To get it to search there for both, I have to set
RPATH to "$ORIGIN/lib", and I suspect that RPATH may not technically be
supposed to support the $ORIGIN syntax.

It looks like it's the expected behaviour after all. From "Shared Object
Dependencies" section in [1]:

"""
The set of directories specified by a given DT_RUNPATH entry is used to find 
only the immediate dependencies of the executable or shared object containing 
the DT_RUNPATH entry. That is, it is used only for those dependencies contained 
in the DT_NEEDED entries of the dynamic structure containing the DT_RUNPATH 
entry, itself. One object's DT_RUNPATH entry does not affect the search for any 
other object's dependencies.
"""

Another interesting bit in [1] is the "Dynamic Array Tags" table, where
it's stated that RUNPATH is optionally considered for both shared
objects and executables, while RPATH is ignored for shared objects. It
seems like that suggests the idea when using RUNPATH is that you'd have
both executables and shared objects specifying it, instead of setting it
just for the "top level" executable and letting that work transitively.

I've investigated this a bit and it seems that the move to using
--enable-new-dtags by default is something Debian changed explicitly a
while ago:

  binutils (2.27.51.20161116-2) unstable; urgency=medium
  
* Stop building the mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 
mips64r6el
  variants; can't continue with this work, because package uploads with
  these architectures are still rejected.
* Add homepage attribute to the control file: Closes: #841432.
* ld: enable new dtags by default for linux/gnu targets. Closes: #835859.
* Fix PR ld/20827, using proposed patch. Closes: #844378.
  
   -- Matthias Klose   Thu, 17 Nov 2016 11:56:55 +0100

While I understand this probably makes sense in a world where everyone
is aware of these differences and either upstream projects are built
considering RUNPATH (e.g. WebKitGTK+) or packagers explicitly workaround
this by passing --disable-new-dtags to projects that haven't been
adapted upstream yet (e.g. GNOME Shell), it still seems to me like this
has huge potential to break things if it just gets enabled in other
Debian-based without further consideration (and rebuilds!), so if you're
having this problem and you control your platform but not every single
package built on top of it, you might consider reverting the Debian
patch that closes #835859 for the time being.

That's precisely what we're considering to do in Endless for now, and I
thought I'd share it here in case this analysis was useful for someone
else, if anything as a sign of gratitude for this bug report in itself,
which was very useful for me to understand better what was going on when
we first encountered this problem ourselves (similar to what was
reported already in [2] and [3])

Hope this helps too!
Mario

[1] 
https://refspecs.linuxfoundation.org/elf/gabi4+/ch5.dynamic.html#shobj_dependencies
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844796#5
[3] https://bugzilla.gnome.org/show_bug.cgi?id=777519

** Bug watch added: Debian Bug tracker #844796
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844796

** Bug watch added: GNOME Bug Tracker #777519
   https://bugzilla.gnome.org/show_bug.cgi?id=777519

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253638

Title:
  dynamic linker does not use DT_RUNPATH for transitive dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1253638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1066529] Re: All jobs stopped, epson_inkjet_printer_filter failed

2016-02-19 Thread Mario Sánchez Prada
This looks to me as a duplicate of
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/840998

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066529

Title:
  All jobs stopped, epson_inkjet_printer_filter failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1066529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1272001] Re: Evolution black background in mail display

2016-01-20 Thread Mario Sánchez Prada
I found this bug today in our downstream platform that is still using
evolution 3.10.1, and thought it would be relevant to mention that this
has been fixed usptream for bug
https://bugzilla.gnome.org/show_bug.cgi?id=731872, and also that the
patch from there applied cleanly on top of my 3.10.1, fixing the problem
seamlessly for me too.

So, perhaps you could consider reverting the hack into the CSS files for
those two themes (as it impacts GtkWindow and GtkPanel widgets in
general) and just backporting that patch on evolution itself too.

My 2 cents

** Bug watch added: GNOME Bug Tracker #731872
   https://bugzilla.gnome.org/show_bug.cgi?id=731872

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272001

Title:
  Evolution black background in mail display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1272001/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 934291] Re: Deleting or stopping print jobs does not work

2015-04-20 Thread Mario Sánchez Prada
I've been investigating this issue recently and can confirm that, while
this is not an issue in my Fedora machine with the very same version of
cups, cups-pk-helper and gnome-control-center installed, it is still
present in Ubuntu, due to what I believe it might be a bug in the way
CUPS is being packaged by debian (thus Ubuntu would have inherited the
bug). Thus it's probably a bug in Debian as well.

Long story short, while Fedora configures root to be part of CUPS
system administration group, Debian/Ubuntu does not do that and instead
defines lpadmin as the only member of that group. Now, because gnome-
control-center actually relies in cups-pk-helper to cancel jobs, CUPS
won't allow doing that in ubuntu because neither the owner of the job
(cups-pk-helper runs as root, not as the username originating the cancel
request from g-c-c) nor an user belonging to SystemGroup is requesting
such an operation. As a result, the operation is not cancelled.

You can see a more detailed explanation here:
https://bugzilla.gnome.org/show_bug.cgi?id=669679#c23

I fixed this locally by changing the debian/rules so that I pass
--with-system-groups='lpadmin root' to dh_auto_configure, instead of
simply passing 'lpadmin' and that works for me. I think it's worth
reporting this to debian, but it's unclear to me how to do so, so I
thought I would report it here for now, in case someone could lend a
hand with it.

Thoughts?

PS: A temporary fix for users facing this problem, better than setting
JobsPrivateValues to 'none', would be to simply edit /etc/cups/cups-
files.conf and manually add 'root' to SystemGroup

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934291

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 718080] Re: TypeError: value is of the wrong type for this column

2011-04-12 Thread Mario Sánchez Prada
At the moment I'm not using ubuntu in this machine but Fedora 14, so I'd
say versions of the dependencies would be pretty much the same (or quite
similar) than in ubuntu maverick. In more detail:

 glib2-2.26.0
 gtk2-2.22
 pygobject2-2.21.5
 pygtk2-2.17
 pygtk2-libglade-2.17
 python-2.7-8

I now it's weird to file a bug in launchpad when it was reproduced in
fedora, but as I got the code from the bazaar repo in launchpad I
thought it was the proper place to do it, specially after finding
exactly the same problem reported here.

But if you feel like this is not the proper place for me to ask just let
me know and I'll do it in any other place :-)

Last, but not least, I think I could try to reproduce it in a ubuntu
environment using a KVM image but that would take me more time which
I'mlacking right now, so let's see if we can fix it this way first.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/718080

Title:
  TypeError: value is of the wrong type for this column

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs