from:"Marcos Alano"

[Bug 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)

2024-03-10 Thread Marcos Alano

Yeah, I opened a bug report for that: https://bugs.launchpad.net/bugs/2056506
It's the Ubuntu Dock extension the culprit. I downgraded it and the problem was 
gone.
Now we need to bisect to see what change caused this.

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

Title:
  gnome-shell crashed in clutter_actor_get_real_resource_scale() with
  assertion failed: (guessed_scale >= 1.f)

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


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

[Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano

I did a rollback on the package gnome-shell-extension-ubuntu-dock to the
version 87ubuntu2 and did work. Closing the applications using the
right-button menu in the dock doesn't crash the session anymore.

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

Title:
  GNOME Shell crashes when I close any application

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


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

[Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano

I confess I used to use noble-proposed enabled globally, but I disabled
it and downgraded all the packages that I could find that came from that
archive.

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

Title:
  GNOME Shell crashes when I close any application

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


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

[Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano

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

Title:
  GNOME Shell crashes when I close any application

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


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

[Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano

I finally was able to upload a crash report for gnome-shell:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056568

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

Title:
  GNOME Shell crashes when I close any application

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


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

[Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano

I think this crash can be enlightening. It's related to mutter:
1859fc3a-dd48-11ee-ba9e-fa163e171f02

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

Title:
  GNOME Shell crashes when I close any application

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


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

[Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano

** Attachment added: "prevjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056506/+attachment/5754030/+files/prevjournal.txt

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

Title:
  GNOME Shell crashes when I close any application

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


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

[Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056506/+attachment/5754029/+files/journal.txt

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

Title:
  GNOME Shell crashes when I close any application

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


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

[Bug 2056506] [NEW] GNOME Shell crashes when I close any application

2024-03-07 Thread Marcos Alano

Public bug reported:

I'm using Noble for sometime and I'm having a very annoying and odd
problem: everytime I close an application on x11 (Wayland doesn't work
any better) clicking with the right button in the dock and choosing
"Quit" I got that screen saying that something went wrong and I need to
close the session and start over. Please, let me know what logs do you
need. I couldn't find any meaningful information by myself.

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

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

Title:
  GNOME Shell crashes when I close any application

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


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

[Bug 2047938] Re: GNOME Shell crash with Wayland session

2024-01-04 Thread Marcos Alano

@vanvugt This crash didn't generate a crash report. There is a less
destructive way to test it? I think deleting, or even moving, my
extensions wouldn't be productive since it's part of my daily use.

GNOME 45.2 wouldn't implement a better way to deal with crashes without
losing all the session? The problem is we are using 45.0, so maybe this
change isn't in place yet.

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

Title:
  GNOME Shell crash with Wayland session

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


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

[Bug 2047938] Re: GNOME Shell crash with Wayland session

2024-01-03 Thread Marcos Alano

I think the last file I added has more useful information because I
executed 'ubuntu-bug gnome-shell' from my X11 session I opened after the
crash.

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

Title:
  GNOME Shell crash with Wayland session

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


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

[Bug 2047938] [NEW] GNOME Shell crash with Wayland session

2024-01-03 Thread Marcos Alano

Public bug reported:

I was using GNOME with Wayland and the session crashed, bringing down
all the open applications.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.2-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan  3 10:55:50 2024
DisplayManager: gdm3
InstallationDate: Installed on 2021-11-26 (768 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-08-18 (139 days ago)

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


** Tags: amd64 apport-bug mantic package-from-proposed third-party-packages 
wayland-session

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

Title:
  GNOME Shell crash with Wayland session

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


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

[Bug 2047938] Re: GNOME Shell crash with Wayland session

2024-01-03 Thread Marcos Alano

** Attachment added: "crash-gnome-shell-wayland.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047938/+attachment/5735898/+files/crash-gnome-shell-wayland.log

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

Title:
  GNOME Shell crash with Wayland session

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


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

[Bug 2045977] Re: GNOME Shell crash with Wayland

2023-12-08 Thread Marcos Alano

Result of the command: journalctl -u org.gnome.Shell@wayland.service
--user --since=2023-12-08

** Attachment added: "gnome-shell-with-wayland.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045977/+attachment/5727514/+files/gnome-shell-with-wayland.log

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

Title:
  GNOME Shell crash with Wayland

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


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

[Bug 2045977] [NEW] GNOME Shell crash with Wayland

2023-12-08 Thread Marcos Alano

Public bug reported:

My GNOME session got idle and crashed. In the journalctl logs there is
more details

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  8 10:43:43 2023
DisplayManager: gdm3
InstallationDate: Installed on 2021-11-26 (742 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RelatedPackageVersions: mutter-common 45.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-08-18 (113 days ago)

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


** Tags: amd64 apport-bug mantic third-party-packages wayland-session

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

Title:
  GNOME Shell crash with Wayland

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


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

[Bug 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()

2023-11-13 Thread Marcos Alano

I tested just with the gnome-shell package 45.1 available on mantic-
proposed and still crashes. I will wait the release of mutter 45.1 to
test again.

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

Title:
  gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
  st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
  from GjsAutoPointer()

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


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

[Bug 2039314] Re: Device security reports "checks failed" even achiving HSI:3

2023-10-16 Thread Marcos Alano

Ubuntu 23.10.

➜ dpkg -l |grep gnome-control-center
ii  gnome-control-center   1:45.0-1ubuntu3  
  amd64utilities to configure the GNOME desktop
ii  gnome-control-center-data  1:45.0-1ubuntu3  
  all  configuration applets for GNOME - data files
ii  gnome-control-center-faces 1:45.0-1ubuntu3  
  all  utilities to configure the GNOME desktop - faces 
images

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

Title:
  Device security reports "checks failed" even achiving HSI:3

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


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

[Bug 2039314] Re: Device security reports "checks failed" even achiving HSI:3

2023-10-13 Thread Marcos Alano

** Package changed: ubuntu => gnome-control-center (Ubuntu)

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

Title:
  Device security reports "checks failed" even achiving HSI:3

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


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

[Bug 2035027] Re: GNOME crashes after resume when using Wayland

2023-09-10 Thread Marcos Alano

I can reproduce the problem when I enter the S2 energy state using the
command: 'echo freeze | sudo tee /sys/power/state'

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

Title:
  GNOME crashes after resume when using Wayland

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


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

[Bug 2035027] Re: GNOME crashes after resume when using Wayland

2023-09-10 Thread Marcos Alano

Here it's a crash ID: a0a547e0-4eb2-11ee-b3a4-fa163e55efd0
It's important to notice that this report is for one of my VMs, but the same 
behavior happens to my bare metal machine, but I couldn't produce a crash 
report on that, I don't know why.


** Description changed:

- Sometimes, now always, when I'm back to my computer after entered in
+ Sometimes, not always, when I'm back to my computer after entered in
  stand-by mode (display turns off), the sessions crashes and comes back
  to GDM. It just happens with Wayland.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 10 10:59:07 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-30 (11 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Sometimes, not always, when I'm back to my computer after entered in
- stand-by mode (display turns off), the sessions crashes and comes back
- to GDM. It just happens with Wayland.
+ stand-by mode (display turned off, sometimes screen locked), the session
+ crashes and comes back to GDM. It just happens with Wayland, never with
+ Xorg.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 10 10:59:07 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-30 (11 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  GNOME crashes after resume when using Wayland

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


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

[Bug 2035027] [NEW] GNOME crashes after resume when using Wayland

2023-09-10 Thread Marcos Alano

Public bug reported:

Sometimes, not always, when I'm back to my computer after entered in
stand-by mode (display turned off, sometimes screen locked), the session
crashes and comes back to GDM. It just happens with Wayland, never with
Xorg.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~rc-0ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 10 10:59:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-08-30 (11 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  GNOME crashes after resume when using Wayland

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


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

[Bug 2034602] Re: libadwaita applications don't respect dark theme

2023-09-07 Thread Marcos Alano

I just got the update and now everything is working again as expected.
Thank you everybody!

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

Title:
  libadwaita applications don't respect dark theme

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


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

[Bug 2029148] Re: cups snap - can't add printer

2023-08-24 Thread Marcos Alano

@jeremy, do you mean Ubuntu 23.10 instead of 23.04?

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

Title:
  cups snap - can't add printer

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


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

[Bug 1993573] Re: Low resolution Ubuntu's logo and name in about tab

2022-10-19 Thread Marcos Alano

If the image is small, works fine, but image can't scale lossless. I
think it has a PNG, but it should be an SVG.

** Attachment added: "Screenshot from 2022-10-19 15-14-16.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993573/+attachment/5625335/+files/Screenshot%20from%202022-10-19%2015-14-16.png

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

Title:
  Low resolution Ubuntu's logo and name in about tab

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


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

[Bug 1993573] ProcEnviron.txt

2022-10-19 Thread Marcos Alano

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1993573/+attachment/5625334/+files/ProcEnviron.txt

** Description changed:

- I have a 4K display running on 1440p and I noticed the Ubuntu logo and text 
are not sharp in the about page
- --- 
+ I have a 4K display running on 1440p and I noticed the Ubuntu's logo and name 
are not sharp in the about page (see attached picture)
+ ---
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-11-26 (326 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:43.0-1ubuntu2
  PackageArchitecture: amd64
  Tags: third-party-packages kinetic
  Uname: Linux 6.1.0-060100rc1-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (126 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
-  # set this to 0 to disable apport, or to 1 to enable it
-  # you can temporarily override this with
-  # sudo service apport start force_start=1
-  enabled=0
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

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

Title:
  Low resolution Ubuntu's logo and name in about tab

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


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

[Bug 1993573] ProcCpuinfoMinimal.txt

2022-10-19 Thread Marcos Alano

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1993573/+attachment/5625333/+files/ProcCpuinfoMinimal.txt

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

Title:
  Low resolution Ubuntu's logo and name in about tab

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


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

[Bug 1993573] [NEW] Low resolution Ubuntu's logo and name in about tab

2022-10-19 Thread Marcos Alano

Public bug reported:

I have a 4K display running on 1440p and I noticed the Ubuntu's logo and name 
are not sharp in the about page (see attached picture)
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2021-11-26 (326 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
NonfreeKernelModules: nvidia_modeset nvidia
Package: gnome-control-center 1:43.0-1ubuntu2
PackageArchitecture: amd64
Tags: third-party-packages kinetic
Uname: Linux 6.1.0-060100rc1-generic x86_64
UpgradeStatus: Upgraded to kinetic on 2022-06-14 (126 days ago)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
_MarkForUpload: True
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

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


** Tags: apport-collected kinetic third-party-packages

** Attachment added: "Screenshot from 2022-10-19 15-03-07.png"
   
https://bugs.launchpad.net/bugs/1993573/+attachment/5625331/+files/Screenshot%20from%202022-10-19%2015-03-07.png

** Summary changed:

- Low resolution log in about tab
+ Low resolution Ubuntu's logo and name in about tab

** Tags added: apport-collected kinetic third-party-packages

** Description changed:

- I have a 4K display running on 1440p and I noticed the Ubuntu logo and
- text are not sharp in the about page
+ I have a 4K display running on 1440p and I noticed the Ubuntu logo and text 
are not sharp in the about page
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu3
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2021-11-26 (326 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-control-center 1:43.0-1ubuntu2
+ PackageArchitecture: amd64
+ Tags: third-party-packages kinetic
+ Uname: Linux 6.1.0-060100rc1-generic x86_64
+ UpgradeStatus: Upgraded to kinetic on 2022-06-14 (126 days ago)
+ UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
+ _MarkForUpload: True
+ modified.conffile..etc.default.apport:
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
+ mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

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

Title:
  Low resolution Ubuntu's logo and name in about tab

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


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

[Bug 1993573] Dependencies.txt

2022-10-19 Thread Marcos Alano

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1993573/+attachment/5625332/+files/Dependencies.txt

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

Title:
  Low resolution Ubuntu's logo and name in about tab

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


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

[Bug 1992519] [NEW] Firefox crashing because libwebp's LTO

2022-10-11 Thread Marcos Alano

Public bug reported:

Full disclosure: I use Firefox from Mozilla repo, not from Snap because
of lack of support to 1Password.

I tried access one site, Dell's website (but the same with AMD's website), and 
Firefox just crashed and asked to report a bug. If I execute on console I just 
get one line multiple times: 'Exiting due to channel error.'.
I found a bug report for Firefox that has a comment about a folk that get a tip 
to compile libwebp without LTO.

I did the same, and worked! I used `apt source libwebp7` to get the
source and `apt build-dep libwebp` to install the dependencies. Than I
executed `export DEB_BUILD_MAINT_OPTIONS=optimize=-lto` to disable LTO
and compiled from source with `dpkg-buildpackage -rfakeroot -uc -b`. No
changes in the code. Installed all relevant packages and browser started
behaving correctly.

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

** Package changed: firefox (Ubuntu) => libwebp (Ubuntu)

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

Title:
  Firefox crashing because libwebp's LTO

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


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

[Bug 1988909] Re: Selected theme Yaru-dark losing selection in dconf

2022-09-06 Thread Marcos Alano

** Attachment removed: "Peek 2022-09-07 00-40.gif"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+attachment/5614188/+files/Peek%202022-09-07%2000-40.gif

** Attachment added: "A screencast showing the problem"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+attachment/5614189/+files/simplescreenrecorder-2022-09-07_00.52.42.webm

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

Title:
  Selected theme Yaru-dark losing selection in dconf

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


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

[Bug 1988909] Re: Selected theme Yaru-dark losing selection in dconf

2022-09-06 Thread Marcos Alano

** Attachment added: "Peek 2022-09-07 00-40.gif"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+attachment/5614188/+files/Peek%202022-09-07%2000-40.gif

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

Title:
  Selected theme Yaru-dark losing selection in dconf

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


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

[Bug 1988909] Re: Selected theme Yaru-dark losing selection in dconf

2022-09-06 Thread Marcos Alano

It is fixed (until the next access to the tab) if I select the orange
(the default) color

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

Title:
  Selected theme Yaru-dark losing selection in dconf

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


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

[Bug 1988909] [NEW] Selected theme Yaru-dark losing selection in dconf

2022-09-06 Thread Marcos Alano

Public bug reported:

Every time I go to Appearance the value for
/org/gnome/desktop/interface/gtk-theme is reset back to "Yaru", even I
selected the dark theme (Yaru-dark). The problem is that some apps (in
my case Tilix) uses this GTK theme value and even all my applications
are in dark mode the Tilix is in light mode.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43~rc-1ubuntu1
Uname: Linux 6.0.0-rc4 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  7 00:04:57 2022
InstallationDate: Installed on 2021-11-26 (284 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

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


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

** Attachment added: "Dark theme selected with Tilix in light theme"
   
https://bugs.launchpad.net/bugs/1988909/+attachment/5614180/+files/Screenshot%20from%202022-09-07%2000-13-24.png

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

Title:
  Selected theme Yaru-dark losing selection in dconf

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


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

[Bug 1988889] ProcEnviron.txt

2022-09-06 Thread Marcos Alano

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/199/+attachment/5614169/+files/ProcEnviron.txt

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

Title:
  Screen blank timeout not adjustable

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


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

[Bug 1988889] ProcCpuinfoMinimal.txt

2022-09-06 Thread Marcos Alano

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/199/+attachment/5614168/+files/ProcCpuinfoMinimal.txt

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

Title:
  Screen blank timeout not adjustable

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


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

[Bug 1988889] Dependencies.txt

2022-09-06 Thread Marcos Alano

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/199/+attachment/5614167/+files/Dependencies.txt

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

Title:
  Screen blank timeout not adjustable

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


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

[Bug 1988889] Re: Screen blank timeout not adjustable

2022-09-06 Thread Marcos Alano

Thanks. It fixed almost anything. Now just Power Mode > Balanced isn't
working (Power Save and Performance are being selected as showed by
"dconf watch /" result)

** Tags added: apport-collected kinetic third-party-packages

** Description changed:

- I tried to adjust screen blank timeout in Power tab, but after I go to
- another tab and come back, the value is the same, 5 min. The same
- behavior of changing the value back occurs for "Power Mode" and "Power
- Button Behavior".
+ I tried to adjust screen blank timeout in Power tab, but after I go to 
another tab and come back, the value is the same, 5 min. The same behavior of 
changing the value back occurs for "Power Mode" and "Power Button Behavior".
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.0-0ubuntu1
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2021-11-26 (284 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-control-center 1:43~rc-1ubuntu1
+ PackageArchitecture: amd64
+ RebootRequiredPkgs: Error: path contained symlinks.
+ Tags: third-party-packages kinetic
+ Uname: Linux 6.0.0-rc4 x86_64
+ UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
+ UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
+ _MarkForUpload: True
+ modified.conffile..etc.default.apport:
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
+ mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

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

Title:
  Screen blank timeout not adjustable

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


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

[Bug 1988889] Re: Screen blank timeout not adjustable

2022-09-06 Thread Marcos Alano

I kept running the command "dconf watch /" and these options don't
change any configurations. The other options, that options working fine,
change the values correctly.

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

Title:
  Screen blank timeout not adjustable

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


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

[Bug 1988889] [NEW] Screen blank timeout not adjustable

2022-09-06 Thread Marcos Alano

Public bug reported:

I tried to adjust screen blank timeout in Power tab, but after I go to
another tab and come back, the value is the same, 5 min. The same
behavior of changing the value back occurs for "Power Mode" and "Power
Button Behavior".

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

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

Title:
  Screen blank timeout not adjustable

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


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

[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-31 Thread Marcos Alano

The fix has landed with version 1.8.4.

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

Title:
  43: New Device Security feature is confusing and unhelpful currently

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


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

[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-29 Thread Marcos Alano

I achieved level 3 with a fix that will be released for fwupd to
correctly detect the presence of Intel CET feature. That is my original
bug report: https://github.com/fwupd/fwupd/issues/4960

** Bug watch added: github.com/fwupd/fwupd/issues #4960
   https://github.com/fwupd/fwupd/issues/4960

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

Title:
  43: New Device Security feature is confusing and unhelpful currently

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


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

[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-28 Thread Marcos Alano

There are some features maybe I couldn't get, like encrypted RAM,
because they're related to corporate level features.

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

Title:
  43: New Device Security feature is confusing and unhelpful currently

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


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

[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-28 Thread Marcos Alano

I achieved level 2 just setting "intel_iommu=on" on GRUB.

** Attachment added: "Screenshot from 2022-08-28 11-48-52.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+attachment/5612149/+files/Screenshot%20from%202022-08-28%2011-48-52.png

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

Title:
  43: New Device Security feature is confusing and unhelpful currently

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


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

[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-06-25 Thread Marcos Alano

@robswc

I understand what you mean. I get the solution from this page:
https://forums.developer.nvidia.com/t/trouble-suspending-with-510-39-01-linux-5-16-0-freezing-of-tasks-failed-after-20-009-seconds/200933/12?u=user126177
I don't even need anyone of these configurations, just the method indicated in 
the post.

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

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


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

[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems

2022-06-11 Thread Marcos Alano

@registrirayme the state is new for the OEM Priority Project. It seems
the fix was released for gdm3 package on Jammy release, so it should be
all good.

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

Title:
  Missing Wayland login option on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


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

[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems

2022-04-27 Thread Marcos Alano

May be a phased rollout? Can you download and install directly from the
repository?

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

Title:
  Missing Wayland login option on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


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

[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems

2022-04-27 Thread Marcos Alano

@sagu,

The version 42.0-1ubuntu7 is in jammy-updates repository.

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

Title:
  Missing Wayland login option on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


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

[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-04-25 Thread Marcos Alano

I executed 'journalctl -b -f' to get the logs (they are in the file) and
executed systemctl suspend.

** Attachment added: "gistfile1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876632/+attachment/5583559/+files/gistfile1.txt

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

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


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

[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-04-25 Thread Marcos Alano

@os369510,

Here is the content of the file as requested.

```
ResmanDebugLevel: 4294967295
RmLogonRC: 1
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 0
DeviceFileMode: 438
InitializeSystemMemoryAllocations: 1
UsePageAttributeTable: 4294967295
EnableMSI: 1
RegisterForACPIEvents: 1
EnablePCIeGen3: 0
MemoryPoolSize: 0
KMallocHeapMaxSize: 0
VMallocHeapMaxSize: 0
IgnoreMMIOCheck: 0
TCEBypassMode: 0
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
NvLinkDisable: 0
RmProfilingAdminOnly: 1
PreserveVideoMemoryAllocations: 1
EnableS0ixPowerManagement: 0
S0ixPowerManagementVideoMemoryThreshold: 256
DynamicPowerManagement: 3
DynamicPowerManagementVideoMemoryThreshold: 200
RegisterPCIDriver: 1
EnablePCIERelaxedOrderingMode: 0
EnableGpuFirmware: 18
EnableDbgBreakpoint: 0
RegistryDwords: ""
RegistryDwordsPerDevice: ""
RmMsg: ""
GpuBlacklist: ""
TemporaryFilePath: "/run"
ExcludedGpus: ""
```

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

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


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

[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-04-24 Thread Marcos Alano

I tried to set both options mentioned on comment #11 and with X11 after resume 
I got corrupted lock screen and corrupted shell. I had to restart shell with 
alt+f2 and type r. Furthermore, I think this is the kind of problem the bug 
talks about.
I have a laptop with an option on BIOS to always use the NVIDIA card instead of 
hybrid approach, so in some cases laptops will be affected too because they act 
as desktops in this aspect.

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

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


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

[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems

2022-04-23 Thread Marcos Alano

I have a Dell laptop that have an option in BIOS to always use the NVIDIA GPU 
instead of Intel/NVIDIA, and that the option I keep selected.
In the login screen, the gear shows "Ubuntu" and "Ubuntu on Wayland" options, 
so I think it's ok for non-hybrid machines until we fix all the problems.

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

Title:
  Missing Wayland login option on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


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

[Bug 1968929] Re: No Wayland support on NVIDIA systems

2022-04-19 Thread Marcos Alano

Here you can see the GNOME extension Vitals showing corrupted values
after a suspend

** Attachment added: "Corrupted screen"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+attachment/5581433/+files/Screenshot%20from%202022-04-19%2008-21-28.png

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

Title:
  No Wayland support on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


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

[Bug 1968929] Re: No Wayland support on NVIDIA systems

2022-04-19 Thread Marcos Alano

I read the comment #19 and I was able to suspend correctly using s0ix
method. The problem is: The method requires using "echo mem |sudo tee
/sys/power/state" to enter on suspend mode, but I think the default
method, when using menu option and "systemctl suspend", is "freeze", not
"mem". Using "echo freeze |sudo tee /sys/power/state" my laptop woke up
again after a few seconds.

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

Title:
  No Wayland support on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


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

[Bug 1968929] Re: No Wayland support on NVIDIA systems

2022-04-19 Thread Marcos Alano

I read the comment #19 and I was able to suspend correctly using s0ix
method. The problem is: The method requires using "echo mem |sudo tee
/sys/power/state" to enter on suspend mode, but I think the default
method, when using menu option and "systemctl suspend", is "freeze", not
"mem". Using "echo freeze |sudo tee /sys/power/state" my laptop woke up
again after a few seconds.

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

Title:
  No Wayland support on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


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

[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy

2022-04-15 Thread Marcos Alano

Kevin,

You can use the bug report I opened since this one is closed: 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929
Also, I would like you to comment that about if 42.0-1ubuntu3 version has the 
problem

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

Title:
  Verify that the gdm cherry-picks are wanted for jammy

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


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

[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy

2022-04-15 Thread Marcos Alano

I put all the information in my original bug report and I will unmark as
duplicate. https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929

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

Title:
  Verify that the gdm cherry-picks are wanted for jammy

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


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

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

2022-04-15 Thread Marcos Alano

This patch implement these checks: https://salsa.debian.org/gnome-
team/gdm/-/blob/ubuntu/master/debian/patches/data-Disable-wayland-on-
nvidia-if-suspend-is-broken.patch

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

Title:
  No Wayland support on my NVIDA laptop

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


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

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

2022-04-15 Thread Marcos Alano

The command executed right in the shell showing preserve option as 1

** Attachment added: "Screenshot from 2022-04-15 10-08-31.png"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+attachment/5580958/+files/Screenshot%20from%202022-04-15%2010-08-31.png

** This bug is no longer a duplicate of bug 1968809
   Verify that the gdm cherry-picks are wanted for jammy

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

Title:
  No Wayland support on my NVIDA laptop

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


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

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

2022-04-15 Thread Marcos Alano

Even with all the steps for suspend/resume checked, I still don´t get
Wayland support.

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

Title:
  No Wayland support on my NVIDA laptop

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


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

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

2022-04-15 Thread Marcos Alano

The preserve option enabled

** Attachment added: "Screenshot from 2022-04-15 10-14-35.png"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+attachment/5580957/+files/Screenshot%20from%202022-04-15%2010-14-35.png

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

Title:
  No Wayland support on my NVIDA laptop

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


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

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

2022-04-15 Thread Marcos Alano

I got the gdm3 package version 42.0-1ubuntu4 and still don't get Wayland. I 
troubleshot and found the problem in the file /lib/udev/rules.d/61-gdm.rules in 
the following lines:
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
If I comment that Wayland appears as an option in GDM.
I had to create a file /etc/modprobe.d/nvidia-hack.conf with the follow content:
options nvidia NVreg_PreserveVideoMemoryAllocations=1
This theoretically enable the option to preserve video memory allocations, but 
still getting the option as "1", still don't enable Wayland.

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

Title:
  No Wayland support on my NVIDA laptop

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


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

[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy

2022-04-15 Thread Marcos Alano

The result of command showing the preserve option enabled in my system

** Attachment added: "Screenshot from 2022-04-15 10-14-35.png"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+attachment/5580954/+files/Screenshot%20from%202022-04-15%2010-14-35.png

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

Title:
  Verify that the gdm cherry-picks are wanted for jammy

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


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

[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy

2022-04-15 Thread Marcos Alano

The command executed right in the shell showing the necessary option as
"1"

** Attachment added: "Screenshot from 2022-04-15 10-08-31.png"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+attachment/5580955/+files/Screenshot%20from%202022-04-15%2010-08-31.png

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

Title:
  Verify that the gdm cherry-picks are wanted for jammy

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


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

[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy

2022-04-15 Thread Marcos Alano

I got the gdm3 package version 42.0-1ubuntu4 and still don't get Wayland. I 
troubleshot and found the problem in the file /lib/udev/rules.d/61-gdm.rules in 
the following lines:
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
If I comment that Wayland appears as an option in GDM.
I had to create a file /etc/modprobe.d/nvidia-hack.conf with the follow content:
options nvidia NVreg_PreserveVideoMemoryAllocations=1
This theoretically enable the option to preserve video memory allocations, but 
still getting the option as "1", still don't enable Wayland.

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

Title:
  Verify that the gdm cherry-picks are wanted for jammy

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


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

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

2022-04-14 Thread Marcos Alano

This screen show the firmware option related to hybrid graphics

** Attachment added: "Screenshot from 2022-04-14 09-01-14.png"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+attachment/5580729/+files/Screenshot%20from%202022-04-14%2009-01-14.png

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

Title:
  No Wayland support on my NVIDA laptop

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


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

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

2022-04-14 Thread Marcos Alano

As you can see in the screen attached, the reported GPU is NVIDIA
because I set the always-on option in BIOS.

** Attachment added: "Screenshot from 2022-04-14 08-58-44.png"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+attachment/5580728/+files/Screenshot%20from%202022-04-14%2008-58-44.png

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

Title:
  No Wayland support on my NVIDA laptop

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


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

[Bug 1968929] [NEW] No Wayland support on my NVIDA laptop

2022-04-13 Thread Marcos Alano

Public bug reported:

I'm using Ubuntu 22.04 on a Dell G15 5511 laptop that have an NVIDIA 3060 GPU. 
I saw in the last update in the gdm3 package that Wayland will be disabled in 
machines with hybrid graphics.
The question is: In this laptop I can enable optimus to use Intel and sometimes 
NVIDIA or keep only on NVIDIA (I use this option). So even it's detected two 
GPUs the Intel one is unused.
I think the problem could extend for people with a desktop with an integrated 
intel GPU and a discrete NVIDIA GPU, since both will be present in the system.
So maybe will be necessary to check with more accuracy to check if there are 
two GPUs, but only one is being used or have a documented option to force the 
enablement of Wayland.

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

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

Title:
  No Wayland support on my NVIDA laptop

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


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

[Bug 1318327] Re: Can't open .webp files

2022-01-07 Thread Marcos Alano

There is available code to fix that. Someone could package so we can get it 
working in Jammy? I think it's quite important since it's a 5-years long 
release.
Here is the code:
https://github.com/aruiz/webp-pixbuf-loader

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

Title:
  Can't open .webp files

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


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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-22 Thread Marcos Alano

I updated  GNOME Shell and Mutter for the latest version, 3.38.2 and the
problem has gone.

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-03 Thread Marcos Alano

Couldn't find crashes for GNOME. For sure is a regression. May be we
should find a way to bisect the patches between the two mentioned
versions or sync the version with Debian which has lots of patches, for
this bug included, I believe.

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-02 Thread Marcos Alano

Removed the package for this extensions and also the extensions in that
directory. After that I logout and login again and started the game
Portal two times, one using GameMode and the other not using it. Both
times the game couldn't go full screen correctly.

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-01 Thread Marcos Alano

** Attachment added: "xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+attachment/5440015/+files/xrandr.txt

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-01 Thread Marcos Alano

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+attachment/5440014/+files/prevboot.txt

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-01 Thread Marcos Alano

** Attachment added: "packages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+attachment/5440013/+files/packages.txt

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-01 Thread Marcos Alano

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+attachment/5440012/+files/lspci.txt

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-11-30 Thread Marcos Alano

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

Why is this a duplicate if the behavior of the bug is different? In this
bug the games can't go full screen, but in the other bug the application
crashes.

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-11-28 Thread Marcos Alano

I think this bug could be related to Debian's bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975453
They already got a fix.

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

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-11-26 Thread Marcos Alano

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-11-26 Thread Marcos Alano

** Summary changed:

- Games don't go full screen correctly with new version of libmutter
+ Games don't go full screen correctly with newer version of libmutter

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

Title:
  Games don't go full screen correctly with newer version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter

2020-11-26 Thread Marcos Alano

I kept the mentioned packages on hold so I can play games, but if you
need I update them or test another package please let me know. I would
like to bisect the patches of the newer version but I have no clue about
how.

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

Title:
  Games don't go full screen correctly with new version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter

2020-11-26 Thread Marcos Alano

I tried to execute the apport-collect command but always happens this:
mhalano@glados:~$ apport-collect 1905637
Package mutter not installed and no hook available, ignoring
mhalano@glados:~$ 
So I executed: apport-collect -p libmutter-7-0 1905637

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

Title:
  Games don't go full screen correctly with new version of libmutter

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

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

[Bug 1905637] ProcEnviron.txt

2020-11-26 Thread Marcos Alano

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1905637/+attachment/5438224/+files/ProcEnviron.txt

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

Title:
  Games don't go full screen correctly with new version of libmutter

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

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

[Bug 1905637] ProcCpuinfoMinimal.txt

2020-11-26 Thread Marcos Alano

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1905637/+attachment/5438223/+files/ProcCpuinfoMinimal.txt

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

Title:
  Games don't go full screen correctly with new version of libmutter

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

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

[Bug 1905637] Dependencies.txt

2020-11-26 Thread Marcos Alano

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1905637/+attachment/5438222/+files/Dependencies.txt

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

Title:
  Games don't go full screen correctly with new version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter

2020-11-26 Thread Marcos Alano

** Attachment added: "monitors.xml"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+attachment/5438221/+files/monitors.xml

** Tags added: apport-collected third-party-packages

** Description changed:

  Some games (I tried using Portal and Tomb Raider 2013, both native
  games) don't go full screen correctly (even configured for it). I
  tracked down the problem to a regression on package libmutter-7-0. The
  problem occurs with latest version, 3.38.1-2ubuntu1, but when I
  downgrade the package (and also the package gir1.2-mutter-7) to
  3.38.1-1ubuntu1 the gomes went full screen normally.
  
  I'm using Ubuntu 20.10.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-10-23 (33 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: libmutter-7-0 3.38.1-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
+ Tags: groovy third-party-packages
+ Uname: Linux 5.8.0-30-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Games don't go full screen correctly with new version of libmutter

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

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

[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter

2020-11-25 Thread Marcos Alano

** Description changed:

- Some games (I tried Portal and Tomb Raider 2013) don't go full screen
- correctly. I tracked down this to a regression on package libmutter-7-0.
- Tee problem occurs with latest version, 3.38.1-2ubuntu1, but when I
+ Some games (I tried using Portal and Tomb Raider 2013, both native
+ games) don't go full screen correctly (even configured for it). I
+ tracked down the problem to a regression on package libmutter-7-0. The
+ problem occurs with latest version, 3.38.1-2ubuntu1, but when I
  downgrade the package (and also the package gir1.2-mutter-7) to
- 3.38.1-1ubuntu1 all works correctly.
+ 3.38.1-1ubuntu1 the gomes went full screen normally.
  
  I'm using Ubuntu 20.10.

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

Title:
  Games don't go full screen correctly with new version of libmutter

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

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

[Bug 1905637] [NEW] Games don't go full screen correctly with new version of libmutter

2020-11-25 Thread Marcos Alano

Public bug reported:

Some games (I tried Portal and Tomb Raider 2013) don't go full screen
correctly. I tracked down this to a regression on package libmutter-7-0.
Tee problem occurs with latest version, 3.38.1-2ubuntu1, but when I
downgrade the package (and also the package gir1.2-mutter-7) to
3.38.1-1ubuntu1 all works correctly.

I'm using Ubuntu 20.10.

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

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

Title:
  Games don't go full screen correctly with new version of libmutter

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

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

Re: [Bug 1715822] Re: "Ubuntu on Xorg" string not available for translation

2017-10-11 Thread Marcos Alano

I think "Ubuntu (Xorg)" is nice, and pretty.

Marcos H. Alano
Linux System Administrator
marcoshal...@gmail.com

On Oct 11, 2017 12:01, "Sebastien Bacher"  wrote:

> It would maybe be easier to just use "Ubuntu (Xorg)" and then no
> translation would be needed (those items might be a bit weird/hard to
> translate anyway)
>
> --
> You received this bug notification because you are a member of Ubuntu
> Desktop, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1715822
>
> Title:
>   "Ubuntu on Xorg" string not available for translation
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-translations/+bug/1715822/+subscriptions
>
> --
> ubuntu-desktop mailing list
> ubuntu-desk...@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
>

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

Title:
  "Ubuntu on Xorg" string not available for translation

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

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

[Bug 1672424] Re: Cannot install Debian files outside of the repositories

2017-03-24 Thread Marcos Alano

I found a plot twist: the package doesn't install if in the same path as
user.

So:
# both user and package are in ~/Downloads. Don't work
marcos@marcos-laptop:~/Downloads$ gnome-software 
--local-filename=google-chrome-stable_current_amd64.deb

# user is in one directory and package are in a subdirectory. Works
marcos@marcos-laptop:~$ gnome-software 
--local-filename=Downloads/google-chrome-stable_current_amd64.deb

# same as before, but indicating the full path using til. Don't work
marcos@marcos-laptop:~$ gnome-software 
--local-filename=~/Downloads/google-chrome-stable_current_amd64.deb

# same as before, but indicating the full path normally. Works
marcos@marcos-laptop:~$ gnome-software 
--local-filename=/home/marcos/Downloads/google-chrome-stable_current_amd64.deb

# different paths, but indicating the relative path using two dots. Don't work
marcos@marcos-laptop:~/Downloads$ gnome-software 
--local-filename=../google-chrome-stable_current_amd64.deb

# same path, but indicating the relative path using one dot. Works
marcos@marcos-laptop:~$ gnome-software 
--local-filename=./google-chrome-stable_current_amd64.deb

May be you could understand I can't understand. :)

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

Title:
  Cannot install Debian files outside of the repositories

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

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

[Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2017-02-13 Thread Marcos Alano

How the status of this problem on a clean system with Ubuntu 16.04 or
16.10 or even 17.04?

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

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

[Bug 1332648] Re: Wrong bluetooth pairing PIN reported for Logitech K810

2016-10-01 Thread Marcos Alano

The solution is easy: Just grab the same code from hcidump. The
implementation is hard, because ssems need an exception for this model.
Any news about that? Someone posts this bug on Gnome Bugzilla?

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

Title:
  Wrong bluetooth pairing PIN reported for Logitech K810

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

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

[Bug 1608155] [NEW] Enable Python plugins support

2016-07-30 Thread Marcos Alano

Public bug reported:

There some plugins for the Totem which need Python support (I'm testing
with https://github.com/dveeden/totem-plugin-airplay). To solve this
just compile with '--enable-python' flag.

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

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

Title:
  Enable Python plugins support

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

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

[Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2016-02-27 Thread Marcos Alano

Mark,

I fixed this bug in may 2015:
https://bugzilla.gnome.org/show_bug.cgi?id=749443

Version 3.16 (used in Ubuntu 15.10 (Wily) didn't come with the patch and
no one backported.

Version 3.18 (used in Ubuntu 16.04 (Xenial) come with the patch.

Best regards and sorry for any trouble.

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

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

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

Re: [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2015-10-23 Thread Marcos Alano

Thanks David.

I will check this and create and submit a patch.

Cheers.

2015-10-23 15:49 GMT-02:00 David Cesarino de Sousa <1094...@bugs.launchpad.net>:
> Hi Marcos,
>
> I did a clean install of 15.10 yesterday, so I also used that
> opportunity to test this issue. In short, pairing using the user
> interface still did not work, but adding the OUI to the XML file was
> enough to persist the connection across reboots and suspends. No need to
> use the command line foo I did in #59.
>
> To be fully precise, this is what I did:
>
> 1. Clean install Ubuntu 15.10.
> 2. Pair using the bluetooth icon in the top right at the desktop.
> 3. Try suspend or reboot. It did not work (connection even refused to set up 
> without removing and adding the device again).
> 4. Added the OUI to the XML file as this, under the Microsoft Mice section:
>
> 
>
> 5. Reboot.
>
> After this, the connection is now persisting across reboots and
> suspends. It would be nice for other users if they didn't need to edit
> the XML and the user interface did all that was needed automatically,
> but I'm satisfied it works easily now.
>
> Cheers.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1094744
>
> Title:
>   MS Sculpt Touch Mouse needs to be re-paired periodically
>
> Status in GNOME Bluetooth:
>   Fix Released
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in gnome-bluetooth package in Ubuntu:
>   Fix Released
> Status in bluez source package in Precise:
>   Confirmed
> Status in gnome-bluetooth source package in Precise:
>   Fix Released
> Status in bluez source package in Quantal:
>   Won't Fix
> Status in gnome-bluetooth source package in Quantal:
>   Fix Released
> Status in bluez source package in Raring:
>   Won't Fix
> Status in gnome-bluetooth source package in Raring:
>   Won't Fix
> Status in bluez package in Fedora:
>   Unknown
>
> Bug description:
>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
> session, watch it automatically re-pair.
>   [Regression Potential] Little. The patched piece of XML is only relevant to 
> hardware having the same ID.
>
>   When you don't use the mouse for a long enough time, the mouse
>   disconnects and won't reconnect. I have to go into bluetooth settings,
>   remove it, and re-pair it.
>
>   1)
>   ~ % lsb_release -rd
>   Description:  Ubuntu 12.04.1 LTS
>   Release:  12.04
>
>   2)
>   ~ % apt-cache policy bluez
>   bluez:
> Installed: 4.98-2ubuntu7
> Candidate: 4.98-2ubuntu7
> Version table:
>*** 4.98-2ubuntu7 0
>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
>   100 /var/lib/dpkg/status
>
>   3)
>   I expected the mouse to reconnect automatically, or at least after I try to 
> reconnect manually through the bluetooth settings.
>
>   4)
>   I have to re-pair the mouse in order to use it again. Turning the mouse off 
> and on doesn't work either.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

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

Re: [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2015-10-23 Thread Marcos Alano

Hi David,

In the version 3.18 of gnome-bluetooth this OUI is already added. May
be someone could backport the patch?

2015-10-23 16:04 GMT-02:00 Marcos Alano <marcoshal...@gmail.com>:
> Thanks David.
>
> I will check this and create and submit a patch.
>
> Cheers.
>
> 2015-10-23 15:49 GMT-02:00 David Cesarino de Sousa 
> <1094...@bugs.launchpad.net>:
>> Hi Marcos,
>>
>> I did a clean install of 15.10 yesterday, so I also used that
>> opportunity to test this issue. In short, pairing using the user
>> interface still did not work, but adding the OUI to the XML file was
>> enough to persist the connection across reboots and suspends. No need to
>> use the command line foo I did in #59.
>>
>> To be fully precise, this is what I did:
>>
>> 1. Clean install Ubuntu 15.10.
>> 2. Pair using the bluetooth icon in the top right at the desktop.
>> 3. Try suspend or reboot. It did not work (connection even refused to set up 
>> without removing and adding the device again).
>> 4. Added the OUI to the XML file as this, under the Microsoft Mice section:
>>
>> 
>>
>> 5. Reboot.
>>
>> After this, the connection is now persisting across reboots and
>> suspends. It would be nice for other users if they didn't need to edit
>> the XML and the user interface did all that was needed automatically,
>> but I'm satisfied it works easily now.
>>
>> Cheers.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1094744
>>
>> Title:
>>   MS Sculpt Touch Mouse needs to be re-paired periodically
>>
>> Status in GNOME Bluetooth:
>>   Fix Released
>> Status in bluez package in Ubuntu:
>>   Confirmed
>> Status in gnome-bluetooth package in Ubuntu:
>>   Fix Released
>> Status in bluez source package in Precise:
>>   Confirmed
>> Status in gnome-bluetooth source package in Precise:
>>   Fix Released
>> Status in bluez source package in Quantal:
>>   Won't Fix
>> Status in gnome-bluetooth source package in Quantal:
>>   Fix Released
>> Status in bluez source package in Raring:
>>   Won't Fix
>> Status in gnome-bluetooth source package in Raring:
>>   Won't Fix
>> Status in bluez package in Fedora:
>>   Unknown
>>
>> Bug description:
>>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
>> session, watch it automatically re-pair.
>>   [Regression Potential] Little. The patched piece of XML is only relevant 
>> to hardware having the same ID.
>>
>>   When you don't use the mouse for a long enough time, the mouse
>>   disconnects and won't reconnect. I have to go into bluetooth settings,
>>   remove it, and re-pair it.
>>
>>   1)
>>   ~ % lsb_release -rd
>>   Description:  Ubuntu 12.04.1 LTS
>>   Release:  12.04
>>
>>   2)
>>   ~ % apt-cache policy bluez
>>   bluez:
>> Installed: 4.98-2ubuntu7
>> Candidate: 4.98-2ubuntu7
>> Version table:
>>*** 4.98-2ubuntu7 0
>>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 
>> Packages
>>   100 /var/lib/dpkg/status
>>
>>   3)
>>   I expected the mouse to reconnect automatically, or at least after I try 
>> to reconnect manually through the bluetooth settings.
>>
>>   4)
>>   I have to re-pair the mouse in order to use it again. Turning the mouse 
>> off and on doesn't work either.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions
>
>
>
> --
> Marcos Alano
> --
> P: Por que este email é tão curto?
> R: http://five.sentenc.es
> --


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

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

Re: [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2015-09-06 Thread Marcos Alano

Did you try add the OUI for your mouse in
/usr/share/gnome-bluetooth/pin-code-database.xml? I thinks there is
many differents OUIs for this model.

PS.: Post your OUI here so I can create and send a patch.

2015-09-05 18:19 GMT-03:00 Rael <rael...@gmail.com>:
> On 14.04 LTS, bought one of this, and I'm facing this issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1094744
>
> Title:
>   MS Sculpt Touch Mouse needs to be re-paired periodically
>
> Status in GNOME Bluetooth:
>   Fix Released
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in gnome-bluetooth package in Ubuntu:
>   Fix Released
> Status in bluez source package in Precise:
>   Confirmed
> Status in gnome-bluetooth source package in Precise:
>   Fix Released
> Status in bluez source package in Quantal:
>   Won't Fix
> Status in gnome-bluetooth source package in Quantal:
>   Fix Released
> Status in bluez source package in Raring:
>   Won't Fix
> Status in gnome-bluetooth source package in Raring:
>   Won't Fix
> Status in bluez package in Fedora:
>   Unknown
>
> Bug description:
>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
> session, watch it automatically re-pair.
>   [Regression Potential] Little. The patched piece of XML is only relevant to 
> hardware having the same ID.
>
>   When you don't use the mouse for a long enough time, the mouse
>   disconnects and won't reconnect. I have to go into bluetooth settings,
>   remove it, and re-pair it.
>
>   1)
>   ~ % lsb_release -rd
>   Description:  Ubuntu 12.04.1 LTS
>   Release:  12.04
>
>   2)
>   ~ % apt-cache policy bluez
>   bluez:
> Installed: 4.98-2ubuntu7
> Candidate: 4.98-2ubuntu7
> Version table:
>*** 4.98-2ubuntu7 0
>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
>   100 /var/lib/dpkg/status
>
>   3)
>   I expected the mouse to reconnect automatically, or at least after I try to 
> reconnect manually through the bluetooth settings.
>
>   4)
>   I have to re-pair the mouse in order to use it again. Turning the mouse off 
> and on doesn't work either.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

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

Re: [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2015-05-17 Thread Marcos Alano

Sorry for this problem. The address 30:59:B7: seems correct. Can you
check the batteries? That is a long shot, but may be can be the
problem.

2015-05-17 19:12 GMT-03:00 David Cesarino de Sousa 1094...@bugs.launchpad.net:
 Marcos, thanks for your help.

 That output was to show that the mouse unpairs after a suspend/reboot.
 If I follow the two steps I said before, I get the correct, expected
 status (paired), and I can move my mouse. See relevant output now that
 it is connected:

 [ /org/bluez/663/hci0 ]
 Discovering = 0
 UUIDs = 0x1000 0x1001 0x112d 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 
 0x110b
 Pairable = 1
 PairableTimeout = 0
 DiscoverableTimeout = 180
 Name = zurg-0
 Class = 0
 Address = C4:17:FE:EF:D8:A4
 Powered = 1
 Discoverable = 0
 Devices = dev_30_59_B7_73_B6_C6
 [ /org/bluez/663/hci0/dev_30_59_B7_73_B6_C6 ]
 Paired = 1
 Vendor = 0x045e
 Services = dbus.Array([], signature=dbus.Signature('o'), 
 variant_level=1)
 Trusted = 1
 Class = 0x002580
 Address = 30:59:B7:73:B6:C6
 Adapter = /org/bluez/663/hci0
 Version = 0x0129
 UUIDs = 0x1000 0x1124 0x1200
 Blocked = 0
 Icon = input-mouse
 Name = Microsoft Sculpt Comfort Mouse
 Connected = 1
 Alias = Microsoft Sculpt Comfort Mouse
 Product = 0x07a2

 The file currently reads this in the Microsoft mice section of the XML
 (I've tried with name as well):

 !-- Microsoft mice
  Again, same as above --
 device oui=30:59:B7: type=mouse pin=/
 device oui=7C:1E:52: type=mouse name=Microsoft Wedge Touch 
 Mouse pin=/
 device oui=00:1D:D8: type=mouse name=Microsoft Wireless 
 Notebook Presenter Mouse 8000 pin=/

 It still unpairs after a reboot or suspend. Changing to the adapter
 address (oui=C4:17:FE:) does not make any difference. As you can see,
 I can reconnect/repair, but I'd like it to be automatic.

 Sorry if I wasn't clear enough. Thank you.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1094744

 Title:
   MS Sculpt Touch Mouse needs to be re-paired periodically

 Status in GNOME Bluetooth:
   Fix Released
 Status in bluez package in Ubuntu:
   Confirmed
 Status in gnome-bluetooth package in Ubuntu:
   Fix Released
 Status in bluez source package in Precise:
   Confirmed
 Status in gnome-bluetooth source package in Precise:
   Fix Released
 Status in bluez source package in Quantal:
   Won't Fix
 Status in gnome-bluetooth source package in Quantal:
   Fix Released
 Status in bluez source package in Raring:
   Won't Fix
 Status in gnome-bluetooth source package in Raring:
   Won't Fix
 Status in bluez package in Fedora:
   Unknown

 Bug description:
   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
 session, watch it automatically re-pair.
   [Regression Potential] Little. The patched piece of XML is only relevant to 
 hardware having the same ID.

   When you don't use the mouse for a long enough time, the mouse
   disconnects and won't reconnect. I have to go into bluetooth settings,
   remove it, and re-pair it.

   1)
   ~ % lsb_release -rd
   Description:  Ubuntu 12.04.1 LTS
   Release:  12.04

   2)
   ~ % apt-cache policy bluez
   bluez:
 Installed: 4.98-2ubuntu7
 Candidate: 4.98-2ubuntu7
 Version table:
*** 4.98-2ubuntu7 0
   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
   100 /var/lib/dpkg/status

   3)
   I expected the mouse to reconnect automatically, or at least after I try to 
 reconnect manually through the bluetooth settings.

   4)
   I have to re-pair the mouse in order to use it again. Turning the mouse off 
 and on doesn't work either.

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

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

Re: [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2015-05-17 Thread Marcos Alano

Ok. Please do more tests in a clean installation and let us know about
the results.

Cheers.

2015-05-17 19:47 GMT-03:00 Marcos Alano marcoshal...@gmail.com:
 Sorry for this problem. The address 30:59:B7: seems correct. Can you
 check the batteries? That is a long shot, but may be can be the
 problem.

 2015-05-17 19:12 GMT-03:00 David Cesarino de Sousa 
 1094...@bugs.launchpad.net:
 Marcos, thanks for your help.

 That output was to show that the mouse unpairs after a suspend/reboot.
 If I follow the two steps I said before, I get the correct, expected
 status (paired), and I can move my mouse. See relevant output now that
 it is connected:

 [ /org/bluez/663/hci0 ]
 Discovering = 0
 UUIDs = 0x1000 0x1001 0x112d 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 
 0x110b
 Pairable = 1
 PairableTimeout = 0
 DiscoverableTimeout = 180
 Name = zurg-0
 Class = 0
 Address = C4:17:FE:EF:D8:A4
 Powered = 1
 Discoverable = 0
 Devices = dev_30_59_B7_73_B6_C6
 [ /org/bluez/663/hci0/dev_30_59_B7_73_B6_C6 ]
 Paired = 1
 Vendor = 0x045e
 Services = dbus.Array([], signature=dbus.Signature('o'), 
 variant_level=1)
 Trusted = 1
 Class = 0x002580
 Address = 30:59:B7:73:B6:C6
 Adapter = /org/bluez/663/hci0
 Version = 0x0129
 UUIDs = 0x1000 0x1124 0x1200
 Blocked = 0
 Icon = input-mouse
 Name = Microsoft Sculpt Comfort Mouse
 Connected = 1
 Alias = Microsoft Sculpt Comfort Mouse
 Product = 0x07a2

 The file currently reads this in the Microsoft mice section of the XML
 (I've tried with name as well):

 !-- Microsoft mice
  Again, same as above --
 device oui=30:59:B7: type=mouse pin=/
 device oui=7C:1E:52: type=mouse name=Microsoft Wedge Touch 
 Mouse pin=/
 device oui=00:1D:D8: type=mouse name=Microsoft Wireless 
 Notebook Presenter Mouse 8000 pin=/

 It still unpairs after a reboot or suspend. Changing to the adapter
 address (oui=C4:17:FE:) does not make any difference. As you can see,
 I can reconnect/repair, but I'd like it to be automatic.

 Sorry if I wasn't clear enough. Thank you.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1094744

 Title:
   MS Sculpt Touch Mouse needs to be re-paired periodically

 Status in GNOME Bluetooth:
   Fix Released
 Status in bluez package in Ubuntu:
   Confirmed
 Status in gnome-bluetooth package in Ubuntu:
   Fix Released
 Status in bluez source package in Precise:
   Confirmed
 Status in gnome-bluetooth source package in Precise:
   Fix Released
 Status in bluez source package in Quantal:
   Won't Fix
 Status in gnome-bluetooth source package in Quantal:
   Fix Released
 Status in bluez source package in Raring:
   Won't Fix
 Status in gnome-bluetooth source package in Raring:
   Won't Fix
 Status in bluez package in Fedora:
   Unknown

 Bug description:
   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
 session, watch it automatically re-pair.
   [Regression Potential] Little. The patched piece of XML is only relevant 
 to hardware having the same ID.

   When you don't use the mouse for a long enough time, the mouse
   disconnects and won't reconnect. I have to go into bluetooth settings,
   remove it, and re-pair it.

   1)
   ~ % lsb_release -rd
   Description:  Ubuntu 12.04.1 LTS
   Release:  12.04

   2)
   ~ % apt-cache policy bluez
   bluez:
 Installed: 4.98-2ubuntu7
 Candidate: 4.98-2ubuntu7
 Version table:
*** 4.98-2ubuntu7 0
   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 
 Packages
   100 /var/lib/dpkg/status

   3)
   I expected the mouse to reconnect automatically, or at least after I try 
 to reconnect manually through the bluetooth settings.

   4)
   I have to re-pair the mouse in order to use it again. Turning the mouse 
 off and on doesn't work either.

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions



 --
 Marcos Alano
 --
 P: Por que este email é tão curto?
 R: http://five.sentenc.es
 --


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com

Re: [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2015-05-17 Thread Marcos Alano

David,

Please connect and pair the mouse. After that execute
bluez-list-devices. If you check the lines:
Connected = 0
Paired = 0
You'll see the mouse is not even connected. The address is the same as
computer Bluetooth adapter so probably because that the line you put
in the file is wrong.

Cheers.



2015-05-17 15:32 GMT-03:00 David Cesarino de Sousa 1094...@bugs.launchpad.net:
 I have the Sculpt Comfort Bluetooth mouse as well (model H3S-3), and
 the connection is not surviving suspends or reboots on Vivid (15.04). To
 fix, I need to:

 1. Put the mouse into pairing mode (holding the bottom button).
 2. Go to the Bluetooth setting for the mouse and activate the Connection 
 switch.

 This _always_ works. Simply trying to connect by activating the
 Connection switch _never_ works.

 I've tried adding the following line to /usr/share/gnome-bluetooth/pin-
 code-database.xml:

 device oui=30:59:B7: type=mouse name=Microsoft Sculpt Comfort
 Mouse pin=/

 Because this information appears in bluez-list-devices:

 [ /org/bluez/661/hci0 ]
 Devices = dev_30_59_B7_73_B6_C6
 UUIDs = 0x1000 0x1001 0x112d 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 
 0x110b
 Address = C4:17:FE:EF:D8:A4
 Name = ubuntu-0
 Powered = 1
 Class = 0
 Pairable = 1
 Discoverable = 0
 DiscoverableTimeout = 180
 PairableTimeout = 0
 Discovering = 0
 [ /org/bluez/661/hci0/dev_30_59_B7_73_B6_C6 ]
 UUIDs = 0x1000 0x1124 0x1200
 Address = 30:59:B7:73:B6:C6
 Name = Microsoft Sculpt Comfort Mouse
 Icon = input-mouse
 Connected = 0
 Paired = 0
 Alias = Microsoft Sculpt Comfort Mouse
 Adapter = /org/bluez/661/hci0
 Trusted = 1
 Version = 0x0129
 Blocked = 0
 Vendor = 0x045e
 Product = 0x07a2
 Class = 0x000580
 Services = dbus.Array([], signature=dbus.Signature('o'), 
 variant_level=1)

 But the connection is still lost after a reboot or suspend, and I still
 need to put it into pairing mode to connect.

 Any help is appreciated.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1094744

 Title:
   MS Sculpt Touch Mouse needs to be re-paired periodically

 Status in GNOME Bluetooth:
   Fix Released
 Status in bluez package in Ubuntu:
   Confirmed
 Status in gnome-bluetooth package in Ubuntu:
   Fix Released
 Status in bluez source package in Precise:
   Confirmed
 Status in gnome-bluetooth source package in Precise:
   Fix Released
 Status in bluez source package in Quantal:
   Won't Fix
 Status in gnome-bluetooth source package in Quantal:
   Fix Released
 Status in bluez source package in Raring:
   Won't Fix
 Status in gnome-bluetooth source package in Raring:
   Won't Fix
 Status in bluez package in Fedora:
   Unknown

 Bug description:
   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
 session, watch it automatically re-pair.
   [Regression Potential] Little. The patched piece of XML is only relevant to 
 hardware having the same ID.

   When you don't use the mouse for a long enough time, the mouse
   disconnects and won't reconnect. I have to go into bluetooth settings,
   remove it, and re-pair it.

   1)
   ~ % lsb_release -rd
   Description:  Ubuntu 12.04.1 LTS
   Release:  12.04

   2)
   ~ % apt-cache policy bluez
   bluez:
 Installed: 4.98-2ubuntu7
 Candidate: 4.98-2ubuntu7
 Version table:
*** 4.98-2ubuntu7 0
   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
   100 /var/lib/dpkg/status

   3)
   I expected the mouse to reconnect automatically, or at least after I try to 
 reconnect manually through the bluetooth settings.

   4)
   I have to re-pair the mouse in order to use it again. Turning the mouse off 
 and on doesn't work either.

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

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

Re: [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2015-05-15 Thread Marcos Alano

Thanks Mark, help me so much. :)

The problem is in the Bluetooth device address: The prefix (which
indicates the manufacturer) is different for your mouse. So the
workaround is add this line in the file
/usr/share/gnome-bluetooth/pin-code-database.xml (close to the Wedge
mouse entrance):
device oui=28:18:78: type=mouse name=Microsoft Sculpt Comfort
Mouse pin=/
Restart the system and try again to check if the problem persists. If
work well I will submit a patch for gnome-bluetooth.

Thanks for report this bug. :)


2015-05-15 12:21 GMT-03:00 Mark Thornton 1094...@bugs.launchpad.net:
 Does this help? Note it is the same mouse that originally gave problems
 when this bug first appeared. It is also appearing twice in the list of
 devices (there is only one).

 Thanks,
 Mark

 mthornton@mark-PBL21:~$ bluez-list-devices
 [ /org/bluez/863/hci0 ]
 Address = 00:02:72:C6:AE:86
 Powered = 1
 UUIDs = 0x1000 0x1000 0x1001 0x1001 0x1112 0x111f 0x111e 0x110c 0x110e
 0x110a 0x110b
 Class = 0
 DiscoverableTimeout = 180
 Discovering = 0
 Name = mark-PBL21-1
 PairableTimeout = 0
 Discoverable = 0
 Devices = dev_28_18_78_5D_C1_65
 Pairable = 1
 [ /org/bluez/863/hci0/dev_28_18_78_5D_C1_65 ]
 Address = 28:18:78:5D:C1:65
 Paired = 1
 Version = 0x0129
 UUIDs = 0x1000 0x1124 0x1200
 Product = 0x07a2
 Icon = input-mouse
 Trusted = 1
 Connected = 1
 Vendor = 0x045e
 Adapter = /org/bluez/863/hci0
 Alias = Microsoft Sculpt Comfort Mouse
 Services = dbus.Array([], signature=dbus.Signature('o'),
 variant_level=1)
 Class = 0x002580
 Name = Microsoft Sculpt Comfort Mouse
 Blocked = 0

 [ /org/bluez/863/hci1 ]
 Address = DC:85:DE:05:4F:6E
 Powered = 1
 UUIDs = 0x1000 0x1001 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 0x110b
 Class = 0
 DiscoverableTimeout = 180
 Discovering = 0
 Name = mark-PBL21-0
 PairableTimeout = 0
 Discoverable = 0
 Devices = dev_28_18_78_5D_C1_65
 Pairable = 1
 [ /org/bluez/863/hci1/dev_28_18_78_5D_C1_65 ]
 Address = 28:18:78:5D:C1:65
 Paired = 0
 Version = 0x0129
 UUIDs = 0x1000 0x1124 0x1200
 Product = 0x07a2
 Icon = input-mouse
 Trusted = 1
 Connected = 0
 Vendor = 0x045e
 Adapter = /org/bluez/863/hci1
 Alias = Microsoft Sculpt Comfort Mouse
 Services = dbus.Array([], signature=dbus.Signature('o'),
 variant_level=1)
 Class = 0x000580
 Name = Microsoft Sculpt Comfort Mouse
 Blocked = 0


 On Friday, 15 May 2015, Marcos Alano 1094...@bugs.launchpad.net wrote:

 Mark, can you find the address of your Sculpt mouse using the command
 bluez-list-devices? If the address prefix is different I need submit a
 new patch (but I can post a workaround as well).

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1094744

 Title:
   MS Sculpt Touch Mouse needs to be re-paired periodically

 Status in GNOME Bluetooth:
   Fix Released
 Status in bluez package in Ubuntu:
   Confirmed
 Status in gnome-bluetooth package in Ubuntu:
   Fix Released
 Status in bluez source package in Precise:
   Confirmed
 Status in gnome-bluetooth source package in Precise:
   Fix Released
 Status in bluez source package in Quantal:
   Won't Fix
 Status in gnome-bluetooth source package in Quantal:
   Fix Released
 Status in bluez source package in Raring:
   Won't Fix
 Status in gnome-bluetooth source package in Raring:
   Won't Fix
 Status in bluez package in Fedora:
   Unknown

 Bug description:
   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay
 connected.
   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart
 session, watch it automatically re-pair.
   [Regression Potential] Little. The patched piece of XML is only relevant
 to hardware having the same ID.

   When you don't use the mouse for a long enough time, the mouse
   disconnects and won't reconnect. I have to go into bluetooth settings,
   remove it, and re-pair it.

   1)
   ~ % lsb_release -rd
   Description:  Ubuntu 12.04.1 LTS
   Release:  12.04

   2)
   ~ % apt-cache policy bluez
   bluez:
 Installed: 4.98-2ubuntu7
 Candidate: 4.98-2ubuntu7
 Version table:
*** 4.98-2ubuntu7 0
   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64
 Packages
   100 /var/lib/dpkg/status

   3)
   I expected the mouse to reconnect automatically, or at least after I try
 to reconnect manually through the bluetooth settings.

   4)
   I have to re-pair the mouse in order to use it again. Turning the mouse
 off and on doesn't work either.

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


 --
 You received this bug notification because you are subscribed

1 2 >

1 - 100 of 102 matches

Mail list logo