from:"Pascal"

I don't think a package recommendation is the right thing here. Instead,
the package containing fuse3 and fusermount3 should here be a package
dependency of the gnome-remote-desktop package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1970411

Title:
  gnome-remote-desktop-daemon crashes on fuse_thread_func →
  g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
  missing fusermount3)

Status in fuse3 package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop package in Debian:
  New

Bug description:
  GNOME Remote desktop crashes if fuse3 package is not installed as it
  provides fusermount3, that fuse_session_mount() implicitly requires.

  libfuse3 is currently suggesting fusermount3, I'm wondering if we
  should instead recommending it, given that one of the library function
  relies on that.

  Otherwise, we should probably make the g-r-d dependency stronger.

  Stack trace:

  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
  writer_func = 
  writer_user_data = 
  recursion = 
  depth = 
  __func__ = "g_log_structured_array"
  _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
  fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
  n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
  domain = 0x0
  data = 0x0
  depth = 
  log_func = 0x7f79092e2ee0 
  domain_fatal_mask = 
  masquerade_fatal = 0
  test_level = 6
  was_fatal = 
  was_recursion = 
  buffer = 
  msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  i = 2
  size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
  args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at 
../src/grd-rdp-fuse-clipboard.c:1321
  rdp_fuse_clipboard = 0x5605ed301820
  args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
  argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
  result = 

  
  Further details:
   - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS

As for the RDP connection problem, please provide enough information.
If you have an updated system, then your FreeRDP build should contain the NTLM 
fixes. Jeremy afaik backported them to Ubuntu in 
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1968577.
Meanwhile, FreeRDP-2.7.0 was released, and distros should update to that 
version.

If you have your system updated (and therefore should have the NTLM
fixes), then the issue is either you provided the wrong credentials or
an error in the client.

Without providing the information, which client and which client settings are 
used, there is nothing, that can be said here.
Please the follow the official help: 
https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html
It contains a section about recommended clients and client settings.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1970139

Title:
  VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu
  22.04 LTS

Status in gnome-remote-desktop package in Ubuntu:
  Incomplete

Bug description:
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # apt-cache policy gnome-remote-desktop
  gnome-remote-desktop:
Instalados: 42.0-4ubuntu1
Candidato:  42.0-4ubuntu1
Tabla de versión:
   *** 42.0-4ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
  100 /var/lib/dpkg/status

  # uname -a
  Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  
  Summary of the bug:
  ---
  When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 
Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect 
(connection is refused). The connection passes the Password check validation 
but don't connect (sometimes shows screen garbage before disconnecting).

  I've used several VNC clients (Remmina in Ubuntu and Real VNC in
  Android) getting the same problem failing either in X11 or Wayland.

  Notes: 
  - VNC connection does work in in previous Ubuntu 21.10 version with the same 
architecture (arm64) and same Raspberry Pi.
  - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and 
gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that 
doesn't work on arm64 (Raspberry Pi).

  There is no apport info at all. Also there is almost no info in the
  journal regarding this problem. When I try to connect to VNC server it
  show this:

  On Wayland:
  ---
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
1884160 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
4169728 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8130560 bytes), total 32768 (slots), used 83 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8294400 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8294400 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8294400 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8294400 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main 
process exited, code=killed, status=11/SEGV
  abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed 
with result 'signal'.
  abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions 
vanished
  abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 1.
  abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop.
  abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop...
  abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop.
  abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load 
libcuda.so.1
  abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load 
libnvidia-encode.so.1
  abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started
  abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started

  
  On X11:
  ---
  abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main 
process exited, code=killed, status=11/SEGV
  abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions 
vanished
  abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed 
with result 'signal'.
  abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 19.
  abr 25 00:12:18 fpgrpi systemd[2859]:

[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS

To be honest, the issue description is insufficient and the crash file useless.
The stacktrace does not contain any debug symbols and for the "sometimes shows
screen garbage before disconnecting" part, a screenshot would be needed,
because the screen content is not just garbage.
It has a pattern, and that is a wrong DRM format modifier. It may not be
obvious for the user, but developers don't have a glass ball in front of them
to see what happens on the other side of the screen, so a screenshot can be
super helpful.

I found similar stacktraces in Ubuntus error tracker. Problem with Ubuntus
error tracker is that a lot stacktraces cannot be retrieved and therefore leave
only a single line of calls, where only the library name is shown.
And this is also here the case.

However, the issue could be fixed upstream and is fixed in the current master
branch of g-r-d, due to kind help of a person in
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/96.
Personally, I don't have an arm64 device, which is why this issue could never
been detected.
And without that help in form of testing patches and providing the stacktrace
with debug symbols, the issue would still exist.

The crash itself is kinda interesting, because it appears, that some
instructions are completed in a different order on arm64.
It was fixed in
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/bdc8d63bddf2ebb0da97e9277267b7398e49710e
and
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/b7b0597ba59072b718a78760c2732e64e080b4bf.

Then, to the part, what is here referred to as 'garbled content':
A screenshot for this is provided here:
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/96#note_1435877
Without the screenshot, I wouldn't been able to have that modifier guess. So,
please, for future reports provide screenshots for such things.
The issue here is that g-r-d always expected explicit DRM format modifiers.
However, it is an implicit modifier here.
There is no such flag to indicate that and as a result the
`DRM_FORMAT_MOD_INVALID` modifier is used to indicate an implicit modifier.
It is a weird thing though: In a screencast, submitting this specific modifier
means, that an implicit modifier is used, while graphics APIs use this to
indicate an error.
However, using `DRM_FORMAT_MOD_INVALID` as modifier was never a problem with
other drivers, like Intel and so it was unnoticed.
The issue was fixed in
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/60244e96333fbeabfee9c1a0e5ce56590dbb313d
and
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/d9923317f0b60621f0aeb219f4d10612a2178e63.

I'll ask Jonas to push another release tag (might be 42.1.1). 42.1 was pushed
saturday, but does not contain these fixes. Personally, I see this issue as
severe, but I am not one, who can push tags in g-r-d. So, I can only ask Jonas
to push one.
In any case, Ubuntu can also build g-r-d from the master branch until commit
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/d9923317f0b60621f0aeb219f4d10612a2178e63
to push the fix to Ubuntu here.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #96
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/96

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1970139

Title:
VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu
22.04 LTS

Status in gnome-remote-desktop package in Ubuntu:
Incomplete

Bug description:
# lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04

# apt-cache policy gnome-remote-desktop
gnome-remote-desktop:
Instalados: 42.0-4ubuntu1
Candidato: 42.0-4ubuntu1
Tabla de versión:
*** 42.0-4ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
100 /var/lib/dpkg/status

# uname -a
Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC
2022 aarch64 aarch64 aarch64 GNU/Linux

Summary of the bug:
---
When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4
Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect
(connection is refused). The connection passes the Password check validation
but don't connect (sometimes shows screen garbage before disconnecting).

I've used several VNC clients (Remmina in Ubuntu and Real VNC in
Android) getting the same problem failing either in X11 or Wayland.

Notes:
- VNC connection does work in in previous Ubuntu 21.10 version with the same
architecture (arm64) and same Raspberry Pi.
- VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and
gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that
doesn't work on arm64 (Raspberry Pi).

There is no apport info at all. Also there

[Desktop-packages] [Bug 1969619] Re: RDP Sharing appears on by default in jammy

While the fix here is correct, the assumptions in this issue are wrong.
I wrote an explanation of this issue in
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-
desktop/+bug/1970039/comments/7.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1969619

Title:
  RDP Sharing appears on by default in jammy

Status in gnome-control-center:
  Unknown
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Jammy:
  Fix Released

Bug description:
  Impact
  ==
  1. It looks like RDP Sharing is turned on but it is not.
  2. To actually turn on RDP Sharing, you would need to turn it off then turn 
it on.

  This bugfix fixes it so that it correctly shown as off by default and
  turning it on works.

  Test Case
  =
  0. Start with a clean Ubuntu 22.04 install.
  Or you can create a new user and log in as the new user.
  1. Open the Settings app.
  2. In the left sidebar, click Sharing. The switch at the top of the page 
needs to be off.
  3. Turn the switch on. Then click Remote Desktop and turn it on.
  4. Close the Settings app.
  5. Open the Settings app and verify that Sharing is on and Remote Desktop is 
on.
  6. Close the Settings app.
  7. From a terminal, run
  systemctl --user status gnome-remote-sharing.service

  It should show the service as active (running) and
  a line at the bottom should say RDP server started
  8. Then run
  systemctl --user stop gnome-remote-sharing.service
  9. Open the Settings app. It should show that Remote Desktop sharing is off.
  10. Turn on Sharing and turn on Remote Desktop sharing.
  11. Run
  systemctl --user status gnome-remote-sharing.service

  It should show the service as active (running) and
  a line at the bottom should say RDP server started

  What Could Go Wrong
  ===
  This is a minimal fix proposed upstream.
  The original implementation was insufficient.
  The bugfix will allow Remote Desktop to be turned on and work correctly from 
the beginning.

  More Details
  
  To simplify this bug report, I removed a lot of troubleshooting details that 
can still be seen with the "See full activity log" link

  Just opening the Sharing panel flips the gsettings key 
org.gnome.desktop.remote-desktop.rdp enable to true
  and apparently tries to start RDP sharing. RDP sharing doesn't work because 
the TLS keys weren't set yet.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970039] Re: cannot disable Remote Desktop in Ubuntu 22.04

Yeah, this issue here is a duplicate of the bug mentioned in comment 6. Jeremy
submitted a patch, which sufficiently fixed the issue in
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1286 (it
should technically check for other aspects too), but for now it is sufficient.
Follow-ups should use an upstream report or MR for this.

Just to note: What people confuses here is the state of what the switch
represents and therefore leads to the wrong conclusions above.
Just because g-r-d is running, does not mean it listens on some ports for
connections, nor that it starts any of the server backends (RDP or VNC).
Before Jeremys change, the state in g-c-c represented, whether the g-r-d
service is enabled and running. However, the backends have their own 'enabled'
settings (default: false ('off')). Also, the RDP backend won't be started by
g-r-d, when the server cert and private keyfile are missing.
These are generated, when the switch in g-c-c is switched to 'on'.

The reason, why this issue was not apparent initially was that due a recent
systemd change, g-r-d did not start automatically, when the service was enabled.
This was fixed in
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd380dffc108e5c7f77c81fbaa271ec7b,
but lead to this issue here.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1970039

Title:
cannot disable Remote Desktop in Ubuntu 22.04

Status in gnome-remote-desktop package in Ubuntu:
Incomplete

Bug description:
1. Go to Settings
2. sharing
3. Disable Remote Desktop and Sharing
4. Restart PC

problem: Remote Desktop is enabled. seems to be connected with RDP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970039/+subscriptions

[Desktop-packages] [Bug 1930297] Re: Clipboard sharing is disabled when using RDP backend

2022-04-25 Thread Pascal Nowack

Marco, Jeremy, while this issue is fixed. You need to adjust the .deb pkg to 
depend on Fuse3.
Currently, it is not done and therefore crashes for some people: 
https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

This was also reported in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=998846.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1930297

Title:
  Clipboard sharing is disabled when using RDP backend

Status in gnome-remote-desktop package in Ubuntu:
  Fix Committed

Bug description:
  We disabled RDP clipoard as part of gnome-remote-desktop 40.1-1 as it
  requires libfuse-3 to be in main.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1930297/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1964976] Re: gnome-remote-desktop is not listening on port 5900, no sign of why

2022-04-25 Thread Pascal Nowack

This was fixed in https://bugs.launchpad.net/ubuntu/+source/gnome-
control-center/+bug/1968518

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1964976

Title:
  gnome-remote-desktop is not listening on port 5900, no sign of why

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  Fix Released

Bug description:
  With all current packages from jammy, gnome-remote-desktop is not
  listening on port 5900. Lsof doesn't show it listening on that port,
  attempting to connect to that port yields connection refused), with no
  indication of why. There are no errors matching the pattern "gnome-
  remote-desktop" in /var/log/syslog, "journalctl --user --unit gnome-
  remote-desktop" doesn't show any errors, "systemctl status --user
  gnome-remote-desktop" shows that it is running, my settings show that
  screen sharing is enabled, this used to work, and I haven't changed
  anything since it did.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-remote-desktop 42~rc-1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 10:49:08 2022
  InstallationDate: Installed on 2019-01-02 (1167 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-remote-desktop
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1964976/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1964976] Re: gnome-remote-desktop is not listening on port 5900, no sign of why

2022-03-16 Thread Pascal Nowack

Me (upstream g-r-d) already predicted this, as soon as I saw that Ubuntu
ships mixed versions (gnome-control-center-41 (g-c-c) for GNOME 42
(that's unsupported upstream and as seen here breaks things)).

For GNOME 42, we finally switched over to the RDP backend in g-r-d. As a result
the UI in g-c-c has been redesigned
(https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1205#note_1393775).
To not also unintentionally listen on VNC in the background without the notice
of the user, the gsettings were adjusted, so that each g-r-d backend has its
internal switch (default: off).

You can check that by checking both g-r-d's and g-c-c's version.
Upstream we make sure that things won't break in the major version. This
means that all components need to have the same major version (i.e.
g-r-d-42 + g-c-c-42 + ...-42). Minor versions are just bugfix releases.

Jeremy and Marco of the Ubuntu Desktop Team are already aware of this from our
discussion on IRC. It's up to Ubuntu now to act. The remote desktop is not the
only thing that breaks here downstream due to mixed versions.
According to Marco, Ubuntus decision would either be to backport the g-r-d UI
changes or adjust their g-c-c build to use VNC again.

Some more info on the RDP backend in 42:
https://gitlab.gnome.org/GNOME/gnome-remote-
desktop/-/issues/26#note_1396166

** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #26
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/26

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1964976

Title:
gnome-remote-desktop is not listening on port 5900, no sign of why

Status in gnome-remote-desktop package in Ubuntu:
New

Bug description:
With all current packages from jammy, gnome-remote-desktop is not
listening on port 5900. Lsof doesn't show it listening on that port,
attempting to connect to that port yields connection refused), with no
indication of why. There are no errors matching the pattern "gnome-
remote-desktop" in /var/log/syslog, "journalctl --user --unit gnome-
remote-desktop" doesn't show any errors, "systemctl status --user
gnome-remote-desktop" shows that it is running, my settings show that
screen sharing is enabled, this used to work, and I haven't changed
anything since it did.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-remote-desktop 42~rc-1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 15 10:49:08 2022
InstallationDate: Installed on 2019-01-02 (1167 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: gnome-remote-desktop
UpgradeStatus: Upgraded to jammy on 2022-02-20 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1964976/+subscriptions

[Desktop-packages] [Bug 1934527] Re: Window switching with Alt-Tab stops working after a while

2021-08-24 Thread Pascal Bercher

*** This bug is a duplicate of bug 1933996 ***
https://bugs.launchpad.net/bugs/1933996

I believe that the bug is related to Wayland. It can be fixed by not
using it as described here:
https://askubuntu.com/questions/1349544/alttab-stops-working-after-a-
while-in-ubuntu-21-04/1359821#1359821

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1934527

Title:
  Window switching with Alt-Tab stops working after a while

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 21.04,since around 01 July 2021, Alt-Tab works as usual for
  a while after logging in, but then stops entirely (that is, it does
  nothing; the switcher overlay fails to appear, and switching between
  windows does not work). I made _no_ configuration change, and Alt-Tab
  continues to be configured in the keyboard shortcuts settings as
  usual.

  This has been described by other users here:
  https://askubuntu.com/questions/1349544/alttab-stops-working-after-a-
  while-in-ubuntu-21-04

  There seems to be some possible connection to Thunderbird in
  particular, and the fact that in the left-hand-side launcher (?) /
  favourites of the Ubuntu desktop, the Thunderbird icon starts behaving
  strangely, e.g. does not show the open Thunderbird windows when
  clicking on it ... while other applications work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934527/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1924778] [NEW] Xorg buggy

2021-04-16 Thread Pascal Kuppler

Public bug reported:

After boot and login the screen flashes and when i open i.e. Firefox i
can see the desktop icons flashing

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 16 17:28:13 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2021-02-21 (53 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20ARS20N00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=d09e8852-af20-45ea-8147-e76491467e1b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2020
dmi.bios.release: 2.54
dmi.bios.vendor: LENOVO
dmi.bios.version: GJETA4WW (2.54 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ARS20N00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrGJETA4WW(2.54):bd03/27/2020:br2.54:efr1.14:svnLENOVO:pn20ARS20N00:pvrThinkPadT440s:rvnLENOVO:rn20ARS20N00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20ARS20N00
dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1924778

Title:
  Xorg buggy

Status in xorg package in Ubuntu:
  New

Bug description:
  After boot and login the screen flashes and when i open i.e. Firefox i
  can see the desktop icons flashing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 17:28:13 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-02-21 (53 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20ARS20N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=d09e8852-af20-45ea-8147-e76491467e1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2020
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJETA4WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARS20N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJETA4WW(2.54):bd03/27/2020:br2.54:efr1.14:svnLENOVO:pn20ARS20N00:pvrThinkPadT440s:rvnLENOVO:rn20ARS20N00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARS20N00
  dmi.product.sku:

[Desktop-packages] [Bug 1923305] [NEW] LibreOffice 6.4 OpenType Features unusable

2021-04-10 Thread Pascal de Bruijn

Public bug reported:

When using OpenType features (Format - Character - Feature) from a
capable font like EB Garamond 12, LibreOffice automatically enables a
fractional style, which essentially makes all numerics unusable, and
there's no obvious way to disable this in the GUI once you've opened the
Features dialog.

There are two workaround, as all OpenType features get disabled when
selecting another font, and back again.

And, of course, one can remove :frac=1 manually from the font name
field.

This has however been fixed in LibreOffice 7.0 onward, but somehow
wasn't cherrypicked into 6.4.x, even though the change seems trivial:

https://github.com/LibreOffice/core/commit/d28c9d56df8a2629321bda116a6d2dcfa587d160

Please consider including this cherrypick in a future package for Ubuntu
Focal.

The patch won't apply directly due to a filename typo getting corrected,
which needs to be uncorrected in the patch:

vcl/source/font/OpenTypeFeatureDefinitionList.cxx
vcl/source/font/OpenTypeFeatureDefinitonList.cxx

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1923305

Title:
  LibreOffice 6.4 OpenType Features unusable

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When using OpenType features (Format - Character - Feature) from a
  capable font like EB Garamond 12, LibreOffice automatically enables a
  fractional style, which essentially makes all numerics unusable, and
  there's no obvious way to disable this in the GUI once you've opened
  the Features dialog.

  There are two workaround, as all OpenType features get disabled when
  selecting another font, and back again.

  And, of course, one can remove :frac=1 manually from the font name
  field.

  This has however been fixed in LibreOffice 7.0 onward, but somehow
  wasn't cherrypicked into 6.4.x, even though the change seems trivial:

  
https://github.com/LibreOffice/core/commit/d28c9d56df8a2629321bda116a6d2dcfa587d160

  Please consider including this cherrypick in a future package for
  Ubuntu Focal.

  The patch won't apply directly due to a filename typo getting
  corrected, which needs to be uncorrected in the patch:

  vcl/source/font/OpenTypeFeatureDefinitionList.cxx
  vcl/source/font/OpenTypeFeatureDefinitonList.cxx

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1922436] [NEW] v38 of pixman causes segfault for some SVGs

2021-04-03 Thread Pascal Wichmann

Public bug reported:

libpixman crashes for some SVGs with:
python[XXX]: segfault at XX ip XX sp XX error 4 in libpixman-1.so.0.38.4[XXX]

The problem (incl. reproducible example) is described here:
https://github.com/Kozea/CairoSVG/issues/319

** Affects: pixman (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pixman in Ubuntu.
https://bugs.launchpad.net/bugs/1922436

Title:
  v38 of pixman causes segfault for some SVGs

Status in pixman package in Ubuntu:
  New

Bug description:
  libpixman crashes for some SVGs with:
  python[XXX]: segfault at XX ip XX sp XX error 4 in libpixman-1.so.0.38.4[XXX]

  The problem (incl. reproducible example) is described here:
  https://github.com/Kozea/CairoSVG/issues/319

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846423] Re: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION

2021-01-05 Thread Pascal Tombelle

I'm also experiencing this bug, with Win 10 and TB78.6.0 (32 bits).

Many occurences of :

BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-P2D
DESCRIPTION:Description par défaut Mozilla
X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame
 ter with an illegal type for property: VALUE=DURATION
END:VALARM

Some events disappear when I close, then reopen TB

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1846423

Title:
  Lightning: Cannot dismiss reminders. Got a VALUE parameter with an
  illegal type for property: VALUE=DURATION

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Cannot dismiss reminders for a recurrence with exceptions. Calendar entries 
like this are generated:
  BEGIN:VALARM
  ACTION:DISPLAY
  DESCRIPTION:My recurrence
  TRIGGER;VALUE=DURATION:-PT120M
  X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame
   ter with an illegal type for property: VALUE=DURATION
  END:VALARM

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2004 F pulseaudio
   /dev/snd/controlC0:  vectro 2004 F pulseaudio
  BuildID: 20190705212852
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Oct  2 17:50:39 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.sku: T4M40UT#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1885159] Re: Firefox 78.0 RC hangs at startup on Ubuntu 16.04

2020-06-30 Thread Pascal Mons

Confirming the fix actually works.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1885159

Title:
  Firefox 78.0 RC hangs at startup on Ubuntu 16.04

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  After latest FF beta update - Firefox doesn't start (also there is no
  crash). In system monitor Firefox process is visible, but still app
  doesn't appear.Starting in safe mode doesn't help.

  Previous version: 77.0.1+build1-0ubuntu0.16.04.1
  Updated version: 78.0+build1-0ubuntu0.16.04.2
  Ubuntu version: Ubuntu 16.04.6 LTS
  Apport bug report attached.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1883197] Re: Headset not working

2020-06-11 Thread Pascal Lambert

I just upgrade to pulseaudio:amd64 1:13.99.1-1ubuntu3.3 and I don't have
the issue anymore :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1883197

Title:
  Headset not working

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I plug the headset in and when the gnome "Select Audio Devices" pop-up 
and select "Headset" (rather than Headphones), the sound doesn't go through. 
But when I select "Headphones" it does. 
  The only way I can get sound coming through the Headset is by choosing 
"Headphones" and manually select the Headset mic in the sound settings to have 
my headset working properly. This issue appears in 20.04. I didn't have this 
issue before I upgrade from 19.10 (and previous releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal274918 F pulseaudio
   /dev/snd/pcmC0D0c:   pascal274918 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Thu Jun 11 19:50:11 2020
  InstallationDate: Installed on 2019-05-14 (394 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Only some of outputs are working
  Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0NFGCT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883197/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1883197] Re: Headset not working

2020-06-11 Thread Pascal Lambert

When running `alasactl monitor` and plugging the headset and choose 
"Headphones", I see the following logs line
```
node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE
node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE
node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE
node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE
node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE
node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE
node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE
node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE
node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE
node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE
node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE
node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE
node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE
node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE
node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE
node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE
```

and when I plug it and select "Headset" I see the following log lines
```
node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE
node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE
node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE
node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE
node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE
node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE
node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE
node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE
node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE
node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE
node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE
node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE
node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE
```

The only difference is when selecting "Headphones" 3 more lines are added
```
node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE
node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE
node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE

```

But after several plugin/plugout (about a dozen of time) I only see the 
following log lines regardless of choosing "Headphones" or "Headset" but still 
no audio coming out to the Headset when choosing "Headset".
```node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE
node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE
node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE
node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE
node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE
node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE
node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE
node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE
node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE
node hw:0, #11 (2,0,0,Capture Source,0) VALUE
node hw:0, #11 (2,0,0,Capture Source,0) VALUE

```


** Description changed:

- When I plug the headset in and when the gnome "Select Audio Devices"
- popup and select "Headset" (rather than Headphones), the sound doesn't
- go through. But when I select "Headphones" it does. But I then need to
- manually select the Headset mic in the sound settings to have my headset
- working properly. This issue appear in 20.04. I didn't had this issue
- before I upgrade from 19.10 (and previous releases).
+ When I plug the headset in and when the gnome "Select Audio Devices" pop-up 
and select "Headset" (rather than Headphones), the sound doesn't go through. 
But when I select "Headphones" it does. 
+ The only way I can get sound coming through the Headset is by choosing 
"Headphones" and manually select the Headset mic in the sound settings to have 
my headset working properly. This issue appears in 20.04. I didn't have this 
issue before I upgrade from 19.10 (and previous releases).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  pascal274918 F.... pulseaudio
-  /dev/snd/pcmC0D0c:   pascal274918 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  pascal274918 F pulseaudio
+  /dev/snd/pcmC0D0c:   pascal274918 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Thu Jun 11 19:50:11 2020
  InstallationDate: Installed on 2019-05-14 (394 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Bla

[Desktop-packages] [Bug 1883197] [NEW] Headset not working

2020-06-11 Thread Pascal Lambert

Public bug reported:

When I plug the headset in and when the gnome "Select Audio Devices"
popup and select "Headset" (rather than Headphones), the sound doesn't
go through. But when I select "Headphones" it does. But I then need to
manually select the Headset mic in the sound settings to have my headset
working properly. This issue appear in 20.04. I didn't had this issue
before I upgrade from 19.10 (and previous releases).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pascal274918 F pulseaudio
 /dev/snd/pcmC0D0c:   pascal274918 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: Unity
Date: Thu Jun 11 19:50:11 2020
InstallationDate: Installed on 2019-05-14 (394 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Only some of outputs are working
Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago)
dmi.bios.date: 12/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 0NFGCT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530
dmi.product.sku: 087D
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1883197

Title:
  Headset not working

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I plug the headset in and when the gnome "Select Audio Devices"
  popup and select "Headset" (rather than Headphones), the sound doesn't
  go through. But when I select "Headphones" it does. But I then need to
  manually select the Headset mic in the sound settings to have my
  headset working properly. This issue appear in 20.04. I didn't had
  this issue before I upgrade from 19.10 (and previous releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal274918 F pulseaudio
   /dev/snd/pcmC0D0c:   pascal274918 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Thu Jun 11 19:50:11 2020
  InstallationDate: Installed on 2019-05-14 (394 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Only some of outputs are working
  Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0NFGCT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883197/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 490935]

2020-01-26 Thread Pascal-crb

I fully agree with ben.bucksch' comment: it is good practice to keep a trace of 
trace of what the original Subject line showed.
Sometimes I like to edit the email itself to add comments/annotations to make 
the content more (re-)usable for myself. In that case I explicitly indicate 
(eg. by 'keyword' like "_ANNOTATIONS") that this was an entry added after 
receiving the email.
This feature is not 'comfortably' provided by all my favorite mail-clients 
though ;-)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/490935

Title:
  it is not possible to modify email subject

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  Microsoft Outlook allows to modify "subject" of incoming emails. This is very 
very useful, especially when sender used a meaningless subject, or a simple 
dot. This feature should be very useful also in Thunderbird.
  Thanks a lot

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: c44b5fa992c605c204076ccbc3a738b7
  CheckboxSystem: b1865df84255b8716d3bcc269ff410d1
  Date: Tue Dec  1 18:36:54 2009
  DistroRelease: Ubuntu 9.10
  Package: mozilla-thunderbird (not installed)
  ProcEnviron:
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  SourcePackage: thunderbird
  Uname: Linux 2.6.31-15-generic i686

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-12-16 Thread Pascal Mons

Thank you Olivier for your effort and the information you provided me as
well.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder 
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM 
Worker",7584:"QuotaManager 
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM 
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver 
#2",7633:"StreamTrans #7",7646:"IndexedDB #2",7647:"StreamTrans 
#8",7648:"StreamTrans #9",7649:"StreamTrans #10",
  Throttleable: 1
  UptimeTS: 98.30915265
  Vendor: Mozilla
  Version: 71.0
  useragent_locale: en-US

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1672139]

2019-10-07 Thread Pascal-crb

Such "feature" of tracing the containing folder is felt by many to be an
almost trivial necessity for people managing their bookmarks ...

While waiting for the solution in Firefox..  I discovered "Pale Moon"
which offers this feature quite nicely ...

I don't know how to put an image in this window, hence I share this 
Dropbox-link for an illustration:
https://www.dropbox.com/s/iw3trcmmh44plr5/Bookmark%20Containing%20Folder%20%2B%20Patch.jpg?dl=0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1672139

Title:
  Add "Open Enclosing Folder" context menu to search results of
  bookmarks in the Library window (link to view/open containing folder,
  parent folder button)

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox is great. It has bookmarks.
  But it is impossible to open bookmark's folder in search results.

  Steps to reproduce:
  1. Open Firefox
  2. Open its Bookmark Manager ()
  3. Search for bookmark
  4. Try to find its folder with right-click menu.
  5. It is impossible to find bookmark's folder.

  Expected results:
  Firefox is mature, so it is expected that user can find bookmark's folder. 
For example Google Chrome has "Show in folder" menu option.

  Note: original bug was reported 8 years ago, but it is not fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 52.0+build2-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-110-generic.
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay8420 F pulseaudio
  BuildID: 20170303013352
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,10431507,00100100 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Channel: Unavailable
  Date: Sun Mar 12 13:59:45 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  IpRoute:
   default via 192.168.3.1 dev wlan3  proto static 
   169.254.0.0/16 dev wlan3  scope link  metric 1000 
   192.168.3.0/24 dev wlan3  proto kernel  scope link  src 192.168.3.6  metric 
2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
   [Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
   
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
   
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
  Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1836805] Re: screen frozen after reboot

2019-08-01 Thread Pascal Gicquel

Back to my computer

I applied step 2 as suggested and got :

whoopsie-id:
e3a8dbc9dbb2e9589754eb397d8ff19924a7bec147827c8e2333de7493dcd433a7cacae13de6185804843502331b4626bb6de5038cc1a182ec3b3aa4ed9c2130

which give the following line:
2019-07-18 07:072019-07-19 20:07 UTCCrash   xserver-xorg-core with 
the link: https://errors.ubuntu.com/oops/8d8b8168-aa67-11e9-b233-fa163e102db1

I will now try step 4 but have to reboot with wayland...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1836805

Title:
  screen frozen after reboot

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After I installed Ubuntu 19.04 (fresh install with hard drive
  erasing), I was able to login once just after install. But then after
  reboot, the screen freezes in the middle of the boot process and I
  never get the login banner.

  I was able to launch the recovery mode and get some information
  through journalctl command and it seems that the problem is related to
  a Wayland server crash. I don't really know if the problem comes from
  Wayland or Gnome. The first worrying error message is :
  "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission
  non accordée" (ie, Permission denied in french)

  Thanks to the recovery mode I was able to upgrade via "apt-get update"
  and "apt-get upgrade", but the symptoms were the same after a reboot

  I uncommented the "Enable=true" flag of the [debug] section of
  /etc/gdm3/custom.conf and I provide and extract of the journalctl
  output related to the error as an attachment to this report
  (journalctl_extract.txt part). I also provide some system information
  (system.txt pat).

  I hope this may help to solve the issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-07-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gdm3 3.32.0-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Tags:  disco
  Uname: Linux 5.0.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-07-18T07:25:10.575513

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1836805] Re: screen frozen after reboot

2019-07-18 Thread Pascal Gicquel

Generated the prevboot.txt (see attached). I did not find any file
related to wayland crash in /var/crash. I did find though an xorg crash
file dated from this morning. I sent it through ubuntu-bug though I was
not asked a bug number (I am not sure it worked). I do not really
understand what happened this morning as the xorg config ended up
working. I don't know if this new fact may help solving the issue or is
rather disturbing...

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+attachment/5277936/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1836805

Title:
  screen frozen after reboot

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After I installed Ubuntu 19.04 (fresh install with hard drive
  erasing), I was able to login once just after install. But then after
  reboot, the screen freezes in the middle of the boot process and I
  never get the login banner.

  I was able to launch the recovery mode and get some information
  through journalctl command and it seems that the problem is related to
  a Wayland server crash. I don't really know if the problem comes from
  Wayland or Gnome. The first worrying error message is :
  "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission
  non accordée" (ie, Permission denied in french)

  Thanks to the recovery mode I was able to upgrade via "apt-get update"
  and "apt-get upgrade", but the symptoms were the same after a reboot

  I uncommented the "Enable=true" flag of the [debug] section of
  /etc/gdm3/custom.conf and I provide and extract of the journalctl
  output related to the error as an attachment to this report
  (journalctl_extract.txt part). I also provide some system information
  (system.txt pat).

  I hope this may help to solve the issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-07-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gdm3 3.32.0-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Tags:  disco
  Uname: Linux 5.0.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-07-18T07:25:10.575513

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823053] [NEW] wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco

2019-04-03 Thread Pascal Ernster

Public bug reported:

Ubuntu 18.10 "Cosmic" and 19.04 "Disco" currently ship with both
wpasupplicant 2.6 and openssl/libssl 1.1.1, although upstream only
supports OpenSSL 1.1.1 starting with wpasupplicant 2.7.

OpenSSL 1.1.1 introduced support for TLS 1.3, and introduced new APIs to
configure the parameters governing TLS connections using TLS >= 1.3.
OpenSSL also decided that it would enable TLS 1.3 by default even for
software that had only been built for libssl <= 1.1.0 and hence couldn't
"know" about the new APIs. This leads to a situation where software that
was designed/built for OpenSSL 1.1.0 and TLS 1.2 will also offer TLS
1.3, without any possibility for end users to disable such behavior.

One case where this causes problems is wpasupplicant: wpasupplicant 2.7
officially introduced support for OpenSSL 1.1.1, which mainly consists
of disabling TLS 1.3 by default and adding a configuration flag allowing
end users to selectively enable it for connections when they see fit.
wpasupplicant 2.6, however, as shipped with Ubuntu 18.10 and 19.04, does
not offer such a possibility, and hence tries negotiating TLS 1.3
(alongside with older versions all the way down to TLS 1.0).

Sadly, there are RADIUS servers which suffer from TLS version
intolerance and will refuse authentication when the client offers TLS
1.3. I know of such a case with a German university's eduroam wifi, but
I doubt this is the only case where this causes problems. As a dirty
stopgap measure, I've installed the wpasupplicant 2.7 package from
Debian Buster (https://packages.debian.org/buster/wpasupplicant), and
I've asked the NOC at the affected university to upgrade/reconfigure
their RADIUS server to make the version intolerance go away - but still,
this is a bug that should be fixed in Ubuntu, preferably by backporting
wpasupplicant 2.7.

** Affects: wpa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: eap eduroam libssl openssl peap tls1.3 tlsv1.3 ttls wpa wpa-enterprise 
wpasupplicant

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1823053

Title:
  wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version
  intolerance on WPA2-Enterprise networks on Cosmic and Disco

Status in wpa package in Ubuntu:
  New

Bug description:
  Ubuntu 18.10 "Cosmic" and 19.04 "Disco" currently ship with both
  wpasupplicant 2.6 and openssl/libssl 1.1.1, although upstream only
  supports OpenSSL 1.1.1 starting with wpasupplicant 2.7.

  OpenSSL 1.1.1 introduced support for TLS 1.3, and introduced new APIs
  to configure the parameters governing TLS connections using TLS >=
  1.3. OpenSSL also decided that it would enable TLS 1.3 by default even
  for software that had only been built for libssl <= 1.1.0 and hence
  couldn't "know" about the new APIs. This leads to a situation where
  software that was designed/built for OpenSSL 1.1.0 and TLS 1.2 will
  also offer TLS 1.3, without any possibility for end users to disable
  such behavior.

  One case where this causes problems is wpasupplicant: wpasupplicant
  2.7 officially introduced support for OpenSSL 1.1.1, which mainly
  consists of disabling TLS 1.3 by default and adding a configuration
  flag allowing end users to selectively enable it for connections when
  they see fit. wpasupplicant 2.6, however, as shipped with Ubuntu 18.10
  and 19.04, does not offer such a possibility, and hence tries
  negotiating TLS 1.3 (alongside with older versions all the way down to
  TLS 1.0).

  Sadly, there are RADIUS servers which suffer from TLS version
  intolerance and will refuse authentication when the client offers TLS
  1.3. I know of such a case with a German university's eduroam wifi,
  but I doubt this is the only case where this causes problems. As a
  dirty stopgap measure, I've installed the wpasupplicant 2.7 package
  from Debian Buster (https://packages.debian.org/buster/wpasupplicant),
  and I've asked the NOC at the affected university to
  upgrade/reconfigure their RADIUS server to make the version
  intolerance go away - but still, this is a bug that should be fixed in
  Ubuntu, preferably by backporting wpasupplicant 2.7.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1814167] [NEW] package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter

2019-01-31 Thread Pascal Villaret

Public bug reported:

problem with ubuntu 16.04 on an external disk, read only. Then i used
grub-customizer. now i try to do again the updates.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: poppler-utils 0.41.0-0ubuntu1.11
ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 poppler-utils: Configure
 cups: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Jan 31 21:55:37 2019
ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  le 
réinstaller avant de tenter de le configurer.
InstallationDate: Installed on 2019-01-11 (20 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29ubuntu0.1
SourcePackage: poppler
Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: poppler (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1814167

Title:
  package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in poppler package in Ubuntu:
  New

Bug description:
  problem with ubuntu 16.04 on an external disk, read only. Then i used
  grub-customizer. now i try to do again the updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: poppler-utils 0.41.0-0ubuntu1.11
  ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   poppler-utils: Configure
   cups: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jan 31 21:55:37 2019
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2019-01-11 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: poppler
  Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1802674] Re: libgphoto2 builds lacks a link to the math library in all Ubuntu releases since at least Xenial 16.04

2018-11-11 Thread Pascal Mons

Well, my Launchpad PPA is currently back to fully working.

After rebuilding libgphoto2 2.5.16 (the Bionic 18.04 version) I found
another missing library link:

dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/
dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.16/konica_qm150.so 
contains an unresolvable reference to symbol exif_data_new_from_data: it's 
probably a plugin
dpkg-shlibdeps: warning: 1 similar warning has been skipped (use -v to see it)

That's the libexif library here missing in the build.

I did update anew my debian/rules files in my PPA, since I did a
backport of this version for Xenial 16.04.

A side note here is that the debian/rules file looks poorly maintained
by Debian.

They apparently add libraries link by editing the CFLAGS and CXXFLAGS
... Though there is dedicated commands to do so.

They missed as well a:

include /usr/share/dpkg/buildflags.mk

and the fully functional --parallel build with the right parameters.

tested with -j12 (processor cores) and working.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgphoto2 in Ubuntu.
https://bugs.launchpad.net/bugs/1802674

Title:
  libgphoto2 builds lacks a link to the math library in all Ubuntu
  releases since at least Xenial 16.04

Status in libgphoto2 package in Ubuntu:
  New

Bug description:
  Background:
  With all recent versions of GCC on GNU/Linux systems like Ubuntu, when you 
use the math library, you have to explicitly link to it.

  I am currently using Xenial 16.04 and did a recompile of source
  package libgphoto2. Then I got warnings fromdpkg-shlibdeps.

  make[1]: Entering directory 
'/home/ubuntu-xenial/user/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
  dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/ptp2.so contains 
an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v 
to see them all)
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/stv0680.so 
contains an unresolvable reference to symbol pow: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sonix.so contains 
an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/jl2005c.so 
contains an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/digigr8.so 
contains an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/mars.so contains 
an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sierra.so 
contains an unresolvable reference to symbol roundf: it's probably a plugin
  make[1]: Leaving directory 
'/home/ubuntu-xenial/user/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'

  I am quite sure that sqrt is the square root function from the math
  library. Usually, at least with GCC version newer than ~ 2013 you have
  to append a -lm to link against the math library. Obviously this isn't
  the case:

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. 
-I../libgphoto2_port -I../libgphoto2_port -D_GPHOTO2_INTERNAL_CODE 
-DLOCALEDIR=\"/usr/share/locale\" 
-DCAMLIBS=\"/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9\" -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/libexif -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wmissing-declarations -Wmissing-prototypes -c gphoto2-filesys.c  -fPIC -DPIC 
-o .libs/libgphoto2_la-gphoto2-filesys.o
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. 
-I../libgphoto2_port -I../libgphoto2_port -D_GPHOTO2_INTERNAL_CODE 
-DLOCALEDIR=\"/usr/share/locale\" 
-DCAMLIBS=\"/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9\" -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/libexif -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wmissing-declarations -Wmissing-prototypes -c gphoto2-filesys.c -fPIE -o 
libgphoto2_la-gphoto2-filesys.o >/dev/null 2>&1

  at the end we should see

  -c gphoto2-filesys.c -fPIE -lm -o libgphoto2_la-gphoto2-filesys.o
  >/dev/null 2>&1

  I did check in the official Ubuntu repository and you did get the same
  warnings:

  dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/jl2005c.so 
contains an unresolvable reference to symbol sqrt: it's probably a

[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

2018-08-13 Thread Pascal A.

Maybe an hint:
  - The first network icon has no sections horizontal bar UI-delimiters (e.g. 
between the 'Wifi' and 'Mobile broadband' sections)
  - The second network icon has those UI-delimiters

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1761606

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 18.04 ISO version: 20180404
  network-manager-applet version: 1.8.10-2ubuntu1
  After logging into my Wi-Fi network then logging out then logging back into 
the Live-USB session Two Wi-Fi network applets appeared where One would be the 
expected outcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  CurrentDesktop: LXDE
  Date: Thu Apr  5 21:06:24 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 
600
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  wifi  
1522962221  Thu Apr  5 21:03:41 2018  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/2  yes wlp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  472b45a7-c95b-3638-b452-3f6720688df8  ethernet  
1522961321  Thu Apr  5 20:48:41 2018  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1761606/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

2018-08-13 Thread Pascal A.

Also present on Lubuntu 18.04 (from a 16.04 upgrade, at least).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1761606

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 18.04 ISO version: 20180404
  network-manager-applet version: 1.8.10-2ubuntu1
  After logging into my Wi-Fi network then logging out then logging back into 
the Live-USB session Two Wi-Fi network applets appeared where One would be the 
expected outcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  CurrentDesktop: LXDE
  Date: Thu Apr  5 21:06:24 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 
600
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  wifi  
1522962221  Thu Apr  5 21:03:41 2018  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/2  yes wlp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  472b45a7-c95b-3638-b452-3f6720688df8  ethernet  
1522961321  Thu Apr  5 20:48:41 2018  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1761606/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

2018-07-09 Thread Pascal Peter

Hello,

I also confirm this bug on 2 computers with Kubuntu 16.04.

By selecting XRender as the rendering engine everything works.

-- 
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/1780664

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After rebooting, all the issues disappeared.

  For example I was once again able to left-click on the Firefox **three
  line/bar** menu and view the drop down list menu.  Also the KDE bottom
  menu bar retured to the normal "breeze" light grey colour.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

2018-06-08 Thread Pascal Bergeron

This is issue is still present in Ubuntu 18.04.

-- 
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/1553669

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1587906] WSJ Articles

2018-06-07 Thread Pascal Mons

*** This bug is a duplicate of bug 1521302 ***
https://bugs.launchpad.net/bugs/1521302

WSJ Articles


** Attachment added: "Wall Street Journal Articles.txt"
   
https://bugs.launchpad.net/bugs/1587906/+attachment/5149650/+files/Wall%20Street%20Journal%20Articles.txt

** Attachment added: "The Wall Street Journal - Articles.txt"
   
https://bugs.launchpad.net/bugs/1587906/+attachment/5149651/+files/The%20Wall%20Street%20Journal%20-%20Articles.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1587906

Title:
  GNOME Terminal 3.18.3 Xenial maximized windows does not return to its
  previous state when un-maximized

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  When a GNOME terminal is maximized then it is impossible to return to
  its initial size (UN-maximized), whatever the circumstances ...

  I have tried with tabs opened, without tabs, under different themes
  ...

  This is again very damaging to an Ubuntu LTS release, and this is the
  second GNOME 3.18.3 bug I report here in less than a week after
  installing Xenial 16.04. The previous one being gEdit.

  Will Ubuntu take care of these bugs ? As the typical answer from the
  GNOME team is that they have already moved to a newer release, so they
  won't provide any support on older versions ...

  The GNOME team appears to be highly unqualified to make stable
  releases of their software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 15:44:50 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-05-23 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587906/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1587906] Fw: Formulaire de retour (SRR-1823143)

2018-06-05 Thread Pascal Mons

*** This bug is a duplicate of bug 1521302 ***
https://bugs.launchpad.net/bugs/1521302

From: Garmin France 
Sent: Tuesday, June 5, 2018 3:27 PM
To: pascal_m...@hotmail.com
Subject: Formulaire de retour (SRR-1823143)

Cher Client,

Veuillez trouver ci-joint votre document concernant votre demande
d'intervention SRR-1823143

Merci de bien vouloir vérifier l’adresse mentionnée qui sera utilisée
pour le retour du produit (adresse, tel, code accès…)

ATTENTION : Seul le produit défectueux doit être retourné au SAV. N’oubliez pas 
la facture pour la prise sous garantie. Nos conditions générales de SAV sont 
disponibles sur :
http://www.garmin.com/fr/support/reparation/conditions-sav/

Pour toute demande d'informations complementaires, vous pouvez nous
contacter à l'adresse mail suivante : sav.fra...@garmin.com ou par
téléphone au 01 55 17 81 83 pour les revendeurs ou
support.fra...@garmin.com ou par téléphone au 01 55 69 33 99 pour les
particuliers

Vous pouvez ouvrir le document joint avec Adobe Acrobat V4 ou version
ultérieure en téléchargement gratuit sur http://www.adobe.com

Cordialement,

Garmin France SAS

http://www.garmin.com/fr

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole
use of the intended recipient(s) and contain information that may be
Garmin confidential and/or Garmin legally privileged. If you have
received this email in error, please notify the sender by reply email
and delete the message. Any disclosure, copying, distribution or use of
this communication (including attachments) by someone other than the
intended recipient is prohibited. Thank you.

** Attachment added: "SRR-1823143.pdf"

https://bugs.launchpad.net/bugs/1587906/+attachment/5148942/+files/SRR-1823143.pdf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1587906

Title:
  GNOME Terminal 3.18.3 Xenial maximized windows does not return to its
  previous state when un-maximized

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  When a GNOME terminal is maximized then it is impossible to return to
  its initial size (UN-maximized), whatever the circumstances ...

  I have tried with tabs opened, without tabs, under different themes
  ...

  This is again very damaging to an Ubuntu LTS release, and this is the
  second GNOME 3.18.3 bug I report here in less than a week after
  installing Xenial 16.04. The previous one being gEdit.

  Will Ubuntu take care of these bugs ? As the typical answer from the
  GNOME team is that they have already moved to a newer release, so they
  won't provide any support on older versions ...

  The GNOME team appears to be highly unqualified to make stable
  releases of their software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 15:44:50 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-05-23 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587906/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-04-26 Thread Pascal Morin

** Description changed:

  Dell XPS 13 9360 (CID 201606-22338)
- pre-installed image Xenial
+ pre-installed (oem) image Xenial
  
  [Description]
  
  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.
  
  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.
  
  We should use "-d" because bionic beaver has not been officially
  released yet.
  
  [Expected Result]
  
  The release update completed and I could start using Bionic instead of
  Xenial.
  
  [Actual Result]
  
  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.
  
  [1]
  
  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)
  
  *** Send problem report to the developers?
  
  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.
  
  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):
  
  .. (a lot of them)
  
   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.
  
  Upgrade complete
  
  The upgrade has completed but there were errors during the upgrade
  process.
  
  To continue please press [ENTER]
  
  ubuntu@201606-22338:~$
  
  ==
  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:
  
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (0 days ago)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-04-26 Thread Pascal Morin

** Changed in: oem-priority
 Assignee: (unassigned) => Chen-Han Hsiao (Stanley) (swem)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.net/bugs/1766890

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  New
Status in gnome-menus package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47

[Desktop-packages] [Bug 1587906] Guide et Comparatif des Balances Connectees

2018-04-02 Thread Pascal Mons

*** This bug is a duplicate of bug 1521302 ***
https://bugs.launchpad.net/bugs/1521302

Guide et Comparatif des Balances Connectees
___

https://www.objetconnecte.net/comparatifs/comparatif-balance-connectee/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1587906

Title:
  GNOME Terminal 3.18.3 Xenial maximized windows does not return to its
  previous state when un-maximized

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  When a GNOME terminal is maximized then it is impossible to return to
  its initial size (UN-maximized), whatever the circumstances ...

  I have tried with tabs opened, without tabs, under different themes
  ...

  This is again very damaging to an Ubuntu LTS release, and this is the
  second GNOME 3.18.3 bug I report here in less than a week after
  installing Xenial 16.04. The previous one being gEdit.

  Will Ubuntu take care of these bugs ? As the typical answer from the
  GNOME team is that they have already moved to a newer release, so they
  won't provide any support on older versions ...

  The GNOME team appears to be highly unqualified to make stable
  releases of their software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 15:44:50 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-05-23 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587906/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1711007] Re: Cannot print to HP printer

2017-08-16 Thread Pascal De Vuyst

Please provide output of
https://wiki.ubuntu.com/DebuggingPrintingProblems#Network_printer

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1711007

Title:
  Cannot print to HP printer

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Wireless connection was properly set up to enable wireless printing
  from my HP laptop to an HP Laser Jet Pro M12w. It worked for 2 weeks
  and stopped dead -- for no  reason.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Aug 15 21:31:56 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:8205]
  InstallationDate: Installed on 2017-07-18 (28 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=0c11b83b-a4fd-4737-b8c4-2969c5dd8ad7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8205
  dmi.board.vendor: HP
  dmi.board.version: 79.61
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd06/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8205:rvr79.61:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Tue Aug 15 10:43:59 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1711007] Re: Cannot print to HP printer

2017-08-16 Thread Pascal De Vuyst

https://wiki.ubuntu.com/DebuggingPrintingProblems#Network_printer

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1711007

Title:
  Cannot print to HP printer

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Wireless connection was properly set up to enable wireless printing
  from my HP laptop to an HP Laser Jet Pro M12w. It worked for 2 weeks
  and stopped dead -- for no  reason.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Aug 15 21:31:56 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:8205]
  InstallationDate: Installed on 2017-07-18 (28 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=0c11b83b-a4fd-4737-b8c4-2969c5dd8ad7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8205
  dmi.board.vendor: HP
  dmi.board.version: 79.61
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd06/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8205:rvr79.61:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Tue Aug 15 10:43:59 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1697789] Re: Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)

2017-06-23 Thread Pascal Wichmann

** Also affects: xorg-server (Arch Linux)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1697789

Title:
  Xorg: page allocation failure: order:0,
  mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE),
  nodemask=(null)

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Arch Linux:
  New

Bug description:
  dmesg:
  [23559.058500] Xorg: page allocation failure: order:0, 
mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)
  [23559.058509] Xorg cpuset=/ mems_allowed=0
  [23559.058516] CPU: 1 PID: 1797 Comm: Xorg Not tainted 
4.12.0-041200rc5-generic #201706112031
  [23559.058517] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 
530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013
  [23559.058519] Call Trace:
  [23559.058528]  dump_stack+0x63/0x8d
  [23559.058532]  warn_alloc+0x114/0x1c0
  [23559.058535]  __alloc_pages_slowpath+0xe07/0xe10
  [23559.058539]  __alloc_pages_nodemask+0x233/0x250
  [23559.058543]  alloc_pages_vma+0xab/0x250
  [23559.058547]  shmem_alloc_page+0x70/0xc0
  [23559.058550]  ? __radix_tree_insert+0x45/0x220
  [23559.058553]  ? __vm_enough_memory+0x29/0x130
  [23559.058555]  shmem_alloc_and_acct_page+0x72/0x1b0
  [23559.058558]  ? find_get_entry+0x1e/0xc0
  [23559.058561]  shmem_getpage_gfp+0x195/0xbd0
  [23559.058564]  shmem_read_mapping_page_gfp+0x44/0x80
  [23559.058611]  i915_gem_object_get_pages_gtt+0x204/0x5a0 [i915]
  [23559.058643]  i915_gem_object_get_pages+0x20/0x60 [i915]
  [23559.058673]  __i915_gem_object_get_pages+0x5c/0x70 [i915]
  [23559.058706]  __i915_vma_do_pin+0x1c6/0x3a0 [i915]
  [23559.058737]  i915_gem_execbuffer_reserve_vma.isra.29+0x14d/0x1b0 [i915]
  [23559.058765]  i915_gem_execbuffer_reserve.isra.30+0x3b7/0x3e0 [i915]
  [23559.058794]  i915_gem_do_execbuffer.isra.36+0x577/0x16c0 [i915]
  [23559.058799]  ? unix_stream_recvmsg+0x54/0x70
  [23559.058801]  ? unix_state_double_lock+0x70/0x70
  [23559.058830]  i915_gem_execbuffer2+0x96/0x1b0 [i915]
  [23559.058849]  drm_ioctl+0x216/0x4c0 [drm]
  [23559.058877]  ? i915_gem_execbuffer+0x2f0/0x2f0 [i915]
  [23559.058881]  ? __remove_hrtimer+0x3c/0x70
  [23559.058885]  do_vfs_ioctl+0xa3/0x600
  [23559.05]  ? do_setitimer+0xe0/0x240
  [23559.058891]  ? SyS_setitimer+0xf1/0x120
  [23559.058894]  SyS_ioctl+0x79/0x90
  [23559.058897]  entry_SYSCALL_64_fastpath+0x1e/0xa9
  [23559.058900] RIP: 0033:0x7fd8c5c7e987
  [23559.058901] RSP: 002b:7ffd494ac738 EFLAGS: 0246 ORIG_RAX: 
0010
  [23559.058904] RAX: ffda RBX: 0006 RCX: 
7fd8c5c7e987
  [23559.058905] RDX: 7ffd494ac790 RSI: 40406469 RDI: 
000c
  [23559.058907] RBP: 0028 R08: 0001 R09: 
000c
  [23559.058908] R10: 0001 R11: 0246 R12: 
0040
  [23559.058909] R13: 0008 R14: 5581c086a6c0 R15: 

  [23559.058912] Mem-Info:
  [23559.058918] active_anon:1016643 inactive_anon:298858 isolated_anon:0
  active_file:395940 inactive_file:1147459 isolated_file:0
  unevictable:129 dirty:124022 writeback:21146 unstable:0
  slab_reclaimable:57926 slab_unreclaimable:23062
  mapped:283483 shmem:248113 pagetables:23247 bounce:0
  free:29069 free_pcp:245 free_cma:0
  [23559.058923] Node 0 active_anon:4066572kB inactive_anon:1195432kB 
active_file:1583760kB inactive_file:4589836kB unevictable:516kB 
isolated(anon):0kB isolated(file):0kB mapped:1133932kB dirty:496088kB 
writeback:84584kB shmem:992452kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 
976896kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
  [23559.058924] Node 0 DMA free:15360kB min:84kB low:104kB high:124kB 
active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15984kB managed:15360kB mlocked:0kB 
slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB 
bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
  [23559.058930] lowmem_reserve[]: 0 3226 11726 11726 11726
  [23559.058935] Node 0 DMA32 free:52176kB min:18568kB low:23208kB high:27848kB 
active_anon:718716kB inactive_anon:177564kB active_file:228516kB 
inactive_file:2067540kB unevictable:0kB writepending:203112kB present:3438520kB 
managed:3354852kB mlocked:0kB slab_reclaimable:98764kB 
slab_unreclaimable:3004kB kernel_stack:576kB pagetables:4384kB bounce:0kB 
free_pcp:0kB local_pcp:0kB free_cma:0kB
  [23559.058941] lowmem_reserve[]: 0 0 8500 8500 8500
  [23559.058945] Node 0 Normal free:48740kB min:48924kB low:61152kB 
high:73380kB active_anon:3347648kB inactive_anon:1017448kB 
active_file:1354180kB inactive_file:2521736kB unevictable:516kB 
writepending:377444kB present:8902656kB

[Desktop-packages] [Bug 1637556] [NEW] package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to install/upgrade: package libavcodec-extra-54:amd64 is already installed and configured

2016-10-28 Thread Pascal CHOUCHEN

Public bug reported:

Tried to install EasyTag and pyRenamer

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-42-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
AptdaemonVersion: 1.1.1-1ubuntu5.2
Architecture: amd64
Date: Fri Oct 28 18:24:13 2016
DuplicateSignature: 
package:libavcodec-extra-54:amd64:6:9.18-0ubuntu0.14.04.1:package 
libavcodec-extra-54:amd64 is already installed and configured
ErrorMessage: package libavcodec-extra-54:amd64 is already installed and 
configured
InstallationDate: Installed on 2016-09-09 (49 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: libav
Title: package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to 
install/upgrade: package libavcodec-extra-54:amd64 is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libav (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed amd64 apport-package need-duplicate-check trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1637556

Title:
  package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to
  install/upgrade: package libavcodec-extra-54:amd64 is already
  installed and configured

Status in libav package in Ubuntu:
  New

Bug description:
  Tried to install EasyTag and pyRenamer

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Fri Oct 28 18:24:13 2016
  DuplicateSignature: 
package:libavcodec-extra-54:amd64:6:9.18-0ubuntu0.14.04.1:package 
libavcodec-extra-54:amd64 is already installed and configured
  ErrorMessage: package libavcodec-extra-54:amd64 is already installed and 
configured
  InstallationDate: Installed on 2016-09-09 (49 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: libav
  Title: package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to 
install/upgrade: package libavcodec-extra-54:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1597124] Re: typo in menu of system-config-printer v1.5.7

2016-07-21 Thread Pascal De Vuyst

Thanks for noticing.
system-config-printer translations are managed by launchpad, it is better to 
make your suggestion here: 
https://translations.launchpad.net/ubuntu/xenial/+source/system-config-printer/+pots/system-config-printer/de/+translate?batch=10=all=warteschlage

** Changed in: system-config-printer (Ubuntu)
   Status: New => Invalid

** Converted to question:
   
https://answers.launchpad.net/ubuntu/+source/system-config-printer/+question/299518

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1597124

Title:
  typo in menu of system-config-printer v1.5.7

Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  i'm using xubuntu 16.04 lts and system-config-printer v1.5.7 (in
  german language). i recognized a missing "n" (between "a" and "g")
  below the "drucker-menü".

  last line of options is: "Druckerwarteschlage anzeigenStrg+F"
  but it should be: "Druckerwarteschlange anzeigenStrg+F"

  please also check my screenshot.
  thx for fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1597124/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2016-06-06 Thread Pascal Garber

Same problem with DisplayLink as 4th Monitor, see #1589446

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1278223

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1589446] [NEW] Mouse Flickering after adding 4rd Monitor with DisplayLink

2016-06-06 Thread Pascal Garber

Public bug reported:

Same Bug linke #1278223?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Jun  6 12:08:26 2016
DistUpgraded: 2016-04-27 13:25:33,537 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2016-01-12 (145 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: ASUS All Series
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-27 (39 days ago)
dmi.bios.date: 08/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2108
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-G
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2108:bd08/11/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Apr 27 12:56:48 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   35217 
 vendor HSD
xserver.version: 2:1.17.2-1ubuntu9.1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug gnome3-ppa third-party-packages ubuntu xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1589446

Title:
  Mouse Flickering after adding 4rd Monitor with DisplayLink

Status in xorg package in Ubuntu:
  New

Bug description:
  Same Bug linke #1278223?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Jun  6 12:08:26 2016
  DistUpgraded: 2016-04-27 13:25:33,537 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2016-01-12 (145 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (39 days ago)
  dmi.bios.date: 08/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2108

[Desktop-packages] [Bug 1589150] [NEW] gEdit 3.18.3 in Xenial 16.04 Displays Wrong Outlined Colors of Bash Scripts

2016-06-04 Thread Pascal Mons

Public bug reported:

I used Bash Scripts in Trusty 14.04 which I write and edit in gEdit.

However when upgrading to Xenial 16.04 a few days ago I had a surprise
on the outlined colours displayed by the new gEdit 3.18.3. On a
particular instruction the text until the end is displayed in pink as if
there should be a Bash error. However there is no error in my Bash
script and gEdit 3.10 from Trusty 14.04 displayed it accordingly.

I attach the screen-shot of the portion of script which shows that the
Bash syntax is not properly checked in gEdit 3.18.3.

The problem is the use of a single quote (backslahed to avoid shell
interpretation). Obviously there should be no second single quote but
gEdit do color the script till the end in pink ... This is quite
appalling ...

SUBJECT="${SUBJECT//[\'\\]}"

Which aim is to remove any single quote from a string.

This is the second bug I found in gEdit in less than a week or so, and a
further proof of the unprofessional way of the GNOME Team for managing
their releases.

These 2 bugs are plain regressions from perfectly working capabilities
in previous versions.

Who will take care of this bug ?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun  4 22:14:49 2016
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2016-05-23 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

** Attachment added: "Portion of  Bash Script Displaying the gEdit 3.18.3 
Colouring Bug"
   
https://bugs.launchpad.net/bugs/1589150/+attachment/4677047/+files/gEdit%203.18.3%20Bash%20Script%20Display%20Bug.png

** Description changed:

  I used Bash Scripts in Trusty 14.04 which I write and edit in gEdit.
  
  However when upgrading to Xenial 16.04 a few days ago I had a surprise
  on the outlined colours displayed by the new gEdit 3.18.3. On a
  particular instruction the text until the end is displayed in pink as if
  there should be a Bash error. However there is no error in my Bash
  script and gEdit 3.10 from Trusty 14.04 displayed it accordingly.
  
  I attach the screen-shot of the portion of script which shows that the
  Bash syntax is not properly checked in gEdit 3.18.3.
  
  The problem is the use of a single quote (backslahed to avoid shell
  interpretation). Obviously there should be no second single quote but
  gEdit do color the script till the end in pink ... This is quite
  appalling ...
  
  SUBJECT="${SUBJECT//[\'\\]}"
  
  Which aim is to remove any single quote from a string.
  
  This is the second bug I found in gEdit in less than a week or so, and a
  further proof of the unprofessional way of the GNOME Team of managing
  their releases.
  
- These 2 bugs are plain regression from perfectly working capabilities in
- previous versions.
+ These 2 bugs are plain regressions from perfectly working capabilities
+ in previous versions.
  
  Who will take care of this bug ?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 22:14:49 2016
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2016-05-23 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  I used Bash Scripts in Trusty 14.04 which I write and edit in gEdit.
  
  However when upgrading to Xenial 16.04 a few days ago I had a surprise
  on the outlined colours displayed by the new gEdit 3.18.3. On a
  particular instruction the text until the end is displayed in pink as if
  there should be a Bash error. However there is no error in my Bash
  script and gEdit 3.10 from Trusty 14.04 displayed it accordingly.
  
  I attach the screen-shot of the portion of script which shows that the
  Bash syntax is not properly checked in gEdit 3.18.3.
  
  The problem is the use of a single quote (backslahed to avoid shell
  interpretation). Obviously there should be no second single quote but
  gEdit do color the script till the end in pink ... This is quite
  appalling ...
  
  SUBJECT="${SUBJECT//[\'\\]}"
  
  Which aim is to remove any single quote from a string.
  
  This is the second bug I found in gEdit in less than a week or so, and a
- further proof of the unprofessional way of the GNOME Team of managing
+ further proof of the unprofessional way of the GNOME Team

[Desktop-packages] [Bug 1587906] [NEW] GNOME Terminal 3.18.3 Xenial maximized windows does not return to its previous state when un-maximized

2016-06-01 Thread Pascal Mons

Public bug reported:

When a GNOME terminal is maximized then it is impossible to return to
its initial size (UN-maximized), whatever the circumstances ...

I have tried with tabs opened, without tabs, under different themes ...

This is again very damaging to an Ubuntu LTS release, and this is the
second GNOME 3.18.3 bug I report here in less than a week after
installing Xenial 16.04. The previous one being gEdit.

Will Ubuntu take care of these bugs ? As the typical answer from the
GNOME team is that they have already moved to a newer release, so they
won't provide any support on older versions ...

The GNOME team appears to be highly unqualified to make stable releases
of their software.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun  1 15:44:50 2016
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2016-05-23 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1587906

Title:
  GNOME Terminal 3.18.3 Xenial maximized windows does not return to its
  previous state when un-maximized

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When a GNOME terminal is maximized then it is impossible to return to
  its initial size (UN-maximized), whatever the circumstances ...

  I have tried with tabs opened, without tabs, under different themes
  ...

  This is again very damaging to an Ubuntu LTS release, and this is the
  second GNOME 3.18.3 bug I report here in less than a week after
  installing Xenial 16.04. The previous one being gEdit.

  Will Ubuntu take care of these bugs ? As the typical answer from the
  GNOME team is that they have already moved to a newer release, so they
  won't provide any support on older versions ...

  The GNOME team appears to be highly unqualified to make stable
  releases of their software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 15:44:50 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-05-23 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587906/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1587090] [NEW] gEdit 3.18.3 in Xenial 16.04 Print Menu capabilities are broken

2016-05-30 Thread Pascal Mons

Public bug reported:

I just upgraded from Trusty 14.04 and had the surprise to see the newer
version of gEdit 3.18 with a broken Print Menu.

First, previously the print menu was accessible from gEdit window
control bar alongside the opened file folders. No more, the print menu
is only accessible from the global menu. The window control bar has 3
times the height from the previous version I used (3.10) and with less
accessible information, as Open, +, and Save are now on a bar of their
own. Why the GNOME guys at each new release feel like they need to re-
invent the wheel ? And occasionally broke previously working features
...

Then when trying to print some text pages I realized that my pages were
printed with excessive margins on all side. That was never the case
before either in Trusty or Precise.

I later tried to configure the margins ... Well there is no margins
configuration available to speak off. But the capability appears on the
Paper Size --> Manage Custom Sizes --> Paper Margin ... I should mention
here that I previously changed the Default Paper Size from U.S. Letter
to A4. Then opening the 'Manage Custom Size' I was expecting the A4
Paper Size listed in the pop-window field Paper Size, but still I got
the U.S. Letter paper size ...

gEdit will provide a name 'Custom Size 1' as the pop-up open. I changed
the margins from 0.25 inch to 0.1 and changed the default name to 'A4
Small Margin' and typing the inches size of A4 instead of the listed
inches size for U.S. Letter. However to no avail, as when closing the
pop-up window the name reverts back to 'Custom Size 1'.

Then using this setting to print a text page wouldn't change anything on
the printed margins ... Using the 'Margins from printer' --> in my case
KONICA-MINOLTA magicolor 1650 EN (which are set at 0.17 inches) wouldn't
change anything either.

The default paper size change (from U.S. Letter to A4) is not set until
you actually print a page ... And there is no option to change inches to
cm ...

When the GNOME team will stop breaking previously perfectly working
application ?

May be when I have time I will provide a scan of before / after update
to Xenial 16.04. I consider this a damaging regression. Previously we
had from the GNOME team a 'blurry' font bug in gEdit 3.10, however
hopefully someone (not part of the GNOME) provided a patch.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May 30 16:12:20 2016
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2016-05-23 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1587090

Title:
  gEdit 3.18.3 in Xenial 16.04 Print Menu capabilities are broken

Status in gedit package in Ubuntu:
  New

Bug description:
  I just upgraded from Trusty 14.04 and had the surprise to see the
  newer version of gEdit 3.18 with a broken Print Menu.

  First, previously the print menu was accessible from gEdit window
  control bar alongside the opened file folders. No more, the print menu
  is only accessible from the global menu. The window control bar has 3
  times the height from the previous version I used (3.10) and with less
  accessible information, as Open, +, and Save are now on a bar of their
  own. Why the GNOME guys at each new release feel like they need to re-
  invent the wheel ? And occasionally broke previously working features
  ...

  Then when trying to print some text pages I realized that my pages
  were printed with excessive margins on all side. That was never the
  case before either in Trusty or Precise.

  I later tried to configure the margins ... Well there is no margins
  configuration available to speak off. But the capability appears on
  the Paper Size --> Manage Custom Sizes --> Paper Margin ... I should
  mention here that I previously changed the Default Paper Size from
  U.S. Letter to A4. Then opening the 'Manage Custom Size' I was
  expecting the A4 Paper Size listed in the pop-window field Paper Size,
  but still I got the U.S. Letter paper size ...

  gEdit will provide a name 'Custom Size 1' as the pop-up open. I
  changed the margins from 0.25 inch to 0.1 and changed the default name
  to 'A4 Small Margin' and typing the inches size of A4 instead of the
  listed inches size for U.S. Letter. However to no avail, as when
  closing the pop-up window the name reverts back to 'Custom Size 1'.

  Then using this setting to print a text page wouldn't change anything

[Desktop-packages] [Bug 1571574] Re: [SRU] 3G (WWAN) icon missing

2016-05-27 Thread Pascal Morin

** Changed in: network-manager-applet (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: network-manager-applet (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  [SRU] 3G (WWAN) icon missing

Status in Network Manager Applet:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  In this report we are trying to address several issues network-
  manager-applet 1.2.0-0ubuntu0.16.04.1 suffers by doing cherry-picks
  from upstream 1.2 stable branch.

  By using a 3G WWAN dongle, after establishing a 3G connection, the
  icon shown in system tray should be a 3G indicator to indicate that 3G
  is connected. However, in Xenial there is no 3G icon at all. After 3G
  connection is established, it remains as the previous icon displayed.

  [Test Case]

  By upgrading to the -proposed package, the icon shown in system tray should 
be a 3G indicator to indicate that 3G is connected when using WWAN.
   
  [Regression Potential]

  This update also includes patches targeting other issues which are not
  related to this bug directly, but all these fix are clear and have
  minimum changes, chance of regression is limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1571574] Re: [SRU] 3G (WWAN) icon missing

2016-05-27 Thread Pascal Morin

** Changed in: network-manager-applet (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: network-manager-applet (Ubuntu Xenial)
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  [SRU] 3G (WWAN) icon missing

Status in Network Manager Applet:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-applet source package in Xenial:
  Confirmed

Bug description:
  [Impact]

  In this report we are trying to address several issues network-
  manager-applet 1.2.0-0ubuntu0.16.04.1 suffers by doing cherry-picks
  from upstream 1.2 stable branch.

  By using a 3G WWAN dongle, after establishing a 3G connection, the
  icon shown in system tray should be a 3G indicator to indicate that 3G
  is connected. However, in Xenial there is no 3G icon at all. After 3G
  connection is established, it remains as the previous icon displayed.

  [Test Case]

  By upgrading to the -proposed package, the icon shown in system tray should 
be a 3G indicator to indicate that 3G is connected when using WWAN.
   
  [Regression Potential]

  This update also includes patches targeting other issues which are not
  related to this bug directly, but all these fix are clear and have
  minimum changes, chance of regression is limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1571574] Re: [SRU] 3G (WWAN) icon missing

2016-05-26 Thread Pascal Morin

Here is possibly (maybe) the reason (feedback from Franz):

applet-device-wifi.c: (used for WIFI to create icon)

1480 case NM_DEVICE_STATE_ACTIVATED:
1481 strength = ap ? nm_access_point_get_strength (ap) : 0;
1482 strength = MIN (strength, 100);
1483
1484 *out_icon_name = mobile_helper_get_quality_icon_name 
(strength);
1485
1486 if (ap) {
1487 char *ssid = get

  mobile_helper_get_icon.c (used for WWAN to create icon)

613 case NM_DEVICE_STATE_ACTIVATED:
614 *out_pixbuf = mobile_helper_get_status_pixbuf (quality,
615
quality_valid,
616mb_state,
617mb_tech,
618applet);
619 *out_icon_name = mobile_helper_get_quality_icon_name 
(quality_valid ?
620   
quality : 0);

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  [SRU] 3G (WWAN) icon missing

Status in Network Manager Applet:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  In this report we are trying to address several issues network-
  manager-applet 1.2.0-0ubuntu0.16.04.1 suffers by doing cherry-picks
  from upstream 1.2 stable branch.

  By using a 3G WWAN dongle, after establishing a 3G connection, the
  icon shown in system tray should be a 3G indicator to indicate that 3G
  is connected. However, in Xenial there is no 3G icon at all. After 3G
  connection is established, it remains as the previous icon displayed.

  [Test Case]

  By upgrading to the -proposed package, the icon shown in system tray should 
be a 3G indicator to indicate that 3G is connected when using WWAN.
   
  [Regression Potential]

  This update also includes patches targeting other issues which are not
  related to this bug directly, but all these fix are clear and have
  minimum changes, chance of regression is limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1571574] Re: 3G (WWAN) icon missing in network-manager-applet

2016-05-20 Thread Pascal Morin

@Sebastien

The last known working network-manger-applet/gnome version for Xenial is
1.0.10-1ubuntu1   https://bugs.launchpad.net/somerville/ford-
constantine/+bug/1571479/comments/6

it used to work fine on Xenial daily builds built before 3/29.

It looks like to be a regression.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  3G (WWAN) icon missing in network-manager-applet

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Incomplete
Status in network-manager-applet source package in Xenial:
  Incomplete

Bug description:
  After establishing a 3G connection, the icon shown in system tray
  should be a 3G indicator to indicate that 3G is connected.

  However, in Xenial there is no 3G icon at all.
  After 3G connection is established, it remains as the previous icon displayed.
  (e.g. 
  If no other connection was established before 3G connection was made, then 
the icon is a "hollow fan shape" after connecting to 3G.
  If wifi was connected before 3G connection was made, then the icon after 3G 
connection shows a wifi icon.)

  network-manager: 1.1.93-0ubuntu3
  OS: Xenial daily (2016 Apr. 15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1571574] Re: 3G (WWAN) icon missing in network-manager-applet

2016-05-19 Thread Pascal Morin

@Sebastien & Aron

The syslog is now included; Can we get a resolution very soon; It is
urgent issue for Dell. If you want more background please let me know by
email or on irc.

Thx.

Pascal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  3G (WWAN) icon missing in network-manager-applet

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Incomplete
Status in network-manager-applet source package in Xenial:
  Incomplete

Bug description:
  After establishing a 3G connection, the icon shown in system tray
  should be a 3G indicator to indicate that 3G is connected.

  However, in Xenial there is no 3G icon at all.
  After 3G connection is established, it remains as the previous icon displayed.
  (e.g. 
  If no other connection was established before 3G connection was made, then 
the icon is a "hollow fan shape" after connecting to 3G.
  If wifi was connected before 3G connection was made, then the icon after 3G 
connection shows a wifi icon.)

  network-manager: 1.1.93-0ubuntu3
  OS: Xenial daily (2016 Apr. 15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1571574] Re: 3G (WWAN) icon missing in network-manager-applet

2016-05-19 Thread Pascal Morin

** Summary changed:

- 3G icon missing in network-manager-applet
+ 3G (WWAN) icon missing in network-manager-applet

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  3G (WWAN) icon missing in network-manager-applet

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-applet source package in Xenial:
  Confirmed

Bug description:
  After establishing a 3G connection, the icon shown in system tray
  should be a 3G indicator to indicate that 3G is connected.

  However, in Xenial there is no 3G icon at all.
  After 3G connection is established, it remains as the previous icon displayed.
  (e.g. 
  If no other connection was established before 3G connection was made, then 
the icon is a "hollow fan shape" after connecting to 3G.
  If wifi was connected before 3G connection was made, then the icon after 3G 
connection shows a wifi icon.)

  network-manager: 1.1.93-0ubuntu3
  OS: Xenial daily (2016 Apr. 15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1571574] Re: 3G icon missing in network-manager-applet

2016-05-18 Thread Pascal Morin

** Changed in: network-manager-applet (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  3G icon missing in network-manager-applet

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-applet source package in Xenial:
  Confirmed

Bug description:
  After establishing a 3G connection, the icon shown in system tray
  should be a 3G indicator to indicate that 3G is connected.

  However, in Xenial there is no 3G icon at all.
  After 3G connection is established, it remains as the previous icon displayed.
  (e.g. 
  If no other connection was established before 3G connection was made, then 
the icon is a "hollow fan shape" after connecting to 3G.
  If wifi was connected before 3G connection was made, then the icon after 3G 
connection shows a wifi icon.)

  network-manager: 1.1.93-0ubuntu3
  OS: Xenial daily (2016 Apr. 15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1577049] Re: The switch user featue has disapeared from indicator applet since upgrade from 15.10 to 16.04

2016-05-01 Thread Pascal S

As additional information, this bug has been noticed in the forum for
the development version here :

http://ubuntuforums.org/showthread.php?t=2309544

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1577049

Title:
  The switch user featue has disapeared from indicator applet since
  upgrade from 15.10 to 16.04

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  Before upgrade to 16.04, I could select "change (or switch) user" from
  the indicator applet (on the top right of the screen in gnome-shell).
  Since 16.04, this option has vanished, only "close session" and
  "account parameters" are present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1577049/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1577049] [NEW] The switch user featue has disapeared from indicator applet since upgrade from 15.10 to 16.04

2016-04-30 Thread Pascal S

Public bug reported:

Before upgrade to 16.04, I could select "change (or switch) user" from
the indicator applet (on the top right of the screen in gnome-shell).
Since 16.04, this option has vanished, only "close session" and "account
parameters" are present.

** Affects: gnome-panel (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1577049

Title:
  The switch user featue has disapeared from indicator applet since
  upgrade from 15.10 to 16.04

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  Before upgrade to 16.04, I could select "change (or switch) user" from
  the indicator applet (on the top right of the screen in gnome-shell).
  Since 16.04, this option has vanished, only "close session" and
  "account parameters" are present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1577049/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1529458] Re: ubuntu 14.04: Epson Stylus Photo 2100 "missing print filter"

2016-01-16 Thread Pascal De Vuyst

** Changed in: gutenprint (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gutenprint in Ubuntu.
https://bugs.launchpad.net/bugs/1529458

Title:
  ubuntu 14.04: Epson Stylus Photo 2100 "missing print filter"

Status in gutenprint package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 on a Dell precision T3400 64bit.

  lsb_release -rd:
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  apt-cache policy cups
  cups:
Installert: 1.7.2-0ubuntu1.7
Kandidat:   1.7.2-0ubuntu1.7
Versjonstabell:
   *** 1.7.2-0ubuntu1.7 0
  500 http://no.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  
  Since I upgraded from 12.04 to 14.04 this printer has not worked well.  
Sometimes it prints after repeatedly pressing the paper feed button.  I often 
get the error message: "missing print filter".  I have had the printer for 
approx. 10 years, and it worked well before 14.04.

  I have tested on a windows 7 laptop and on a mac.  Both work well.

  Conclusion: printer is working.  Someting has happened to cups or the
  cups driver for this printer.

  I have tried the Open Printing user forum and only gotten a report
  from someone with the same problem

  I attach the error log (/var/log/cups/error_log)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1416897] Re: static image of desktop and windows displayed instead of lockscreen

2016-01-14 Thread Pascal Opitz

Same behaviour in 15.10

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1416897

Title:
  static image of desktop and windows displayed instead of lockscreen

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-on from bug 1375271(
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though
  it may actually implicate a different underlying problem.

  .

  Expectation --

  Given any one of the following actions:
   - (from active desktop session) choosing "lock" from the Unity Panel power 
menu;
   - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
  - (from suspend) initiating a resume,

  ...the expected result is to display an interactive lockscreen where
  the active user's password can be entered to access the session. On
  this particular machine, which is a touch hybrid, the lockscreen also
  includes the Onboard soft keyboard.

  .

  Observed behavior --

  Instead of the lockscreen, each of these actions triggers the machine
  to display an image of the desktop/window session as it had been near
  the time of the lock or suspend.  The cursor is visible and can be
  moved.  The Unity Panel and Launcher usually appear as normal,
  although sometimes they are missing.

  Nothing happens when the user attempts to interact with the visible
  session by mouse or keyboard input.  Keyboard input will actually be
  fed to the lockscreen's password entry window, however.  So blindly
  typing the password from the zombie GUI session image -- and then
  pressing "enter" -- will bring up an active, working session.

  TTY session logins are available by the keyboard shortcuts ctrl-
  alt-F[number].  After pulling up one of these login screens (without
  actually logging in), then returning with ctrl-alt-F7, the lockscreen
  appears as expected.

  .

  Regression timeframe:

  I believe this behavior began sometime during January 2015.

  .

  Replication:

  This unexpected behavior takes place almost every time one of the
  listed actions is taken.  During one period of testing on 2015-01-31,
  the bug disappeared for a few rounds of lock and unlock. However, it
  re-appeared shortly thereafter (I believe after the next restart or
  suspend-resume).

  .

  Video attachment:

  A 1-minute video (.webm, no audio) is attached showing one form of
  this bug (simple lock-unlock).  The main feed was taken from a
  smartphone, but the video also includes an inset of what
  SimpleScreenRecorder (SSR) "saw" during the process.

  On "lock", the actual screen became fully black. SSR, by contrast, recorded a 
black screen that included a clock in the top-right.
  On mouse movement, the actual screen displayed the static image of the 
GUI/desktop session. SSR, by contrast, recorded a delayed but normal lockscreen 
appearing.

  .

  Security tag reasoning:

  This bug displays a snapshot of recent  screen contents from a user's
  GUI session even when the user has (actively or indirectly) locked the
  session.  It also prevents a user from turning on the screen to
  command a user switch, go into TTY, etc. without displaying an image
  of her private GUI session.

  .

  Current graphics-related system info:

  OEM: HP Envy x360 15t (convertible hybrid notebook)
  CPU/GPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz | Intel HD Graphics 4400
  OpenGL Core Profile version: 3.3 Mesa 10.5.0-devel
  OpenGL Extensions version: 3.0 Mesa 10.5.0-devel
  OS: Ubuntu 14.10 64-bit
  Kernel: 3.16.0-29 generic
  X Server: xorg-server 2:1.16.1.901-1ubuntu1~utopic1
  Pixman version: 0.32.4
  Compiz version: 0.9.12

  Please let me know if there is further config information that would
  be helpful.

  .

  Upstream testing:

  This is a production machine. I am willing to test pre-release
  packages provided the testing configurations are easy to revert (such
  as upstream kernels).  I have been burned in the past with broken
  package systems and protracted  config repairs after testing
  experimental graphics and video driver software. But I would still be
  willing give it a shot if there is a simple and reliable process to
  roll back the changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1416897/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1517116] Re: A3 printer is only printing A4's worth of image

In order to determine whether the problem is caused by the application
or by the printing subsystem please provide
https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1517116

Title:
  A3 printer is only printing A4's worth of image

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  There is a long-standing bug in CUPS or one of its drivers (PPD
  files?) or components (GS?) whereby if you try to print using a
  printer capable of A3 (mine are HP K7100 and HP K8600) you always get
  just an A4-shaped image in the top left corner of the sheet, with the
  rest of the image cut off unprinted (see links to examples below).
  This also applies when you try to print an A4 document scaled up
  ("scale to fit").

  This happens in Okular, Evince, qpdfview, and even Adobe Reader 9, on
  all Xubuntu releases since at least 12.10 running stock unmodified
  CUPS as installed by the system. It continues to happen even if I
  install HPLIP (any version, currently 3.15.2)

  This may possibly be related to Bug #357732 ("cups always prints with
  the default page size") but it is NOT the same bug because it also
  occurs if I reconfigure the printer to be an A3 default paper size.
  Weirdly, CUPS' test print does print correctly full-page A3.

  I have seen -- once only -- a colleague print on my printers and NOT
  getting this cropped output, and he was printing from a Mac (also of
  course running CUPS) but I need to gain access to a Mac and identify
  the PPD file it's using and report back.

  To avoid any misunderstanding, this is a photo of an A4 document printed on 
A3 paper set to "scale to fit" (enlarged):
  http://oimelc.ucc.ie/a4-document-printed-enlarged-on-a3-paper.jpg
  And this is the same document printed at normal size on A4 paper:
  http://oimelc.ucc.ie/a4-document-printed-normalsize-on-a4-paper.jpg

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1508931] Re: printer is not responding

Please describe your problem/printer setup in more detail and provide
your https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS_error_log

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1508931

Title:
  printer is not responding

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I am not able to use the printer connected by the server

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.6
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 22 15:19:53 2015
  KernLog:
   
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 SFF
  Papersize: letter
  PpdFiles: Printomat: Ricoh Aficio MP C2800 PXL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=f3918aff-93ef-4311-a489-da0eff87a33c ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.65
  dmi.board.asset.tag: CZC5382971
  dmi.board.name: 1998
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC5382971
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.65:bd07/13/2015:svnHewlett-Packard:pnHPEliteDesk800G1SFF:pvr:rvnHewlett-Packard:rn1998:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP EliteDesk 800 G1 SFF
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1510162] Re: Brother Scanner (MFC-465CN) no longer works

Have a look here: http://askubuntu.com/questions/461487/install-brother-
mfc-465cn-as-a-network-scanner

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1510162

Title:
  Brother Scanner (MFC-465CN) no longer works

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Upgrade from 64 bit 15.04 to 64 bit 15.10...  Brother scanner (MFC-465CN) has 
worked since it I bought it (Ubuntu 8.04).  Sometime you have to jump through 
some hoops but I have always made it work.  
  I have now tried everything, uninstalled and reinstalled 
brscan2-0.2.5-1.amd64.deb, brscan-skey-0.2.4-1.amd64.deb and 
brother-udev-rule-type1-1.0.0-1.all.deb.  Also, updated the rules manually and 
applied permission changes manually.  NOTHING!
  Something is broken!!!
  GTH

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1451183] Re: printing job (multiple-page PDF) stops half way, status stays 'processing'

Please provide
https://wiki.ubuntu.com/DebuggingPrintingProblems#USB_printer_does_not_print_or_prints_garbage

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1451183

Title:
  printing job (multiple-page PDF) stops half way, status stays
  'processing'

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  When printing a multiple-file pdf page sent from Adobe PDF Reader
  (other situations not tested), a printing job starts as normal, but
  gets stuck after one or 1,5 page. Both CUPS and the printer display
  say 'processing', the page gets stuck wherever the printer stopped
  printing.

  Curious thing: after a full reboot (Shut Down... -> Restart), the
  printer starts the job again, then (often) does finish it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May  3 14:17:20 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-10 (326 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for HP-Photosmart-2570-series: 
hp:/usb/Photosmart_2570_series?serial=MY722312F404DY
  MachineType: ECS G43T-3L
  Papersize: a4
  PpdFiles: HP-Photosmart-2570-series: HP Photosmart 2570 Series, hpcups 3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G43T-3L
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd04/10/2009:svnECS:pnG43T-3L:pvr1.0:rvnECS:rnG43T-3L:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.name: G43T-3L
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1529458] Re: ubuntu 14.04: Epson Stylus Photo 2100 "missing print filter"

In Ubuntu 15.10 please provide your
https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS_error_log and
https://wiki.ubuntu.com/DebuggingPrintingProblems#USB_printer_does_not_print_or_prints_garbage

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gutenprint in Ubuntu.
https://bugs.launchpad.net/bugs/1529458

Title:
ubuntu 14.04: Epson Stylus Photo 2100 "missing print filter"

Status in gutenprint package in Ubuntu:
Incomplete

Bug description:
Ubuntu 14.04 on a Dell precision T3400 64bit.

lsb_release -rd:
Description: Ubuntu 14.04.3 LTS
Release: 14.04

apt-cache policy cups
cups:
Installert: 1.7.2-0ubuntu1.7
Kandidat: 1.7.2-0ubuntu1.7
Versjonstabell:
*** 1.7.2-0ubuntu1.7 0
500 http://no.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
100 /var/lib/dpkg/status
1.7.2-0ubuntu1 0
500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

Since I upgraded from 12.04 to 14.04 this printer has not worked well.
Sometimes it prints after repeatedly pressing the paper feed button. I often
get the error message: "missing print filter". I have had the printer for
approx. 10 years, and it worked well before 14.04.

I have tested on a windows 7 laptop and on a mac. Both work well.

Conclusion: printer is working. Someting has happened to cups or the
cups driver for this printer.

I have tried the Open Printing user forum and only gotten a report
from someone with the same problem

I attach the error log (/var/log/cups/error_log)

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

[Desktop-packages] [Bug 1409153] Re: printer not working

This printer uses a proprietary closed source printer driver, have a
look here: https://help.ubuntu.com/community/CanonCaptDrv190

** Changed in: cups (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1409153

Title:
  printer not working

Status in cups package in Ubuntu:
  Invalid

Bug description:
  I am using Canon Laser printer LBP6000. I tried installing the printer
  drivers as described in forum and it worked only once. Once the USB
  port is unplugged or system restarted it stopped working.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Jan  9 17:32:33 2015
  InstallationDate: Installed on 2013-05-10 (609 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Lpstat:
   device for Brother-MFC-J470DW: dnssd://Brother%20MFC-J470DW._ipp._tcp.local/
   device for LBP6000: ccp://localhost:59687
   device for LBP6000-LBP6018: usb://Canon/LBP6000/LBP6018?serial=B2D78FLg
  MachineType: HP Pavilion 061 RN638AA-ABA m7658n
  Papersize: letter
  PpdFiles:
   Brother-MFC-J470DW: Brother MFC-J470DW CUPS
   LBP6000: Canon LBP6000/LBP6018 CAPT (US)
   LBP6000-LBP6018: Canon LBP6000/LBP6018 CAPT (US)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to trusty on 2014-08-22 (140 days ago)
  dmi.bios.date: 09/15/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 3.17
  dmi.board.name: LEUCITE
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 2.00
  dmi.chassis.type: 3
  dmi.chassis.version: 
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr3.17:bd09/15/2006:svnHPPavilion061:pnRN638AA-ABAm7658n:pvr0nx1114RE101LEUCI00:rvnASUSTekComputerINC.:rnLEUCITE:rvr2.00:cvn:ct3:cvr:
  dmi.product.name: RN638AA-ABA m7658n
  dmi.product.version: 0nx1114RE101LEUCI00
  dmi.sys.vendor: HP Pavilion 061
  mtime.conffile..etc.cups.cupsd.conf: 2014-05-28T23:59:31.487145

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1529881] Re: CUPS 1.7.2 distorts colors on Canon PIXMA MG5250

The official drivers for this printer are part proprietary and closed
source, therefore we cannot/are not allowed to include them into Ubuntu.

The gutenprint opensource driver included in Ubuntu is EXPERIMENTAL
because reverse engineering needs to be done, there is already an
upstream report about this http://sourceforge.net/p/gimp-print/bugs/688/

Actually your printer manufacturer needs to provide a openprinting distribution 
independent driver package as described here: 
http://www.linux-foundation.org/en/OpenPrinting/WritingAndPackagingPrinterDrivers
This would allow automatic download and installation of the manufacturers 
printer driver by system-config-printer as already implemented by this 
specification: 
https://blueprints.launchpad.net/ubuntu/+spec/printerdriverautodownload since 
Ubuntu Intrepid.
As mentioned the system-config-printer part is implemented.
You should ask your manufacturer in this case Canon to provide a distibution 
independent package that allows their printer driver to be installed 
automatically on Linux in general (not only Ubuntu).


** Package changed: cups (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1529881

Title:
  CUPS 1.7.2 distorts colors on Canon PIXMA MG5250

Status in gutenprint package in Ubuntu:
  Incomplete

Bug description:
  1)

  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  2)
  apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.7
Candidate: 1.7.2-0ubuntu1.7
Version table:
   *** 1.7.2-0ubuntu1.7 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

  3)
  print colors accurately

  4)
  colors are distorted (not a printer problem, because copying and scanning 
works accurately)

  Original USB open-source printer driver (cnijfilter-
  mg5200series-3.40-1) works, after installing
  libtiff4_3.9.6-9ubuntu1.2_i386:

  see
  
http://www.canon.de/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg5250.aspx?type=drivers==Linux%20%2832-bit%29)

  The current driver in CUPS 1.7.2 distorts the colors (turning black
  into red, blue into red etc.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Tue Dec 29 15:22:47 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-23 (36 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lpstat: device for MG5200USB: cnijusb:/dev/usb/lp1
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  Papersize: a4
  PpdFiles: MG5200USB: Canon MG5200 series Ver.3.40
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic 
root=UUID=77b44b32-8187-4e4e-9ef0-8003061826a2 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01KY.M008.20100430.RHU
  dmi.board.asset.tag: SAMSUNG
  dmi.board.name: N150P/N210P/N220P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: N150P/N210P/N220P
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1334446] Re: Installing printer driver via control panel hangs

Thanks!

** Changed in: system-config-printer (Ubuntu)
   Status: Confirmed => Fix Released

** Package changed: system-config-printer (Fedora) => system-config-
printer

** Changed in: system-config-printer
   Importance: Unknown => Undecided

** Changed in: system-config-printer
   Status: Unknown => New

** Changed in: system-config-printer
 Remote watch: Red Hat Bugzilla #1052203 => None

** Changed in: system-config-printer
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1334446

Title:
  Installing printer driver via control panel hangs

Status in System Config Printer:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Trying to add a printer via system settings.
  Got to a messagebox that said "Installing driver openprinting-gutenprint.  
Installing..."
  and then hung at 50% progress.

  ps shows that dpkg and dpkg-preconfigure terminated, but no parent
  reaped them:

  dank 16336  0.6  0.9 1212316 111316 ?  Sl   14:17   0:05 
/usr/bin/python /usr/share/system-config-printer/system-config-printer.py
  dank 16434  0.0  0.0 238912 11924 ?Sl   14:22   0:00 
/usr/bin/python /usr/share/system-config-printer/install-printerdriver.py 
openprinting-gutenprint deb 
http://www.openprinting.org/download/printdriver/debian/ lsb3.2 contrib 
F8897B6F00075648E248B7EC24CBF5474CFD1E2F
  root 16438  2.4  0.8 298400 99004 ?SNl  14:22   0:13 
/usr/bin/python3 /usr/sbin/aptd
  root 16606  0.0  0.4 298400 57456 pts/39   SNs+ 14:23   0:00 
/usr/bin/python3 /usr/sbin/aptd
  root 16607  0.0  0.0  0 0 pts/39   ZN+  14:23   0:00 [dpkg] 

  root 16608  0.0  0.0      648 pts/39   SN+  14:23   0:00 /bin/sh -c 
/usr/sbin/dpkg-preconfigure --apt || true
  root 16609  0.0  0.1  64272 15816 pts/39   SN+  14:23   0:00 
/usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt
  root 16611  0.0  0.0  0 0 pts/39   ZN+  14:23   0:00 
[dpkg-preconfigu] 

  Clicking cancel on the messagebox did nothing; everything was still
  hung.

  Looks like this was mentioned once before,
  http://ubuntuforums.org/showthread.php?t=2186209

  Doing kill -HUP to the process "/usr/bin/python 
/usr/share/system-config-printer/system-config-printer.py"
  unblocked everything, and dpkg-cache policy reported that 
openprinting-gutenprint was installed.
  Control panel still didn't show the printer I'd wanted, so I tried it again, 
and this time it completed (slowly).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: system-config-printer-gnome 1.4.3+20140219-0ubuntu2.1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Wed Jun 25 14:31:21 2014
  Lpstat: device for EPSON-Stylus-CX6600: 
ipps://trudge.local:631/printers/EPSON_Stylus_CX6600
  MachineType: Dell Inc. Precision WorkStation T7500
  PackageArchitecture: all
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=114bd4a5-fd4b-4701-8155-506c50cb9da9 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 06FW8P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/30/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA02:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1334446/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1529881] Re: CUPS 1.7.2 distorts colors on Canon PIXMA MG5250

Try changing the colour model to CMYK in the printer config with the
gutenprint driver as suggested in the upstream bug report.

** Package changed: ubuntu => gutenprint (Ubuntu)

** Changed in: gutenprint (Ubuntu)
   Status: Invalid => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gutenprint in Ubuntu.
https://bugs.launchpad.net/bugs/1529881

Title:
  CUPS 1.7.2 distorts colors on Canon PIXMA MG5250

Status in gutenprint package in Ubuntu:
  Incomplete

Bug description:
  1)

  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  2)
  apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.7
Candidate: 1.7.2-0ubuntu1.7
Version table:
   *** 1.7.2-0ubuntu1.7 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

  3)
  print colors accurately

  4)
  colors are distorted (not a printer problem, because copying and scanning 
works accurately)

  Original USB open-source printer driver (cnijfilter-
  mg5200series-3.40-1) works, after installing
  libtiff4_3.9.6-9ubuntu1.2_i386:

  see
  
http://www.canon.de/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg5250.aspx?type=drivers==Linux%20%2832-bit%29)

  The current driver in CUPS 1.7.2 distorts the colors (turning black
  into red, blue into red etc.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Tue Dec 29 15:22:47 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-23 (36 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lpstat: device for MG5200USB: cnijusb:/dev/usb/lp1
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  Papersize: a4
  PpdFiles: MG5200USB: Canon MG5200 series Ver.3.40
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic 
root=UUID=77b44b32-8187-4e4e-9ef0-8003061826a2 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01KY.M008.20100430.RHU
  dmi.board.asset.tag: SAMSUNG
  dmi.board.name: N150P/N210P/N220P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: N150P/N210P/N220P
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1529458] Re: ubuntu 14.04: Epson Stylus Photo 2100 "missing print filter"

Can you try if newer printer-driver-gutenprint 5.2.11-pre1 included in 15.10 or 
higher solves your problem.
You can test without installing by using an ubuntu-desktop live-cd.

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

** Package changed: cups (Ubuntu) => gutenprint (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1529458

Title:
  ubuntu 14.04: Epson Stylus Photo 2100 "missing print filter"

Status in gutenprint package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04 on a Dell precision T3400 64bit.

  lsb_release -rd:
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  apt-cache policy cups
  cups:
Installert: 1.7.2-0ubuntu1.7
Kandidat:   1.7.2-0ubuntu1.7
Versjonstabell:
   *** 1.7.2-0ubuntu1.7 0
  500 http://no.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  
  Since I upgraded from 12.04 to 14.04 this printer has not worked well.  
Sometimes it prints after repeatedly pressing the paper feed button.  I often 
get the error message: "missing print filter".  I have had the printer for 
approx. 10 years, and it worked well before 14.04.

  I have tested on a windows 7 laptop and on a mac.  Both work well.

  Conclusion: printer is working.  Someting has happened to cups or the
  cups driver for this printer.

  I have tried the Open Printing user forum and only gotten a report
  from someone with the same problem

  I attach the error log (/var/log/cups/error_log)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1217090] Re: Problem with margins with MAF7460DN

2015-12-27 Thread Pascal De Vuyst

** Changed in: cups (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1217090

Title:
  Problem with margins with MAF7460DN

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  Since I installed Xubuntu 13.04, when I printing a page, the content
  is not centered in the page. The hazardous option is 'media-bottom-
  margin' but whet I try to remove it, it come back automatically vhen I
  apply the settings. I havn't got the problem with Xubuntu 12.04 : it
  appears with Xubuntu 13.04

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1217090] Re: Problem with margins with MAF7460DN

2015-12-27 Thread Pascal De Vuyst

Xubuntu 13.04 is no longer supported, do you still have this problem
with 14.04 LTS or higher?

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1217090

Title:
  Problem with margins with MAF7460DN

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Since I installed Xubuntu 13.04, when I printing a page, the content
  is not centered in the page. The hazardous option is 'media-bottom-
  margin' but whet I try to remove it, it come back automatically vhen I
  apply the settings. I havn't got the problem with Xubuntu 12.04 : it
  appears with Xubuntu 13.04

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1523013] Re: "Paper & Quality options" issue with translation

2015-12-25 Thread Pascal De Vuyst

Fixed upstream with 5f8a44e

** Changed in: system-config-printer (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1523013

Title:
  "Paper & Quality options" issue with translation

Status in system-config-printer package in Ubuntu:
  Fix Committed

Bug description:
  See screenshot.

  "Paper & Quality options<\b>" is not translated in French (I don't
  know if this happens for other languages) and should be in bold
  (instead of showing the  signs).

  On Ubuntu 14.04 fully updated.
  system-config-printer 1.4.3+20140219-0ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1523013/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 779465] Re: Multiple identical drivers for PostScript printers

2015-12-25 Thread Pascal De Vuyst

This is no longer the case in Ubuntu 14.04 LTS

** Changed in: hplip (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/779465

Title:
  Multiple identical drivers for PostScript printers

Status in hplip package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: cups

  When adding a printer using cups webinterface multiple identical PostScript 
drivers are listed for my HP LaserJet 4000N (see screenshot).
  Running lpinfo -m in a terminal shows this is the case for other PostScript 
printers too.
  This makes a user wonder which one (s)he has to choose, there should only be 
one PostScript driver or if there are multiple they should have a different 
name.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  CupsErrorLog:
   
  Date: Sun May  8 14:41:17 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  Lpstat: device for Hewlett-Packard-HP-LaserJet-4000-Series: 
hp:/net/HP_LaserJet_4000_Series?ip=10.0.0.51
  MachineType: Gigabyte Technology Co., Ltd. P55M-UD2
  Papersize: a4
  PpdFiles: Hewlett-Packard-HP-LaserJet-4000-Series: HP LaserJet 4000 Series 
Postscript (recommended)
  ProcEnviron:
   LANGUAGE=nl_BE:en
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae 
root=UUID=a65daa64-0400-4bd6-9294-7e12cab5d10d ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: P55M-UD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55M-UD2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55M-UD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55M-UD2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1523013] Re: "Paper & Quality options" issue with translation

2) reported upstream https://github.com/twaugh/system-config-
printer/issues/25

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1523013

Title:
  "Paper & Quality options" issue with translation

Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  See screenshot.

  "Paper & Quality options<\b>" is not translated in French (I don't
  know if this happens for other languages) and should be in bold
  (instead of showing the  signs).

  On Ubuntu 14.04 fully updated.
  system-config-printer 1.4.3+20140219-0ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1523013/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1476655] Re: need PCL6 and new PS PPDs for HP Color Laserjet 2605dn

The problem here is that printer-driver-postscript-hp provides 3 identical PPD 
with the same *NickName: "HP Color LaserJet 2605 Postscript (recommended)" 
while it should differentiate between 2605/2605dn/2605dtn.
In cups webinterface 3 identical PPD entries are shown while  
system-config-printer only shows one under 2605 and since the 
Foomatic/Postscript 2605dn is more specific this one is (incorrectly) matched.

$ lpinfo -m | grep 2605
foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/HP-Color_LaserJet_2605-Postscript.ppd
 HP Color LaserJet 2605 Foomatic/Postscript
postscript-hp:0/ppd/hplip/HP/hp-color_laserjet_2605-ps.ppd HP Color LaserJet 
2605 Postscript (recommended)
postscript-hp:1/ppd/hplip/HP/hp-color_laserjet_2605-ps.ppd HP Color LaserJet 
2605 Postscript (recommended)
postscript-hp:2/ppd/hplip/HP/hp-color_laserjet_2605-ps.ppd HP Color LaserJet 
2605 Postscript (recommended)
foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/HP-Color_LaserJet_2605dn-Postscript.ppd
 HP Color LaserJet 2605dn Foomatic/Postscript

Reassigning to hplip.

** Package changed: system-config-printer (Ubuntu) => hplip (Ubuntu)

** Changed in: hplip (Ubuntu)
   Status: New => Confirmed

** Also affects: hplip
   Importance: Undecided
   Status: New

** Changed in: hplip
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1476655

Title:
  need PCL6 and new PS PPDs for HP Color Laserjet 2605dn

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  The only PPD for 2605dn is Foomatic/Postscript. Each time I install
  this printer, I must change the model for 2605 and then choose the
  recommended Postscript PPD to have correct resolution and color
  options for this printer (e.g. ProRes 1200, ImageRET 2400).

  Since 2605dn is only a 2605 with duplex and network, it should have
  the same default PPD and the same choices.

  Also, a PCL6 PPD (with adequate resolution and color options) is
  needed for this printer. Maybe as a default, since Postscript is
  hideously slow sometimes (like bug #1095498). Actually, I have
  installed a generic PCL6 with Guntenprint and a HP2500 with hpcups.
  With these, the printer is quick but I only have monochrome output.

  Ubuntu 14.04 (actually Linux Mint 17.2)
  system-config-printer-gnome 1.4.3+20140219-0ubuntu2.6
  system-config-printer-common 1.4.3+20140219-0ubuntu2.6
  system-config-printer-udev 1.4.3+20140219-0ubuntu2.6

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1511878] Re: Pixma 920 printer no longer working via wifi

E [30/Oct/2015:14:07:16 -0700] Unable to bind socket for address
[v1.::1]:631 - Address already in use.

Can you browse to the cups webinterface? http://localhost:631

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1511878

Title:
  Pixma 920 printer no longer working via wifi

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I have a Canon printer,  Pixma 920, that I installed and was working
  great.  I used the driver/install script via the Asian Canon site (as
  recommended by others.)

  I'm not sure what changed but I can no longer print/scan with it from
  my Ubuntu laptop (the app on my Android phone accesses it just fine.)

  I am able to ping the IP address of it, and access it's web interface.
  Attempts to print result in no response.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.6
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic i686
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Oct 30 15:34:46 2015
  InstallationDate: Installed on 2013-09-28 (762 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Lpstat:
   device for MX9222: cnijnet:/F4-81-39-93-E3-26
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. Latitude E6420
  Papersize: letter
  PpdFiles:
   PDF: Generic CUPS-PDF Printer
   MX9222: Canon MX920 series Ver.3.90
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=b920ac1c-3bf7-4673-8486-fa2cf9f89162 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to trusty on 2014-07-24 (463 days ago)
  dmi.bios.date: 01/01/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0K0DNP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd01/01/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1518208] Re: Canon LBP7200Cdn installed but won't print

This printer uses a proprietary closed source printer driver, have a
look here: https://help.ubuntu.com/community/CanonCaptDrv190

** Changed in: cups (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1518208

Title:
  Canon LBP7200Cdn installed but won't print

Status in cups package in Ubuntu:
  Invalid

Bug description:
  ubuntu@ubuntu:~$ ping 192.168.1.180
  PING 192.168.1.180 (192.168.1.180) 56(84) bytes of data.
  64 bytes from 192.168.1.180: icmp_seq=1 ttl=255 time=0.498 ms
  64 bytes from 192.168.1.180: icmp_seq=2 ttl=255 time=0.396 ms
  64 bytes from 192.168.1.180: icmp_seq=3 ttl=255 time=0.352 ms
  64 bytes from 192.168.1.180: icmp_seq=4 ttl=255 time=0.495 ms
  ^C
  --- 192.168.1.180 ping statistics ---
  4 packets transmitted, 4 received, 0% packet loss, time 3000ms
  rtt min/avg/max/mdev = 0.352/0.435/0.498/0.064 ms
  ubuntu@ubuntu:~$ nmap 192.168.1.180

  Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-20 18:06 AEST
  Nmap scan report for 192.168.1.180
  Host is up (0.0032s latency).
  Not shown: 997 closed ports
  PORT STATE SERVICE
  80/tcp   open  http
  427/tcp  open  svrloc
  9100/tcp open  jetdirect

  Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds
  ubuntu@ubuntu:~$ /usr/lib/cups/backend/snmp 
  network socket://192.168.1.180 "Canon LBP7200C" "Canon LBP7200C 1.02" 
"MFG:Canon;MDL:LBP7200C;CMD:CAPT;VER:3.0;CLS:PRINTER;DES:Canon LBP7200C" ""
  ubuntu@ubuntu:~$ sudo /usr/lib/cups/backenddnsd
  [sudo] password for ubuntu: 
  sudo: /usr/lib/cups/backenddnsd: command not found
  ubuntu@ubuntu:~$ sudo /usr/lib/cups/backend/dnssd
  DEBUG: sent=0, count=0
  DEBUG: sent=0, count=0
  ubuntu@ubuntu:~$ /usr/lib/cups/backend/snmp 192.168.1.180
  network socket://192.168.1.180 "Canon LBP7200C" "Canon LBP7200C 1.02" 
"MFG:Canon;MDL:LBP7200C;CMD:CAPT;VER:3.0;CLS:PRINTER;DES:Canon LBP7200C" ""
  ubuntu@ubuntu:~$ lpinfo -v
  network ipp14
  direct ccp
  network lpd
  network socket
  network http
  network ipps
  network ipp
  network https
  direct hp
  network smb
  direct hpfax
  network socket://192.168.1.180
  ubuntu@ubuntu:~$ avahi-browse -a -v -t -r
  Server version: avahi 0.6.31; Host name: ubuntu.local
  E Ifce Prot Name  Type
 Domain
  +   eth0 IPv6 ubuntu [08:00:27:25:b9:12]Workstation   
   local
  +   eth0 IPv4 ubuntu [08:00:27:25:b9:12]Workstation   
   local
  =   eth0 IPv6 ubuntu [08:00:27:25:b9:12]Workstation   
   local
 hostname = [ubuntu.local]
 address = [fe80::a00:27ff:fe25:b912]
 port = [9]
 txt = []
  =   eth0 IPv4 ubuntu [08:00:27:25:b9:12]Workstation   
   local
 hostname = [ubuntu.local]
 address = [192.168.1.185]
 port = [9]
 txt = []
  : Cache exhausted
  +   eth0 IPv6 linuxmint [50:e5:49:e3:00:76] Workstation   
   local
  +   eth0 IPv4 linuxmint [50:e5:49:e3:00:76] Workstation   
   local
  =   eth0 IPv6 linuxmint [50:e5:49:e3:00:76] Workstation   
   local
 hostname = [linuxmint.local]
 address = [fe80::52e5:49ff:fee3:76]
 port = [9]
 txt = []
  =   eth0 IPv4 linuxmint [50:e5:49:e3:00:76] Workstation   
   local
 hostname = [linuxmint.local]
 address = [192.168.1.110]
 port = [9]
 txt = []
  +   eth0 IPv4 ipcamera(id:00EA216238CE) Web Site  
   local
  =   eth0 IPv4 ipcamera(id:00EA216238CE) Web Site  
   local
 hostname = [ipcamera_00EA216238CE.local]
 address = [192.168.1.210]
 port = [88]
 txt = []
  +   eth0 IPv6 linuxmint's remote desktop on linuxmint   VNC Remote Access 
   local
  +   eth0 IPv6 linuxmint's remote desktop on linuxmint   Web Site  
   local
  +   eth0 IPv6 linuxmint Remote Disk 
Management local
  +   eth0 IPv4 linuxmint's remote desktop on linuxmint   VNC Remote Access 
   local
  +   eth0 IPv4 linuxmint's remote desktop on linuxmint   Web Site  
   local
  +   eth0 IPv4 linuxmint Remote Disk 
Management local
  =   eth0 IPv6 linuxmint's remote desktop on linuxmint   VNC Remote Access 
   local
 hostname = [linuxmint.local]
 address = [fe80::52e5:49ff:fee3:76]
 port = [5900]
 txt = []
  =   eth0 IPv6 linuxmint's remote desktop on linuxmint   Web Site  
   local
 hostname = [linuxmint.local]
 address = [fe80::52e5:49ff:fee3:76]
 port = [5800]
 txt = []
  =   eth0 IPv6 linuxmint Remote Disk 
Management local
 hostname = [linuxmint.local]
 address = [fe80::52e5:49ff:fee3:76]
 port = [22]
 txt = []
  =   eth0 IPv4 linuxmint's

[Desktop-packages] [Bug 1511878] Re: Pixma 920 printer no longer working via wifi