[Desktop-packages] [Bug 1966529] Re: xdg-desktop-portal-gnome crashed with SIGSEGV in gtk_tree_view_update_rubber_band_selection_range.constprop.0()

2023-01-25 Thread Mat 
Could GTK 4.6.9 be packaged for Ubuntu 22.04 in the near future to
resolve this issue? Thank you.

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

Title:
  xdg-desktop-portal-gnome crashed with SIGSEGV in
  gtk_tree_view_update_rubber_band_selection_range.constprop.0()

Status in GTK+:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Committed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/44bd0ca893055a3c496a03038023a8d0d4860802

  ---

  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  xdg-desktop-portal-gnome:
    Instalado: 42.0.1-1
    Candidato: 42.0.1-1
    Tabela de versão:
   *** 42.0.1-1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal-gnome 42.0.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Mar 25 20:29:58 2022
  ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome
  ProcCmdline: /usr/libexec/xdg-desktop-portal-gnome
  SegvAnalysis:
   Segfault happened at: 0x7fe18cf2c03f:movzwl (%rsi),%edx
   PC (0x7fe18cf2c03f) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal-gnome
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: xdg-desktop-portal-gnome crashed with SIGSEGV in g_signal_emit_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1966529/+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 2002228] Re: incorrect maximum window geometry on secondary monitor makes contextmenu of gtk4 apps unusable

2023-01-11 Thread Mat 
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4790 was backported
to GTK 4.8.3.

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

Title:
  incorrect maximum window geometry on secondary monitor makes
  contextmenu of gtk4 apps unusable

Status in gtk4 package in Ubuntu:
  New
Status in sway package in Ubuntu:
  New

Bug description:
  since upgrade to 22.10 gtk4 apps like nautilus on sway on the external
  monitors are restricted to size of the resolution of the first monitor
  (which is the laptop lcd, hence smaller) which results in broken apps
  contextmenu (like renaming files in nautilus is impossible).

  There is a bugreport in sway for it 
https://github.com/swaywm/sway/issues/7000 but i dont quite understand where 
the correct fix should be located: sway, wlroots, gtk4?
  However there seems to be a fix (workaround) for gtk4: 
https://gitlab.gnome.org/GNOME/gtk/-/issues/5402   -> 
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4790

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: sway 1.7-5 [modified: usr/share/wayland-sessions/sway.desktop]
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  Uname: Linux 5.19.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Jan  8 01:04:27 2023
  InstallationDate: Installed on 2022-03-24 (290 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: sway
  UpgradeStatus: Upgraded to kinetic on 2022-10-20 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2002228/+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 1668309] Re: Scaling on xps13 means only a part of the screen is visible at any time.

2019-06-26 Thread No Mat 
Can confirm comment #5. Fails as described on a Macbook Pro with Retina
display (2560x1600) in Ubuntu 18.04.

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

Title:
  Scaling on xps13 means only a part of the screen is visible at any
  time.

Status in vino package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. On a 4K system
  2. Do a default install of the current iso for Zesty
  3. Make sure scalling is set to 2
  4. Once in the user session activate desktop-sharing
  5. Connect from another machine

  EXPECTED:
  I expect to see the whole screen or for the screen to scroll to allow access 
to the whole screen

  ACTUAL:
  Top left hand quarter is the only thing visible and no changes to remina make 
it better.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2016-11-09 (109 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161109)
  Package: vino 3.8.1-0ubuntu12
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1668309/+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-07-29 Thread mat 
Just for your information, I have the same issue on my laptop (HP ZBook
G3) since I upgrade my OS to 18.04.

-- 
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 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/network-manager/+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 1726922] Re: gnome-calendar keeps asking for my google password

2018-01-07 Thread mat 
On this page

https://askubuntu.com/questions/967137/calendar-constantly-requiring-
google-authentication-on-17-10

a solution is suggested:


"I was having the same problem and resolve it by deleting the
configuration files of Evolution. Do this:

rm -rf ./.config/goa-1.0/accounts.conf
rm -rf ./.config/evolution
rm -rf ./.local/share/evolution"


Worked for me

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

Title:
  gnome-calendar keeps asking for my google password

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Once in a while, perhaps two or three times a day gnome-calendar pops
  up a dialog asking for my google password.

  I have two online google accounts set, but the problem begun after I
  upgraded from zesty, where I had those two accounts as well. They
  didn't appear in the new settings application, but still gnome-
  calendar was asking for the password. One of them has two phase
  authentication set and the other not.

  After I added the online accounts in the new settings app, the
  calendar is synchronized but it still popping the authentication
  window and is very annoying.

  bug report in gnome-calendar:
  https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726922

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.26.2-1
  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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:45:09 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-04-14 (193 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=es_UY:es
   LANG=es_UY.UTF-8
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726922/+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 1556357] Re: WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli resume?

2016-10-30 Thread Stew Mat 
*** This bug is a duplicate of bug 1585863 ***
https://bugs.launchpad.net/bugs/1585863

I'm having this with my Lenovo Thinkpad T420. It happens around 1 time
out of 3. Sometimes the connected wifi icon is replaced by the ethernet
one, sometimes by the unconnected wifi icon.

"wpa_cli resume" fixes it.

Thanks @Haw for the workaround.

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

Title:
  WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli
  resume?

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

Bug description:
  Hi,

  I'm constantly having issues where my WiFi connection doesn't re-
  establish after resuming from suspend. I think it may be a race where
  the interface isn't ready yet and systemd-sleep calls /lib/systemd
  /system-sleep/wpasupplicant (which is a wrapper to wpa_cli).

  I normally restart NetworkManager but then found that calling 'wpa_cli
  resume' works also.

  Here's the logs:

  | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked 
min/max coordinates: x [1024..5112], y [2024..4832]
  | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 
562.709 msecs
  | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed
  | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed
  | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to 
non-global ctrl_ifname: (nil)  error: No such file or directory
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 255.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed 
anymore. Stopping.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to 
inactive unit systemd-suspend.service. Stopping, too.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   wake requested 
(sleeping: yes  enabled: yes)
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   waking up...
  | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' 
finished.
  | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   NetworkManager 
state is now DISCONNECTED
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to 
construct signal
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read 
interface p2p-dev-wlp3s0 flags: No such device
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
supplicant interface state: starting -> ready
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   Device 'wlp3s0' 
has no connection; scheduling activate_check in 0 seconds.
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready


  Thanks,

  Haw
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-24 (687 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: wpasupplicant
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (p

[Desktop-packages] [Bug 1575614] Re: [SRU]Can't select secret key for TLS auth for 802.1X authentication

2016-06-02 Thread Mat 
i've tested the new version, but I can't select my private key either.
it's a .key file in my case.

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

Title:
  [SRU]Can't select secret key for TLS auth for 802.1X authentication

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

Bug description:
  [Impact]

  Users cannot select TLS certificate when connecting to a network that
  requires TLS type 802.1X authentication

  [Test case]
  STR:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wired connection
  4. Go to 802.1x tab
  5. Check the Use 802.1X checkbox
  6. Choose TLS
  7. Click on Secret key button
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  For wifi connection:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wi-Fi connection
  4. Go to Wi-Fi Security tab
  5. Select WPA & WPA2 Enterprise in the drop-down list
  6. Choose TLS
  7. Click on (None) next to Private key
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  [Regression Potential]
  The fix is quite straight forward and the possibility of causing regression 
is limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1575614/+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 1482680] [NEW] libnl-route-3-200 missing symlink

2015-08-07 Thread Mat 
Public bug reported:

$ dpkg -L libnl-route-3-200
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.16.1
/usr/share
/usr/share/doc
/usr/share/doc/libnl-route-3-200
/usr/share/doc/libnl-route-3-200/copyright
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
/usr/share/doc/libnl-route-3-200/changelog.Debian.gz

There should be a symlink:
/usr/lib/x86_64-linux-gnu/libnl-route-3.so -> 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
otherwise compilers (gcc) complain that they can't find -lnl-route-3

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libnl-route-3-200 3.2.21-1
ProcVersionSignature: Ubuntu 3.19.0-21.21~14.04.1-lowlatency 3.19.8
Uname: Linux 3.19.0-21-lowlatency x86_64
NonfreeKernelModules: ue_ip
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Aug  7 16:58:29 2015
Dependencies:
 gcc-4.9-base 4.9.1-0ubuntu1
 libc6 2.19-0ubuntu6.6
 libgcc1 1:4.9.1-0ubuntu1
 libnl-3-200 3.2.21-1
 multiarch-support 2.19-0ubuntu6.6
InstallationDate: Installed on 2015-05-22 (77 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: libnl3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  libnl-route-3-200 missing symlink

Status in libnl3 package in Ubuntu:
  New

Bug description:
  $ dpkg -L libnl-route-3-200
  /.
  /usr
  /usr/lib
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.16.1
  /usr/share
  /usr/share/doc
  /usr/share/doc/libnl-route-3-200
  /usr/share/doc/libnl-route-3-200/copyright
  /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  /usr/share/doc/libnl-route-3-200/changelog.Debian.gz

  There should be a symlink:
  /usr/lib/x86_64-linux-gnu/libnl-route-3.so -> 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  otherwise compilers (gcc) complain that they can't find -lnl-route-3

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libnl-route-3-200 3.2.21-1
  ProcVersionSignature: Ubuntu 3.19.0-21.21~14.04.1-lowlatency 3.19.8
  Uname: Linux 3.19.0-21-lowlatency x86_64
  NonfreeKernelModules: ue_ip
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  7 16:58:29 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.6
   libgcc1 1:4.9.1-0ubuntu1
   libnl-3-200 3.2.21-1
   multiarch-support 2.19-0ubuntu6.6
  InstallationDate: Installed on 2015-05-22 (77 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: libnl3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1482680/+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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-07-27 Thread mat 
What I don't understand, the proposed drivers are they already implemented
in the routine update (I thought they had to be updated manually)?
Otherwise I might have had a completely different problem with the
bumblebee and nvidia drivers, solved by chance with Your approach.

2015-07-27 18:33 GMT+02:00 KennoVO :

> Mat, I am happy you got past your blank-screen problem, even though the
> things mentioned in my previous post may or may not have played a role
> in solving it.
>
> To be perfectly clear toward other people who come across this
> discussion, the points (1)-(4) in my previous post DO NOT represent a
> step-by-step solution for getting a graphical desktop back after running
> a routine kernel upgrade. They are a few things *I* tried for the
> specific case of APPLYING THE DRIVERS FROM TRUSTY-PROPOSED TO AN
> EXISTING BUMBLEBEE SETUP. And it's quite likely some of them are not
> useful or even harmful.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1411919).
> https://bugs.launchpad.net/bugs/1431753
>
> Title:
>   Nvidia binary driver FTBS due to DKMS layer violation
>
> Status in nvidia-graphics-drivers-331 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-340 package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-346 package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-331 source package in Trusty:
>   Triaged
> Status in nvidia-graphics-drivers-331-updates source package in Trusty:
>   Triaged
> Status in nvidia-graphics-drivers-340 source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-340-updates source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-346 source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-346-updates source package in Trusty:
>   Fix Committed
>
> Bug description:
>   Filing this against the 340-updates version but possibly the same
>   applies to older versions, too. The nvidia source package produces two
>   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
>   The problem is that the DKMS build of the nvidia-uvm module runs
>   compile steps inside the nvidia modules build directory. This is
>   violating the DKMS assumption that each module can be build
>   independently (there is no way of describing cross-modules
>   dependencies and even more important, the autoinstall step after a new
>   kernel is installed will run the modules build in parallel).
>
>   Since nvidia and nvidia-uvm are very dependent on each other the right
>   course of action seems to be to combine both sources in one DKMS
>   module that produces two kernel modules (this is supported by DKMS).
>   For the transition this resulting dkms package needs to have a
>   breaks/replaces for the nvidia-uvm package.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
>


-- 
Dr. M. Tiede


Clausola di Riservatezza

Si fa presente che tutte le notizie (nomi, fatti, notizie sanitarie, etc)
contenute in questo messaggio sono sottoposte alla normativa sulla tutela
della riservatezza (D. Lgs 196/2003) e in particolare sulla tutela dei dati
sensibili. E' pertanto richiesta ai destinatari della presente la massima
riservatezza nel trattare la documentazione. Se il ricevente non è il
destinatario diretto del presente messaggio è pregato di contattare
l'originario mittente e di cancellare questo messaggio ed ogni suo allegato
dal sistema di posta, sono vietati l'uso, la riproduzione e la stampa di
questo messaggio e di ogni suo allegato, nonché la diffusione del
loro contenuto a qualsiasi altro soggetto.

This e-mail message and any files transmitted with it may contain
confidential information intended only for the person(s) to whom it is
addressed. If you are not the intended recipient, you are hereby notified
that any use or distribution of this e-mail is strictly prohibited: please
notify the sender and delete the original message.

Thank you.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-07-27 Thread mat 
After routine kernel-update yesterday, today blank screen like KennoVO,
bongos rumbling on start but without video.

After booting with previous kernel I applied the solutions KennoVO
suggested, (2)-(3)-(4) but not (1) as I didn't know what I was doing and
didn't understand how it had to be done. But in the end after reboot it
worked. No errors or other failures.

I must say that while Ubuntu 10 and 12 were simply great, rapid booting,
almost no bugs, this 14.04 has caused me a lot of grievance - slow on boot,
updates that cause more problems than they solve, updates almost every time
I turn on the computer (just like Windows...). Iif I didn't have an allergy
towards Windows I would long have turned my back on Ubuntu. And if You add
to it that Chromium has a sloppy Flash-player that doesn't work half the
times, and the alternative Firefox is pretty slow.
Takes a lot of passion to stick to Ubuntu...

2015-07-27 1:35 GMT+02:00 KennoVO :

> Fix confirmed on 2 very different machines both running Ubuntu 14.04
> "Trusty" with the 3.13 kernel. Detailed notes:
>
> AMD workstation with only a discrete nvidia GPU (nothing else)
> 
> Synaptic complained about conflicts when selecting updated driver from
> trusty-proposed (something involving nvidia-libopencl1-* vs
> nvidia-opencl-icd-* IIRC). Installing through aptitude worked better. No
> further issues when rebooting, updating the kernel and rebooting again.
>
> Intel laptop running bumblebee
> ==
> Blank screen after updating. Solutions tried:
> (1) starting the kernel with nogpumanager and removing /etc/X11/xorg.conf
> generated by gpu-manager
> (2) removing the newly created file /etc/prime-discrete
> (3) sudo sed -i 's/-current/-346-updates/g' /etc/bumblebee/bumblebee.conf
> (4) adding lines for 340 and 346 to /etc/modprobe.d/bumblebee.conf
>
> Applying all of the above fixed the problem, and (1)-(3) without (4)
> didn't, so it's very likely that (4) is necessary. What I cannot tell is
> which of (1)-(3) are also necessary and which are optional.(*) Bottom
> line is that special precautions should be taken to prevent bumblebee
> from breaking when rolling this out.
>
> (*) I could of course figure that out by reverting the changes one-by-
> one, but this bug already robbed me of an outrageous amount of my time
> and all of my goodwill, so you're on your own. Thanks a lot for finally
> fixing it, though.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1411919).
> https://bugs.launchpad.net/bugs/1431753
>
> Title:
>   Nvidia binary driver FTBS due to DKMS layer violation
>
> Status in nvidia-graphics-drivers-331 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-340 package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-346 package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-331 source package in Trusty:
>   Triaged
> Status in nvidia-graphics-drivers-331-updates source package in Trusty:
>   Triaged
> Status in nvidia-graphics-drivers-340 source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-340-updates source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-346 source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-346-updates source package in Trusty:
>   Fix Committed
>
> Bug description:
>   Filing this against the 340-updates version but possibly the same
>   applies to older versions, too. The nvidia source package produces two
>   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
>   The problem is that the DKMS build of the nvidia-uvm module runs
>   compile steps inside the nvidia modules build directory. This is
>   violating the DKMS assumption that each module can be build
>   independently (there is no way of describing cross-modules
>   dependencies and even more important, the autoinstall step after a new
>   kernel is installed will run the modules build in parallel).
>
>   Since nvidia and nvidia-uvm are very dependent on each other the right
>   course of action seems to be to combine both sources in one DKMS
>   module that produces two kernel modules (this is supported by DKMS).
>   For the transition this resulting dkms package needs to have a
>   breaks/replaces for the nvidia-uvm package.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
>


-- 
Dr. M. Tiede


Clausola di Riservatezza

Si fa presente che tutte le notizie (nomi, fatti, notizie sanitarie, etc)
contenute in questo messaggio sono sottoposte alla normativa sul

[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"

2015-05-05 Thread mat 
It's higly annoying, half a year and the error still popps up every
update. I'll revert to Ubuntu 12, Ubuntu 14 has become a mayor delusion
- slow, constant updates with rebbot, like or worse than Windows.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: "objdump: '... .tmp_nv.o': No such
  file"

Status in NVIDIA Drivers Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released

Bug description:
  **WARNING:** This bug has been widely reported and has *many*
  automatic subscribers. Please be considerate.

  **If you need help:** try searching and asking on
  http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a
  nearby user group (see http://loco.ubuntu.com or search for "LUG" in
  your area). Link back to this bug for clarity.

  ---

  This seems to fix it (at least for one version upgrade) for many
  people

  $ sudo dpkg-reconfigure nvidia-331

  after that...

  $ sudo dpkg-reconfigure nvidia-331-uvm

  (some users may be on the versions of these packages suffixed with
  -updates )

  ---

  **If you want to unsubscribe:** see
  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
  drivers-331-updates/+bug/1268257/+subscribe. You can also change your
  settings so you don't get comments but do get notified when the bug is
  solved - see https://askubuntu.com/questions/576523 for details.

  **If you want to comment:** Please consider if you have something
  meaningful to contribute to the 2500+ people who will get an email.

  **If you are an Ubuntu developer:** thanks for looking into this! :D

  

  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"

2015-01-21 Thread mat 
ci ho provato ma non ha funzionato - all'avvio mi ha dato un sacco di error
messages.

ciao
matteo

2015-01-21 10:16 GMT+01:00 Davide Mannarelli
<1268...@bugs.launchpad.net>:

> Solved in this way:
>
> 1) boot with old kernel (3.13.0-44)
> 2) login without gui (ctrl-alt-f1)
> 3) login with root (if enabled)
> 3) stopping lightdm (service lightdm stop)
> 4) a little cleaning (apt-get clean && apt-get autoclean && apt-get
> autoremove)
> 5) update source and fix (apt-get update && apt-get install -f)
> 6) install nvidia (apt-get install --reinstall nvidia-331-updates-uvm)
> 7) upgrade (apt-get upgrade)
> 8) reboot (shutdown -r now)
> 9) boot with new kernel (3.13.0-45)
> 10) :-)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1411919).
> https://bugs.launchpad.net/bugs/1268257
>
> Title:
>   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
>   failed to build, with only error: "objdump: '... .tmp_nv.o': No such
>   file"
>
> Status in nvidia-graphics-drivers-331 package in Ubuntu:
>   Triaged
> Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
>   Triaged
>
> Bug description:
>   Nvidia kernel module failed to build on kernel 3.13.0-2
>   Yesterday when the new kernel was pushed, the dkms process failed.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 14.04
>   Package: nvidia-331-updates 331.20-0ubuntu9
>   ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
>   Uname: Linux 3.12.0-7-generic x86_64
>   ApportVersion: 2.13.1-0ubuntu1
>   Architecture: amd64
>   DKMSKernelVersion: 3.13.0-2-generic
>   Date: Sun Jan 12 01:28:35 2014
>   InstallationDate: Installed on 2013-11-03 (69 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   PackageVersion: 331.20-0ubuntu9
>   SourcePackage: nvidia-graphics-drivers-331-updates
>   Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel
> module failed to build
>   UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+subscriptions
>


-- 
Dr. M. Tiede


Clausola di Riservatezza

Si fa presente che tutte le notizie (nomi, fatti, notizie sanitarie, etc)
contenute in questo messaggio sono sottoposte alla normativa sulla tutela
della riservatezza (D. Lgs 196/2003) e in particolare sulla tutela dei dati
sensibili. E' pertanto richiesta ai destinatari della presente la massima
riservatezza nel trattare la documentazione. Se il ricevente non è il
destinatario diretto del presente messaggio è pregato di contattare
l'originario mittente e di cancellare questo messaggio ed ogni suo allegato
dal sistema di posta, sono vietati l'uso, la riproduzione e la stampa di
questo messaggio e di ogni suo allegato, nonché la diffusione del
loro contenuto a qualsiasi altro soggetto.

This e-mail message and any files transmitted with it may contain
confidential information intended only for the person(s) to whom it is
addressed. If you are not the intended recipient, you are hereby notified
that any use or distribution of this e-mail is strictly prohibited: please
notify the sender and delete the original message.

Thank you.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: "objdump: '... .tmp_nv.o': No such
  file"

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+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 1413177] [NEW] package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: tentata sovrascrittura di "/etc/OpenCL/vendors/nvidia.icd" presente anche nel pa

2015-01-21 Thread mat 
Public bug reported:

tried the non-gui approach posted by davide mannarelli, this is the
result on my acer aspire 5750g

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-opencl-icd-331-updates (not installed)
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Wed Jan 21 12:55:16 2015
DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):tentata sovrascrittura di "/etc/OpenCL/vendors/nvidia.icd" presente 
anche nel pacchetto nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
ErrorMessage: tentata sovrascrittura di "/etc/OpenCL/vendors/nvidia.icd" 
presente anche nel pacchetto nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
InstallationDate: Installed on 2014-02-19 (335 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
SourcePackage: nvidia-graphics-drivers-331-updates
Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: tentata sovrascrittura di "/etc/OpenCL/vendors/nvidia.icd" 
presente anche nel pacchetto nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
UpgradeStatus: Upgraded to trusty on 2014-08-23 (151 days ago)

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


** Tags: apport-package i386 trusty

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

Title:
  package nvidia-opencl-icd-331-updates (not installed) failed to
  install/upgrade: tentata sovrascrittura di
  "/etc/OpenCL/vendors/nvidia.icd" presente anche nel pacchetto nvidia-
  opencl-icd-331 331.113-0ubuntu0.0.4

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  tried the non-gui approach posted by davide mannarelli, this is the
  result on my acer aspire 5750g

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-opencl-icd-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Wed Jan 21 12:55:16 2015
  DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):tentata sovrascrittura di "/etc/OpenCL/vendors/nvidia.icd" presente 
anche nel pacchetto nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
  ErrorMessage: tentata sovrascrittura di "/etc/OpenCL/vendors/nvidia.icd" 
presente anche nel pacchetto nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
  InstallationDate: Installed on 2014-02-19 (335 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: tentata sovrascrittura di "/etc/OpenCL/vendors/nvidia.icd" 
presente anche nel pacchetto nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
  UpgradeStatus: Upgraded to trusty on 2014-08-23 (151 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1413177/+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 1411919] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

2015-01-17 Thread mat 
Public bug reported:

maybe same bug as the others, can't see any other information to add

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
DKMSKernelVersion: 3.13.0-45-generic
Date: Sat Jan 17 08:36:09 2015
InstallationDate: Installed on 2014-02-19 (331 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
UpgradeStatus: Upgraded to trusty on 2014-08-23 (146 days ago)

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


** Tags: apport-package i386 trusty

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

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

Bug description:
  maybe same bug as the others, can't see any other information to add

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  DKMSKernelVersion: 3.13.0-45-generic
  Date: Sat Jan 17 08:36:09 2015
  InstallationDate: Installed on 2014-02-19 (331 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: Upgraded to trusty on 2014-08-23 (146 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1411919/+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 1064453] [NEW] Corrupt keyboard layout chart

2012-10-09 Thread Mat 
Public bug reported:

On a system configured with Arabic system locale (right to left layout)
and with both English (UK) and Arabic keyboards available the keyboard
layout shown by the 'Show Layout Chart' menu item appears corrupt due to
some of the four characters on each key being overlaid on each other.
What seems to be happening is that under the Arabic locale, the two
characters which would normally be displayed at the left and right of
each key are instead both placed on the right of the key.

An English (US) keyboard layout does not exhibit this behaviour.

OS: Ubuntu 12.04.1 LTS
gnome-settings-daemon: 3.4.2-0ubuntu0.4

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

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

Title:
  Corrupt keyboard layout chart

Status in “gnome-settings-daemon” package in Ubuntu:
  New

Bug description:
  On a system configured with Arabic system locale (right to left
  layout) and with both English (UK) and Arabic keyboards available the
  keyboard layout shown by the 'Show Layout Chart' menu item appears
  corrupt due to some of the four characters on each key being overlaid
  on each other. What seems to be happening is that under the Arabic
  locale, the two characters which would normally be displayed at the
  left and right of each key are instead both placed on the right of the
  key.

  An English (US) keyboard layout does not exhibit this behaviour.

  OS: Ubuntu 12.04.1 LTS
  gnome-settings-daemon: 3.4.2-0ubuntu0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1064453/+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 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)

2012-08-02 Thread Mat 
I'm seeing this bug consistently whenever I go to the Keyboard Layout
page in System Settings ("gnome-control-center region") on one of my
machines when running as a normal user. Running as root it works fine
(but accesses different settings so is no use to me). I do get an error
"(gnome-control-center:3304) common-cc-panel-WARNING **: locale
'"en_US.UTF-8"' isn't valid" when running as a normal user from a
terminal but am unsure of the significance of this.

I'm currently seeing gnome-control-center at 100% CPU but previously had
gnome-settings-daemon at 100% CPU instead/as well as in this
circumstance. A gdb backtrace of gnome-settings-daemon pointed at a
g_dbus_proxy_call_sync call to "SetXKeyboardLayouts" of
"org.freedesktop.Accounts" in gsk-keyboard-manager.c. This correlates
nicely with comment #33's suggestion to remove the keyboard.gnome-
settings-plugin file.

This leads me down the dbus route. I see what seems to be a lot of dbus
AddMatch traffic with dbus-monitor, but I'm not sure whether this is
normal.

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

Title:
  [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking
  numlock)

Status in Gnome Settings Daemon:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” source package in Precise:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown

Bug description:
  Check comment 33 for a possible workaround.

  Original message:
  -

  I don't know how to reproduce this bug, but after varying amounts of
  normal usage of my laptop, I notice gnome-settings-daemon is consuming
  100% (approx) CPU.

  I am not sure how to restart gnome-settings-daemon, I tried opening a
  terminal and running gnome-settings-daemon again but this crashes my
  system - my external monitor switches off and my laptop locks up. I am
  able to reboot with SysRq+REISUB.

  Sorry I cannot provide more information - it happens twice now, maybe
  someone can tell me how to get more information for the next time this
  happens.

  $ lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  $ apt-cache policy gnome-settings-daemon
  gnome-settings-daemon:
    Installed: 3.4.0-0ubuntu2
    Candidate: 3.4.0-0ubuntu2
    Version table:
   *** 3.4.0-0ubuntu2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-settings-daemon 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 30 17:16:02 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  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/969359/+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 867806] Re: df -h permission denied error

2012-02-08 Thread Mat Ludlam 
So to summarise I have exactly the same problem when I use ssh to
connect to Ubuntu 11.10 with all patches up to and including 8th of Feb
2012.

Output from "uname -a" is

Linux dev4 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux

Generally this error occurs when I am a normal user but does not show if
I am root.  I also believe that I have seen the problem when running
"sudo df" but I cannot 100% confirm this.

If the error appears then the return code is set to 1.

I also believe that this is a reasonably recent behavioural change on my
system.  I have added a lot of packages recently so one could have
triggered this.

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

Title:
  df -h permission denied error

Status in “lightdm” package in Ubuntu:
  Fix Released

Bug description:
  Running "df -h" from the cli as a normal user returns:

  FilesystemSize  Used Avail Use% Mounted on
  /dev/md0   37G  6.6G   29G  19% /
  udev  796M  8.0K  796M   1% /dev
  tmpfs 322M  888K  321M   1% /run
  none  5.0M 0  5.0M   0% /run/lock
  none  805M   92K  805M   1% /run/shm
  /dev/sda3 1.8T  265G  1.6T  15% /mnt/d1
  /dev/sdb3 1.8T  1.7T  102G  95% /mnt/d2
  /dev/sdc3 893G   33M  893G   1% /mnt/d3
  df: `/var/lib/lightdm/.gvfs': Permission denied
  $

  running with "su"

  $ sudo df -h
  FilesystemSize  Used Avail Use% Mounted on
  /dev/md0   37G  6.6G   29G  19% /
  udev  796M  8.0K  796M   1% /dev
  tmpfs 322M  888K  321M   1% /run
  none  5.0M 0  5.0M   0% /run/lock
  none  805M   92K  805M   1% /run/shm
  /dev/sda3 1.8T  265G  1.6T  15% /mnt/d1
  /dev/sdb3 1.8T  1.7T  102G  95% /mnt/d2
  /dev/sdc3 893G   33M  893G   1% /mnt/d3
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: bash 4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-10.16-server 3.0.4
  Uname: Linux 3.0.0-10-server x86_64
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Tue Oct  4 14:17:28 2011
  InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 
(20110426)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  SourcePackage: bash
  UpgradeStatus: Upgraded to oneiric on 2011-09-05 (29 days ago)

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