[Desktop-packages] [Bug 2022851] Re: Nautilus displays invalid directory content after deleting

[Julien Olivier]

I confirm that CTRL-Click is indeed broken in list view, but works in
grid view.

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

Title:
  Nautilus displays invalid directory content after deleting

Status in GTK+:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  When files are deleted in Nautilus, they can still show up but in the wrong 
order. This can also happen if the files are rearranged.

  This bug is marked Critical because it happen with gtk4
  4.10.3+ds-0ubuntu1 in lunar-updates but not with 4.10.1+ds-2ubuntu1
  which was originally released with Lunar.

  Test Case
  -
  Install the gtk4 update

  1. Close the file browser windows if they are open
  2. From  a terminal, run these commands:
  mkdir delete-test
  cd delete-test
  touch a b c d e f
  3. Open the Nautilus file browser window
  4. Navigate to the delete-test folder
  5. Select the f file and press the Delete key to delete the file.

  The file should be deleted and you should see only the files
  a b c d e
  in the current folder view

  What Could Go Wrong
  ---
  This fix is included in gtk4 4.10.4 update so see the master bug LP: #2023031

  Original Bug Report
  ---
  When I delete or reorganize files, they can be displayed wrong. After going 
to another directory and then back, everything displays properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  4 18:25:47 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)'
  InstallationDate: Installed on 2022-07-22 (317 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2022851/+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 1915498] Re: Copy / paste in Firefox randomly broken

[Julien Olivier]

Should i open a new bug, or can you update this one to reflect this?

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

Title:
  Copy / paste in Firefox randomly broken

Status in firefox package in Ubuntu:
  New

Bug description:
  Most of the time (but not always), when i copy content from an
  application (for example Gedit) to Firefox, the pasted content doesn't
  match what was copied. If I then try to paste in another application,
  the right content is pasted.

  I have to copy / paste the same content several times before the right
  content finally gets pasted to Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv5429 F pulseaudio
   /dev/snd/controlC0:  juloliv5429 F pulseaudio
  BuildID: 20210204182252
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Feb 12 09:22:04 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-07 (370 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.22 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=85.0.1/20210204182252 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (112 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915498/+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 1915498] Re: Copy / paste in Firefox randomly broken

[Julien Olivier]

After further investigation, the bug is in Gedit (or GTK?), not in
Firefox: I have noticed that,  when the bug occurs, I cannot paste (the
data copied from gedit) in LibreOffice either. If I close gedit and open
it again, I can copy / paste from Gedit to Firefox (or LibreOffice)
again.

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

Title:
  Copy / paste in Firefox randomly broken

Status in firefox package in Ubuntu:
  New

Bug description:
  Most of the time (but not always), when i copy content from an
  application (for example Gedit) to Firefox, the pasted content doesn't
  match what was copied. If I then try to paste in another application,
  the right content is pasted.

  I have to copy / paste the same content several times before the right
  content finally gets pasted to Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv5429 F pulseaudio
   /dev/snd/controlC0:  juloliv5429 F pulseaudio
  BuildID: 20210204182252
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Feb 12 09:22:04 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-07 (370 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.22 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=85.0.1/20210204182252 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (112 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915498/+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 1915498] Re: Copy / paste in Firefox randomly broken

[Julien Olivier]

Sorry, my bugzilla.mozilla account is disabled, and i have no clue why,
so i can't open a new bug. I'll do it as soon as my account is back (if
ever...).

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

Title:
  Copy / paste in Firefox randomly broken

Status in firefox package in Ubuntu:
  New

Bug description:
  Most of the time (but not always), when i copy content from an
  application (for example Gedit) to Firefox, the pasted content doesn't
  match what was copied. If I then try to paste in another application,
  the right content is pasted.

  I have to copy / paste the same content several times before the right
  content finally gets pasted to Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv5429 F pulseaudio
   /dev/snd/controlC0:  juloliv5429 F pulseaudio
  BuildID: 20210204182252
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Feb 12 09:22:04 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-07 (370 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.22 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=85.0.1/20210204182252 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (112 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915498/+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 1915498] Re: Copy / paste in Firefox randomly broken

[Julien Olivier]

BTW: I found this bug report, but it's closed:
https://bugzilla.mozilla.org/show_bug.cgi?id=1438136

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

Title:
  Copy / paste in Firefox randomly broken

Status in firefox package in Ubuntu:
  New

Bug description:
  Most of the time (but not always), when i copy content from an
  application (for example Gedit) to Firefox, the pasted content doesn't
  match what was copied. If I then try to paste in another application,
  the right content is pasted.

  I have to copy / paste the same content several times before the right
  content finally gets pasted to Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv5429 F pulseaudio
   /dev/snd/controlC0:  juloliv5429 F pulseaudio
  BuildID: 20210204182252
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Feb 12 09:22:04 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-07 (370 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.22 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=85.0.1/20210204182252 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (112 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915498/+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 1915498] [NEW] Copy / paste in Firefox randomly broken

[Julien Olivier]

Public bug reported:

Most of the time (but not always), when i copy content from an
application (for example Gedit) to Firefox, the pasted content doesn't
match what was copied. If I then try to paste in another application,
the right content is pasted.

I have to copy / paste the same content several times before the right
content finally gets pasted to Firefox.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: firefox 85.0.1+build1-0ubuntu0.20.10.1
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  juloliv5429 F pulseaudio
 /dev/snd/controlC0:  juloliv5429 F pulseaudio
BuildID: 20210204182252
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: GNOME
Date: Fri Feb 12 09:22:04 2021
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
DefaultProfileThemes: extensions.sqlite corrupt or missing
EcryptfsInUse: Yes
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-07 (370 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IpRoute:
 default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.22 metric 600
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=85.0.1/20210204182252 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: Upgraded to groovy on 2020-10-22 (112 days ago)
dmi.bios.date: 06/28/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X570DD.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X570DD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug groovy wayland-session

** Bug watch added: Mozilla Bugzilla #1438136
   https://bugzilla.mozilla.org/show_bug.cgi?id=1438136

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

Title:
  Copy / paste in Firefox randomly broken

Status in firefox package in Ubuntu:
  New

Bug description:
  Most of the time (but not always), when i copy content from an
  application (for example Gedit) to Firefox, the pasted content doesn't
  match what was copied. If I then try to paste in another application,
  the right content is pasted.

  I have to copy / paste the same content several times before the right
  content finally gets pasted to Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv5429 F pulseaudio
   /dev/snd/controlC0:  juloliv5429 F pulseaudio
  BuildID: 20210204182252
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Feb 12 09:22:04 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close 

[Desktop-packages] [Bug 1742482] Re: firefox is used to open ftp share files

[Julien Olivier]

The bug is still there in Ubuntu 20.10. I'm even almost certain it was
fixed and re-appeared recently.

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

Title:
  firefox is used to open ftp share files

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04
  Nautilus 1:3.26.0-0ubuntu1
  Bluefish 2.2.10

  When I open a .php file from a FTP server browsed with Nautilus,
  Chrome is opened instead of the default application Bluefish.

  Steps to reproduce:
  1. Connect to an FTP server via Nautilus
  2a. Double-click on a .php file: chrome opens and the file is downloaded
  2b. Right click and select 'open with' and then Bluefish: the file is opened 
in bluefish as expected

  So, on the double-click from Nautilus the wrong app (chrome!) is
  opened even if the .php files are associated with bluefish.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluefish 2.2.9-1
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 10 17:12:27 2018
  ExecutablePath: /usr/bin/bluefish
  InstallationDate: Installed on 2015-12-07 (765 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bluefish
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1742482/+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 1901391] [NEW] screen recording not working

[Julien Olivier]

Public bug reported:

I'm using gnome-shell with wayland (don't know if that matters), and,
when I press CTRL-ALT-SHIFT-R, nothing happens. I checked my keyboard
shortcuts, and this shortcut is supposed to trigger screencasting.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Oct 25 10:39:48 2020
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-02-07 (260 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to groovy on 2020-10-22 (2 days ago)

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


** Tags: amd64 apport-bug groovy wayland-session

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

Title:
  screen recording not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm using gnome-shell with wayland (don't know if that matters), and,
  when I press CTRL-ALT-SHIFT-R, nothing happens. I checked my keyboard
  shortcuts, and this shortcut is supposed to trigger screencasting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Oct 25 10:39:48 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-07 (260 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901391/+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 1876908] Re: Screen not locked after resume from suspend

[Julien Olivier]

I found the problem (and the solution ;)).

It's actually the org.gnome.desktop.lockdown disable-lock-screen
gesettings key that's been set to "true". No idea how it got set to
"true" though because i never changed it, and it used to work before.
Apparently, I'm not the only one in this case:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851992

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

Title:
  Screen not locked after resume from suspend

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Whenever I suspend my laptop, and then resume, I get directly to the
  gnome-shell desktop without having to log in.

  This used to work perfectly before the upgrade to 20.04.

  For information, I'm using pure gnome-shell, not Unity, in case that
  matters.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv1699 F pulseaudio
   /dev/snd/controlC0:  juloliv1699 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 14:08:39 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-07 (87 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-24 (10 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876908/+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 1876908] Re: Screen not locked after resume from suspend

[Julien Olivier]

I confirm Lock Screen on Suspend is ON.

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

Title:
  Screen not locked after resume from suspend

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Whenever I suspend my laptop, and then resume, I get directly to the
  gnome-shell desktop without having to log in.

  This used to work perfectly before the upgrade to 20.04.

  For information, I'm using pure gnome-shell, not Unity, in case that
  matters.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv1699 F pulseaudio
   /dev/snd/controlC0:  juloliv1699 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 14:08:39 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-07 (87 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-24 (10 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876908/+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 1875005] Re: [amdgpu] Launching apps on the Nvidia GPU via PRIME does not work (in the presence of an integrated amdgpu)

[Julien Olivier]

Daniel,

there are actually two bugs here: the first one being that 3D
acceleration doesn't work out of the box using Ubuntu's installation of
the Nvidia driver through "additional pilots": for that to work, you
need to add “Option “PrimaryGPU” “Yes”” to
/usr/share/X11/xorg.conf.d/10-nvidia.conf.

The second bug is that, once this configuration fixed, it's impossible
to easily switch between integrated card and dedicated card without
rebooting (either through prime-select or with the new gnome-shell's
shortcut).

Let's say that this report is about the 2nd one, and I've opened a new
report for the first one:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875794

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

Title:
  [amdgpu] Launching apps on the Nvidia GPU via PRIME does not work (in
  the presence of an integrated amdgpu)

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  I have a laptop with both AMD Raven and Nvidia GTX 1050 video
  adapters. I wanted to test the new game mode in Ubuntu 20.04, and
  noticed that only the AMD Raven actually works. To do the test, I
  tried launching a terminal and running gxgears, both in a normal way,
  and then using the "start using dedicated video adapter" (or whatever
  it really is in English) option in gnome-shell.

  Using the standard video adapter (probably the AMD Raven), it works, but 
slowly.
  Using the dedicated video adapter, I get the following:

  juloliv@juloliv:~$ glxgears 
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  152 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  25
Current serial number in output stream:  26

  NB: in both cases, I tried launching nvidia-settings and got the
  following:

  juloliv@juloliv:~$ nvidia-settings

  ERROR: Unable to load info from any available system

  
  (nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  ** Message: 12:33:29.273: PRIME: No offloading required. Abort
  ** Message: 12:33:29.273: PRIME: is it supported? no

  And then a blank window...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr 25 12:26:50 2020
  DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1]
  InstallationDate: Installed on 2020-02-07 (77 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Desktop-packages] [Bug 1875794] [NEW] Only AMD GPU works on laptop with hybrid AMD / Nvidia GPUs

[Julien Olivier]

Public bug reported:

I have a laptop with both AMD Raven and Nvidia GTX 1050 video adapters.
After installing the nvidia-driver-440 package through Ubuntu's
additional drivers" tool, only the AMD GPU could be used.

To fix this, I had to add “Option “PrimaryGPU” “Yes”” to
/usr/share/X11/xorg.conf.d/10-nvidia.conf

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Apr 29 08:05:46 2020
DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1]
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1]
InstallationDate: Installed on 2020-02-07 (81 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-24 (4 days ago)
dmi.bios.date: 06/28/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X570DD.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X570DD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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 20.0.4-2ubuntu1
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

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


** Tags: amd64 apport-bug focal performance possible-manual-nvidia-install 
ubuntu wayland-session

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

Title:
  Only AMD GPU works on laptop with hybrid AMD / Nvidia GPUs

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a laptop with both AMD Raven and Nvidia GTX 1050 video
  adapters. After installing the nvidia-driver-440 package through
  Ubuntu's additional drivers" tool, only the AMD GPU could be used.

  To fix this, I had to add “Option “PrimaryGPU” “Yes”” to
  /usr/share/X11/xorg.conf.d/10-nvidia.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Apr 29 08:05:46 2020
  DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1]
   Advanced Micro Devices, Inc. 

[Desktop-packages] [Bug 1875005] Re: 3D acceleration not working with NVidia driver

[Julien Olivier]

Actually, I’ve just found out that adding “Option “PrimaryGPU” “Yes”” to
/usr/share/X11/xorg.conf.d/10-nvidia.conf made the 3D acceleration (and
nvidia-settings) work! However, now, I have no way to switch between AMR
Raven and GTX: it always uses the GTX.

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

Title:
  3D acceleration not working with NVidia driver

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a laptop with both AMD Raven and Nvidia GTX 1050 video
  adapters. I wanted to test the new game mode in Ubuntu 20.04, and
  noticed that only the AMD Raven actually works. To do the test, I
  tried launching a terminal and running gxgears, both in a normal way,
  and then using the "start using dedicated video adapter" (or whatever
  it really is in English) option in gnome-shell.

  Using the standard video adapter (probably the AMD Raven), it works, but 
slowly.
  Using the dedicated video adapter, I get the following:

  juloliv@juloliv:~$ glxgears 
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  152 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  25
Current serial number in output stream:  26

  NB: in both cases, I tried launching nvidia-settings and got the
  following:

  juloliv@juloliv:~$ nvidia-settings

  ERROR: Unable to load info from any available system

  
  (nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  ** Message: 12:33:29.273: PRIME: No offloading required. Abort
  ** Message: 12:33:29.273: PRIME: is it supported? no

  And then a blank window...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr 25 12:26:50 2020
  DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1]
  InstallationDate: Installed on 2020-02-07 (77 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  

[Desktop-packages] [Bug 1875005] Re: 3D acceleration not working with NVidia driver

[Julien Olivier]

** Attachment added: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875005/+attachment/5361617/+files/nvidia-bug-report.log.gz

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

Title:
  3D acceleration not working with NVidia driver

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a laptop with both AMD Raven and Nvidia GTX 1050 video
  adapters. I wanted to test the new game mode in Ubuntu 20.04, and
  noticed that only the AMD Raven actually works. To do the test, I
  tried launching a terminal and running gxgears, both in a normal way,
  and then using the "start using dedicated video adapter" (or whatever
  it really is in English) option in gnome-shell.

  Using the standard video adapter (probably the AMD Raven), it works, but 
slowly.
  Using the dedicated video adapter, I get the following:

  juloliv@juloliv:~$ glxgears 
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  152 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  25
Current serial number in output stream:  26

  NB: in both cases, I tried launching nvidia-settings and got the
  following:

  juloliv@juloliv:~$ nvidia-settings

  ERROR: Unable to load info from any available system

  
  (nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  ** Message: 12:33:29.273: PRIME: No offloading required. Abort
  ** Message: 12:33:29.273: PRIME: is it supported? no

  And then a blank window...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr 25 12:26:50 2020
  DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1]
  InstallationDate: Installed on 2020-02-07 (77 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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 

[Desktop-packages] [Bug 1875005] Re: 3D acceleration not working with NVidia driver

[Julien Olivier]

PS: Forgot to say that I'm using nvidia-driver-440 installed through
"additional drivers".

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

Title:
  3D acceleration not working with NVidia driver

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a laptop with both AMD Raven and Nvidia GTX 1050 video
  adapters. I wanted to test the new game mode in Ubuntu 20.04, and
  noticed that only the AMD Raven actually works. To do the test, I
  tried launching a terminal and running gxgears, both in a normal way,
  and then using the "start using dedicated video adapter" (or whatever
  it really is in English) option in gnome-shell.

  Using the standard video adapter (probably the AMD Raven), it works, but 
slowly.
  Using the dedicated video adapter, I get the following:

  juloliv@juloliv:~$ glxgears 
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  152 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  25
Current serial number in output stream:  26

  NB: in both cases, I tried launching nvidia-settings and got the
  following:

  juloliv@juloliv:~$ nvidia-settings

  ERROR: Unable to load info from any available system

  
  (nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  ** Message: 12:33:29.273: PRIME: No offloading required. Abort
  ** Message: 12:33:29.273: PRIME: is it supported? no

  And then a blank window...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr 25 12:26:50 2020
  DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1]
  InstallationDate: Installed on 2020-02-07 (77 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: 

[Desktop-packages] [Bug 1875005] [NEW] 3D acceleration not working with NVidia driver

[Julien Olivier]

Public bug reported:

I have a laptop with both AMD Raven and Nvidia GTX 1050 video adapters.
I wanted to test the new game mode in Ubuntu 20.04, and noticed that
only the AMD Raven actually works. To do the test, I tried launching a
terminal and running gxgears, both in a normal way, and then using the
"start using dedicated video adapter" (or whatever it really is in
English) option in gnome-shell.

Using the standard video adapter (probably the AMD Raven), it works, but slowly.
Using the dedicated video adapter, I get the following:

juloliv@juloliv:~$ glxgears 
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  25
  Current serial number in output stream:  26

NB: in both cases, I tried launching nvidia-settings and got the
following:

juloliv@juloliv:~$ nvidia-settings

ERROR: Unable to load info from any available system


(nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
** Message: 12:33:29.273: PRIME: No offloading required. Abort
** Message: 12:33:29.273: PRIME: is it supported? no

And then a blank window...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Apr 25 12:26:50 2020
DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1]
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1]
InstallationDate: Installed on 2020-02-07 (77 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
dmi.bios.date: 06/28/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X570DD.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X570DD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
nvidia-settings:
 ERROR: Unable to load info from any available system
 
 
 ERROR: Unable to load info from any available system
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 20.0.4-2ubuntu1
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

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


** Tags: amd64 apport-bug focal performance possible-manual-nvidia-install 
ubuntu

-- 
You received 

[Desktop-packages] [Bug 1754125] Re: Rhythmbox stays running in the background after quit

[Julien Olivier]

Paul, the "Stop & Quit" action is certainly a plus, but it doesn't solve
this precise bug report, as there still is a case where "Rhythmbox stays
running in the background after quit" (if you just close the window).
I'm not the one to decide whether or not this is the desired behaviour,
but I just think that the "Stop & Quit" action is only a workaround for
this bug.

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

Title:
  Rhythmbox stays running in the background after quit

Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  If you do ps -alx you will see rhythmbox process still running. It
  causes opening rhythmbox to hang when trying to open again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 13:21:51 2018
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1754125] Re: Rhythmbox stays running in the background after quit

[Julien Olivier]

@Paul White

The problem is that, in gnome-shell, if you close Rhythmbox while music
is playing, Rhythmbox's icon simply disappears. So, there is no way to
reach this "Stop & Quit" quickmenu option. Unless I'm missing something,
of course...

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

Title:
  Rhythmbox stays running in the background after quit

Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  If you do ps -alx you will see rhythmbox process still running. It
  causes opening rhythmbox to hang when trying to open again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 13:21:51 2018
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1754125] Re: Rhythmbox stays running in the background after quit

[Julien Olivier]

This behaviour might me perfect in the default Ubuntu desktop (gnome-
shell + Unity plugins), but it's broken if you use upstream gnome-shell
because there is no tray to control Rhythmbox from once closed.

I understand that Ubuntu's focus is on the default experience, but I
guess it's also important to make it easy to use alternatives
(especially when the "alternative" is actually upstream's default). So,
wouldn't it be possible to detect whether the desktop has a "tray" (or
"indicator" or whatever it's called in Unity), and really quit Rhythmbox
on close if it doesn't?

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

Title:
  Rhythmbox stays running in the background after quit

Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  If you do ps -alx you will see rhythmbox process still running. It
  causes opening rhythmbox to hang when trying to open again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 13:21:51 2018
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1855757] Re: [nvidia] Background image corrupted after standby

[Julien Olivier]

By the way, I don't know what happened but I don't have the bug any
more. Has there been any update recently?

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

Title:
  [nvidia] Background image corrupted after standby

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

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  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: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/ubuntu/+source/gnome-shell/+bug/1855757/+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 1855757] Re: [nvidia] Background image corrupted after standby

[Julien Olivier]

@Daniel: the Nouveau driver may work, but, in my case, it's way slower
than the NVidia official driver, making it simply unusable for any 3D
usage.

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

Title:
  [nvidia] Background image corrupted after standby

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

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  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: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/ubuntu/+source/gnome-shell/+bug/1855757/+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 1855757] Re: [nvidia] Background image corrupted after standby 19.10

[Julien Olivier]

I confirm that I have this bug with Nvidia-340, but not with the Nouveau
driver.

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

Title:
  [nvidia] Background image corrupted after standby 19.10

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

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  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: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/ubuntu/+source/gnome-shell/+bug/1855757/+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 1855757] Re: [nvidia] Background image corrupted after standby 19.10

[Julien Olivier]

By the way, there is a much simpler workaround: just restart gnome-shell
using ALT-F2, then "r".

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

Title:
  [nvidia] Background image corrupted after standby 19.10

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

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  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: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/ubuntu/+source/gnome-shell/+bug/1855757/+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 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

Yes, the bug happens on the client side, when trying to download files
from a server.

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1853961/+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 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

Here it is: https://gitlab.gnome.org/GNOME/gvfs/issues/434

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #434
   https://gitlab.gnome.org/GNOME/gvfs/issues/434

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in gvfs package in Ubuntu:
  New

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1853961/+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 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

So, what now? Do you need me to do try anything else? Or send you logs
using another method?

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853961/+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 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

https://errors.ubuntu.com/user/48706022a1eb9a1460914442b5800ac75480d612cb57c8df5cd3cf920eb42797803624177a2fa97cc4c46fd865fa40a4b32225eb30790d2d7cde0622a541b5db

I can see some of my error reports, but the last ones (sent via ubuntu-
bug /var/crash/_usr_lib_gvfs_gvfsd-sftp.1000.crash) don't appear.

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853961/+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 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

Also note that I have an empty /var/crash/_usr_lib_gvfs_gvfsd-
sftp.1000.upload, in case it matters.

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853961/+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 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

I've just run "ubuntu-bug /var/crash/_usr_lib_gvfs_gvfsd-
sftp.1000.crash", then clicked on "send". Now, nothing happens. Is it
normal?

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853961/+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 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

** Attachment added: "_usr_lib_gvfs_gvfsd-sftp.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853961/+attachment/5307919/+files/_usr_lib_gvfs_gvfsd-sftp.1000.crash

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853961/+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 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

I just attached the .crash updated by apport-retrace.

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853961/+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 1853961] [NEW] Nautilus segfaults while transferring files via SFTP

[Julien Olivier]

Public bug reported:

Every time I try to transfer a large file (or several small files) via
Nautilus/SFTP, it ends up failing after a minute or so (connection
closed).

For example, I tried the same transfer twice, and got the following log:

[505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
[505587.786958] Code: Bad RIP value.
[505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 7fa35323bc04 
sp 7ffc3f4d7d90 error 4 in libc-2.30.so[7fa3531c8000+178000]
[505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 16 
44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 43 
08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

If I try the same transfer using Filezilla, it completes flawlessly.
Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
with the same server either.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Nov 26 07:48:38 2019
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
InstallationDate: Installed on 2018-05-14 (560 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug eoan

** Description changed:

- Everytime I try to transfer a bug file via Nautilus/SFTP, it ends up
+ Every time I try to transfer a file via Nautilus/SFTP, it ends up
  failing after a minute or so (connection closed).
  
  For example, I tried the same transfer twice, and got the following log:
  
  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85
  
  If I try the same transfer using Filezilla, it completes flawlessly.
+ Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
+ with the same server either.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
-  b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
-  b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
-  b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
+  b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
+  b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
+  b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

** Description changed:

- Every time I try to transfer a file via Nautilus/SFTP, it ends up
+ Every time I try to transfer a large file via Nautilus/SFTP, it ends up
  failing after a minute or so (connection closed).
  
  For example, I tried the same transfer twice, and got the following log:
  
  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85
  
  If I try the same transfer using Filezilla, it 

[Desktop-packages] [Bug 377322] Re: Nautilus sftp connection breaks spontaneously after a while, needing re-login to fix it

[Julien Olivier]

Seems like the bug is back in Nautilus 3.34 and Ubuntu 19.10 :(

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

Title:
  Nautilus sftp connection breaks spontaneously after a while, needing
  re-login to fix it

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  When I have used an sftp connection for a while - started from
  Places/Connect to Server or from a bookmark - it breaks, typically
  after an hour or so. The only way to get an sftp connection to that
  server again is to re login to my computer. The error message I get is

  Could not open location 'sftp://..'

  DBus error org.freedesktop.DBus.Error.NoReply: 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

  Sometimes when this happens, my computer freezes for about 60 seconds.

  I have Ubuntu 9.04 64 bits - error happened on Hardy also - on a
  computer with an AMD64 processor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/377322/+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 1850925] [NEW] package nvidia-340 340.107-0ubuntu7 failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui appartient aussi au paquet

[Julien Olivier]

Public bug reported:

???

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: nvidia-340 340.107-0ubuntu7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
Date: Fri Oct 25 22:00:29 2019
ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules 
», qui appartient aussi au paquet nvidia-kernel-common-430 430.50-0ubuntu2
InstallationDate: Installed on 2018-05-14 (535 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 340.107-0ubuntu7 failed to install/upgrade: tentative 
de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui appartient aussi 
au paquet nvidia-kernel-common-430 430.50-0ubuntu2
UpgradeStatus: Upgraded to eoan on 2019-10-18 (14 days ago)

** Affects: nvidia-graphics-drivers-340 (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-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1850925

Title:
  package nvidia-340 340.107-0ubuntu7 failed to install/upgrade:
  tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules »,
  qui appartient aussi au paquet nvidia-kernel-common-430
  430.50-0ubuntu2

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

Bug description:
  ???

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-340 340.107-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  Date: Fri Oct 25 22:00:29 2019
  ErrorMessage: tentative de remplacement de « 
/lib/udev/rules.d/71-nvidia.rules », qui appartient aussi au paquet 
nvidia-kernel-common-430 430.50-0ubuntu2
  InstallationDate: Installed on 2018-05-14 (535 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.107-0ubuntu7 failed to install/upgrade: 
tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui 
appartient aussi au paquet nvidia-kernel-common-430 430.50-0ubuntu2
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1850925/+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 1822351] Re: Nautilus does not open after updating to 19.04

[Julien Olivier]

Hi,

in case that helps, I have noticed that this bug is 100% reproducible
for me hen I try to start Nautilus right after booting my laptop. If,
however, I wait for a few minutes after booting, I can start Nautilus
without any delay.

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

Title:
  Nautilus does not open after updating to 19.04

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 19.04 dev branch, nautilus does not open at
  all. Moreover, trying to open nautilus from the terminal does not give
  any error, nor any output at all, and no window opens.

  I don't really know how to report this bug without any terminal
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 13:58:12 2019
  InstallationDate: Installed on 2018-02-23 (398 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+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 841409] Re: GEdit is the only choice as Calendar application in Default Applications dialog

[Julien Olivier]

I've reported is as a gnome-calendar bug here:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1828491

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

Title:
  GEdit is the only choice as Calendar application in Default
  Applications dialog

Status in gnome-control-center:
  Expired
Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in desktop-file-utils source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Triaged

Bug description:
  In Ubuntu Oneiric (11.10) beta1, opening the Default Applications dialog 
(System Settings -> System Information), GEdit is selected (and only possible 
choice) for Calendar items.
  I think this is not expected, since it is not so useful to open calendar data 
as standard text).

  In Oneiric Thunderbird is default email client. Currently Thunderbird7 beta 
is installed, and I noticed the Lightning extension for Calendar is not 
compatible with it yet.
  Will Thunderbird/Lightining be possible values for Calendar applications?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Mon Sep  5 00:56:27 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-09-03 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/841409/+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 841409] Re: GEdit is the only choice as Calendar application in Default Applications dialog

[Julien Olivier]

I have gnome-calendar installed on Ubuntu 19.04, and gedit is still
displayed as the only available choice in the default app settings. The
workaround was to run the following: gio mime text/calendar
org.gnome.Calendar.desktop

Now gnome-calendar appears as the default (and only) calendar app...

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

Title:
  GEdit is the only choice as Calendar application in Default
  Applications dialog

Status in gnome-control-center:
  Expired
Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in desktop-file-utils source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Triaged

Bug description:
  In Ubuntu Oneiric (11.10) beta1, opening the Default Applications dialog 
(System Settings -> System Information), GEdit is selected (and only possible 
choice) for Calendar items.
  I think this is not expected, since it is not so useful to open calendar data 
as standard text).

  In Oneiric Thunderbird is default email client. Currently Thunderbird7 beta 
is installed, and I noticed the Lightning extension for Calendar is not 
compatible with it yet.
  Will Thunderbird/Lightining be possible values for Calendar applications?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Mon Sep  5 00:56:27 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-09-03 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/841409/+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 1828491] [NEW] gnome-calendar not listed as a calendar app in default app settings

[Julien Olivier]

Public bug reported:

Gnome-Calendar doesn't appear in the list of default apps for calendar
in gnome settings. This is probably due to the fact that, in the
.desktop file, the "text/calendar" mime type is not registered?

Anyway, a workaround exists: just type "gio mime text/calendar
org.gnome.Calendar.desktop".

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

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

Title:
  gnome-calendar not listed as a calendar app in default app settings

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Gnome-Calendar doesn't appear in the list of default apps for calendar
  in gnome settings. This is probably due to the fact that, in the
  .desktop file, the "text/calendar" mime type is not registered?

  Anyway, a workaround exists: just type "gio mime text/calendar
  org.gnome.Calendar.desktop".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1828491/+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 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver

[Julien Olivier]

Removing mesa-va-drivers and gstreamer-1.0-vaapi fixed the bug. Thanks a
lot for your help!

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

Title:
  Fatal IO error 11 on totem startup when using the Nvidia binary driver

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Whenever I try to launch totem, I get the following error:
  Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1.

  Then, it just crashes.

  This bug only occurs when using the Nvidia binary driver. However,
  even using the Nvidia binary driver, it doesn't occur on VLC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul  6 20:52:08 2018
  InstallationDate: Installed on 2018-05-14 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+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 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver

[Julien Olivier]

I've done that and the bug still occurs, but it doesn't generate any
core or crash file.

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

Title:
  Fatal IO error 11 on totem startup when using the Nvidia binary driver

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Whenever I try to launch totem, I get the following error:
  Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1.

  Then, it just crashes.

  This bug only occurs when using the Nvidia binary driver. However,
  even using the Nvidia binary driver, it doesn't occur on VLC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul  6 20:52:08 2018
  InstallationDate: Installed on 2018-05-14 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+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 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver

[Julien Olivier]

Sorry Daniel, I don't understand what you need. The bug occurs
immediately after I try to launch totem:

juloliv@juloliv:~$ totem
Gdk-Message: 10:52:39.290: totem: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1.

There is no particular "context": it crashes all the time, as soon as
it's launched, and there is no log to attach that I know of.

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

Title:
  Fatal IO error 11 on totem startup when using the Nvidia binary driver

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Whenever I try to launch totem, I get the following error:
  Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1.

  Then, it just crashes.

  This bug only occurs when using the Nvidia binary driver. However,
  even using the Nvidia binary driver, it doesn't occur on VLC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul  6 20:52:08 2018
  InstallationDate: Installed on 2018-05-14 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+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 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver

[Julien Olivier]

I tried steps 1, 2 and 3, but it doesn't change a thing: the crash
occurs, the message "totem: Fatal IO error 11 (Resource temporarily
unavailable) on X server :1." is spawned in the terminal, but no .crash
file is generated.

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

Title:
  Fatal IO error 11 on totem startup when using the Nvidia binary driver

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Whenever I try to launch totem, I get the following error:
  Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1.

  Then, it just crashes.

  This bug only occurs when using the Nvidia binary driver. However,
  even using the Nvidia binary driver, it doesn't occur on VLC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul  6 20:52:08 2018
  InstallationDate: Installed on 2018-05-14 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+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 1780475] [NEW] Fatal IO error 11 on startup

[Julien Olivier]

Public bug reported:

Whenever I try to launch totem, I get the following error:
Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1.

Then, it just crashes.

This bug only occurs when using the Nvidia binary driver. However, even
using the Nvidia binary driver, it doesn't occur on VLC.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul  6 20:52:08 2018
InstallationDate: Installed on 2018-05-14 (53 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: totem (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 totem in Ubuntu.
https://bugs.launchpad.net/bugs/1780475

Title:
  Fatal IO error 11 on startup

Status in totem package in Ubuntu:
  New

Bug description:
  Whenever I try to launch totem, I get the following error:
  Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1.

  Then, it just crashes.

  This bug only occurs when using the Nvidia binary driver. However,
  even using the Nvidia binary driver, it doesn't occur on VLC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul  6 20:52:08 2018
  InstallationDate: Installed on 2018-05-14 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+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 1760450] Re: [nvidia] Xorg crashed with signal 7 in _dl_fixup() from _dl_runtime_resolve_xsavec() called from nvidia_drv.so

[Julien Olivier]

I confirm that adding "scsi_mod.scan=sync" does indeed fix this bug.

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

Title:
  [nvidia] Xorg crashed with signal 7 in _dl_fixup() from
  _dl_runtime_resolve_xsavec() called from nvidia_drv.so

Status in xorg-server package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  after login session(suspend mode)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 20:34:29 2018
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  InstallationDate: Installed on 2017-09-02 (211 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   _dl_fixup (l=0x559c10faa5a0, reloc_arg=) at 
../elf/dl-runtime.c:84
   _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125
   ?? () from /usr/lib/xorg/modules/libwfb.so
   wfbComposite () from /usr/lib/xorg/modules/libwfb.so
   ?? () from /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so
  Title: Xorg crashed with signal 7 in _dl_fixup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/+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 106621] Re: GNOME Trash doesn't show deleted files on other partitions (ecryptfs / encfs / Private / ntfs-3g)

[Julien Olivier]

Sorry, I'm lost here: I still see the bug in Nautilus 3.20.4. Is it
supposed to be fixed ?

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

Title:
  GNOME Trash doesn't show deleted files on other partitions (ecryptfs /
  encfs / Private / ntfs-3g)

Status in GnomeVFS:
  Fix Released
Status in gvfs:
  Fix Released
Status in Nautilus:
  Invalid
Status in ecryptfs-utils package in Ubuntu:
  Won't Fix
Status in gnome-vfs2 package in Ubuntu:
  Invalid
Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  If I remove files from FUSE partitions with Nautilus they are moved to
  .Trash-$USER on the FUSE partition but they aren't shown in Trash so
  the only solution to free space is to remove the trash directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-vfs/+bug/106621/+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 816669] Re: encrypted-home support in new user dialog

[Julien Olivier]

** Tags added: yakkety zesty

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

Title:
  encrypted-home support in new user dialog

Status in One Hundred Papercuts:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center source package in Precise:
  Triaged

Bug description:
  seb128 asked me to file this bug...

  He noticed that the Gnome3 new user dialog does not support the
  encrypt-home-directory feature that was present in previous versions
  of Gnome.

  To solve this, the new user dialog would have a boolean checkbox
  (defaulted to un-checked), which asks if this new user's home
  directory should be created.  Talk to mpt about the wordsmithing.  If
  checked, then you need to add --encrypt-home to the 'adduser'
  invocation.  Before running adduser, you'd also need to ensure that
  ecryptfs-utils is installed.

  For real security, you would also need to run (as root) ecryptfs-
  setup-swap, which would encrypt the user's swap space.  This is
  necessary, as any files/data that gets swapped out to disk could be
  written in the clear, thereby circumventing the user's requested
  encryption.  Further note that if swap is encrypted, hibernation
  should be disabled (suspend continues to work just fine).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/816669/+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 1575354] Re: Connecting to VPN times out after 25 seconds if login credentials not entered

[Julien Olivier]

Mike, here's what I get in /var/log/syslog after trying to connect to
the VPN. Could you tell me if this is the same bug or if I need to file
another one?

** Attachment added: "/var/log/syslog after trying to connect to VPN"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1575354/+attachment/4660586/+files/syslog

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

Title:
  Connecting to VPN times out after 25 seconds if login credentials not
  entered

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connecting to OpenConnect VPN through the Gnome GUI fails because
  NetworkManager times out while requesting credentials through the GUI
  form in Ubuntu 16.04.

  It worked (is working on other computers I'm working on) fine from
  Ubuntu 12.04-15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openconnect 1.0.2-1build1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 22:06:41 2016
  SourcePackage: network-manager-openconnect
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1575354/+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 1353951] Re: gnome online accounts require autentication on startup

[Julien Olivier]

Please re-open this bug. It's not fixed as of today.

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

Title:
  gnome online accounts require autentication on startup

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in evolution-data-server source package in Trusty:
  Fix Released
Status in gnome-online-accounts source package in Trusty:
  Invalid

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case]
  1) open gnome-online-accounts
  2) click + and add a google account
  3) enter user name and password
  4) confirm permissions for gnome
  5) Black window pops up and asks for google password, but does not accept the 
correct password.
  Google Contacts are not available in Gnome or Thunderbird

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  

  Gnome online accounts requires autentication on startup, but even typing the 
correct password in the box, the program says the password is wrong. By the way 
evolution and other programs work well with online accounts. I'm using 
Ubuntu-gnome 14.04 LTS 64bit on different machines and have the same behaviour.
  Just to be clear: online-accounts works well, just at startup it opens an 
"administration" window where it requires to insert the password for my google 
accounts; if I type the correct password it says that the password is wrong, 
the only way to close the window is to click on "discard" and then all works 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1353951/+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 1295994] Re: Unable to use Printscreen Button on Ubuntu 14.04 in GNOME Shell

[Julien Olivier]

I have the exact same problem on my HP Pavilion and Ubuntu GNOME 15.04.

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

Title:
  Unable to use Printscreen Button on Ubuntu 14.04 in GNOME Shell

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Hi, I am trying Ubuntu 14.04 and I noticed that Printscreen button
  doesn't work. I had no problems in 13.10. If I run "gnome-screenshot",
  or "gnome-screenshot -a"  in a Terminal it says "Unable to use GNOME
  Shell's builtin screenshot interface, resorting to fallback X11.I
  noticed that the function works if custom shortcuts are set. Can
  anyone help? Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1295994/+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 1412057] Re: nvidia-prime 0.7 does not work as expected in 15.04

[Julien Olivier]

Seems that gpumanager is responsible for erasing the configuration after
every reboot. However, if I add the nogpumanager option to grub, then
select the nvidia profile, xorg doesn't start at next boot.

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

Title:
  nvidia-prime 0.7 does not work as expected  in 15.04

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Last days nvidia-prime 0.7 has been released but this version, like
  previous one, does not work in Vivid.

  I'm not sure exactly how long this problem exists (i think something
  like 2-3 or more weeks), but it is impossible to switch to nvidia
  profile. Before nvidia-settings package offered controls to switch
  profile Nvidia/Intel but now its gone.

  If we try:
  #prime-select nvidia

  we have:
  Info: the current alternatives in use are: ['mesa', 'mesa']
  Info: selecting nvidia-346 for the nvidia profile
  update-alternatives: using /usr/lib/nvidia-346/ld.so.conf to provide 
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual 
mode
  update-alternatives: using /usr/lib/nvidia-346/alt_ld.so.conf to provide 
/etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode

  so it seems like switching to nvidia profile, but after relogin or
  reboot again mesa is marked as used.

  If we try:
  #prime-switch nvidia

  we have:
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
  update-alternatives: using /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf to 
provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) 
in manual mode
  update-alternatives: using /usr/lib/i386-linux-gnu/mesa/ld.so.conf to provide 
/etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  I have tried various driver versions but none of them work now.

  I'm running:
  Kubuntu 15.04 (current/daily)
  Kernel: 3.18.0-9

  If you need any extra info, please comment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1412057/+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 1300308] Re: select items matching (ctrl+s) only selects one file in list view (due to interactive_search ubuntu change)

[Julien Olivier]

@seb128: OK, sorry, just replace Canonical by Ubuntu everywhere in my
post. But my opinion stands.

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

Title:
  select items matching (ctrl+s) only selects one file in list view
  (due to interactive_search ubuntu change)

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  steps to reproduce:
  1. open folder in files/nautilus which contains multiple files and/or folders
  2. type ctrl+s to bring up the select items matching dialog
  3. type glob pattern into text entry field which should match multiple files
  4. choose OK

  observed behavior:
   - only the first matching file is selected

  expected benavior:
   - all matching files should be selected

  This bug makes the select items matching feature completely
  nonfunctional, and is a regression from earlier versions of nautilus /
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 12:06:55 2014
  InstallationDate: Installed on 2014-03-01 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140228)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1300308/+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 1300308] Re: select items matching (ctrl+s) only selects one file in list view (due to interactive_search ubuntu change)

[Julien Olivier]

OFF TOPIC
For me, this bug would have never happened if Canonical stopped fixing 
upstream code. When upstream (here GNOME) chooses to modify its own code, 
Canonical should respect the developers and not patch the software to make it 
act like they desire. If the sofwtare isn't considered good enough by 
Canonical, instead of patching it, they should just switch to another piece of 
software, leaving the original code untouched.
/OFF TOPIC

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

Title:
  select items matching (ctrl+s) only selects one file in list view
  (due to interactive_search ubuntu change)

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  steps to reproduce:
  1. open folder in files/nautilus which contains multiple files and/or folders
  2. type ctrl+s to bring up the select items matching dialog
  3. type glob pattern into text entry field which should match multiple files
  4. choose OK

  observed behavior:
   - only the first matching file is selected

  expected benavior:
   - all matching files should be selected

  This bug makes the select items matching feature completely
  nonfunctional, and is a regression from earlier versions of nautilus /
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 12:06:55 2014
  InstallationDate: Installed on 2014-03-01 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140228)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1300308/+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 1300308] Re: select items matching (ctrl+s) only selects one file in list view

[Julien Olivier]

Hi, I've tested in Nautilus 3.12.1 from Debian and I don't see this bug.
So it seems that this is *not* an upstream bug.

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

Title:
  select items matching (ctrl+s) only selects one file in list view

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  steps to reproduce:
  1. open folder in files/nautilus which contains multiple files and/or folders
  2. type ctrl+s to bring up the select items matching dialog
  3. type glob pattern into text entry field which should match multiple files
  4. choose OK

  observed behavior:
   - only the first matching file is selected

  expected benavior:
   - all matching files should be selected

  This bug makes the select items matching feature completely
  nonfunctional, and is a regression from earlier versions of nautilus /
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 12:06:55 2014
  InstallationDate: Installed on 2014-03-01 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140228)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1300308/+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 1240198] Re: Wrong keyboard layout active after booting into desktop

[Julien Olivier]

@mniess

Apparently, you need to test your patch against Utopic to get this
finally fixed. Could you do it please?

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=de_DE.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL=pc105
  XKBLAYOUT=de
  XKBVARIANT=
  XKBOPTIONS=

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+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 995788] Re: rhythmbox music player keeps playing after being closed down

[Julien Olivier]

Now that there's an Ubuntu-Gnome distribution, the patch should be
reverted so that Rhythmbox works as expected in Ubuntu-GNOME. And stock
Ubuntu should fix Rhythmbox by having a rhythmbox-unity package or
something like that.

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

Title:
  rhythmbox music player keeps playing after being closed down

Status in “rhythmbox” package in Ubuntu:
  Invalid

Bug description:
  I was playing a song using rhythmbox music player and had enough so I
  closed the program by clicking the little x in the top-left corner.
  This closed the window alright, but the music kept playing.  In fact,
  after the current song finished, the next song in the list started to
  play.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: rhythmbox 2.96-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Mon May  7 16:44:59 2012
  ExecutablePath: /usr/bin/rhythmbox
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to precise on 2012-05-01 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/995788/+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 38512] Re: Window close should close, not quit

[Julien Olivier]

Now that there's an Ubuntu-Gnome distribution, the patch should be
reverted so that Rhythmbox works as expected in Ubuntu-GNOME. And stock
Ubuntu should fix Rhythmbox by having a rhythmbox-unity package or
something like that. There's no reason why GNOME users shuld suffer from
Unity's behaviour.

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

Title:
  Window close should close, not quit

Status in The Rhythmbox Music Management Application:
  Fix Released
Status in “rhythmbox” package in Ubuntu:
  Fix Released
Status in “rhythmbox” package in Debian:
  Fix Released

Bug description:
  Clicking the close button in the window titlebar should be the same as
  choosing File - Close -- it should minimize rhythmbox to the tray.
  Currently, clicking the window close button quits the application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/38512/+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 798377] Re: empathy is using lot of cpu when opening the window chat

[Julien Olivier]

I confirm the bug is back in Trusty when using gnome-online-accounts
with a GMail account. And, by the way, the same bug occurs with gnome-
contacts too. Both workd perfectly a few weeks ago, so something must
have broken very recently.

Tasks: 208 total,   4 running, 204 sleeping,   0 stopped,   0 zombie
%Cpu(s): 58,3 us,  5,8 sy,  0,4 ni, 33,4 id,  1,7 wa,  0,0 hi,  0,5 si,  0,0 st
KiB Mem:   3884928 total,  2837084 used,  1047844 free,80588 buffers
KiB Swap:  8388604 total,   181340 used,  8207264 free.  1221000 cached Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
29634 julien20   0  487608 119572  63156 R  83,9  3,1   0:12.47 empathy-ch+ 
 4050 julien20   0  443464  59092  33484 R  73,5  1,5   1:27.30 empathy 
 3598 julien20   0  566412 138292  48756 S   5,2  3,6  14:19.65 gnome-shell 
29675 julien20   07084   2724   2328 R   5,2  0,1   0:00.02 top 
1 root  20   04424   2268   1268 S   0,0  0,1   0:06.56 init
2 root  20   0   0  0  0 S   0,0  0,0   0:00.01 kthreadd

** Changed in: empathy (Ubuntu)
   Status: Invalid = New

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

Title:
  empathy is using lot of cpu when opening the window chat

Status in Chat app, and Telepathy user interface:
  Fix Released
Status in “empathy” package in Ubuntu:
  New
Status in “gtk+3.0” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: empathy

  1) Open empathy
  2) Connect to network
  3) open windows of chat
  4) full load empathy-chat

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.1.2.1-1ubuntu1
  Uname: Linux 3.0.0-0300rc3-generic x86_64
  Architecture: amd64
  Date: Thu Jun 16 14:39:06 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110531.1)
  ProcEnviron:
   LANGUAGE=es_CL:es_ES:en
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/798377/+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 1079315] Re: Gnome contacts hangs with 100% CPU and growing memory.

[Julien Olivier]

I confirm this bug in Trusty.

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

Title:
  Gnome contacts hangs with 100% CPU and growing memory.

Status in “gnome-contacts” package in Ubuntu:
  Confirmed

Bug description:
  What I expected:
  That gnome-contacts would open and allow me to edit my contacts.

  What actually happened:
  The WM window decoration appeared but no application was drawn inside the 
window.  The gnome-contacts process run with 100% cpu usage and continuously 
growing memory usage until I kill it.

  This appears to be the same behavior as bug #1070315 that I filed against 
empathy so it's probably a common library.
  I've attached three backtraces which I collected by attaching to the 
gnome-contacts process and running the following commands:

  thread apply all bt
  cont
  wait ~ 10 seconds
  thread apply all bt
  cont
  wait ~10 seconds
  thread apply all bt

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-contacts 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Nov 15 12:58:36 2012
  InstallationDate: Installed on 2012-05-25 (173 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: gnome-contacts
  UpgradeStatus: Upgraded to quantal on 2012-10-22 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1079315/+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 1070315] Re: empathy hang at 100% cpu and 3Gig of memory

[Julien Olivier]

I confirm the bug is still present in Trusty.

** Changed in: empathy (Ubuntu)
   Status: Expired = New

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

Title:
  empathy hang at 100% cpu and 3Gig of memory

Status in “empathy” package in Ubuntu:
  New

Bug description:
  When I start empathy it becomes unresponsive while consuming 100% cpu
  and rapidly growing it's memory footprint.  I killed it at 3.2Gig
  reported by process manager after running strace for a few seconds.
  It appears to be repeatedly mmap'ing something.

  empathy worked fine on 12.04, I upgraded to 12.10 via the updater last
  night.

  Process 10517 attached - interrupt to quit
  brk(0xbcb52000) = 0xbcb52000
  brk(0xbcb7a000) = 0xbcb7a000
  brk(0xbcba4000) = 0xbcba4000
  brk(0xbcbcf000) = 0xbcbcf000
  brk(0xbcbfd000) = 0xbcbfd000
  brk(0xbcc2c000) = 0xbcc2c000
  mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fc527e6
  brk(0xbcc5d000) = 0xbcc5d000
  brk(0xbcc91000) = 0xbcc91000
  brk(0xbccc7000) = 0xbccc7000
  brk(0xbccff000) = 0xbccff000
  brk(0xbcd2) = 0xbcd2
  brk(0xbcd43000) = 0xbcd43000
  brk(0xbcd6b000) = 0xbcd6b000
  brk(0xbcd91000) = 0xbcd91000
  brk(0xbcdb3000) = 0xbcdb3000
  brk(0xbcdd8000) = 0xbcdd8000
  brk(0xbce02000) = 0xbce02000
  brk(0xbce31000) = 0xbce31000
  brk(0xbce57000) = 0xbce57000
  brk(0xbce7f000) = 0xbce7f000
  brk(0xbceaa000) = 0xbceaa000
  brk(0xbced8000) = 0xbced8000
  brk(0xbcf0b000) = 0xbcf0b000
  brk(0xbcf42000) = 0xbcf42000
  brk(0xbcf63000) = 0xbcf63000
  brk(0xbcf9d000) = 0xbcf9d000
  brk(0xbcfbf000) = 0xbcfbf000
  brk(0xbcfe1000) = 0xbcfe1000
  brk(0xbd005000) = 0xbd005000
  brk(0xbd02b000) = 0xbd02b000
  mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fc527e58000
  brk(0xbd052000) = 0xbd052000
  brk(0xbd07b000) = 0xbd07b000
  brk(0xbd0a6000) = 0xbd0a6000
  brk(0xbd0d2000) = 0xbd0d2000
  brk(0xbd101000) = 0xbd101000
  brk(0xbd131000) = 0xbd131000
  brk(0xbd164000) = 0xbd164000
  brk(0xbd198000) = 0xbd198000
  brk(0xbd1cf000) = 0xbd1cf000
  brk(0xbd1f) = 0xbd1f
  brk(0xbd211000) = 0xbd211000
  brk(0xbd235000) = 0xbd235000
  brk(0xbd25d000) = 0xbd25d000
  brk(0xbd285000) = 0xbd285000
  brk(0xbd2a7000) = 0xbd2a7000
  brk(0xbd2cf000) = 0xbd2cf000
  brk(0xbd2fc000) = 0xbd2fc000
  brk(0xbd31d000) = 0xbd31d000
  brk(0xbd342000) = 0xbd342000
  brk(0xbd369000) = 0xbd369000
  brk(0xbd394000) = 0xbd394000
  brk(0xbd3c3000) = 0xbd3c3000
  brk(0xbd3f6000) = 0xbd3f6000
  brk(0xbd42d000) = 0xbd42d000
  mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fc527e5
  brk(0xbd468000) = 0xbd468000
  brk(0xbd4a5000) = 0xbd4a5000
  brk(0xbd4cc000) = 0xbd4cc000
  brk(0xbd4f) = 0xbd4f
  brk(0xbd516000) = 0xbd516000
  brk(0xbd53d000) = 0xbd53d000
  brk(0xbd566000) = 0xbd566000
  brk(0xbd591000) = 0xbd591000
  brk(0xbd5bd000) = 0xbd5bd000
  brk(0xbd5eb000) = 0xbd5eb000
  brk(0xbd61c000) = 0xbd61c000
  brk(0xbd64e000) = 0xbd64e000
  brk(0xbd683000) = 0xbd683000
  brk(0xbd6ba000) = 0xbd6ba000
  brk(0xbd6de000) = 0xbd6de000
  brk(0xbd701000) = 0xbd701000
  brk(0xbd724000) = 0xbd724000
  brk(0xbd746000)

[Desktop-packages] [Bug 1070315] Re: empathy hang at 100% cpu and 3Gig of memory

[Julien Olivier]

OK, I found the culprit: I had thousands of bogus gmail contacts. I
deleted them and now everything is fine. Sorry!

** Changed in: empathy (Ubuntu)
   Status: New = Invalid

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

Title:
  empathy hang at 100% cpu and 3Gig of memory

Status in “empathy” package in Ubuntu:
  Invalid

Bug description:
  When I start empathy it becomes unresponsive while consuming 100% cpu
  and rapidly growing it's memory footprint.  I killed it at 3.2Gig
  reported by process manager after running strace for a few seconds.
  It appears to be repeatedly mmap'ing something.

  empathy worked fine on 12.04, I upgraded to 12.10 via the updater last
  night.

  Process 10517 attached - interrupt to quit
  brk(0xbcb52000) = 0xbcb52000
  brk(0xbcb7a000) = 0xbcb7a000
  brk(0xbcba4000) = 0xbcba4000
  brk(0xbcbcf000) = 0xbcbcf000
  brk(0xbcbfd000) = 0xbcbfd000
  brk(0xbcc2c000) = 0xbcc2c000
  mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fc527e6
  brk(0xbcc5d000) = 0xbcc5d000
  brk(0xbcc91000) = 0xbcc91000
  brk(0xbccc7000) = 0xbccc7000
  brk(0xbccff000) = 0xbccff000
  brk(0xbcd2) = 0xbcd2
  brk(0xbcd43000) = 0xbcd43000
  brk(0xbcd6b000) = 0xbcd6b000
  brk(0xbcd91000) = 0xbcd91000
  brk(0xbcdb3000) = 0xbcdb3000
  brk(0xbcdd8000) = 0xbcdd8000
  brk(0xbce02000) = 0xbce02000
  brk(0xbce31000) = 0xbce31000
  brk(0xbce57000) = 0xbce57000
  brk(0xbce7f000) = 0xbce7f000
  brk(0xbceaa000) = 0xbceaa000
  brk(0xbced8000) = 0xbced8000
  brk(0xbcf0b000) = 0xbcf0b000
  brk(0xbcf42000) = 0xbcf42000
  brk(0xbcf63000) = 0xbcf63000
  brk(0xbcf9d000) = 0xbcf9d000
  brk(0xbcfbf000) = 0xbcfbf000
  brk(0xbcfe1000) = 0xbcfe1000
  brk(0xbd005000) = 0xbd005000
  brk(0xbd02b000) = 0xbd02b000
  mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fc527e58000
  brk(0xbd052000) = 0xbd052000
  brk(0xbd07b000) = 0xbd07b000
  brk(0xbd0a6000) = 0xbd0a6000
  brk(0xbd0d2000) = 0xbd0d2000
  brk(0xbd101000) = 0xbd101000
  brk(0xbd131000) = 0xbd131000
  brk(0xbd164000) = 0xbd164000
  brk(0xbd198000) = 0xbd198000
  brk(0xbd1cf000) = 0xbd1cf000
  brk(0xbd1f) = 0xbd1f
  brk(0xbd211000) = 0xbd211000
  brk(0xbd235000) = 0xbd235000
  brk(0xbd25d000) = 0xbd25d000
  brk(0xbd285000) = 0xbd285000
  brk(0xbd2a7000) = 0xbd2a7000
  brk(0xbd2cf000) = 0xbd2cf000
  brk(0xbd2fc000) = 0xbd2fc000
  brk(0xbd31d000) = 0xbd31d000
  brk(0xbd342000) = 0xbd342000
  brk(0xbd369000) = 0xbd369000
  brk(0xbd394000) = 0xbd394000
  brk(0xbd3c3000) = 0xbd3c3000
  brk(0xbd3f6000) = 0xbd3f6000
  brk(0xbd42d000) = 0xbd42d000
  mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fc527e5
  brk(0xbd468000) = 0xbd468000
  brk(0xbd4a5000) = 0xbd4a5000
  brk(0xbd4cc000) = 0xbd4cc000
  brk(0xbd4f) = 0xbd4f
  brk(0xbd516000) = 0xbd516000
  brk(0xbd53d000) = 0xbd53d000
  brk(0xbd566000) = 0xbd566000
  brk(0xbd591000) = 0xbd591000
  brk(0xbd5bd000) = 0xbd5bd000
  brk(0xbd5eb000) = 0xbd5eb000
  brk(0xbd61c000) = 0xbd61c000
  brk(0xbd64e000) = 0xbd64e000
  brk(0xbd683000) = 0xbd683000
  brk(0xbd6ba000) = 0xbd6ba000
  brk(0xbd6de000) = 0xbd6de000
  brk(0xbd701000) = 0xbd701000
  

[Desktop-packages] [Bug 798377] Re: empathy is using lot of cpu when opening the window chat

[Julien Olivier]

OK, I found the culprit: I had thousands of bogus gmail contacts
(created by a bug in thunderbird's google contacts addon). I deleted
them and now everything is fine. Sorry!

** Changed in: empathy (Ubuntu)
   Status: New = Invalid

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

Title:
  empathy is using lot of cpu when opening the window chat

Status in Chat app, and Telepathy user interface:
  Fix Released
Status in “empathy” package in Ubuntu:
  Invalid
Status in “gtk+3.0” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: empathy

  1) Open empathy
  2) Connect to network
  3) open windows of chat
  4) full load empathy-chat

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.1.2.1-1ubuntu1
  Uname: Linux 3.0.0-0300rc3-generic x86_64
  Architecture: amd64
  Date: Thu Jun 16 14:39:06 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110531.1)
  ProcEnviron:
   LANGUAGE=es_CL:es_ES:en
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/798377/+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 1079315] Re: Gnome contacts hangs with 100% CPU and growing memory.

[Julien Olivier]

OK, I found the culprit (for me, at least): I had thousands of bogus
gmail contacts (created by a bug in thunderbird's google contacts
addon). I deleted them and now everything is fine. Sorry!

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

Title:
  Gnome contacts hangs with 100% CPU and growing memory.

Status in “gnome-contacts” package in Ubuntu:
  Confirmed

Bug description:
  What I expected:
  That gnome-contacts would open and allow me to edit my contacts.

  What actually happened:
  The WM window decoration appeared but no application was drawn inside the 
window.  The gnome-contacts process run with 100% cpu usage and continuously 
growing memory usage until I kill it.

  This appears to be the same behavior as bug #1070315 that I filed against 
empathy so it's probably a common library.
  I've attached three backtraces which I collected by attaching to the 
gnome-contacts process and running the following commands:

  thread apply all bt
  cont
  wait ~ 10 seconds
  thread apply all bt
  cont
  wait ~10 seconds
  thread apply all bt

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-contacts 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Nov 15 12:58:36 2012
  InstallationDate: Installed on 2012-05-25 (173 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: gnome-contacts
  UpgradeStatus: Upgraded to quantal on 2012-10-22 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1079315/+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 1312769] Re: Bogus desktop bookmark in Nautilus sidebar under gnome-shell

[Julien Olivier]

The bug is still present in Utopic. Is there any reason why this bug is
stuck in this state?

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

Title:
  Bogus desktop bookmark in Nautilus sidebar under gnome-shell

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

Bug description:
  In Nautils 3.10.1 from Ubuntu GNOME Trusty, there is a desktop
  bookmark in the sidebar, but gnome-shell doesn't have a desktop
  metaphor, so it doesn't make any sense. More over, clicking on it
  doesn't do anything, and it doesn't appear in Nautilus' bookmark
  editor, so it's impossible to remove.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Apr 25 16:13:50 2014
  GsettingsChanges:
   
  InstallationDate: Installed on 2010-09-15 (1317 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1312769/+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 1079731] Re: Minecraft can't go fullscreen

[Julien Olivier]

I confirm this bug, using gnome-shell in Ubuntu-GNOME 14.04. I found a
simple workaround though: just launch the display properties from gnome
control center and change the resolution, then change it back to the
normal resolution. Now, if you press F11, minecraft should go
fullscreen.

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

Title:
  Minecraft can't go fullscreen

Status in Compiz:
  Confirmed
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  Hello ,

  I got problems with minecraft after upgrade to 12.10 .Minecraft can't
  go to fullscreen .After pressing F11 i see black screen for 3 seconds
  and after that minecraft is in window again ( no errors in terminal ).
  It works in fluxbox and gnome3 without problems so i suspect this is
  compiz/nvidia related bug .

  I had this bug also  in 12.04 after upgrade to nvidia 304.xx driver
  from stock 295.xx . Also tried upgrade to beta driver 310.14 but still
  the same issue .

  Additional info : minecraft is written in java, fresh installed 12.10
  without any ccsm tweaks .

  Please let me know if you need additional info

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  310.14  Tue Oct  9 11:52:41 
PDT 2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov 16 16:02:37 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-experimental-310, 310.14, 3.5.0-18-generic, x86_64: 
installed
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Giga-byte Technology Device [1458:3527]
  InstallationDate: Installed on 2012-11-13 (2 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic 
root=UUID=4a084bc7-c3db-4f85-9026-ba35d1a18f5e ro quiet splash
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77M-D3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1079731/+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 1312769] [NEW] Bogus desktop bookmark in Nautilus sidebar

[Julien Olivier]

Public bug reported:

In Nautils 3.10.1 from Ubuntu GNOME Trusty, there is a desktop
bookmark in the sidebar, but gnome-shell doesn't have a desktop
metaphor, so it doesn't make any sense. More over, clicking on it
doesn't do anything, and it doesn't appear in Nautilus' bookmark editor,
so it's impossible to remove.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CurrentDesktop: GNOME
Date: Fri Apr 25 16:13:50 2014
GsettingsChanges:
 
InstallationDate: Installed on 2010-09-15 (1317 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
SourcePackage: nautilus
UpgradeStatus: Upgraded to trusty on 2014-04-18 (7 days ago)

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


** Tags: apport-bug i386 trusty

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

Title:
  Bogus desktop bookmark in Nautilus sidebar

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  In Nautils 3.10.1 from Ubuntu GNOME Trusty, there is a desktop
  bookmark in the sidebar, but gnome-shell doesn't have a desktop
  metaphor, so it doesn't make any sense. More over, clicking on it
  doesn't do anything, and it doesn't appear in Nautilus' bookmark
  editor, so it's impossible to remove.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Apr 25 16:13:50 2014
  GsettingsChanges:
   
  InstallationDate: Installed on 2010-09-15 (1317 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312769/+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 880657] Re: stuck retrieving emails from IMAP

[Julien Olivier]

This problem appeared for me on Ubuntu Trusty with a GMail account
created using Gnome Online Accounts. The same account worked flawlessly
on previous version of Evolution.

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

Title:
  stuck retrieving emails from IMAP

Status in “evolution” package in Ubuntu:
  Confirmed

Bug description:
  Evolution starts fine, collects email messages.  On subsequent
  checking of server get stuck i fetching mail, I am unable to cancel
  this nor able to close evolution.   Other accounts on POP servers not
  affected

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.2.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Mon Oct 24 16:48:20 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: evolution
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/880657/+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 915906] Re: Vino does not work with compositing using ATI open source driver

[Julien Olivier]

This seems fixed now.

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

Title:
  Vino does not work with compositing using ATI open source driver

Status in “xorg-server” package in Ubuntu:
  Incomplete

Bug description:
  Vino, the built in VNC server in Ubuntu, has had a problem for many
  releases where it won't update the display when connected remotely if
  compositing is enabled. This can be easily reproduced using Unity and
  gnome-shell.

  Apparently, bug #772873 only takes care of the same bug with the fglrx
  driver, so this bug is there to take care of the issue with ATI's open
  source driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/915906/+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 1247468] Re: Network-manager is disabled after suspend

[Julien Olivier]

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

** This bug has been marked a duplicate of bug 1184262
   times out too early, stuck in PrepareForSleep, causing network and other 
services to not resume

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

Title:
  Network-manager is disabled after suspend

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Upgraded recently to 13.10 (saucy). After the upgrade I could not
  connect to a wireless network after resuming from suspend. (It worked
  before the upgrade.) Eventually I figured out that I could kill
  network manager and restart it to fix the problem.

  Steps to Reproduce:
  1. suspend
  2. resume. nm-applet show networking is disabled. Checking Enable 
Networking has no effect.

  Workaround:
  After resume:
   sudo stop network-manager
   sudo start network-manager

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Sat Nov  2 16:12:01 2013
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2010-04-30 (1282 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.7  metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (15 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1247468/+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 1057986] Re: Graphical artifacts when open some images with EOG

[Julien Olivier]

@seb128: No, sorry, I didn't see the OS version in the report. In my
case, it's in Saucy.

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

Title:
  Graphical artifacts when open some images with EOG

Status in “eog” package in Ubuntu:
  Incomplete

Bug description:
  OS: Ubuntu 12.04.1 LTS
  (latest updates installed for 2012-09-28)
  EOG: 3.4.2-0ubuntu1.1

  I experience some artifacts when open images with EOG (see attached 
screenshot):
- to much bright image;
- random bright vertical lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1057986/+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 1247800] [NEW] Picture displayed with noise in EOG

[Julien Olivier]

Public bug reported:

In the attached screenshot, you can clearly see artifacts in a PNG
opened in both EOG and GIMP. The picture in EOG seems to have a lot of
noise, but not in GIMP.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: eog 3.8.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
Date: Mon Nov  4 12:24:10 2013
InstallationDate: Installed on 2010-09-15 (1145 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
MarkForUpload: True
SourcePackage: eog
UpgradeStatus: Upgraded to saucy on 2011-04-01 (948 days ago)

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


** Tags: apport-bug i386 saucy

** Attachment added: The glitch in action
   
https://bugs.launchpad.net/bugs/1247800/+attachment/3899752/+files/eog-bug.png

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

Title:
  Picture displayed with noise in EOG

Status in “eog” package in Ubuntu:
  New

Bug description:
  In the attached screenshot, you can clearly see artifacts in a PNG
  opened in both EOG and GIMP. The picture in EOG seems to have a lot of
  noise, but not in GIMP.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eog 3.8.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Nov  4 12:24:10 2013
  InstallationDate: Installed on 2010-09-15 (1145 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: eog
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (948 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1247800/+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 1057986] Re: Graphical artifacts when open some images with EOG

[Julien Olivier]

@seb128: I think my bug is totally unrelated to the color profile bugs.
I submitted a new report as bug #1247800.

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

Title:
  Graphical artifacts when open some images with EOG

Status in “eog” package in Ubuntu:
  Incomplete

Bug description:
  OS: Ubuntu 12.04.1 LTS
  (latest updates installed for 2012-09-28)
  EOG: 3.4.2-0ubuntu1.1

  I experience some artifacts when open images with EOG (see attached 
screenshot):
- to much bright image;
- random bright vertical lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1057986/+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 1247800] Re: Picture displayed with noise in EOG

[Julien Olivier]

The original picture is here: http://julien.olivier.free.fr/Scans-1.png
.

The picture is very large, so the issue may be in the scaling method
used by EOG vs the one used in GIMP. More over, if I open it right into
Firefox, I notice that, while the picture is loading, it displays the
same nois all over it. But, when finally loaded, it's clean again.

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

Title:
  Picture displayed with noise in EOG

Status in “eog” package in Ubuntu:
  Incomplete

Bug description:
  In the attached screenshot, you can clearly see artifacts in a PNG
  opened in both EOG and GIMP. The picture in EOG seems to have a lot of
  noise, but not in GIMP.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eog 3.8.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Nov  4 12:24:10 2013
  InstallationDate: Installed on 2010-09-15 (1145 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: eog
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (948 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1247800/+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 1247800] Re: Picture displayed with noise in EOG

[Julien Olivier]

It's here: https://bugzilla.gnome.org/show_bug.cgi?id=711410

Thanks.

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

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

Title:
  Picture displayed with noise in EOG

Status in “eog” package in Ubuntu:
  New

Bug description:
  In the attached screenshot, you can clearly see artifacts in a PNG
  opened in both EOG and GIMP. The picture in EOG seems to have a lot of
  noise, but not in GIMP.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eog 3.8.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Nov  4 12:24:10 2013
  InstallationDate: Installed on 2010-09-15 (1145 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: eog
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (948 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1247800/+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 1057986] Re: Graphical artifacts when open some images with EOG

[Julien Olivier]

In the attached screenshot, you can clearly see artifacts in a JPEG
opened in both EOG and GIMP. The picture in EOG seems to have a lot of
noise, but not in GIMP.

** Attachment added: Another kind of artifact
   
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1057986/+attachment/3898351/+files/Capture%20d%27%C3%A9cran%20de%202013-11-02%2012%3A26%3A38.png

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

Title:
  Graphical artifacts when open some images with EOG

Status in “eog” package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 12.04.1 LTS
  (latest updates installed for 2012-09-28)
  EOG: 3.4.2-0ubuntu1.1

  I experience some artifacts when open images with EOG (see attached 
screenshot):
- to much bright image;
- random bright vertical lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1057986/+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 1057986] Re: Graphical artifacts when open some images with EOG

[Julien Olivier]

Just a correction: the original picture opened in both EOG and GIMP is a
PNG, not a JPEG.

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

Title:
  Graphical artifacts when open some images with EOG

Status in “eog” package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 12.04.1 LTS
  (latest updates installed for 2012-09-28)
  EOG: 3.4.2-0ubuntu1.1

  I experience some artifacts when open images with EOG (see attached 
screenshot):
- to much bright image;
- random bright vertical lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1057986/+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 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume

[Julien Olivier]

I occasionally have another suspend-related proble that might be related
to this one somehow: after opening my lid, sometimes the laptop resumes,
then suspends again automatically after a few seconds. If I then press
the power button to resume again, it does the same again and again. And,
after 3 or 4 suspend-resume loops, it finally settles down and resumes
correctly. I guess some internal value is randomly stuck to the
suspended state...

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

Title:
  [logind] stuck in PrepareForSleep, causing network and other services
  to not resume

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1235933] Re: Evolution not translated to French

[Julien Olivier]

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

** This bug has been marked a duplicate of bug 1241109
   evolution is no longer translated

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

Title:
  Evolution not translated to French

Status in “evolution” package in Ubuntu:
  Confirmed

Bug description:
  My desktop is set up in the French language, but Evolution is the only
  installed application to be displayed in English. Gnome-language-
  selector doesn't suggest to install any missing package though. This
  is after upgrading to Saucy. It was in French when running Raring.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evolution 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Sun Oct  6 13:25:49 2013
  InstallationDate: Installed on 2010-09-15 (1116 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (919 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1235933/+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 1234469] Re: Network does not come up after resuming from suspend.

[Julien Olivier]

That kind of bugs should really prevent a distribution from being
released... I know it's not Debian, but I didn't think the quality
standard was *that* low.

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

Title:
  Network does not come up after resuming from suspend.

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  When my computer wakes up from being suspended, the wireless network 
connection doesn't come back up.
  I'm able to fix the problem by running nmcli nm sleep false, which causes 
the wireless card to reconnect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu21
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  2 20:21:33 2013
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-09 (54 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  IpRoute:
   default via 192.168.125.1 dev wlan0  proto static 
   192.168.125.0/24 dev wlan0  proto kernel  scope link  src 192.168.125.8  
metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to saucy on 2013-08-09 (54 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 199a6c07f-9a94-4c8e-82dd-0381befd6f90   
802-3-ethernet1380753272   Wed 02 Oct 2013 05:34:32 PM CDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   9739  172c6f5c-b69c-40dd-ac1b-a279c84a17f8   
802-11-wireless   1380763079   Wed 02 Oct 2013 08:17:59 PM CDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+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 1238663] Re: Laptop suspends itself while on AC power

[Julien Olivier]

It happened again, and I attached the requested log.

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Invalid = New

** Attachment added: gnome-settings-daemon.log
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1238663/+attachment/3877304/+files/gnome-settings-daemon.log

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

Title:
  Laptop suspends itself while on AC power

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

Bug description:
  When I set my laptop to not supend when on AC power, it still suspend
  automatically after about an hour. It did work correctly in raring but
  not anymore in saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Fri Oct 11 15:20:43 2013
  InstallationDate: Installed on 2010-09-15 (1121 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (924 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1238663/+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 1234469] Re: Network does not come up after resuming from suspend.

[Julien Olivier]

Maybe a hint:

pm-utils (1.4.1-9git1) raring; urgency=low

  Upload current Debian packaging git head.

  * debian/rules: Stop installing sleep.d/55NetworkManager. Current
NetworkManager does not even expose this API any more, so the
sleep()/wake() calls just always fail. As NM is apparently able to deal
with suspends just fine, no need to waste cycles on this.

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

Title:
  Network does not come up after resuming from suspend.

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  When my computer wakes up from being suspended, the wireless network 
connection doesn't come back up.
  I'm able to fix the problem by running nmcli nm sleep false, which causes 
the wireless card to reconnect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu21
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  2 20:21:33 2013
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-09 (54 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  IpRoute:
   default via 192.168.125.1 dev wlan0  proto static 
   192.168.125.0/24 dev wlan0  proto kernel  scope link  src 192.168.125.8  
metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to saucy on 2013-08-09 (54 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 199a6c07f-9a94-4c8e-82dd-0381befd6f90   
802-3-ethernet1380753272   Wed 02 Oct 2013 05:34:32 PM CDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   9739  172c6f5c-b69c-40dd-ac1b-a279c84a17f8   
802-11-wireless   1380763079   Wed 02 Oct 2013 08:17:59 PM CDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+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 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm

[Julien Olivier]

I had the exact same bug a few months ago. The issue was that
NetworkManager is supposed to work with systemd, but Ubuntu chose to
implement its own replacement to systemd instead (libsystemd-daemon0 I
think). The issue I had previously was caused by libsystemd-daemon0 not
sending the resume event to NetworkManager. I'd bet this is tre same
issue here...

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

Title:
  network-manager has decided that networking is disabled, cannot be re-
  enabled from lightdm

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm

[Julien Olivier]

I've just found it: it's probably this bug: https://bugs.launchpad.net
/ubuntu-gnome/+bug/1187005

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

Title:
  network-manager has decided that networking is disabled, cannot be re-
  enabled from lightdm

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1238663] [NEW] Laptop suspends itself while on AC power

[Julien Olivier]

Public bug reported:

When I set my laptop to not supend when on AC power, it still suspend
automatically after about an hour. It did work correctly in raring but
not anymore in saucy.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-settings-daemon 3.8.5-0ubuntu7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Fri Oct 11 15:20:43 2013
InstallationDate: Installed on 2010-09-15 (1121 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
MarkForUpload: True
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to saucy on 2011-04-01 (924 days ago)

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


** Tags: apport-bug i386 saucy

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

Title:
  Laptop suspends itself while on AC power

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

Bug description:
  When I set my laptop to not supend when on AC power, it still suspend
  automatically after about an hour. It did work correctly in raring but
  not anymore in saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Fri Oct 11 15:20:43 2013
  InstallationDate: Installed on 2010-09-15 (1121 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (924 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1238663/+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 1238663] Re: Laptop suspends itself while on AC power

[Julien Olivier]

This might be a duplicate of #1055874, but I'm not quite sure...

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

Title:
  Laptop suspends itself while on AC power

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

Bug description:
  When I set my laptop to not supend when on AC power, it still suspend
  automatically after about an hour. It did work correctly in raring but
  not anymore in saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Fri Oct 11 15:20:43 2013
  InstallationDate: Installed on 2010-09-15 (1121 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (924 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1238663/+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 1238663] Re: Laptop suspends itself while on AC power

[Julien Olivier]

Yes, I use Ubuntu GNOME, not stock Ubuntu. I don't even have Unity
installed but I'll try it if needed as soon as I can.

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

Title:
  Laptop suspends itself while on AC power

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

Bug description:
  When I set my laptop to not supend when on AC power, it still suspend
  automatically after about an hour. It did work correctly in raring but
  not anymore in saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Fri Oct 11 15:20:43 2013
  InstallationDate: Installed on 2010-09-15 (1121 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (924 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1238663/+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 1238663] Re: Laptop suspends itself while on AC power

[Julien Olivier]

Oddly enough, I am now unable to reproduce this bug... Sorry for the
noise, you can close it and I'll re-open it if it bites me again.

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

Title:
  Laptop suspends itself while on AC power

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

Bug description:
  When I set my laptop to not supend when on AC power, it still suspend
  automatically after about an hour. It did work correctly in raring but
  not anymore in saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Fri Oct 11 15:20:43 2013
  InstallationDate: Installed on 2010-09-15 (1121 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (924 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1238663/+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 1235864] [NEW] Network down after resume

[Julien Olivier]

Public bug reported:

In Saucy, after resuming from suspend, the network is disabled. Running
sudo restart network-manager fixes the problem each time.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: network-manager 0.9.8.0-0ubuntu21
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Sun Oct  6 08:11:23 2013
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2010-09-15 (1116 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
IpRoute:
 default via 192.168.0.254 dev wlan2  proto static 
 192.168.0.0/24 dev wlan2  proto kernel  scope link  src 192.168.0.11  metric 9 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
MarkForUpload: True
NetworkManager.state:
 [main]
 WirelessEnabled=true
 NetworkingEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to saucy on 2011-04-01 (918 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth2   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
 wlan2  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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


** Tags: apport-bug i386 saucy

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

Title:
  Network down after resume

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  In Saucy, after resuming from suspend, the network is disabled.
  Running sudo restart network-manager fixes the problem each time.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu21
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Sun Oct  6 08:11:23 2013
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2010-09-15 (1116 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  IpRoute:
   default via 192.168.0.254 dev wlan2  proto static 
   192.168.0.0/24 dev wlan2  proto kernel  scope link  src 192.168.0.11  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   WirelessEnabled=true
   NetworkingEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (918 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth2   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan2  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1235864/+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 1235933] [NEW] Evolution not translated to French

[Julien Olivier]

Public bug reported:

My desktop is set up in the French language, but Evolution is the only
installed application to be displayed in English. Gnome-language-
selector doesn't suggest to install any missing package though. This is
after upgrading to Saucy. It was in French when running Raring.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: evolution 3.8.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Sun Oct  6 13:25:49 2013
InstallationDate: Installed on 2010-09-15 (1116 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
MarkForUpload: True
SourcePackage: evolution
UpgradeStatus: Upgraded to saucy on 2011-04-01 (919 days ago)

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


** Tags: apport-bug i386 saucy

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

Title:
  Evolution not translated to French

Status in “evolution” package in Ubuntu:
  New

Bug description:
  My desktop is set up in the French language, but Evolution is the only
  installed application to be displayed in English. Gnome-language-
  selector doesn't suggest to install any missing package though. This
  is after upgrading to Saucy. It was in French when running Raring.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evolution 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Sun Oct  6 13:25:49 2013
  InstallationDate: Installed on 2010-09-15 (1116 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (919 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1235933/+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 1180947] Re: online-accounts-preferences crashes immediately

[Julien Olivier]

Actually, I think I still had empathy 3.8.1. It seems fixed now.

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

Title:
  online-accounts-preferences crashes immediately

Status in “gnome-control-center-signon” package in Ubuntu:
  Incomplete

Bug description:
  julien@julien:~$ online-accounts-preferences

  ** (gnome-control-center:5296): WARNING **: Ignoring launcher gufw (missing 
desktop file)
  credentials-cc-panel-Message: cc-credentials-providers-model.vala:108: No 
desktop app info found for application name: evolution-data-server

  (gnome-control-center:5296): accounts-glib-CRITICAL **:
  ag_provider_get_icon_name: assertion `provider != NULL' failed

  (gnome-control-center:5296): GLib-GIO-CRITICAL **:
  g_icon_new_for_string: assertion `str != NULL' failed

  (gnome-control-center:5296): accounts-glib-CRITICAL **:
  ag_provider_get_name: assertion `provider != NULL' failed

  (gnome-control-center:5296): credentials-cc-panel-CRITICAL **:
  cc_credentials_providers_model_format_provider_description: assertion
  `provider != NULL' failed

  (gnome-control-center:5296): credentials-cc-panel-CRITICAL **: 
cc_credentials_providers_model_format_provider_tooltip: assertion `provider != 
NULL' failed
  credentials-cc-panel-Message: cc-credentials-providers-model.vala:108: No 
desktop app info found for application name: evolution-data-server

  (gnome-control-center:5296): credentials-cc-panel-WARNING **: cc-
  credentials-account-details-page.vala:442: Error looking up theme
  color

  (gnome-control-center:5296): credentials-cc-panel-WARNING **: 
cc-credentials-account-details-page.vala:346: Error looking up theme color
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'shotwell' with account '19'
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:129: No desktop app info found 
for application name: evolution-data-server
  **
  ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec 
!= NULL)
  Aborted (core dumped)

  This seems like a duplicate of bug #1177285, except that the other one
  seems fixed, but this one is very well alive in Raring.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Thu May 16 20:38:43 2013
  InstallationDate: Installed on 2010-09-15 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center-signon
  UpgradeStatus: Upgraded to raring on 2011-04-01 (776 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1180947/+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 1180275] Re: No way to update Google account credential

[Julien Olivier]

Adding the Google account to GOA (after removing everything related to
UOA) works for me. I'm using the staging PPA though.

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

Title:
  No way to update Google account credential

Status in “gnome-control-center-signon” package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu Gnome 13.04 + Gnome 3 ppa.

  To enable chat with Empathy, I added my Google account to UOA (GOA
  doesn't enable the chat yet). It works...for a while.

  After few days, the Google credentials get outdated. The issue is
  there is no way to update the credential except to remove the account
  and add it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Wed May 15 10:24:24 2013
  InstallationDate: Installed on 2013-05-06 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 
(20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center-signon
  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-signon/+bug/1180275/+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 1180947] [NEW] online-accounts-preferences crashes immediately

[Julien Olivier]

Public bug reported:

julien@julien:~$ online-accounts-preferences

** (gnome-control-center:5296): WARNING **: Ignoring launcher gufw (missing 
desktop file)
credentials-cc-panel-Message: cc-credentials-providers-model.vala:108: No 
desktop app info found for application name: evolution-data-server

(gnome-control-center:5296): accounts-glib-CRITICAL **:
ag_provider_get_icon_name: assertion `provider != NULL' failed

(gnome-control-center:5296): GLib-GIO-CRITICAL **:
g_icon_new_for_string: assertion `str != NULL' failed

(gnome-control-center:5296): accounts-glib-CRITICAL **:
ag_provider_get_name: assertion `provider != NULL' failed

(gnome-control-center:5296): credentials-cc-panel-CRITICAL **:
cc_credentials_providers_model_format_provider_description: assertion
`provider != NULL' failed

(gnome-control-center:5296): credentials-cc-panel-CRITICAL **: 
cc_credentials_providers_model_format_provider_tooltip: assertion `provider != 
NULL' failed
credentials-cc-panel-Message: cc-credentials-providers-model.vala:108: No 
desktop app info found for application name: evolution-data-server

(gnome-control-center:5296): credentials-cc-panel-WARNING **: cc-
credentials-account-details-page.vala:442: Error looking up theme color

(gnome-control-center:5296): credentials-cc-panel-WARNING **: 
cc-credentials-account-details-page.vala:346: Error looking up theme color
credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'shotwell' with account '19'
credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:129: No desktop app info found 
for application name: evolution-data-server
**
ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec 
!= NULL)
Aborted (core dumped)

This seems like a duplicate of bug #1177285, except that the other one
seems fixed, but this one is very well alive in Raring.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Thu May 16 20:38:43 2013
InstallationDate: Installed on 2010-09-15 (974 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
MarkForUpload: True
SourcePackage: gnome-control-center-signon
UpgradeStatus: Upgraded to raring on 2011-04-01 (776 days ago)

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


** Tags: apport-bug gnome3-ppa i386 raring third-party-packages

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

Title:
  online-accounts-preferences crashes immediately

Status in “gnome-control-center-signon” package in Ubuntu:
  New

Bug description:
  julien@julien:~$ online-accounts-preferences

  ** (gnome-control-center:5296): WARNING **: Ignoring launcher gufw (missing 
desktop file)
  credentials-cc-panel-Message: cc-credentials-providers-model.vala:108: No 
desktop app info found for application name: evolution-data-server

  (gnome-control-center:5296): accounts-glib-CRITICAL **:
  ag_provider_get_icon_name: assertion `provider != NULL' failed

  (gnome-control-center:5296): GLib-GIO-CRITICAL **:
  g_icon_new_for_string: assertion `str != NULL' failed

  (gnome-control-center:5296): accounts-glib-CRITICAL **:
  ag_provider_get_name: assertion `provider != NULL' failed

  (gnome-control-center:5296): credentials-cc-panel-CRITICAL **:
  cc_credentials_providers_model_format_provider_description: assertion
  `provider != NULL' failed

  (gnome-control-center:5296): credentials-cc-panel-CRITICAL **: 
cc_credentials_providers_model_format_provider_tooltip: assertion `provider != 
NULL' failed
  credentials-cc-panel-Message: cc-credentials-providers-model.vala:108: No 
desktop app info found for application name: evolution-data-server

  (gnome-control-center:5296): credentials-cc-panel-WARNING **: cc-
  credentials-account-details-page.vala:442: Error looking up theme
  color

  (gnome-control-center:5296): credentials-cc-panel-WARNING **: 
cc-credentials-account-details-page.vala:346: Error looking up theme color
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'shotwell' with account '19'
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:129: No desktop app info found 
for application name: evolution-data-server
  **
  ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec 
!= NULL)
  Aborted (core dumped)

  This seems like a duplicate of bug #1177285, except that the other one
  seems fixed, but this one is very well alive in Raring.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: 

[Desktop-packages] [Bug 1177285] Re: gnome-control-center crashes on fill_contact_info_grid: assertion failed: (spec != NULL) after few seconds after opening online accounts

[Julien Olivier]

I'm using Ubuntu GNOME with the staging PPA, so I have Empathy 3.8.1,
which crashes the control center. I guess this fix should be ported to
this version too.

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

Title:
  gnome-control-center crashes on fill_contact_info_grid: assertion
  failed: (spec != NULL) after few seconds after opening online accounts

Status in “empathy” package in Ubuntu:
  Fix Released
Status in “gnome-online-accounts” package in Ubuntu:
  Invalid
Status in “empathy” source package in Raring:
  Fix Committed
Status in “gnome-online-accounts” source package in Raring:
  Invalid

Bug description:
  * Impact:
  empathy segfault sometimes on receiving invalid vcard informations

  * Test Case:
  not sure, some users seem to be getting that when opening the online accounts 
configuration dialog

  * Regression potential:
  limited, that's only addind an extra check to the code

  

  Ubuntu 13.04 x86_64

  Open system settings, click on online accounts. Accounts window
  appears for about a second, and then closes.

  Ran with gdb (with empathy-dbg) to get this:

  ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion
  failed: (spec != NULL)

  Backtrace:
  #0  0x75873037 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x75876698 in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2  0x761c63b6 in g_assertion_message () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x761c6914 in g_assertion_message_expr () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x7fffba276359 in fill_contact_info_grid (self=0x55dee1b0) at 
empathy-user-info.c:252
  #5  request_contact_info_cb (object=optimized out, res=optimized out, 
user_data=0x55dee1b0) at empathy-user-info.c:343
  #6  0x767171d7 in g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #7  0x767172d9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #8  0x761a3f05 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x761a4248 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x761a4304 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7674452c in g_application_run () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #12 0xb2ba in main ()

  Had no problems before upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1177285/+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 1176389] [NEW] Vertical scrolling disabled by default

[Julien Olivier]

Public bug reported:

On raring, vertical scrolling is disabled by default (no
/etc/X11/xorg.conf file). I have to execute synclient vertedgescroll=1
to activate it.

For information, it used to be activated by default on all previous
releases.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Sat May  4 19:50:49 2013
DistUpgraded: 2011-04-01 10:00:41,930 DEBUG enabling apt cron job
DistroCodename: raring
DistroVariant: ubuntu
InstallationDate: Installed on 2010-09-15 (962 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
MachineType: Dell Inc. Inspiron M301Z
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=63c58b0a-b2cc-4c78-87d0-4e1c0e8fc6a6 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to raring on 2011-04-01 (764 days ago)
dmi.bios.date: 07/16/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A03
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/16/2010:svnDellInc.:pnInspironM301Z:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
dmi.product.name: Inspiron M301Z
dmi.product.version: A03
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug gnome3-ppa i386 raring third-party-packages ubuntu

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

Title:
  Vertical scrolling disabled by default

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  New

Bug description:
  On raring, vertical scrolling is disabled by default (no
  /etc/X11/xorg.conf file). I have to execute synclient
  vertedgescroll=1 to activate it.

  For information, it used to be activated by default on all previous
  releases.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Sat May  4 19:50:49 2013
  DistUpgraded: 2011-04-01 10:00:41,930 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  InstallationDate: Installed on 2010-09-15 (962 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MachineType: Dell Inc. Inspiron M301Z
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=63c58b0a-b2cc-4c78-87d0-4e1c0e8fc6a6 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: Upgraded to raring on 2011-04-01 (764 days ago)
  dmi.bios.date: 07/16/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/16/2010:svnDellInc.:pnInspironM301Z:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Inspiron M301Z
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1176389/+subscriptions

-- 
Mailing list: 

[Desktop-packages] [Bug 1173611] Re: Software center's category menu is unreadable on GNOME 3

[Julien Olivier]

** Attachment added: Screenshot from 2013-04-27 15:01:06.png
   
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1173611/+attachment/3656196/+files/Screenshot%20from%202013-04-27%2015%3A01%3A06.png

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

Title:
  Software center's category menu is unreadable on GNOME 3

Status in “software-center” package in Ubuntu:
  New

Bug description:
  In Ubuntu GNOME, the category menu of the software center is
  unreadable.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: software-center 5.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Sat Apr 27 15:01:45 2013
  InstallationDate: Installed on 2010-09-15 (954 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to raring on 2011-04-01 (757 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1173611/+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 1067901] Re: can't configure any accounts in empathy

[Julien Olivier]

@Bilal: the problem is that you can't configure Empathy accounts when
using gnome-online-accounts instead of ubuntu-online-accounts. So, the
bug is *not* in ubuntu-online-accounts because it happens when ubuntu-
online-accounts is not even installed. The problem is simply that
empathy should be able to launch gnome-online-accounts configuration
when you use this one instead of ubuntu-online-accounts.

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

Title:
  can't configure any accounts in empathy

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Accounts can't be configured in empathy in 12.10.  I think this is
  because of the online accounts fork (I have the gnome-shell version of
  online accounts, but not the ubuntu version).  I think maybe I should
  have both?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: empathy 3.6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  Date: Wed Oct 17 15:03:54 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to quantal on 2012-10-11 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1067901/+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 1067901] Re: can't configure any accounts in empathy

[Julien Olivier]

The bug is still there, and cofirmed.

** Changed in: empathy (Ubuntu)
   Status: Expired = Confirmed

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

Title:
  can't configure any accounts in empathy

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Accounts can't be configured in empathy in 12.10.  I think this is
  because of the online accounts fork (I have the gnome-shell version of
  online accounts, but not the ubuntu version).  I think maybe I should
  have both?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: empathy 3.6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  Date: Wed Oct 17 15:03:54 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to quantal on 2012-10-11 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1067901/+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 1067901] Re: can't configure any accounts in empathy

[Julien Olivier]

As I said in
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1060060 (now
marked as a duplicate of this one):

The bug is about the fact that it doesn't work when gnome-control-
center-signon is not installed. I don't use stock Ubuntu, I use ubuntu
gnome so I don't want gnome-control-center-signon. gnome-control-center-
signon is the configuration tool for Ubuntu-Online-Accounts not for
Gnome-Online-Accounts (as you know those are 2 different things).

So, there is a way to configure Empathy accounts through Ubuntu-Online-
Accounts, but there is no way to confirgure them when using Gnome-
Online-Accounts.

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

Title:
  can't configure any accounts in empathy

Status in “empathy” package in Ubuntu:
  Incomplete

Bug description:
  Accounts can't be configured in empathy in 12.10.  I think this is
  because of the online accounts fork (I have the gnome-shell version of
  online accounts, but not the ubuntu version).  I think maybe I should
  have both?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: empathy 3.6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  Date: Wed Oct 17 15:03:54 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to quantal on 2012-10-11 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1067901/+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 1060506] Re: file-roller crashed with SIGSEGV in on_bus_acquired_for_archive_manager()

[Julien Olivier]

It just needs an update: https://bugs.launchpad.net/ubuntu/+source/file-
roller/+bug/1069443

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

Title:
  file-roller crashed with SIGSEGV in
  on_bus_acquired_for_archive_manager()

Status in File Roller:
  Invalid
Status in “file-roller” package in Ubuntu:
  Triaged

Bug description:
  Tried to open a zip file.  Got this.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: file-roller 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Tue Oct  2 17:46:43 2012
  ExecutablePath: /usr/bin/file-roller
  ProcCmdline: file-roller 
/home/username/Downloads/hackedbellini-Gnome-Shell-Notifications-Alert-233b3f5\ 
(1).tar.gz
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x809d3f2: mov0x8(%eax),%eax
   PC (0x0809d3f2) ok
   source 0x8(%eax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1060506/+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 875002] Re: choosing quit from unity launcher doesn't close rhythmbox if music is playing

[Julien Olivier]

Or you could make this non-standard behaviour a plugin that you install
(or not) by default, so that users can disable it if they don't want it.
I think this was already done this way in the past.

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

Title:
  choosing quit from unity launcher doesn't close rhythmbox if music is
  playing

Status in One Hundred Paper Cuts:
  New
Status in “rhythmbox” package in Ubuntu:
  Triaged

Bug description:
  To reproduce:  Start rhythmbox. Start playing a song. Left click
  rhythmbox icon in unity launcher. Choose Quit.

  Application doesn't quit, music keeps playing, only the window closes.
  To really quit the application, put the song on pause and then choose
  quit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: rhythmbox 2.90.1~20110908-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 15 15:43:51 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  ProcEnviron:
   LC_CTYPE=en_GB.UTF-8
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/875002/+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 875002] Re: choosing quit from unity launcher doesn't close rhythmbox if music is playing

[Julien Olivier]

The problem is simply due to the fact that Ubuntu has other standards
than GNOME. And that's why I think it would be better for them to change
those standards using removable plugins instead of directly patching the
application. This way, it is still possible to use Ubuntu as a base for
a standard GNOME-based distribution while still benefitting from the
greatness of Ubuntu.

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

Title:
  choosing quit from unity launcher doesn't close rhythmbox if music is
  playing

Status in One Hundred Paper Cuts:
  New
Status in “rhythmbox” package in Ubuntu:
  Triaged

Bug description:
  To reproduce:  Start rhythmbox. Start playing a song. Left click
  rhythmbox icon in unity launcher. Choose Quit.

  Application doesn't quit, music keeps playing, only the window closes.
  To really quit the application, put the song on pause and then choose
  quit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: rhythmbox 2.90.1~20110908-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 15 15:43:51 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  ProcEnviron:
   LC_CTYPE=en_GB.UTF-8
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

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