from:"Andre"

For any poor saps that encounter this in the future in a similar
situation, replacing the graphics driver with 'virtio' in the KVM/qemu
config fixes this:


  
  


Instead of the default 'cirrus' or whatever. Found this in my age-old
notes from the last time I encountered this problem a year ago. I'm not
sure whether this triggered a cache clear or whether the bit depth is
different or what...

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

Title:
  gnome-shell crashed in
  mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code
  should not be reached

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+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 1766938] Re: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached

I get this error which the internet suggests means a problem getting a
core dump. Upping the limits didn't in apport didn't seem to help. I
attached the file in /var/crash

$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

*** Error: Problem in gnome-shell

Sorry, the program "gnome-shell" closed unexpectedly

Your computer does not have enough free memory to automatically analyze
the problem and send a report to the developers.

Press any key to continue...

** Attachment added: "_usr_bin_gnome-shell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+attachment/5478034/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  gnome-shell crashed in
  mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code
  should not be reached

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+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 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

I've attached the full logs I see. Can anyone tell me where to look for
more details?

** Attachment added: "ubuntu-logs"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+attachment/5478029/+files/ubuntu-logs

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

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+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 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

I'm seeing this crash on a brand new Ubuntu 18.04 install running on KVM
(the host itself is on 16.04). When I connect via KVM's VNC and try to
open settings app, I get a 100% crash. It's weird because I haven't
installed any additional software.

Mar 18 22:42:11 riv18 org.gnome.Shell.desktop[2561]: **
Mar 18 22:42:11 riv18 org.gnome.Shell.desktop[2561]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
Mar 18 22:42:11 riv18 org.gnome.Shell.desktop[2561]: == Stack trace for context 
0x55663fe03320 ==
Mar 18 22:42:11 riv18 gnome-session[2482]: gnome-session-binary[2482]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
Mar 18 22:42:11 riv18 gnome-session-binary[2482]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6
Mar 18 22:42:12 riv18 gsd-media-keys[2649]: g_variant_get_va: assertion 'value 
!= NULL' failed
Mar 18 22:42:12 riv18 gsd-media-keys[2649]: g_variant_unref: assertion 'value 
!= NULL' failed
Mar 18 22:42:12 riv18 org.gnome.Shell.desktop[2942]: current session already 
has an ibus-daemon.
Mar 18 22:42:12 riv18 dbus-daemon[445]: [system] Activating via systemd: 
service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by 
':1.178' (uid=1000 pid=2942 comm="/usr/bin/gnome-shell " label="unconfined")
Mar 18 22:42:12 riv18 systemd[1]: Starting Location Lookup Service...
Mar 18 22:42:13 riv18 dbus-daemon[445]: [system] Successfully activated service 
'org.freedesktop.GeoClue2'
Mar 18 22:42:13 riv18 systemd[1]: Started Location Lookup Service.
Mar 18 22:42:13 riv18 gnome-shell[2942]: Telepathy is not available, chat 
integration will be disabled.
Mar 18 22:42:13 riv18 gsd-media-keys[2649]: g_variant_get_va: assertion 'value 
!= NULL' failed
Mar 18 22:42:13 riv18 gsd-media-keys[2649]: g_variant_unref: assertion 'value 
!= NULL' failed
Mar 18 22:42:13 riv18 gnome-shell[2942]: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: 
unreachable code after return statement
Mar 18 22:42:13 riv18 org.gnome.Shell.desktop[2942]: **
Mar 18 22:42:13 riv18 org.gnome.Shell.desktop[2942]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached

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

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App

[Desktop-packages] [Bug 1754671]

2020-11-14 Thread Andre Klapper

bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which 
have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want
this feature in a recent and supported version of NetworkManager, then
please feel free to report it at
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be
implemented (workforce and time is unfortunately limited).

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 942856]

2020-11-13 Thread Andre Klapper

bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which 
have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want
this feature in a recent and supported version of NetworkManager, then
please feel free to report it at
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be
implemented (workforce and time is unfortunately limited).

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  Selecting AES-{192,256}-CBC keys to connect isn't working

  * Test case

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key. 

  That should work

  * Regression potential

  That's new code for an extra type of keys, it shouldn't impact
  existing options

  --

  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+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 1831483]

2020-11-13 Thread Andre Klapper

bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which 
have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want
this feature in a recent and supported version of NetworkManager, then
please feel free to report it at
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be
implemented (workforce and time is unfortunately limited).

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

Title:
  metrics on pushed routes not applied

Status in NetworkManager-OpenVPN:
  Expired
Status in network-manager-openvpn package in Ubuntu:
  Triaged

Bug description:
  We have a couple of VPN endpoints located in different places.  These
  each provide access to a bunch of things located in both places.  We
  decided that it would be a good idea to let people connect to both
  endpoints so that by adjusting the metrics on the pushed routes (we
  used 500 and 1000) our users would always use the shortest available
  path.

  This works great with vanilla openvpn, but when using network-manager-
  openvpn, the metrics are lost and instead "50" is used, which means
  that only one gateway is used.  Ideally network-manager-openvpn would
  use the supplied metrics so that traffic is routed as intended.

  This seems to affect network-manager-openvpn in releases of Ubuntu up
  to 18.04 LTS, and possibly beyond.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1831483/+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 1728045]

2020-11-07 Thread Andre Klapper

bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing
all old bug reports in Bugzilla which have not seen updates for many
years.

If you can still reproduce this issue in a currently supported version
of GNOME (currently that would be 3.38), then please feel free to report
it at https://gitlab.gnome.org/GNOME/gnome-power-manager/-/issues/

Thank you for reporting this issue and we are sorry it could not be
fixed.

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

Title:
  Please restore battery time remaining to top bar!

Status in GNOME Shell:
  Expired
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 17.04 and earlier, I was able to display the amount of
  battery life remaining AS TIME in the top bar of my screen.

  Now all I'm able to display, in 17.10, is the battery percentage.

  Frankly, I don't give a flying fig about battery percentage, and I'm
  not sure most other people do either. What I care about is how much
  time I have left to work on my laptop before it's out of power.

  If you want to display _both_ the percentage and the time remaining,
  or allow the user to choose which to display, that would be great. But
  just taking away the eminently useful time remaining and replacing it
  with the much less useful percentage is annoying and should be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 09:13:40 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (160 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1728045/+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 1883174] Re: Some desktop icons disappear

2020-09-30 Thread Andre Ruiz

My guess. “/home/ion420/Desktop/.goutputstream-0LONR0” is a temporary
file, probably the editor is saving a new file to then move over the
original one when you save. The extension notices the new file but when
trying to get more info about it, it's gone (race condition). It
probably does not recover well from this scenario.

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

Title:
Some desktop icons disappear

Status in gnome-shell-extension-desktop-icons:
Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
In Progress

Bug description:
OS: Ubuntu 20.04
GNOME: 3.36.2
Extension: 3.36.2

Sometimes, some icons in my Desktop folder just don't appear on the
desktop. The missing icons aren't invisible, it's like they're not in
the folder. Clicking on the empty space where they should be does
nothing. Mousing over the empty space does nothing. See attached
screenshot. As you can see, there are many missing.

Not consistently reproducible, but frequent.

This isn't great info, I know. Let me know what else I can provide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1892064] [NEW] unable to login google account

2020-08-18 Thread Andre Felipe Machado

Public bug reported:

deja-dup freeze its backup process, then I found that gnome-control-center 
ubuntu 18.04 is unable to login on google account anymore.
Maybe google changed its API for login accounts.
Regards.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 18 12:30:40 2020
InstallationDate: Installed on 2019-10-17 (306 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  unable to login google account

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  deja-dup freeze its backup process, then I found that gnome-control-center 
ubuntu 18.04 is unable to login on google account anymore.
  Maybe google changed its API for login accounts.
  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 18 12:30:40 2020
  InstallationDate: Installed on 2019-10-17 (306 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892064/+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 1890384] [NEW] Xorg crash

2020-08-05 Thread andre

Public bug reported:

ls -l /var/crash

backport-iwlwifi-dkms.0.crash
_opt_google_chrome_chrome.1000.crash
_usr_bin_gnome-control-center.1000.crash

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18
Uname: Linux 4.15.0-111-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  5 09:12:04 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 backport-iwlwifi, 7906: added
 rtl8812au, 5.6.4.2~ppa: added
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 510 [1043:8694]
InstallationDate: Installed on 2018-12-21 (592 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1c4f:0026 SiGma Micro Keyboard
 Bus 001 Device 003: ID 062a: Creative Labs Optical mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic 
root=UUID=239295ef-655d-4e9d-986a-bc396201c864 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3408
dmi.board.asset.tag: Default string
dmi.board.name: H110M-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3408:bd09/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic crash 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/1890384

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  ls -l /var/crash

  backport-iwlwifi-dkms.0.crash
  _opt_google_chrome_chrome.1000.crash
  _usr_bin_gnome-control-center.1000.crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18
  Uname: Linux 4.15.0-111-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 09:12:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 7906: added
   rtl8812au, 5.6.4.2~ppa: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 510 [1043:8694]
  InstallationDate: Installed on 2018-12-21 (592 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c4f:0026 SiGma Micro Keyboard
   Bus 001 Device 003: ID 062a: Creative Labs Optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic 
root=UUID=239295ef-655d-4e9d-986a-bc396201c864 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)

[Desktop-packages] [Bug 1885136] Re: Nautilus connection to SSH IPv6 address fails

2020-06-26 Thread Andre Klapper

@seb128: No, please do not ask folks to report issues upstream when this
was only tested with software versions which are 30 months old. Upstream
does not want such reports as long as issues have not been reproduced
before in a recent and supported software version. Thanks.

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

Title:
  Nautilus connection to SSH IPv6 address fails

Status in nautilus package in Ubuntu:
  New

Bug description:
  After reading answer
  https://answers.launchpad.net/ubuntu/+question/151402

  I have tested that
  1) on the command line
  """
  sftp 'USER@[IPv6_ADDR%INTERFACE]'
  """
  connects successfully

  , but
  2) on the address field of nautilus 1:3.26.4-0~ubuntu18.04.5, both protocols 
'ssh' and 'sftp' result in "Connection failed" for the same form of address.

  Expectation was for this connection to succeed.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18
  Uname: Linux 4.15.0-106-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 25 16:52:53 2020
  InstallationDate: Installed on 2018-01-10 (896 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2019-02-12 (499 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1885136/+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 1883005] [NEW] Xorg freeze

2020-06-10 Thread adsson andre da silva gomes

Public bug reported:

This bug have been happing on my PC, in the applications when i open
some application folder and after click out of it, to close it. The
screen just freeze and i have to reboot my notebook (Lenovo-
ideapad-310).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 15:08:37 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: I don't know
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
InstallationDate: Installed on 2020-06-09 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 80UH
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=31e5e6b9-3228-4c0a-b10a-d78f6218b8db ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 5A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UH:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UH
dmi.product.sku: LENOVO_MT_80UH_BU_idea_FM_Lenovo ideapad 310-15ISK
dmi.product.version: Lenovo ideapad 310-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
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
 Assignee: adsson andre da silva gomes (adsson)
 Status: New


** Tags: amd64 apport-bug focal freeze ubuntu

** Attachment added: "Screenshot from 2020-06-10 15-29-03.png"
   
https://bugs.launchpad.net/bugs/1883005/+attachment/5382591/+files/Screenshot%20from%202020-06-10%2015-29-03.png

** Changed in: xorg (Ubuntu)
 Assignee: (unassigned) => adsson andre da silva gomes (adsson)

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug have been happing on my PC, in the applications when i open
  some application folder and after click out of it, to close it. The
  screen just freeze and i have to reboot my notebook (Lenovo-
  ideapad-310).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 15:08:37 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: I don't know
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
  InstallationDate: Installed on 2020-06-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 80UH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=31e5e6b9-3228-4c0a-b10a-d78f6218b8db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LE

[Desktop-packages] [Bug 1881453] Re: Screen corruption on resize (Android Studio start screen)

2020-06-03 Thread Andre Klapper

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1281
   Importance: Unknown
   Status: Unknown

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

Title:
  Screen corruption on resize (Android Studio start screen)

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2) (not installed from software center)
  Android Studio 4.0
  Build #AI-193.6911.18.40.6514223, built on May 20, 2020
  Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64
  VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
  Linux 5.4.0-33-generic
  GC: ParNew, ConcurrentMarkSweep
  Memory: 1981M
  Cores: 8
  Registry: ide.new.welcome.screen.force=true
  Non-Bundled Plugins: 

  3) It should resize without problems

  4) Resizing the window corrupts the image

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 31 04:41:37 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:380a]
 Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
  InstallationDate: Installed on 2020-04-23 (37 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 5986:0670 Acer, Inc Lenovo EasyCamera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=5b998715-8d22-4261-a707-c6958e6eeb81 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN63WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN63WW:bd06/14/2018:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1881453/+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 1862650] Re: Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd upgrade

2020-05-14 Thread Andre Ruiz

Today, doing a simple apt update + apt upgrade in Eoan:


Setting up systemd (242-7ubuntu3.8) ...
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher → 
/run/speech-dispatcher; please update the tmpfiles.d/ drop-in file acco
rdingly.
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → 
/run/speech-dispatcher/.cache; please update the tmpfiles.d/ dro
p-in file accordingly.
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below 
legacy directory /var/run/, updating 
/var/run/speech-dispatcher/.speech-dispatcher → 
/run/speech-dispatcher/.speech-dispatcher; please up
date the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below 
legacy directory /var/run/, updating 
/var/run/speech-dispatcher/.cache/speech-dispatcher → 
/run/speech-dispatcher/.cache/speech-dispatche
r; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher/log → 
/run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in f
ile accordingly.

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

Title:
  Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd
  upgrade

Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  When upgrading to the latest systemd SRU:

  Setting up systemd (242-7ubuntu3.6) ...
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher → 
/run/speech-dispatcher; please upda
  te the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → 
/run/speech-dispatcher/.cach
  e; please update the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below 
legacy directory /var/run/, updating 
/var/run/speech-dispatcher/.speech-dispatcher → /run/speech-disp
  atcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file 
accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below 
legacy directory /var/run/, updating 
/var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speec
  h-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in 
file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher/log → 
/run/speech-dispatcher/log; ple
  ase update the tmpfiles.d/ drop-in file accordingly.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: i3
  Date: Mon Feb 10 10:50:26 2020
  InstallationDate: Installed on 2019-08-13 (181 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: speech-dispatcher
  UpgradeStatus: Upgraded to eoan on 2020-01-10 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1862650/+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 659661] Re: Sound problems since upgrading from 10.04 to 10.10 with kernel 2.6.35-22.

2020-03-05 Thread Andre Mangan

This is no longer an issue, the problem was solved (see above).  Please
close this ten-year-old bug report, thank you.

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

Title:
  Sound problems since upgrading from 10.04 to 10.10 with kernel
  2.6.35-22.

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Sound problems since upgrading from 10.04 to 10.10 with kernel 2.6.35-22.
  Any sound track from the introductory drum roll to playing a music track is 
erratic, it races and sounds garbled.

  Using the old kernel 2.6.32-25 sound is perfect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/659661/+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 1862478] Re: gnome-system-monitor can't measure network transfer rate

2020-03-03 Thread Andre Brait

I can confirm 3.35.92-1 fixed it too.

** Changed in: gnome-system-monitor (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gnome-system-monitor can't measure network transfer rate

Status in gnome-system-monitor package in Ubuntu:
  Fix Released

Bug description:
  It started happening since I updated today and version 3.35.90 got
  installed. It had been working normally before that.

  The total number of bytes received seems to be accurate (I really
  downloaded a bit over 1GB of data when the screenshot was taken), but
  the transfer rate is not being measured accurately. The real transfer
  rate when the screenshot was taken was around 10 MB/s while it shows
  just a few bytes/second.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-system-monitor 3.35.90-1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  8 22:29:41 2020
  InstallationDate: Installed on 2019-05-15 (269 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to focal on 2020-01-20 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1862478/+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 1862478] [NEW] gnome-system-monitor can't measure network transfer rate

2020-02-08 Thread Andre Brait

Public bug reported:

It started happening since I updated today and version 3.35.90 got
installed. It had been working normally before that.

The total number of bytes received seems to be accurate (I really
downloaded a bit over 1GB of data when the screenshot was taken), but
the transfer rate is not being measured accurately. The real transfer
rate when the screenshot was taken was around 10 MB/s while it shows
just a few bytes/second.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-system-monitor 3.35.90-1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb  8 22:29:41 2020
InstallationDate: Installed on 2019-05-15 (269 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-system-monitor
UpgradeStatus: Upgraded to focal on 2020-01-20 (19 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot during a time when I was downloading files at 
around  10MB/s"
   
https://bugs.launchpad.net/bugs/1862478/+attachment/5326550/+files/Screenshot%20from%202020-02-08%2022-30-23.png

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

Title:
  gnome-system-monitor can't measure network transfer rate

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  It started happening since I updated today and version 3.35.90 got
  installed. It had been working normally before that.

  The total number of bytes received seems to be accurate (I really
  downloaded a bit over 1GB of data when the screenshot was taken), but
  the transfer rate is not being measured accurately. The real transfer
  rate when the screenshot was taken was around 10 MB/s while it shows
  just a few bytes/second.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-system-monitor 3.35.90-1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  8 22:29:41 2020
  InstallationDate: Installed on 2019-05-15 (269 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to focal on 2020-01-20 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1862478/+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 1857633] Re: Source ID was not found when attempting to remove it

2019-12-26 Thread Andre Klapper

Clinton H: Please see
https://gitlab.gnome.org/GNOME/gdm/issues/547#note_673701 which
information to provide.

** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #547
   https://gitlab.gnome.org/GNOME/gdm/issues/547

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

Title:
  Source ID was not found when attempting to remove it

Status in nautilus package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) Files 1:3.34.1-1ubuntu1
  3) I clicked on a folder in Nautilus, a busy indicator was displayed for 
several minutes, instead of the folder contents. I clicked the back arrow and 
then clicked the same folder again. The folder contents displayed immediately. 
I decided to run Nautilus from the terminal. This error and some other errors 
were displayed in the terminal output.
  4) Error in terminal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857633/+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 525507]

2019-11-06 Thread Andre Klapper

@zamarac: (On a meta level:) People have different interests and
priorities. People are free [not] to work on something. If you really
want something to be implemented, feel free to provide a software patch
and getting it reviewed or to convince someone else to write that
software patch. "What have you done in the last 10 years to fix this
problem?", basically. Also see https://www.mozilla.org/en-
US/about/governance/policies/participation/ - thanks! :)

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

Title:
  Empty All Trash for Smart Folders

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

Bug description:
  Binary package hint: thunderbird

  Add the possibility of emptying all trash by right click on the trash
  roots

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/525507/+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 1181666]

2019-10-05 Thread Andre Klapper

Can anyone still reproduce this in 3.34?

(3.28 or 3.30 are not supported anymore.)

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 1846094] [NEW] package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: »installiertes nvidia-dkms-430-Skript des Paketes post-installation«-Unterprozess gab den Fehl

2019-09-30 Thread Andre Cibis

Public bug reported:

E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3989 
(apt) - open (11: Die Ressource ist zur Zeit nicht verfügbar)
N: Be aware that removing the lock file is not a solution and may break your 
system.
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: nvidia-dkms-430 430.50-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Mon Sep 30 20:56:20 2019
ErrorMessage: »installiertes nvidia-dkms-430-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
InstallationDate: Installed on 2019-08-14 (47 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: nvidia-graphics-drivers-430
Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: 
»installiertes nvidia-dkms-430-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-430 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package eoan

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

Title:
  package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade:
  »installiertes nvidia-dkms-430-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 10 zurück

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  New

Bug description:
  E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3989 
(apt) - open (11: Die Ressource ist zur Zeit nicht verfügbar)
  N: Be aware that removing the lock file is not a solution and may break your 
system.
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-dkms-430 430.50-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 30 20:56:20 2019
  ErrorMessage: »installiertes nvidia-dkms-430-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  InstallationDate: Installed on 2019-08-14 (47 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-430
  Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: 
»installiertes nvidia-dkms-430-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1846094/+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 1734095]

2019-09-29 Thread Andre Klapper

Maciej: Is this still an issue? Or can this be closed as RESOLVED
OBSOLETE?

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1572363] Re: Gnome-terminal-server missing icon

2019-07-27 Thread Andre Ruiz

Humm, actually this happens only when using byobu and the terminal is started 
through it's icon, if I start the terminal directly it works ok. So this may be 
related to byobu and not the terminal itsef. Sorry for the noise.

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

Title:
  Gnome-terminal-server missing icon

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Overview
  

  Launching gnome terminal using the Gnome overview launches gnome-
  terminal-server, which does not have an application icon.

  Setup
  

  ❯ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ❯ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.18.3-1ubuntu1
Candidate: 3.18.3-1ubuntu1
Version table:
   *** 3.18.3-1ubuntu1 500
  500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Gnome Wayland Session

  What you expected to happen
  -

  I expected to see a Gnome Terminal icon shown for the terminal

  What happened instead
  

  I have the 'application missing' icon.

  Another user has a similar issue [0].

  
  [0] 
https://www.reddit.com/r/gnome/comments/3t25m0/bug_gnome_terminal_grouped_as_gnometerminalserver/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1572363/+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 1572363] Re: Gnome-terminal-server missing icon

2019-07-27 Thread Andre Ruiz

Ubuntu Disco Dingo, gnome 3.32, happens only on wayland.

When you start gnome-terminal, it instead spawn a separate icon which is
named gnome-terminal-server and has no icon (actually the missing icon
icon).

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

Title:
  Gnome-terminal-server missing icon

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Overview
  

  Launching gnome terminal using the Gnome overview launches gnome-
  terminal-server, which does not have an application icon.

  Setup
  

  ❯ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ❯ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.18.3-1ubuntu1
Candidate: 3.18.3-1ubuntu1
Version table:
   *** 3.18.3-1ubuntu1 500
  500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Gnome Wayland Session

  What you expected to happen
  -

  I expected to see a Gnome Terminal icon shown for the terminal

  What happened instead
  

  I have the 'application missing' icon.

  Another user has a similar issue [0].

  
  [0] 
https://www.reddit.com/r/gnome/comments/3t25m0/bug_gnome_terminal_grouped_as_gnometerminalserver/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1572363/+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 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)

2019-07-25 Thread Andre Ruiz

I have seen this on bionic, then on cosmic and now on disco. Type
password and it takes 5 to 6 seconds to give you the desktop.

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

Title:
  Unlocking the  screen takes 5 seconds in Xorg sessions (not so much in
  Wayland sessions)

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  This is a fresh installation of 18.04. After entering the password and
  pressing enter, it takes 5 seconds for the lock screen to disappear.
  This problem didn't happen on the same machine with 16.04 or 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:31:48 2018
  InstallationDate: Installed on 2018-05-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+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 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-07-09 Thread Andre Klapper

** Bug watch added: gitlab.gnome.org/GNOME/seahorse/issues #205
   https://gitlab.gnome.org/GNOME/seahorse/issues/205

** Also affects: seahorse via
   https://gitlab.gnome.org/GNOME/seahorse/issues/205
   Importance: Unknown
   Status: Unknown

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  Unknown
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Fedora:
  New

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/1771880/+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 1245473]

2019-06-19 Thread Andre Klapper

yanp.b...@gmail.com: Why did you reopen this task without any comment
explaining the reason? See comment 201?

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+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 1683383]

2019-06-18 Thread Andre Klapper

yanp.b...@gmail.com: Why did you reopen this task without any comment
explaining the reason? See comment 201?

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

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

Bug description:
  From duplicate bug 1720364 report.

  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher in mate-control-center
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ---
  Original description below:

  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1683383/+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 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'

2019-05-15 Thread Andre Klapper

** Also affects: gvfs via
https://gitlab.gnome.org/GNOME/gvfs/issues/398
Importance: Unknown
Status: Unknown

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

Title:
Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access
based share enumeration = yes'

Status in gvfs:
Unknown
Status in gvfs package in Ubuntu:
New

Bug description:
From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other
Locations", I see my samba/SMB server. If I double click it, it then
lists *some* of my shares. Specifically, it lists those where I didn't
use Samba's 'access based share enumeration = yes'[1] (which allows
some shares to be made completely invisible to some users). Note that
Ubuntu has *not* yet asked me to authenticate, so it makes sense that
I shouldn't yet be able to see shares I'm not entitled to.

The bug is: even after I authenticate (and let it remember my
password), then go back to Other Locations>MyServer, it *still*
doesn't show the other shares. In fact, I can't find *any* way to see
the other shares.

Contrast this with macOS Finder. If I navigate to MyServer in the
share list, it doesn't show *any* shares until I authenticate, then it
shows *all* shares that the user has access to (and none of the shares
the user doesn't have access to).

Ubuntu could either:
- adopt macOS Finder behaviour and get authentication first, or
- update the share list after authentication is performed.

Its current behaviour makes some shares totally inaccessible (the crux
of the bug).

I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest)
using ZFS, running samba 4.9.6. Other users on the FreeNAS forum see
the same behaviour[2], so it's not particular to my setup.

[1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
[2]
https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/

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

[Desktop-packages] [Bug 1827727]

*** Bug 1549198 has been marked as a duplicate of this bug. ***

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1827727/+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 1827727]

*** Bug 1549120 has been marked as a duplicate of this bug. ***

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1827727/+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 1827727]

*** Bug 1549124 has been marked as a duplicate of this bug. ***

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1827727/+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 1827727]

*** Bug 1549094 has been marked as a duplicate of this bug. ***

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1827727/+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 1827199] Re: firefox menu font can not set by gnome tweak 3.32.0

2019-05-03 Thread Andre Klapper

> gnome tweak developer says "Tweaks on Fedora 30 allows changing the
font of Firefox 66.0.3", so I doubt this is a ubuntu's bug.

@widon1104: For the records, GNOME Tweak developer did not say that, as
you're quoting me and I am not a GNOME Tweak developer.

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

Title:
  firefox menu font can not set by gnome tweak 3.32.0

Status in firefox package in Ubuntu:
  New

Bug description:
  I use ubuntu19.04, gnome 3.32.1, gnome tweak version 3.32.0, firefox version 
66.0.3
  In ubuntu18.04, firefox menu font can be set by gnome-tweak, but in 
ubuntu19.04 firefox menu font can not set by gnome tweak now.(The default menu 
font for firefox is too big and ugly I think)
  I don't know how to set firefox menu font now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827199/+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 1825720] Re: No option to 'star' file in 19.04

2019-04-22 Thread Andre Almeida

I can't find this settings.

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

Title:
  No option to 'star' file in 19.04

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  New feature in 19.04 is not working on my system.
  As I understand, I should be able to right-click a file/folder and select 
star. That option is not available though 'Starred' is now a location in 
places. This option is missing under both Wayland and X.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1825720/+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 1338492]

2019-01-18 Thread Andre Klapper

No further information provided by reporter, hence unfortunately closing
as WORKSFORME.

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  At startup, my screen flashes in light green, and can't log to lightdm. 
Adding the ATI driver, it will install with a missing link... Erasing cyrillic 
path and 75 and 100 dpi path folders.
  At this time, can't find again the missing link, and  just install missings 
fonts don't fix the bug..

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.15.0-6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   [128G 
[122G[ OK ]
* Starting automatic crash report generation: apport   [128G 
[122G[ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Jul  7 10:44:49 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB 
DDR3 [174b:e164]
  InstallationDate: Installed on 2014-07-03 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=68f3fab7-5c4e-4d3a-9d6d-a493c47946db ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7ffb7ec04db0, argc=11, argv=0x7fff4f6b2e88, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff4f6b2e78) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55
  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.:bvr5401:bd11/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jul  7 10:48:37 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputEee PC WMI hotkeys   KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 583797]

2018-12-12 Thread Andre Klapper

*** Bug 1350747 has been marked as a duplicate of this bug. ***

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

Title:
  "Warn on closing with multiple tabs open" not honored

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: firefox

  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy firefox
  firefox:
    Installed: 11.0+build1-0ubuntu0.11.10.1
    Candidate: 11.0+build1-0ubuntu0.11.10.1
    Version table:
   *** 11.0+build1-0ubuntu0.11.10.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ oneiric-security/main i386 
Packages
  100 /var/lib/dpkg/status
   7.0.1+build1+nobinonly-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

  3) What is expected to happen in Firefox, with Edit -> Preferences -> Tabs -> 
"Warn on closing with multiple tabs open" checkbox checked, is when one click 
the X, File -> Quit, Ctrl+Q , or Alt+Space -> C, one get's the confirmation box:
  Confirm close
  You are about to close x tabs. Are you sure you want to continue?

  4) What happens instead is one is not warned and the window closes.

  PARTIAL WORKAROUND: about:config -> browser.tabs.maxOpenBeforeWarn ->
  change from 15 to 2. This will pop up the confirmation box clicking
  the X and Alt+Space -> C only.

  WORKAROUND: Disable Ctrl+Q quiting the browser by installing keyconfig add-on:
  http://mozilla.dorando.at/keyconfig.xpi

  Then Tools -> Add-Ons -> Extensions -> keyconfig Preferences ->
  highlight Quit -> Disable

  Original Reporter Comments: I found a "workaround" that says to set
  "open to a blank page" somewhere else, and I set this, but it still
  doesn't warn me.

  I work from home and frequently spend an hour or so putting in data,
  all on one screen. If I accidentally hit the stupid little x (which is
  now in the left hand corner just where you don't need it, it is too
  easy to hit it by accident, but i can't change this, it comes with the
  distro), i lose all that work.

  Please tell me how to fix this terrible bug.

  Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.3) Gecko/20100423
  Ubuntu/10.04 (lucid) Firefox/3.6.3 GTB7.1

  THIS BUG AFFECTS MY SECURITY (INCOME) but i guess would not be
  classifed as a security bug per se

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Fri May 21 14:07:40 2010
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/583797/+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 1767322] Re: "Activation of network connection failed" popup shows incessantly

2018-09-11 Thread ANDRE LUIZ DE PINHO CAVALCANTE

My wireless connections works fine in Windows, but in Ubuntu it does't
even connect and the message of error is as above: "activation of
network connection failed".  I am using the version 18.04.01.

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => ANDRE LUIZ DE PINHO CAVALCANTE (andreluizpinho)

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

Title:
  "Activation of network connection failed" popup shows incessantly

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/linux/+bug/1767322/+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 1596361] Re: MFP M476DW Error 5002 on status / No toner levels in HP Device Manager

2018-09-10 Thread Andre Hufschmidt

Hi G,

Thanks a lot. I am still using Ubunutu 16.04.5. I will soon upgrade my
laptop to a newer version and provide feedback than.

Kind regards,

André

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

Title:
  MFP M476DW Error 5002 on status / No toner levels in HP Device Manager

Status in HPLIP:
  Fix Committed
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  HP Device Manager always showed Error 5002 (device is busy powered
  down or unplugged) as Status for my M476DW. In addition, under
  supplies, no toner levels were shown.

  I have modified the "[hp_color_laserjet_mfp_m476dw]" entry in
  /usr/share/hplip/data/models/models.dat. The full entry I have
  attached below.

  By changing status-type=12 to status-type=10 error 5002 disappeared.
  Adding the r0-agent* entries made the supplies display (and hp-levels)
  work.

  [hp_color_laserjet_mfp_m476dw]
  align-type=0
  clean-type=0
  color-cal-type=0
  copy-type=0
  embedded-server-type=0
  fax-type=7
  fw-download=False
  icon=HP_Color_LaserJet_2840.png
  io-mfp-mode=1
  io-mode=1
  io-support=14
  job-storage=0
  linefeed-cal-type=0
  model1=HP Color Laserjet Pro MFP M476dw
  monitor-type=0
  panel-check-type=0
  pcard-type=0
  plugin=1
  plugin-reason=64
  power-settings=0
  ppd-name=color_laserjet_pro_mfp_m476
  pq-diag-type=0
  r-type=0
  r0-agent1-kind=4
  r0-agent1-sku=CB380A
  r0-agent1-type=1
  r0-agent2-kind=4
  r0-agent2-sku=CB381A
  r0-agent2-type=4
  r0-agent3-kind=4
  r0-agent3-sku=CB383A
  r0-agent3-type=5
  r0-agent4-kind=4
  r0-agent4-sku=CB382A
  r0-agent4-type=6
  scan-src=3
  scan-type=5
  status-battery-check=0
  status-dynamic-counters=0
  status-type=12
  support-released=True
  support-subtype=447b
  support-type=2
  support-ver=3.14.4
  tech-class=Postscript
  tech-subclass=Normal
  tech-type=4
  usb-pid=342a
  usb-vid=3f0
  wifi-config=3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1596361/+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 1759462] Re: Keyboard shortcuts not operational on 18.04

2018-09-01 Thread Andre

Fix from #11 works for me:

A workaround is to delay compiz launch for a few seconds.

Open up /usr/lib/systemd/user/unity7.service and add
ExecStartPre=/bin/sleep 2
before
ExecStart=/usr/bin/compiz

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

Title:
  Keyboard shortcuts not operational on 18.04

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+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 1759462] Re: Keyboard shortcuts not operational on 18.04

2018-09-01 Thread Andre

Upgraded from Ubuntu 16.04 to 18.04 and media keys, Ctrl-`, Ctrl-Alt-T, and 
many more are not working.
Now I can't assign Ctrl-` any more, very annoying, now I use shift-` but this 
is a bad fix (it blocks ~).

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

Title:
  Keyboard shortcuts not operational on 18.04

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+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 1783415] [NEW] Network-Manager misses option to disconnect VPN

2018-07-24 Thread Andre

Public bug reported:

There is no menu item in the VPN submenu to disconnect a VPN connection.
Only "configuring VPN" is offered. The only way to terminate a VPN
connection is to click on the ongoing VPN connection again to trigger an
error.

Issue also discussed here: 
https://ubuntuforums.org/showthread.php?t=2355162 

Such menu option did exit in Ubuntu 14.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.4
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 24 23:16:02 2018
EcryptfsInUse: Yes
IpRoute:
 default via 192.168.178.1 dev enp0s25  proto static  metric 100 
 169.254.0.0/16 dev enp0s25  scope link  metric 1000 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 192.168.178.0/24 dev enp0s25  proto kernel  scope link  src 192.168.178.37  
metric 100
IwConfig:
 lono wireless extensions.
 
 enp0s25   no wireless extensions.
 
 docker0   no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/2  
docker0 edcde2ee-239e-42a5-808a-afa29c27e05c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp0s25  ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  Wired 
connection 1  3d00e91a-e309-402c-b847-0c1d7444192e  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "No menu item to terminate VPN connection"
   
https://bugs.launchpad.net/bugs/1783415/+attachment/5167308/+files/Auswahl_002.jpg

** Summary changed:

- Network-Manager missiong option to disconnect VPN
+ Network-Manager missing option to disconnect VPN

** Summary changed:

- Network-Manager missing option to disconnect VPN
+ Network-Manager misses option to disconnect VPN

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167309/+files/CRDA.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167310/+files/Dependencies.txt

** Attachment removed: "IpAddr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167312/+files/IpAddr.txt

** Attachment removed: "PciNetwork.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167317/+files/PciNetwork.txt

** Attachment removed: "nmcli-con.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167321/+files/nmcli-con.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167320/+files/WifiSyslog.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167319/+files/ProcEnviron.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167318/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167316/+files/NetworkManager.conf.txt

** Attachment removed: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167315/+files/NetDevice.lo.txt

** Attachment removed: "NetDevice.enp0s25.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167314/+files/NetDevice.enp0s25.txt

** Attachment removed: "NetDevice.docker0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167313/+files/NetDevice.docker0.txt

** Attachment removed: "IfupdownConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167311/+files/IfupdownConfig.txt

-- 
You received this bug notification

[Desktop-packages] [Bug 1763691] Re: Copy/paste to message body does not work on Bionic

@Lukas: Great! Feel free to close this ticket. :)

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

Title:
  Copy/paste to message body does not work on Bionic

Status in evolution package in Ubuntu:
  Incomplete

Bug description:
  Wether using ctrl-v nor context menu or middle mouse button works to
  paste text (plain text) into message body on Ubuntu Bionic.

  (On Debian Stretch it is working fine)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1763691/+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 1776978] Re: Update to calendar invitations cannot be processed: HTTP error code 412

** Summary changed:

- Update to calendar invitations cannot be processes
+ Update to calendar invitations cannot be processed: HTTP error code 412

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

Title:
  Update to calendar invitations cannot be processed: HTTP error code
  412

Status in evolution package in Ubuntu:
  New

Bug description:
  I am using a caldav calendar on a synology NAS and observed issues with 
calendar invitations I previously received. When I open one of these events I 
get the warning 'Event cannot be fully edited, because you are not the 
organizer' which I can live with. However, I cannot process any update I 
receive to these invitation.
  The calendar entry is identified. Message: 
Found the appointment in the calendar “myCal”
  When I click on 'Accept' I get the message:
Unable to send item to calendar “mycal”. Cannot receive calendar objects: 
Failed to put data: HTTP error code 412 (Precondition Failed): Existing 
resource matches "If-None-Match" header - not accepted.[if-none-match]
  and the event remains unchanged.

  Updates are both possible with Thunderbird on the same machine and on
  my iPhone

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution 3.28.1-2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 14 21:59:26 2018
  InstallationDate: Installed on 2018-05-02 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1776978/+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 1741948] Re: Evolution ignores tile window commands in GNOME

This should be moved to gnome-shell instead; see
https://bugzilla.gnome.org/show_bug.cgi?id=636416

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

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

Title:
  Evolution ignores tile window commands in GNOME

Status in evolution package in Ubuntu:
  New

Bug description:
  As per the Help "Ubuntu Desktop Guide -> Desktop -> Applications and
  windows -> Windows and workspaces -> Windows" documentation for "Tile
  windows:"

  "To maximize a window along a side of the screen, grab the titlebar
  and drag it to the left or right side until half of the screen is
  highlighted. Using the keyboard, hold down Super and press the Left or
  Right key."

  When the Evolution main window has focus, the Super + Left and Super +
  Right commands are ignored. Additionally, it does not snap to the left
  or right when the titlebar is grabbed and dragged to either side of
  the screen.

  All other GNOME apps do behave as expected. Testing was done with a
  GNOME/Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan  8 13:34:57 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-12 (149 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: Upgraded to artful on 2017-10-21 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1741948/+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 1732454] Re: Reply to message composer window opens behind main evolution window

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

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

Title:
  Reply to message composer window opens behind main evolution window

Status in evolution package in Ubuntu:
  Fix Released

Bug description:
  In evolution, open a message which opens a 'message reader' window.

  In that window press the 'Reply' button - this opens a new 'message
  composer' window in which to type the reply

  In 17.10 running under gnome-shell, the composer window is opened, but
  it also seems that the main Evolution window is also brought to the
  front ... leaving the newly opened composer window behind in the
  window stack.

  Running 17.10 with the old unity does not have this problem

  So I guess this bug may be a problem with gnome-shell rather than
  evolution - something is making it ping the main application window to
  the front.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1732454/+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 1777240] Re: Pop-up window from panel indicator qbirthday too much to the left, not fully visible

2018-06-16 Thread Andre Klapper

Please always provide references to previous discussions about the very
same topic in other venues, to not make people spend time having the
same discussions again and again and again.

https://gitlab.gnome.org/GNOME/gnome-panel/issues/2
https://github.com/lafrech/qbirthday/issues/14
https://github.com/lafrech/qbirthday/issues/13
https://answers.launchpad.net/ubuntu/+question/669732

** Bug watch added: github.com/lafrech/qbirthday/issues #14
   https://github.com/lafrech/qbirthday/issues/14

** Bug watch added: github.com/lafrech/qbirthday/issues #13
   https://github.com/lafrech/qbirthday/issues/13

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

Title:
   Pop-up window from panel indicator qbirthday too much to the left,
  not fully visible

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I managed to install the great birthday reminder tool qbirthday
  (https://github.com/lafrech/qbirthday, Qt port of GBirthday, a GTK
  application) on normal Ubuntu 18.04 (GNOME). It works fine but the
  displayed list (pop-up window) is placed to the left side and
  therefore not fully visible (it works without flaws with the desktop
  MATE), see attached screenshot.

  It is interesting that once every other week, the window opens with
  one click and mostly visible (just a bit too much to the right).

  Thanks for any help and hint in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777240/+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 1732454] Re: Reply to message composer window opens behind main evolution window

2018-06-05 Thread Andre Klapper

For GNOME 3.26 and Evolution 3.26 under Wayland this could have been
https://bugzilla.gnome.org/show_bug.cgi?id=780820 . This should be fixed
in mutter 3.28 and was not an issue in Evolution itself.

Can someone confirm this?

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

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

Title:
  Reply to message composer window opens behind main evolution window

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  In evolution, open a message which opens a 'message reader' window.

  In that window press the 'Reply' button - this opens a new 'message
  composer' window in which to type the reply

  In 17.10 running under gnome-shell, the composer window is opened, but
  it also seems that the main Evolution window is also brought to the
  front ... leaving the newly opened composer window behind in the
  window stack.

  Running 17.10 with the old unity does not have this problem

  So I guess this bug may be a problem with gnome-shell rather than
  evolution - something is making it ping the main application window to
  the front.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1732454/+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 1725315] Re: evolution crashes with SIGSEGV in g_hash_table_lookup_node() when "evolution-indicator" package is installed

** Summary changed:

- evolution crashed with SIGSEGV in g_hash_table_lookup_node()
+ evolution crashes with SIGSEGV in g_hash_table_lookup_node() when 
"evolution-indicator" package is installed

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

Title:
  evolution crashes with SIGSEGV in g_hash_table_lookup_node() when
  "evolution-indicator" package is installed

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Every few minutes, evolution exits the desktop.  Sometimes it will
  only stay up for seconds, and sometimes it exits in the first second.
  Occasionally it stays up for ~20 minutes.  When it is running, it
  seems to function normally.  This machine was upgraded from 17.04
  (where Evolution was stable) to 17.10 release.

  Apport crashdump analysis attached.

  Looking at /var/log/syslog after one of these crashes, I see the
  following entries:

  Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: 
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string 
constant "murrine-scrollbar", expected valid string constant
  Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (254): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (287): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (300): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (417): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: 
segfault at 0 ip   (null) sp 7ffee4f96718 error 14 in 
evolution[557e54c52000+7000]

  It is not clear that the first few syslog entries are related.

  Running evolution with debugging enabled:
  CAMEL_DEBUG=all evolution

  I see the following output when the crash occurs:

  ###
  message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 
(john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not 
(system-flag "deleted")) (not (system-flag "junk" (and  (and  (match-all 
(not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") 
(user-flag "important" (match-all (not (or (= (user-tag "label") "work") 
(user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag 
"label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" 
(match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") 
(user-flag "todo" (match-all (not (or (= (user-tag "label") "later") 
(user-flag "$Labellater") (user-flag "later")))---
 message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 
(john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1
  Segmentation fault (core dumped)

  Not sure if I can provide further information.  This crash is highly-
  repeatable, happening hundreds of times/day.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:50:57 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2017-05-31 (142 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: evolution -c current
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? ()
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gdk_x11_atom_to_xatom_for_display () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from 
/usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so
   org_gnome_mail_new_notify () from 
/usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so
  Title: evolution crashed with SIGSEGV in

[Desktop-packages] [Bug 1741948] Re: Evolution ignores tile window commands in GNOME

What is your screen size? I am afraid that the Evolution window needs a
certain minimum width and if that width is more than 50% of your screen
width this might fail? (Just a theory!)

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

Title:
  Evolution ignores tile window commands in GNOME

Status in evolution package in Ubuntu:
  New

Bug description:
  As per the Help "Ubuntu Desktop Guide -> Desktop -> Applications and
  windows -> Windows and workspaces -> Windows" documentation for "Tile
  windows:"

  "To maximize a window along a side of the screen, grab the titlebar
  and drag it to the left or right side until half of the screen is
  highlighted. Using the keyboard, hold down Super and press the Left or
  Right key."

  When the Evolution main window has focus, the Super + Left and Super +
  Right commands are ignored. Additionally, it does not snap to the left
  or right when the titlebar is grabbed and dragged to either side of
  the screen.

  All other GNOME apps do behave as expected. Testing was done with a
  GNOME/Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan  8 13:34:57 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-12 (149 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: Upgraded to artful on 2017-10-21 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1741948/+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 1743739] Re: Evolution: editing HTML-formatted email slowly leaks memory, freezes computer

If this is reproducible and if your machine allows and if this still
happens in 3.28, could you provide valgrind logs? Something like:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --num-callers=50
--tool=memcheck --leak-check=full --show-leak-kinds=definite --track-
origins=yes evolution &>valgrindevolog.txt

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

Title:
  Evolution: editing HTML-formatted email slowly leaks memory, freezes
  computer

Status in evolution package in Ubuntu:
  New

Bug description:
  This shows up in top as "webkitwebproces". If email editing window is closed, 
memory consumption returns to normal. If I save the email as a draft, then 
re-open it, memory usage is OK. 
  Evolution also freezes for about two-three seconds every now and then when 
trying to type, paste, or erase text in the email. This is on Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jan 17 12:23:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-10 (371 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1743739/+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 1718613] Re: “Unknown option --debug” although listed in manpage

Upstream Evolution has no manpage, as far as I know. Is this an Ubuntu
downstream change?

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

Title:
  “Unknown option --debug” although listed in manpage

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 16.04.3 LTS

  Package version: evolution_3.18.5.2-0ubuntu3.2

  What I expected to happen: When started with “--debug=error_log”,
  evolution should start normally and write an error log to “error_log”.

  What happened instead: “Unknown option --debug” and exit.

  The manpage lists the “--debug” option, the output of “evolution
  --help” does not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1718613/+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 1763691] Re: Copy/paste to message body does not work on Bionic

https://mail.gnome.org/archives/evolution-list/2018-April/msg00086.html
implies that this problem has been fixed in a newer Evolution package on
Ubuntu.

Lukas: Can you confirm?

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

Title:
  Copy/paste to message body does not work on Bionic

Status in evolution package in Ubuntu:
  Incomplete

Bug description:
  Wether using ctrl-v nor context menu or middle mouse button works to
  paste text (plain text) into message body on Ubuntu Bionic.

  (On Debian Stretch it is working fine)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1763691/+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 1773527] Re: Problem of authentification Oauth2 non trouvé

Also see
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1765713
(similar issue)

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

Title:
  Problem of authentification Oauth2 non trouvé

Status in evolution package in Ubuntu:
  New

Bug description:
  Good day.

  I have two computers. One is a desktop with Ubuntu Mate 18.04
  installed onto it. Evolution 3.28.1.2 is running fine on it although I
  had problems overcoming the Oauth2 not found but working fine now

  My second computer is a Laptop HP Pavilion with Ubuntu Mate 18.04 onto
  it.Evolution 3.28.1.2 is installed onto it but I have this attach
  screen appearing saying Oauth2 not found. I used to have it on Linux
  Mint and it did install,set and run flawlessly.

  It tell me to cut and paste the code into the application. What
  application ???

  Also apparently it is suppose to be able to import profiles but I
  never succeded doing that as it does not gives any clue of what the
  name could look like.

  Thanks for reading me and for your help if you can.

  Regards

  Daniel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1773527/+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 1765713] Re: Evolution on restarting for Google imap account chnage automatically receiving/ sending options to OAuth 2.0 and then it does not work

Make sure that Ubuntu packagers include the patch in 
https://gitlab.gnome.org/GNOME/evolution-data-server/commit/5c6b22b8eb72ccac07c7e5867aa6074347f7fd78
 for https://bugzilla.gnome.org/show_bug.cgi?id=795997 (the patch was merged 
after the release of evolution-data-server 3.28 in GNOME). 
And/or, if you did not set up your Google account via "Online Accounts" in the 
control center / settings but instead in Evolution directly, see 
https://bugzilla.gnome.org/show_bug.cgi?id=749974#c4

Also see
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1773527
(similar issue)

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

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

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

Title:
  Evolution on restarting for Google imap account chnage automatically
  receiving/ sending options to OAuth 2.0 and then it does not work

Status in evolution package in Ubuntu:
  New

Bug description:
  Evolution 3.28.1-2 on Ubuntu 18.04.

  On restarting evolution for Google imap account, settings for
  receiving/ sending options change automatically to OAuth 2.0

  And I get the error: 
  "The reported error was “Failed to authenticate: Data source 
“xx...@gmail.com” does not support OAuth 2.0 authentication”."

  If I change the settings again in preferences manually, on restarting
  the account settings for receiving - change itself from Password to
  OAuth2(Google), and for sending - from login to OAuth2(Google).

  Do let me if it is not clear or more information is needed.

  Please suggest a solution.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution 3.28.1-2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 18:45:02 2018
  InstallationDate: Installed on 2018-04-16 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1765713/+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 1707667] Re: evolution segfault on startup

Please provide a backtrace of the segmentation fault. See
https://wiki.ubuntu.com/Backtrace and
https://wiki.ubuntu.com/DebuggingGNOME - thanks!

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

Title:
  evolution segfault on startup

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  I'm using awesomewm and not any of the full desktop environments. I
  have this same configuration on my laptop and Evolution runs without
  problems.

  Terminal output:

  > evolution

  ** (evolution:10624): WARNING **: Couldn't register with accessibility
  bus: Did not receive a reply. Possible causes include: the remote
  application did not send a reply, the message bus security policy
  blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (evolution:10624): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' 
failed
  [1]10624 segmentation fault (core dumped)  evolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution 3.18.5.2-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Jul 31 08:16:00 2017
  InstallationDate: Installed on 2015-06-14 (777 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: evolution
  UpgradeStatus: Upgraded to xenial on 2017-01-18 (194 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1707667/+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 1773527] Re: Problem of authentification Oauth2 non trouvé

Make sure that Ubuntu packagers include the patch in 
https://gitlab.gnome.org/GNOME/evolution-data-server/commit/5c6b22b8eb72ccac07c7e5867aa6074347f7fd78
 for https://bugzilla.gnome.org/show_bug.cgi?id=795997 (the patch was merged 
after the release of evolution-data-server 3.28 in GNOME). 
And/or, if you did not set up your Google account via "Online Accounts" in the 
control center / settings but instead in Evolution directly, see 
https://bugzilla.gnome.org/show_bug.cgi?id=749974#c4

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

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

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

Title:
  Problem of authentification Oauth2 non trouvé

Status in evolution package in Ubuntu:
  New

Bug description:
  Good day.

  I have two computers. One is a desktop with Ubuntu Mate 18.04
  installed onto it. Evolution 3.28.1.2 is running fine on it although I
  had problems overcoming the Oauth2 not found but working fine now

  My second computer is a Laptop HP Pavilion with Ubuntu Mate 18.04 onto
  it.Evolution 3.28.1.2 is installed onto it but I have this attach
  screen appearing saying Oauth2 not found. I used to have it on Linux
  Mint and it did install,set and run flawlessly.

  It tell me to cut and paste the code into the application. What
  application ???

  Also apparently it is suppose to be able to import profiles but I
  never succeded doing that as it does not gives any clue of what the
  name could look like.

  Thanks for reading me and for your help if you can.

  Regards

  Daniel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1773527/+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 1750146] Re: Xbox (One) Wireless Controller won't connect

2018-05-09 Thread Andre Lima

I'm using this workaround as a permanent solution. (while waiting for
kernel patches for this problem)

- Install sysfsutils. (with synaptic or on terminal)
- edit this file with sudo - sudo nano /etc/sysfs.conf
- add this line at the end - /module/bluetooth/parameters/disable_ertm = 1
- reboot. 

Now the controller is working without problems on Ubuntu 18.04.

On ubuntu 16.04.4 the controller start moving the mouse after the first 
workaround. If it happens use this: 
- On terminal type - xinput list - and copy how your system recognize the 
gamepad. Generally is something 
  like "Xbox Wireless Controller"
- Open a terminal and type - xinput --set-prop "Xbox Wireless Controller" 
"Device Enabled" 0
- Repeat that second trick every time you got the problem.

Regards! Hope it helps.

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

Title:
  Xbox (One) Wireless Controller won't connect

Status in gnome-control-center:
  Confirmed
Status in Linux:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+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 1750146] Re: Xbox (One) Wireless Controller won't connect

2018-04-19 Thread Andre Lima

Hello Guys!

I have the same problem in Ubuntu 16.04.4 x64. I'm using the white Xbox
One Controller. The light just start blinking and never paired the
controller.

Researching on forums i find a trick to solve the problem. But that just
works one time. After that the problem returns.

The trick is: edit this file -> /etc/sysfs.conf 
  adding this line -> module/bluetooth/parameters/disable_ertm = 1

So, maybe it's an error with bluetooth ERTM (Enhanced Re-Transmission
Mode a L2CAP Bluetooth stack feature).


Best Regards!

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

Title:
  Xbox (One) Wireless Controller won't connect

Status in gnome-control-center:
  Confirmed
Status in Linux:
  Unknown
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+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 1725865] Re: Network shows Cable Unplugged

2018-01-14 Thread Andre Klapper

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=792506
   Importance: Unknown
   Status: Unknown

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

Title:
  Network shows Cable Unplugged

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  This was working perfectly on 17.04, but after installing 17.10 from
  scratch, the wired network is not detected. It simply shows as Cable
  Unplugged when in fact there is the same cable still connected
  directly to the router. This same computer has Windows 10 and it
  detects the network correctly. I also tested Fedora and it detected
  the network correctly (The wired one). I am currently using only the
  Wireless connection because of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 17:59:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   ecb8e125-48ff-4994-94c8-bdf3731334ce  
/org/freedesktop/NetworkManager/ActiveConnection/13 
   enp0s31f6  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.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1725865/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2017-01-24 Thread Andre Mack

For me the same error: the internal microphone is not recognized. I have
an Acer Aspire VN7-572G-56VP with ALS255.

An external headset works when I write in the file: 
'/etc/modprobe.d/alsa-base.conf' the following entries: 
'options snd-hda-intel model = dell-headset-multi'

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1637988] Re: gvfsd-nfs not present in gvfs-backends, why?

2017-01-10 Thread Andre

Just got here when trying to migrate a user from Solaris to Ubuntu
(16.04).

It would be nice to get at least some statement why it isn't
included/when it might be included.

>From what I can see 16.04.1 has gvfs 1.28.2 (e.g. >1.23.90) and libnfs 1.9.8 
>(e.g. >1.9.7).
That suggests that all prerequisites are covered based on the nfs support 
announcment post 
https://mail.gnome.org/archives/gvfs-list/2015-March/msg0.html .

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

Title:
  gvfsd-nfs not present in gvfs-backends, why?

Status in gvfs package in Ubuntu:
  New

Bug description:
  We're at the end of 2016 and it's still impossible to browse nfs
  shares through nautilus, even though this is supported since version
  1.23 of gvfs. What's keeping gvfsd-nfs out of the gvfs-backends
  package?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+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 1640971] Re: Evolution consumes a huge amount of ram even if it´s closed

2016-12-12 Thread Andre Klapper

Please provide steps to reproduce seeing the problem. 
When Evolution is closed and not running I don't know where I could see/check 
that it consumes 200MB...

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

Title:
  Evolution consumes a huge amount of ram even if it´s closed

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Evolution consumes a minimum of 200 MB even if its closed, that must
  be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1640971/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-11-14 Thread Andre Hufschmidt

Other sites affected (Xenial): amazon.de 
In addition my banks' online banking portal.

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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

Re: [Desktop-packages] [Bug 163963] Re: Copy to iPod fail causes hundreds of popup windows

2016-10-20 Thread andre

So that took nearly 10 years!

On 21/10/2016 8:05 am, "Bug Watch Updater" <163...@bugs.launchpad.net>
wrote:

> ** Changed in: rhythmbox
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/163963
>
> Title:
>   Copy to iPod fail causes hundreds of popup windows
>
> Status in Rhythmbox:
>   Confirmed
> Status in rhythmbox package in Ubuntu:
>   Triaged
>
> Bug description:
>   Binary package hint: rhythmbox
>
>
>   If I drag 200 songs to an ipod which has space for only 10 of them, I am
> presented with 190 pop up windows informing me that I do not have enough
> space.
>
>   One would suffice! ;)
>
>   ProblemType: Bug
>   Architecture: i386
>   Date: Mon Nov 19 18:34:03 2007
>   DistroRelease: Ubuntu 7.10
>   ExecutablePath: /usr/bin/rhythmbox
>   NonfreeKernelModules: nvidia
>   Package: rhythmbox 0.11.2-0ubuntu4
>   PackageArchitecture: i386
>   ProcCmdline: rhythmbox
>   ProcCwd: /home/mcrawfor
>   ProcEnviron:
>PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/
> sbin:/bin:/usr/bin/X11:/usr/games
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: rhythmbox
>   Uname: Linux Green 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007
> i686 GNU/Linux
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/rhythmbox/+bug/163963/+subscriptions
>

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

Title:
  Copy to iPod fail causes hundreds of popup windows

Status in Rhythmbox:
  Confirmed
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  
  If I drag 200 songs to an ipod which has space for only 10 of them, I am 
presented with 190 pop up windows informing me that I do not have enough space.

  One would suffice! ;)

  ProblemType: Bug
  Architecture: i386
  Date: Mon Nov 19 18:34:03 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: nvidia
  Package: rhythmbox 0.11.2-0ubuntu4
  PackageArchitecture: i386
  ProcCmdline: rhythmbox
  ProcCwd: /home/mcrawfor
  ProcEnviron:
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  Uname: Linux Green 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/163963/+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 1537482] Re: nm-applet regularly crashes at logon, in combination with failing 3G connection

2016-08-30 Thread Andre

What seemed to work for me is to modify the NetworkManager systemd
service (/lib/systemd/system/NetworkManager.service) and add
"ModemManager.service" to the "After" list:

After=network-pre.target dbus.service ModemManager.service

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

Title:
  nm-applet regularly crashes at logon, in combination with failing 3G
  connection

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

Bug description:
  I'm running Ubuntu 15.10 with network-manager 1.0.4-0ubuntu5.2.

  Regularly (if not always) the nm-applet icon is not showing in the
  Unity panel after logon.  Syslog shows these error messages:

  Jan 23 21:07:21 desk1 gnome-session[3904]: (nm-applet:4812): 
nm-applet-WARNING **: Could not find ShellVersion property on org.gnome.Shell 
after 5 tries
  Jan 24 09:42:37 desk1 gnome-session[19922]: (nm-applet:20700): 
libnm-glib-WARNING **: Error in get_property: Method "Get" with signature "ss" 
on interface "org.freedesktop.DBus.Properties" doesn't exist
  Jan 24 09:42:38 desk1 gnome-session[19922]: (nm-applet:20700): 
nm-applet-WARNING **: Cannot grab information for modem at 
/org/freedesktop/ModemManager1/Modem/0: No ModemManager support
  Jan 24 09:42:38 desk1 gnome-session[19922]: (nm-applet:20700): 
nm-applet-WARNING **: ModemManager is not available for modem at 
/org/freedesktop/ModemManager1/Modem/0
  Jan 24 09:42:38 desk1 gnome-session[19922]: message repeated 3 times: [ 
(nm-applet:20700): nm-applet-WARNING **: ModemManager is not available for 
modem at /org/freedesktop/ModemManager1/Modem/0]
  Jan 24 09:42:38 desk1 gnome-session[19922]: 
nm-applet:ERROR:applet-device-broadband.c:644:get_icon: assertion failed: (info)

  Manually starting nm-applet from a Terminal works, sometimes however
  only after some attempts where error messages similar to the ones
  above are shown (btw, even when succeeding, the first 2 warning/error
  messages on the ss signature and the ShellVersion show up). Once nm-
  applet is started, the 3G modem connection signal bars are shown and
  sometimes indeed a network connection (through 3G modem) is available.
  Often however, several manual disconnect and subsequent connect
  operations are needed before having the  network connection really up
  and running.

  I suspect hence that there is an issue with my ModemManager and/or
  NetworkManager configuration or implementation, and that nm-applet is
  not robust enough to properly deal with these connection failures.

  I have no issues on another Ubuntu 15.10 system with the same version
  of network-manager installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1537482/+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 1596361] Re: MFP M476DW Error 5002 on status / No toner levels in HP Device Manager

2016-08-04 Thread Andre Hufschmidt

Thanks a lot! 
Much appreciated.

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

Title:
  MFP M476DW Error 5002 on status / No toner levels in HP Device Manager

Status in HPLIP:
  Fix Committed
Status in hplip package in Ubuntu:
  New

Bug description:
  HP Device Manager always showed Error 5002 (device is busy powered
  down or unplugged) as Status for my M476DW. In addition, under
  supplies, no toner levels were shown.

  I have modified the "[hp_color_laserjet_mfp_m476dw]" entry in
  /usr/share/hplip/data/models/models.dat. The full entry I have
  attached below.

  By changing status-type=12 to status-type=10 error 5002 disappeared.
  Adding the r0-agent* entries made the supplies display (and hp-levels)
  work.

  [hp_color_laserjet_mfp_m476dw]
  align-type=0
  clean-type=0
  color-cal-type=0
  copy-type=0
  embedded-server-type=0
  fax-type=7
  fw-download=False
  icon=HP_Color_LaserJet_2840.png
  io-mfp-mode=1
  io-mode=1
  io-support=14
  job-storage=0
  linefeed-cal-type=0
  model1=HP Color Laserjet Pro MFP M476dw
  monitor-type=0
  panel-check-type=0
  pcard-type=0
  plugin=1
  plugin-reason=64
  power-settings=0
  ppd-name=color_laserjet_pro_mfp_m476
  pq-diag-type=0
  r-type=0
  r0-agent1-kind=4
  r0-agent1-sku=CB380A
  r0-agent1-type=1
  r0-agent2-kind=4
  r0-agent2-sku=CB381A
  r0-agent2-type=4
  r0-agent3-kind=4
  r0-agent3-sku=CB383A
  r0-agent3-type=5
  r0-agent4-kind=4
  r0-agent4-sku=CB382A
  r0-agent4-type=6
  scan-src=3
  scan-type=5
  status-battery-check=0
  status-dynamic-counters=0
  status-type=12
  support-released=True
  support-subtype=447b
  support-type=2
  support-ver=3.14.4
  tech-class=Postscript
  tech-subclass=Normal
  tech-type=4
  usb-pid=342a
  usb-vid=3f0
  wifi-config=3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1596361/+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 1596361] Re: MFP M476DW Error 5002 on status / No toner levels in HP Device Manager

2016-06-27 Thread Andre Hufschmidt

** Also affects: hplip (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  MFP M476DW Error 5002 on status / No toner levels in HP Device Manager

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  HP Device Manager always showed Error 5002 (device is busy powered
  down or unplugged) as Status for my M476DW. In addition, under
  supplies, no toner levels were shown.

  I have modified the "[hp_color_laserjet_mfp_m476dw]" entry in
  /usr/share/hplip/data/models/models.dat. The full entry I have
  attached below.

  By changing status-type=12 to status-type=10 error 5002 disappeared.
  Adding the r0-agent* entries made the supplies display (and hp-levels)
  work.

  [hp_color_laserjet_mfp_m476dw]
  align-type=0
  clean-type=0
  color-cal-type=0
  copy-type=0
  embedded-server-type=0
  fax-type=7
  fw-download=False
  icon=HP_Color_LaserJet_2840.png
  io-mfp-mode=1
  io-mode=1
  io-support=14
  job-storage=0
  linefeed-cal-type=0
  model1=HP Color Laserjet Pro MFP M476dw
  monitor-type=0
  panel-check-type=0
  pcard-type=0
  plugin=1
  plugin-reason=64
  power-settings=0
  ppd-name=color_laserjet_pro_mfp_m476
  pq-diag-type=0
  r-type=0
  r0-agent1-kind=4
  r0-agent1-sku=CB380A
  r0-agent1-type=1
  r0-agent2-kind=4
  r0-agent2-sku=CB381A
  r0-agent2-type=4
  r0-agent3-kind=4
  r0-agent3-sku=CB383A
  r0-agent3-type=5
  r0-agent4-kind=4
  r0-agent4-sku=CB382A
  r0-agent4-type=6
  scan-src=3
  scan-type=5
  status-battery-check=0
  status-dynamic-counters=0
  status-type=12
  support-released=True
  support-subtype=447b
  support-type=2
  support-ver=3.14.4
  tech-class=Postscript
  tech-subclass=Normal
  tech-type=4
  usb-pid=342a
  usb-vid=3f0
  wifi-config=3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1596361/+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 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3

I can't figure out how to edit my comments, so big apology in advance.
My work around works if and only if gcc and g++ have not been changed or
restored to the default version (currently v5.3.1). In other word,
changing the default system compiler would create this type of issue, so
this isn't really a bug on your side. You may close this bug report,
unless you feel that nvidia-361 should be able to build on any gcc/g++
versions.

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  when gcc and g++ are set to v4.8 instead of default v5.3

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1591785/+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 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3

Work-around confirmed: After adding these two lines in my ~/.bashrc

# For Ubuntu 12.04 backward compatibility.
export CC=gcc-4.7
export CXX=g++-4.7

Then I can build our products with the correct glibc version for Ubuntu
12.04, while gcc-5.3 is used during the updates and via sudo.

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  when gcc and g++ are set to v4.8 instead of default v5.3

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1591785/+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 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3

Do any of you have any recommendations on how to safely build
static/shared libraries for Ubuntu 12.04 on Ubuntu 16.04 without
breaking closed source packages such as the nvidia driver? I'm thinking
of setting ${CC} and ${CXX} in my ~/.bashrc to point to gcc/g++ 4.8
instead of setting them globally via update-alternative. This should
probably be the best solution to ensure that this doesn't happen again.

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  when gcc and g++ are set to v4.8 instead of default v5.3

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1591785/+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 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3

** Summary changed:

- nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
+ nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc 
and g++ are set to v4.8 instead of default v5.3

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  when gcc and g++ are set to v4.8 instead of default v5.3

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1591785/+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 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build

2016-06-12 Thread Mathieu-Andre Chiasson

Found the issue. I set my gcc and g++ to 4.8 or 4.9 via update-
alternative because we to support Ubuntu 12.04. I moved gcc and g++ back
to the default 5.3, did `apt-get remove nvidia-* --purge`, then `apt-get
install nvidia-361` and it worked.

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1591785/+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 1591785] [NEW] nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build

2016-06-12 Thread Mathieu-Andre Chiasson

Public bug reported:

after a routine system update, Linux kernel was upgraded to
4.4.0-24-generic. Since then, the nvidia graphic drivers simply refuses
to build:


> Building initial module for 4.4.0-24-generic
> Error! Bad return status for module build on kernel: 4.4.0-24-generic (x86_64)
> Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-361 361.42-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
DKMSKernelVersion: 4.4.0-24-generic
Date: Sun Jun 12 19:45:40 2016
DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
InstallationDate: Installed on 2015-10-31 (225 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
PackageVersion: 361.42-0ubuntu2
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: nvidia-graphics-drivers-361
Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

** Affects: nvidia-graphics-drivers-361 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

** Attachment added: "nvidia-361 make.log"
   https://bugs.launchpad.net/bugs/1591785/+attachment/4682454/+files/make.log

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1591785/+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 1557370] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

I cannot find the stacktrace in comment 3 in upstream
bugzilla.gnome.org.

Note the #10 config_data_get_timezone () at config-data.c:73 in the
trace.

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

Title:
  evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

Status in evolution package in Ubuntu:
  New

Bug description:
  After rebooting my PC I was presented with an error report dialogue
  which lead me to filing this report.  I do not know at what point the
  error was originally generated.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libevolution 3.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-67.87~14.04.1-generic 3.16.7-ckt24
  Uname: Linux 3.16.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Mar 15 08:31:41 2016
  ExecutablePath: /usr/lib/evolution/3.10/evolution-alarm-notify
  InstallationDate: Installed on 2015-03-12 (368 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/3.10/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1557370/+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 1511333] Re: Spanish translate template evolution wily 15.10

Javier: Did you contact the Spanish translators? Is anything else needed
in this bug report?

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

Title:
  Spanish translate template evolution wily 15.10

Status in evolution package in Ubuntu:
  New

Bug description:
  I have been translating part of the evolution of Spanish template. It
  remained to translate strings 574,  and I translated 414 but take a
  week now and no one has gone to the changed state.

  They can pass the state changed to continue the translation, and
  nobody answers me and the translation is blocked.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1511333/+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 1516483] Re: evolution fails to start

Hi checoimg, thanks for reporting this.

The terminal output provided here only has the relevant line
"Segmentation fault (core dumped)".

Journal says:

hostname org.gnome.evolution.dataserver.Calendar7[1296]: 
(evolution-calendar-factory-subprocess:1651): GLib-GIO-WARNING **: Error 
releasing name 
org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx1581x4: The 
connection is closed
hostname org.gnome.evolution.dataserver.AddressBook9[1296]: 
(evolution-addressbook-factory-subprocess:1657): GLib-GIO-WARNING **: Error 
releasing name 
org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx1631x2: The 
connection is closed

If this still happens, could you provide a backtrace? See
https://wiki.ubuntu.com/Backtrace and
https://wiki.ubuntu.com/DebuggingProgramCrash for more information.
Thanks in advance!

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

Title:
  evolution fails to start

Status in evolution package in Ubuntu:
  New

Bug description:
  Terminal output :

  (evolution:5757): Gtk-WARNING **: Failed to register client:
  GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to
  register client

  (evolution:5757): camel-WARNING **: Failed to initialize NSS SQL database in 
sql:/etc/pki/nssdb: NSS error -8126
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: evolution 3.16.5-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 15 22:48:00 2015
  InstallationDate: Installed on 2015-11-14 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1516483/+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 1510658] Re: evolution crashes when clicked on a specific message