[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

[Daniel van Vugt]

Ignore the fullscreen-maximize failure...
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/comments/18

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Desktop-packages] [Bug 58171] Re: Connection to ICE-unix/.. socket times out so programs take minutes to start

[buguldey]

I still have this (or very similar) bug on Ubuntu 20.04.6 at March 2024.
Researching it.

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

Title:
  Connection to ICE-unix/.. socket times out so programs take minutes to
  start

Status in gnome-session package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Sometimes X11 programs take ages to start, there is no CPU activity
  and the programs seem to wait for something. Same affected programs
  are gthumb, openoffice, totem, but e.g. firefox is not affected. The
  behaviour does not always occur, but if, then it happens for all
  programs.

  Here's a strace from gthumb:

  [0] nokile:~$ strace -o log gthumb

  [ Nothing happens for about 5 minutes ]

  [1]+  Stopped strace -o log gthumb
  [148] nokile:~$ bg
  [1]+ strace -o log gthumb &

  [0] nokile:~$ tail  log
  chmod("/home/nikratio/.gnome2_private/", 0700) = 0
  mkdir("/home/nikratio/.gnome2/accels", 0700) = -1 EEXIST (File exists)
  socket(PF_FILE, SOCK_STREAM, 0) = 10
  uname({sys="Linux", node="nokile", ...}) = 0
  connect(10, {sa_family=AF_FILE, path="/tmp/.ICE-unix/5122"}, 21) = 0
  fcntl64(10, F_SETFD, FD_CLOEXEC)= 0
  write(10, "\0\1\0\0\0\0\0\0", 8)= 8
  read(10, 0x8118548, 8)  = ? ERESTARTSYS (To be restarted)
  --- SIGCONT (Continued) @ 0 (0) ---

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


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

[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg

[Daniel van Vugt]

That test passed in the actual build:
https://launchpadlibrarian.net/719148617/buildlog_ubuntu-jammy-armhf.mutter_42.9-0ubuntu7_BUILDING.txt.gz

It is known to be a flaky test (moreso on Arm) and its failure is not related 
to the code changes here.
https://gitlab.gnome.org/GNOME/mutter/-/issues/3050

Other examples of the same test failing upstream:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1984247

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

Title:
  Incomplete screen redraws in virtual machines running Xorg

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  When using software rendering on Xorg (so usually just in VMs), some
  parts of app windows may fail to redraw.

  https://gitlab.gnome.org/GNOME/mutter/-/issues/2880

  [ Test Plan ]

  1. Set up a virtual machine without graphics acceleration.
  2. Log into 'Ubuntu on Xorg'.
  3. Open Settings > About and verify Graphics = llvmpipe (or "Software 
Rendering"), and Windowing System = X11.
  4. sudo snap install chromium
  5. Open Chromium and find a web page with lots of text. Plain text without 
any links and staying at the top of the page will work best because you don't 
want to trigger any scrolling.
  6. Start selecting text with the mouse and while holding the button move the 
mouse up and down rapidly. Avoid triggering any page scrolling.
  7. Release the mouse button in roughly the middle of the area of text that 
was selected.
  8. Verify the remaining text selection is contiguous and not broken into 
multiple disconnected text selections (the bug).
  9. Repeat steps 7 and 8 several times to be sure.

  [ Where problems could occur ]

  The fix adds a new synchronization point between the compositor and X
  server. This should be inconsequential, although there is a "sync
  ring" in mutter used for this, and if a mistake occurs there then
  other parts of the desktop could appear to stop responding in Xorg
  sessions.

  [ Other Info ]

  This is a regression that started in 3.37.3 due to
  https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda.

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


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

[Desktop-packages] [Bug 2047595] Re: Too many settings can be modified on the lock screen

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Too many settings can be modified on the lock screen

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  The controls in the upper right hand corner, which consist of WiFi Bar, Sound 
Bar, and Battery Bar icons are unlocked when the machine is locked. This will 
enable anyone, who has physical access to the machine to change, disable or 
rearrange any settings available in this interface; 
  1. WiFi-- add or remove access points, disconnect WiFi, change power modes, 
styles, keyboard, etc. Power Modes. 
  2. Sounds, disable or modify sounds, lighting settings 
  3. Change or modify battery schemes. Power off machines, or sleep / Hibernate 
machine, etc. 
   
  lsb_release -rd  Ubuntu 23.10

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


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

[Desktop-packages] [Bug 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Fix Released

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions


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

[Desktop-packages] [Bug 1729433]

[Stephane-guillou-i]

Ben didn't provide version details in comment 55.

Jeff, thank you for the follow-up, but because this report is about the barely 
visible, minuscule window issue, and because there's 60+ comments, let's see if 
your issue is already better described elsewhere, or if it needs a fresh start 
in a new report, with clear steps.
Thank you!

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions


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

[Desktop-packages] [Bug 2058647] Re: GNOME OAuth2 Handler desktop entry not hidden

[Jeremy Bícha]

This is already fixed in noble-proposed. Therefore, I'm closing this
bug.

https://gitlab.gnome.org/GNOME/gnome-online-
accounts/-/merge_requests/177

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Fix Released

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

Title:
  GNOME OAuth2 Handler desktop entry not hidden

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  The GNOME OAuth2 Handler desktop entry should be hidden (it is not an
  user app and clicking it does nothing), but is displayed in Shell
  Overview on latest Ubuntu 24.04. This is because the "X-Ubuntu-
  Gettext-Domain" line that is incorrectly added to the file without a
  newline character:

  $ cat org.gnome.OnlineAccounts.OAuth2.desktop
  [Desktop Entry]
  Name=GNOME OAuth2 Handler
  Exec=/usr/libexec/goa-oauth2-handler %u
  Type=Application
  
MimeType=x-scheme-handler/goa-oauth2;x-scheme-handler/com.googleusercontent.apps.44438659992-7kgjeitenc16ssihbtdjbgguch7ju55s
  NoDisplay=trueX-Ubuntu-Gettext-Domain=gnome-online-accounts

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


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

[Desktop-packages] [Bug 2056767] Re: DRAFT [FFe] gnome-software package split

[Jeremy Bícha]

** Description changed:

  As requested by the Ubuntu Release Team, I am providing early notice of
- a Feature Freeze Exception I intend to request soon (later this week
- hopefully) to split the gnome-software package into separate binary
- plugins. This will allow users and flavors to specifically opt into the
- parts of the GNOME Software experience they want. For instance, someone
- may want to use only the Flatpak part or only the apt/.deb part.
+ a Feature Freeze Exception I intend to request soon (approximately March
+ 27)
  
  What is Needed Now
  -
- Finish the Salsa merge request to get some review from others.
- Evaluate different use case workflows and how well the changes help and any 
issues that may result
+ Waiting a few days for review of 
https://salsa.debian.org/gnome-team/gnome-software/-/merge_requests/16
  
  Impact
  --
+ I request permission to land a change I am making in Debian to split 
gnome-software's .deb support into a separate package, 
gnome-software-plugin-deb, to match the existing -snap and -flatpak packages. 
This will allow users and flavors to specifically opt into the parts of the 
GNOME Software experience they want. For instance, someone may want to use only 
the Flatpak part because they use the Snap Store to manage .debs and Snaps. Or 
maybe they want a different combination.
+ 
+ This has been requested by multiple users on Ubuntu Discourse and at
+ least one Launchpad bug and one Debian bug.
  
  Potential Problems
  ---
+ For new installs, gnome-software has Depends: gnome-software-plugin-deb | 
gnome-software-plugin. Where gnome-software-plugin is a virtual package 
provided by each plugin so a user would get gnome-software-plugin-deb installed 
unless they specifically chose a different plugin or the metapackage they 
installed did.
  
+ However, I think this won't work right for upgrades. I am going to
+ investigate whether I can add a ubuntu-release-upgrader quirk to install
+ gnome-software-plugin-deb for people who already have gnome-software
+ installed. Maybe I need to treat gnome-software like a metapackage so I
+ can use PostUpgradeInstall
+ 
+ Otherwise, people are likely to lose support for installing .debs with
+ GNOME Software and it is not obvious why.
  
  Other Related Changes
  -
- fwupd
+ I am dropping the fwupd plugin. Ubuntu Desktop includes the firmware-updater 
snap. Several Ubuntu desktop flavors also include it. For people who don't want 
snaps, there is also the gnome-firmware app packaged as a .deb.
  
+ Because Ubuntu already has update-manager to handle apt update
+ notifications, I am also dropping the autostart file to reduce
+ background RAM use.
+ 
+ A few Ubuntu desktop flavors do not provide any firmware updater app at
+ all. Ubuntu Budgie developers thought a firmware updater app was too
+ technical for inclusion in the default Ubuntu 24.04 LTS install.
  
  Desktop Flavors Affected
  
  GNOME Software is currently included in the default install for only
  Ubuntu Cinnamon

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

Title:
  DRAFT [FFe] gnome-software package split

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  As requested by the Ubuntu Release Team, I am providing early notice
  of a Feature Freeze Exception I intend to request soon (approximately
  March 27)

  What is Needed Now
  -
  Waiting a few days for review of 
https://salsa.debian.org/gnome-team/gnome-software/-/merge_requests/16

  Impact
  --
  I request permission to land a change I am making in Debian to split 
gnome-software's .deb support into a separate package, 
gnome-software-plugin-deb, to match the existing -snap and -flatpak packages. 
This will allow users and flavors to specifically opt into the parts of the 
GNOME Software experience they want. For instance, someone may want to use only 
the Flatpak part because they use the Snap Store to manage .debs and Snaps. Or 
maybe they want a different combination.

  This has been requested by multiple users on Ubuntu Discourse and at
  least one Launchpad bug and one Debian bug.

  Potential Problems
  ---
  For new installs, gnome-software has Depends: gnome-software-plugin-deb | 
gnome-software-plugin. Where gnome-software-plugin is a virtual package 
provided by each plugin so a user would get gnome-software-plugin-deb installed 
unless they specifically chose a different plugin or the metapackage they 
installed did.

  However, I think this won't work right for upgrades. I am going to
  investigate whether I can add a ubuntu-release-upgrader quirk to
  install gnome-software-plugin-deb for people who already have gnome-
  software installed. Maybe I need to treat gnome-software like a
  metapackage so I can use PostUpgradeInstall

  Otherwise, people are likely to lose 

[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

[Kai-Heng Feng]

May I know where can I find the test result?

Everything looks fine at [0].

[0]
https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu7/+build/27912046

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Desktop-packages] [Bug 2058693] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()

[Brian Murray]

I looked at the log files on the server which does the retracing of
these crashes and I did not find anything informative. If you still have
the .crash file available on your system (its located in /var/crash/) I
might be able to have a look at it.  You may want to make the bug
private again if you do upload the core dump as it could contain
personal information.

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  Uname: Linux 6.8.1 x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 20 23:12:46 2024
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2024-02-14 (37 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcAttrCurrent: Error: [Errno 22] Invalid argument
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: network-manager
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2024-02-18T15:43:08.117195
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

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


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

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntustudio-default-settings -
24.04.21

---
ubuntustudio-default-settings (24.04.21) noble; urgency=medium

  * desktop-provision:
- New "done" graphic
- Prepare storage icon

 -- Erich Eickmeyer   Thu, 21 Mar 2024 13:16:17
-0700

** Changed in: ubuntustudio-default-settings (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-artwork package in Ubuntu:
  In Progress
Status in budgie-desktop-environment package in Ubuntu:
  In Progress
Status in budgie-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-unity-backgrounds package in Ubuntu:
  Confirmed
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntucinnamon-environment package in Ubuntu:
  Fix Committed
Status in ubuntucinnamon-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntukylin-wallpapers package in Ubuntu:
  In Progress
Status in ubuntustudio-default-settings package in Ubuntu:
  Fix Released
Status in ubuntustudio-look package in Ubuntu:
  Fix Released

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-artwork/+bug/2056591/+subscriptions


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

[Desktop-packages] [Bug 2058261] Re: cups-browsed crashed with SIGSEGV in httpAddrFamily()

[Roman]

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

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

Title:
  cups-browsed crashed with SIGSEGV in httpAddrFamily()

Status in cups-browsed package in Ubuntu:
  New

Bug description:
  Triggered after `apt upgrade`, don't know why, I don't even have any
  printers installed

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: cups-browsed 2.0.0-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   W [18/Mar/2024:16:28:04 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Kyocera_ECOSYS_M5526cdn-Gray..\' already exists
   W [18/Mar/2024:16:28:04 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Kyocera_ECOSYS_M5526cdn-DeviceN..\' already exists
  Date: Mon Mar 18 16:28:09 2024
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2024-02-14 (34 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  JournalErrors:
   Mar 18 16:28:12 hostname systemd[1]: cups-browsed.service: Main process 
exited, code=dumped, status=11/SEGV
   Mar 18 16:28:12 hostname systemd[1]: cups-browsed.service: Failed with 
result 'core-dump'.
   Mar 18 16:28:12 hostname system-crash-no[445844]: 
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 
'GDK_IS_WAYLAND_WINDOW (window)' failed
  Lpstat:
   device for Kyocera_ECOSYS_M5521cdn: implicitclass://Kyocera_ECOSYS_M5521cdn/
   device for Kyocera_ECOSYS_M5526cdn: implicitclass://Kyocera_ECOSYS_M5526cdn/
   device for RICOH_IM_C3010_5838798EBA01: 
implicitclass://RICOH_IM_C3010_5838798EBA01/
  MachineType: Micro-Star International Co., Ltd. Prestige 16 AI Evo B1MG
  Papersize: a4
  PpdFiles:
   Kyocera_ECOSYS_M5521cdn: ECOSYS M5521cdn, driverless, 2.0.0
   RICOH_IM_C3010_5838798EBA01: RICOH IM C3010 PS3, driverless, 2.0.0
   Kyocera_ECOSYS_M5526cdn: ECOSYS M5526cdn, driverless, 2.0.0
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash mitigations=off 
transparent_hugepage=always iommu=pt intel_iommu=on vt.handoff=7
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'Error:'
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: cups-browsed
  StacktraceTop:
   httpAddrFamily () from /lib/x86_64-linux-gnu/libcups.so.2
   httpAddrConnect2 () from /lib/x86_64-linux-gnu/libcups.so.2
   httpReconnect2 () from /lib/x86_64-linux-gnu/libcups.so.2
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   cupsSendRequest () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cups-browsed crashed with SIGSEGV in httpAddrFamily()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 11/03/2023
  dmi.bios.release: 1.6
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E15A1IMS.106
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-15A1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15A1IMS.106:bd11/03/2023:br1.6:svnMicro-StarInternationalCo.,Ltd.:pnPrestige16AIEvoB1MG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15A1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku15A1.1:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 16 AI Evo B1MG
  dmi.product.sku: 15A1.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  separator:

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


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

[Desktop-packages] [Bug 2058693] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()

[Roman]

All reports from my machine are getting this "core dump is invalid"
messages, why? It is frustrating when you try to properly report bugs
just to get them automatically closed as invalid.

Also seems that this robot automatically removes dumps so you can't even
see them afterwards?

I tried to contact Brian via email without respond, let's try ping him
here somehow - not sure how this is done properly.

** Information type changed from Private to Public

** Changed in: network-manager (Ubuntu)
   Status: Invalid => New

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  Uname: Linux 6.8.1 x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 20 23:12:46 2024
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2024-02-14 (37 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcAttrCurrent: Error: [Errno 22] Invalid argument
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: network-manager
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2024-02-18T15:43:08.117195
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

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


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

[Desktop-packages] [Bug 2054183] Re: nautilus not generating thumbnails anymore

[olive]

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

for me the bug has disappeared since the version of Gnome 46

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

Title:
  nautilus not generating thumbnails anymore

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade to 24.04, nautilus is not generating thumbnails for new 
files.
  Old thumbnails are displayed ok.

  I cleaned out $HOME/.cache/thumbnails/ and found that only a subdirectory 
"fail" is being generated.
  It contains a subdirectory "gnome-thumbnail-factory" which in turn contains 
lots of PNG files:

  ece577c54f5ca98e1f7aaa5b4e932aa4.png: PNG image data, 1 x 1, 8-bit/color 
RGBA, non-interlaced
  ee638c64b1c285684412717bf120e295.png: PNG image data, 1 x 1, 8-bit/color 
RGBA, non-interlaced
  ef811735cfb8e69447b5d3a53f361c63.png: PNG image data, 1 x 1, 8-bit/color 
RGBA, non-interlaced
  f0b3ab2f77c342daa3579bfcf9c72481.png: PNG image data, 1 x 1, 8-bit/color 
RGBA, non-interlaced
  f0ddb101b8342e4b298b4c7121881422.png: PNG image data, 1 x 1, 8-bit/color 
RGBA, non-interlaced

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:45.2.1-4ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 08:49:55 2024
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-04-16 (1767 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to noble on 2024-02-14 (3 days ago)
  usr_lib_nautilus:
   file-roller   43.1-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

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


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

[Desktop-packages] [Bug 2058691] [NEW] No sound card detected on the Dell xps 16 2024 (9640)

[Moritz]

Public bug reported:

The sound card is not detected on the Dell XPS 16 2024 (9640). A Cirrus
Logic CS42L43 card is used which apparently got support in Linux 6.6

https://www.google.com/url?sa=t=web=j=89978449=https://www.phoronix.com/forums/forum/software/general-
linux-open-source/1408193-linux-6-6-lands-support-for-the-cirrus-logic-
cs42l43-audio-codec=2ahUKEwiukq-ZroaFAxUWhf0HHe-
jCngQFnoECA8QAQ=AOvVaw3VW5hROJFzdJPUaIX-3igC

https://www.reddit.com/r/DellXPS/comments/1ax1i4t/support_for_xps_16_9640_documentation/


No LSB modules are available.
Description:Ubuntu Noble Numbat (development branch)
Release:24.04

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 21 23:00:06 2024
InstallationDate: Installed on 2024-03-19 (2 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319)
MachineType: Dell Inc. XPS 16 9640
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2024
dmi.bios.release: 1.1
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.0
dmi.board.name: 0YFT36
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/15/2024:br1.1:efr1.2:svnDellInc.:pnXPS169640:pvr:rvnDellInc.:rn0YFT36:rvrA00:cvnDellInc.:ct10:cvr:sku0C62:
dmi.product.family: XPS
dmi.product.name: XPS 16 9640
dmi.product.sku: 0C62
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  No sound card detected on the Dell xps 16 2024 (9640)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound card is not detected on the Dell XPS 16 2024 (9640). A
  Cirrus Logic CS42L43 card is used which apparently got support in
  Linux 6.6

  
https://www.google.com/url?sa=t=web=j=89978449=https://www.phoronix.com/forums/forum/software/general-
  linux-open-source/1408193-linux-6-6-lands-support-for-the-cirrus-
  logic-cs42l43-audio-codec=2ahUKEwiukq-ZroaFAxUWhf0HHe-
  jCngQFnoECA8QAQ=AOvVaw3VW5hROJFzdJPUaIX-3igC

  
https://www.reddit.com/r/DellXPS/comments/1ax1i4t/support_for_xps_16_9640_documentation/

  
  No LSB modules are available.
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 21 23:00:06 2024
  InstallationDate: Installed on 2024-03-19 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319)
  MachineType: Dell Inc. XPS 16 9640
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2024
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0YFT36
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/15/2024:br1.1:efr1.2:svnDellInc.:pnXPS169640:pvr:rvnDellInc.:rn0YFT36:rvrA00:cvnDellInc.:ct10:cvr:sku0C62:
  dmi.product.family: XPS
  dmi.product.name: XPS 16 9640
  dmi.product.sku: 0C62
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 2058514] Re: System crashes/freezes when suspending

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Confirmed

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

Title:
  System crashes/freezes when suspending

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Sometimes (I'd say 20% of the time) either a manual or automatic
  suspend fails in these ways:

  * power button remains lit (on succesful suspend it flashes)
  * Fans may remain spinning and (indirectly observed) battery drains quite fast
  * Screen black, impossible to wake, only to shut down by long power button 
press

  Bug occurs BOTH on Wayland and Xorg Gnome, so not sure which package
  is at fault.

  
  In addition, bug submission documentation is not very good, I'm filing this 
bug after 30 minutes of bug documentation and I'm still confident this is filed 
incorrectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xserver-xorg-video-amdgpu 23.0.0-1
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 19:57:53 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Lucienne [17aa:5097]
  InstallationDate: Installed on 2023-12-08 (103 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=112bce1c-b1dd-49e6-b6e9-7c913a1842d9 ro quiet splash 
usbcore.autosuspend=-1 vt.handoff=7
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2023
  dmi.bios.release: 1.16
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1OET37W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20YG00BRMH
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1OET37W(1.16):bd09/29/2023:br1.16:efr1.16:svnLENOVO:pn20YG00BRMH:pvrThinkPadE15Gen3:rvnLENOVO:rn20YG00BRMH:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YG_BU_Think_FM_ThinkPadE15Gen3:
  dmi.product.family: ThinkPad E15 Gen 3
  dmi.product.name: 20YG00BRMH
  dmi.product.sku: LENOVO_MT_20YG_BU_Think_FM_ThinkPad E15 Gen 3
  dmi.product.version: ThinkPad E15 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/2058514/+subscriptions


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

[Desktop-packages] [Bug 2015405] Re: spice-vdagent crashed with SIGSEGV

[nelsinchi]

I recently installed Ubuntu 24.04 Noble Numbat (development branch),
then I did `sudo apt update && sudo apt upgrade -y`, then I rebooted the
VM. After that I got the error.

I installed this OS just for testing purposes via LXD VM.

Thanks.

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

Title:
  spice-vdagent crashed with SIGSEGV

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Just launching an ubuntu 23.04 beta VM on libvirtd/qemu/KVM and this
  brings the reporting crash app as soon as loging into the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: spice-vdagent 0.22.1-3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  5 23:21:08 2023
  ExecutablePath: /usr/bin/spice-vdagent
  InstallationDate: Installed on 2023-03-31 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  ProcCmdline: /usr/bin/spice-vdagent
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x559a23cd00e0:mov(%r15),%rdi
   PC (0x559a23cd00e0) ok
   source "(%r15)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: spice-vdagent
  StacktraceTop:
   ()
   __libc_start_call_main (main=main@entry=0x559a23ccfe80, argc=argc@entry=1, 
argv=argv@entry=0x7ffce18a7c08) at ../sysdeps/nptl/libc_start_call_main.h:58
   __libc_start_main_impl (main=0x559a23ccfe80, argc=1, argv=0x7ffce18a7c08, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffce18a7bf8) at ../csu/libc-start.c:360
   ()
  Title: spice-vdagent crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2015405/+subscriptions


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

[Desktop-packages] [Bug 2058687] Re: [SRU] libreoffice 7.6.6 for mantic

[Rico Tzschichholz]

** Description changed:

  [Impact]
  
   * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release
  
   * Version 7.6.5 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 
(that's a total of ? bugs):
   https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.6/RC2#List_of_fixed_bugs
+  https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs
  
-  7.6.6 RC2 is identical to the 7.6.6 release
+  7.6.6 RC3 is identical to the 7.6.6 release
  
   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU a
  minor release rather than cherry-pick selected bug fixes.
  
  [Testing]
  
   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).
  
    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_76/1898/
  
    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
  
   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
- Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15867518/+listing-archive-extra
+ Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra
  * [amd64] ...
  * [arm64] ...
  * [armhf] ...
  * [ppc64el] ...
  * [riscv64] not available
  * [s390x] ...
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
  
  [Regression Potential]
  
   * A minor release with a total of ? bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.
  
   * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

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

Title:
  [SRU] libreoffice 7.6.6 for mantic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Mantic:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release

   * Version 7.6.5 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 
(that's a total of ? bugs):
   https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.6/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs

   7.6.6 RC3 is identical to the 7.6.6 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_76/1898/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 

[Desktop-packages] [Bug 2058687] [NEW] [SRU] libreoffice 7.6.6 for mantic

[Rico Tzschichholz]

Public bug reported:

[Impact]

 * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line:
 https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release

 * Version 7.6.5 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 
(that's a total of ? bugs):
 https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/7.6.6/RC2#List_of_fixed_bugs

 7.6.6 RC2 is identical to the 7.6.6 release

 * Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU a
minor release rather than cherry-pick selected bug fixes.

[Testing]

 * Upstream testing. Bugs fixed upstream typically include
unit/regression tests, and the release itself is extensively exercised
(both in an automated manner and manually).

  * A recent set of upstream's automated jenkins testing can be found here:
https://ci.libreoffice.org/job/gerrit_76/1898/

  * More information about the upstream QA testing can be found here:
* Automated tests
  https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
  https://wiki.documentfoundation.org/Development/UITests
* Regression tests
  https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
  https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

 * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15867518/+listing-archive-extra
* [amd64] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [riscv64] not available
* [s390x] ...
 * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

[Regression Potential]

 * A minor release with a total of ? bug fixes always carries the
potential for introducing regressions, even though it is a bugfix-only
release, meaning that no new features were added, and no existing
features were removed.

 * A combination of autopkgtests and careful smoke testing as described
above should provide reasonable confidence that no regressions sneaked
in.

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: libreoffice (Ubuntu Mantic)
 Importance: Medium
 Assignee: Rico Tzschichholz (ricotz)
 Status: In Progress

** Also affects: libreoffice (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu)
   Status: New => Fix Released

** Changed in: libreoffice (Ubuntu Mantic)
   Importance: Undecided => Medium

** Changed in: libreoffice (Ubuntu Mantic)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

** Changed in: libreoffice (Ubuntu Mantic)
   Status: New => In Progress

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

Title:
  [SRU] libreoffice 7.6.6 for mantic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Mantic:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release

   * Version 7.6.5 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 
(that's a total of ? bugs):
   https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.6/RC2#List_of_fixed_bugs

   7.6.6 RC2 is identical to the 7.6.6 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_76/1898/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

[Erich Eickmeyer]

** Changed in: ubuntustudio-default-settings (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: ubuntucinnamon-wallpapers (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: ubuntucinnamon-environment (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-artwork package in Ubuntu:
  In Progress
Status in budgie-desktop-environment package in Ubuntu:
  In Progress
Status in budgie-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-unity-backgrounds package in Ubuntu:
  Confirmed
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntucinnamon-environment package in Ubuntu:
  Fix Committed
Status in ubuntucinnamon-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntukylin-wallpapers package in Ubuntu:
  In Progress
Status in ubuntustudio-default-settings package in Ubuntu:
  Fix Committed
Status in ubuntustudio-look package in Ubuntu:
  Fix Released

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-artwork/+bug/2056591/+subscriptions


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

[Desktop-packages] [Bug 2056767] Re: DRAFT [FFe] gnome-software package split

[Milachew]

Maybe, some work which I did before can help you to make this change:
https://discourse.ubuntu.com/t/ideas-for-improving-the-experience-with-
flatpak-packages-in-ubuntu/39643/16?u=milachew

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

Title:
  DRAFT [FFe] gnome-software package split

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  As requested by the Ubuntu Release Team, I am providing early notice
  of a Feature Freeze Exception I intend to request soon (later this
  week hopefully) to split the gnome-software package into separate
  binary plugins. This will allow users and flavors to specifically opt
  into the parts of the GNOME Software experience they want. For
  instance, someone may want to use only the Flatpak part or only the
  apt/.deb part.

  What is Needed Now
  -
  Finish the Salsa merge request to get some review from others.
  Evaluate different use case workflows and how well the changes help and any 
issues that may result

  Impact
  --

  Potential Problems
  ---

  
  Other Related Changes
  -
  fwupd

  
  Desktop Flavors Affected
  
  GNOME Software is currently included in the default install for only
  Ubuntu Cinnamon

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


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

[Desktop-packages] [Bug 2037961] Re: xdg-desktop-portal crashed with SIGSEGV in g_variant_builder_add_value()

[Erich Eickmeyer]

This just occurred with me for no reason that I can see. And seeing no
user identifiable information in the original report, I'm opening this
up to public.

** Tags added: noble

** Information type changed from Private to Public

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

Title:
  xdg-desktop-portal crashed with SIGSEGV in
  g_variant_builder_add_value()

Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  https://asciinema.org/a/Na0XLlrzdhsshdG69WHiX372P

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: xdg-desktop-portal 1.17.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  2 09:15:16 2023
  ExecutablePath: /usr/libexec/xdg-desktop-portal
  InstallationDate: Installed on 2023-09-30 (2 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
  ProcCmdline: /usr/libexec/xdg-desktop-portal
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7ff9091b5976 :  
mov0x30(%rbp),%ecx
   PC (0x7ff9091b5976) ok
   source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal
  StacktraceTop:
   g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: xdg-desktop-portal crashed with SIGSEGV in 
g_variant_builder_add_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2037961/+subscriptions


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

[Desktop-packages] [Bug 192056] Re: [Upstream] [hardy] Cannot Open password-encrypted MS Office 2003 files

[Bug Watch Updater]

Launchpad has imported 37 comments from the remote bug at
http://qa.openoffice.org/issues/show_bug.cgi?id=46307.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2005-03-30T15:25:29+00:00 Thomas-hovezak wrote:

when trying to open an password-encrypted ppt you get following message:

read error
the loading of password-encrypted Microsoft PowerPoint presentation is not
supported..

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/0


On 2005-03-30T15:31:59+00:00 Thomas-hovezak wrote:

Created attachment 24419
the ppt file which caused the issue

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/1


On 2005-03-30T16:13:16+00:00 Wolframgarten wrote:

Changed to defect, reassigned.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/2


On 2005-04-06T15:16:11+00:00 Christian-guenther-v wrote:

set to new and change the target.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/3


On 2005-04-06T15:20:00+00:00 Christian-guenther-v wrote:

With the internal bug 115982 you fixed something about password protected 
PPT-Files.
Why can't we load this file.
Has  this file another encryption?
Please have a look.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/4


On 2005-04-26T11:11:54+00:00 Sven-jacobi wrote:

sj->cgu: As you can read in 115982 PowerPoint is providing RC4 encryption only,
and RC4 is not be supported by OOo. That time I added the new error message"read
error the loading of password-encrypted Microsoft PowerPoint presentation is not
supported.." so that you are not getting the general io error if trying to load
protected files.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/5


On 2005-05-02T18:40:41+00:00 Christian-guenther-v wrote:

OOo should support RC4 encryption to load Password protected PPT-Files.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/6


On 2005-05-23T13:54:49+00:00 Bettina-haberer wrote:

Set issue type, target and keywords.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/7


On 2006-03-09T09:03:44+00:00 Christian-guenther-v wrote:

*** Issue 62955 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/8


On 2006-05-15T08:47:49+00:00 Wolframgarten wrote:

*** Issue 65376 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/9


On 2007-12-19T09:05:43+00:00 Marcelly-bernard wrote:

We can see in various OOo forums that PowerPoint files password protected for 
modifications, but not protected for reading, are becoming common.

Windows users (Win 200 and above) can display them with the free PowerPoint 
Viewer 
2007.
But users of other OS (Linux, Mac) cannot read these PowerPoint files.

This is a real lack of compatibility for OpenOffice.org in the non-
Microsoft world.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/10


On 2008-04-07T09:18:17+00:00 Wolframgarten wrote:

*** Issue 61691 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/17


On 2008-04-07T09:18:38+00:00 Wolframgarten wrote:

*** Issue 87922 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/18


On 2008-04-07T09:28:22+00:00 Cno wrote:

added 'Powerpoint' to the issues summary

Reply at:

[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript

[Bug Watch Updater]

** Changed in: firefox
   Status: Confirmed => Fix Released

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

Title:
  [snap] chromium snap does not allow to read symlinks to
  /usr/share/javascript

Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1) Install chromium snap
  snap install chromium
  2) Install openjdk-21 documentation
  sudo apt install openjdk-21-doc
  3) Browse API documentation
  chromium /usr/share/doc/openjdk-21-doc/api/index.html

  The search bar is inactive and dev console contains:
  jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND

   
  $ls -l 
/usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js
  lrwxrwxrwx 1 root root 43 Mar 17 13:31 
/usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> 
../../../../javascript/jquery/jquery.min.js

  cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js
  prints the file contents

  Downloaded version of chrome opens documentation with active search bar and 
no javascript errors
  /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html

  Expected results:

  Chromium snap should be able to follow symlink into
  /usr/share/javascript and correctly load OpenJDK API documentation.

  Note: this probably should be a specific exclusion for Debian-based
  systems.

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


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

[Desktop-packages] [Bug 2032992]

[Lissyx+mozillians]

Merged and will get fixed when snapd 2.62 gets released:
https://github.com/snapcore/snapd/pull/13130

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

Title:
  [snap] chromium snap does not allow to read symlinks to
  /usr/share/javascript

Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1) Install chromium snap
  snap install chromium
  2) Install openjdk-21 documentation
  sudo apt install openjdk-21-doc
  3) Browse API documentation
  chromium /usr/share/doc/openjdk-21-doc/api/index.html

  The search bar is inactive and dev console contains:
  jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND

   
  $ls -l 
/usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js
  lrwxrwxrwx 1 root root 43 Mar 17 13:31 
/usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> 
../../../../javascript/jquery/jquery.min.js

  cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js
  prints the file contents

  Downloaded version of chrome opens documentation with active search bar and 
no javascript errors
  /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html

  Expected results:

  Chromium snap should be able to follow symlink into
  /usr/share/javascript and correctly load OpenJDK API documentation.

  Note: this probably should be a specific exclusion for Debian-based
  systems.

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


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

[Desktop-packages] [Bug 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main

[Jeremy Bícha]

The promotion to main is done. This bug will be automatically closed
once gnome-remote-desktop and remmina migrate out of noble-proposed.

** Changed in: freerdp3 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  FFe: [MIR] freedp2 -> freerdp3 in main

Status in freerdp3 package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop package in Ubuntu:
  Fix Committed
Status in remmina package in Ubuntu:
  Fix Committed

Bug description:
  Feature Freeze Exception Request
  --
  There are only 2 packages in Ubuntu main that use freerdp2: remmina and 
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore 
only one version of freerdp will be in main. freerdp2 will be demoted to 
universe since many universe packages use it and are not prepared to switch to 
freerdp3.

  This also requests updating gnome-control-center to fully enable the
  features of gnome-remote-desktop 46.

  Impact
  --
  A headline feature of GNOME 46 is support as a Remote Desktop server without 
requiring someone to already be logged in locally ("headless" mode). This 
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires 
freerdp3.

  Impact if this does not happen
  --
  - We would need to patch gnome-control-center to use the older Remote Desktop 
panel (or at least hide the new tab for Remote Login)
  - We would need to keep using gnome-remote-desktop 45 instead of 46. The 
gnome-remote-desktop upstream maintainers would be unhappy with this decision. 
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may 
require changes in gnome-remote-desktop for things to work well although a 
simple test showed that basic remote desktop seems to work ok with the 
mismatch. (See comment #1 from upstream developer.)

  Why this did not land sooner
  ---
  It required the packaging of a new source package freerdp3. And we had to do 
this sooner than Debian. Sorry too many things to do before Feature Freeze and 
this did not make it.

  Affected Packages
  -
  - gnome-remote-desktop 45 -> 46
  - gnome-control-center (to update the Remote Desktop settings page)
  - remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not 
work  with freerdp 3.3 in my testing
  - gnome-connections (build-dependency swap): Not required by other changes 
and not in Main but makes sense to switch it also

  Affected Flavors
  
  Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center, 
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships 
gnome-control-center but this appears to be a bug since they ship 
cinnamon-control-center and is likely already fixed in noble-proposed)

  Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.

  gnome-connections has no reverse dependencies or recommends.

  Upstream Changes
  
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS

  https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md

  gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature 
Freeze. It will be updated to 46.0. The relevant part here is whether we use 
the 46~beta version of the Remote Desktop page or the 46.0 version.
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS

  Build Logs
  --
  I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA. 
The PPA currently has noble-proposed disabled so that it is easily possible to 
try this set of packages without dealing with the incomplete 32-bit time 
transition in noble-proposed. In addition, the PPA has the affected packages 
from this FFe.

  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages

  Testing Done
  ---
  1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect 
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46 
RC. Remote control worked.

  2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
  freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
  worked.

  3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
  with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
  control worked.

  4. I added a new Remote Login test case to
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
  verified that remote login worked. Notably, enabling this changes the
  port for the older service, now called "Desktop Sharing" to 3390.
  Since 3389 is the default port, users would then need to manually
  specific port 3390 for Desktop Sharing in their remote connection app
  (Remmina, GNOME Connections, etc.).

To manage notifications about this bug go to:

[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg

[Andreas Hasenack]

The test failure on armhf persists:

939s # Running test: mutter-13/fullscreen-maximize.test
940s # Executing: mutter-13/fullscreen-maximize.test
941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code 
1)
941s not ok - mutter-13/fullscreen-maximize.test

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

Title:
  Incomplete screen redraws in virtual machines running Xorg

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  When using software rendering on Xorg (so usually just in VMs), some
  parts of app windows may fail to redraw.

  https://gitlab.gnome.org/GNOME/mutter/-/issues/2880

  [ Test Plan ]

  1. Set up a virtual machine without graphics acceleration.
  2. Log into 'Ubuntu on Xorg'.
  3. Open Settings > About and verify Graphics = llvmpipe (or "Software 
Rendering"), and Windowing System = X11.
  4. sudo snap install chromium
  5. Open Chromium and find a web page with lots of text. Plain text without 
any links and staying at the top of the page will work best because you don't 
want to trigger any scrolling.
  6. Start selecting text with the mouse and while holding the button move the 
mouse up and down rapidly. Avoid triggering any page scrolling.
  7. Release the mouse button in roughly the middle of the area of text that 
was selected.
  8. Verify the remaining text selection is contiguous and not broken into 
multiple disconnected text selections (the bug).
  9. Repeat steps 7 and 8 several times to be sure.

  [ Where problems could occur ]

  The fix adds a new synchronization point between the compositor and X
  server. This should be inconsequential, although there is a "sync
  ring" in mutter used for this, and if a mistake occurs there then
  other parts of the desktop could appear to stop responding in Xorg
  sessions.

  [ Other Info ]

  This is a regression that started in 3.37.3 due to
  https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda.

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


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

[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

[Andreas Hasenack]

The test failure on armhf persists:

939s # Running test: mutter-13/fullscreen-maximize.test
940s # Executing: mutter-13/fullscreen-maximize.test
941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code 
1)
941s not ok - mutter-13/fullscreen-maximize.test

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Desktop-packages] [Bug 2057835] Re: migration to snap broke openpgp; no private key found

[Timo Aaltonen]

it works fine on my laptop, even without adding gnupg permissions

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

Title:
  migration to snap broke openpgp; no private key found

Status in thunderbird package in Ubuntu:
  New

Bug description:
  This means that it keeps complaining when trying to save emails to
  drafts, also the openpgp settings show that the private key can't be
  found.

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


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

[Desktop-packages] [Bug 2058647] [NEW] GNOME OAuth2 Handler desktop entry not hidden

[AsciiWolf]

Public bug reported:

The GNOME OAuth2 Handler desktop entry should be hidden (it is not an
user app and clicking it does nothing), but is displayed in Shell
Overview on latest Ubuntu 24.04. This is because the "X-Ubuntu-Gettext-
Domain" line that is incorrectly added to the file without a newline
character:

$ cat org.gnome.OnlineAccounts.OAuth2.desktop
[Desktop Entry]
Name=GNOME OAuth2 Handler
Exec=/usr/libexec/goa-oauth2-handler %u
Type=Application
MimeType=x-scheme-handler/goa-oauth2;x-scheme-handler/com.googleusercontent.apps.44438659992-7kgjeitenc16ssihbtdjbgguch7ju55s
NoDisplay=trueX-Ubuntu-Gettext-Domain=gnome-online-accounts

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


** Tags: noble

** Attachment added: "oauth2 handler desktop entry.png"
   
https://bugs.launchpad.net/bugs/2058647/+attachment/5757904/+files/oauth2%20handler%20desktop%20entry.png

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

Title:
  GNOME OAuth2 Handler desktop entry not hidden

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  The GNOME OAuth2 Handler desktop entry should be hidden (it is not an
  user app and clicking it does nothing), but is displayed in Shell
  Overview on latest Ubuntu 24.04. This is because the "X-Ubuntu-
  Gettext-Domain" line that is incorrectly added to the file without a
  newline character:

  $ cat org.gnome.OnlineAccounts.OAuth2.desktop
  [Desktop Entry]
  Name=GNOME OAuth2 Handler
  Exec=/usr/libexec/goa-oauth2-handler %u
  Type=Application
  
MimeType=x-scheme-handler/goa-oauth2;x-scheme-handler/com.googleusercontent.apps.44438659992-7kgjeitenc16ssihbtdjbgguch7ju55s
  NoDisplay=trueX-Ubuntu-Gettext-Domain=gnome-online-accounts

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


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

[Desktop-packages] [Bug 2058635] Re: /dev/nvme* disappear in Linux 6

[Victor Porton]

** Summary changed:

- Internal hard disk partition cannot be mounted manually
+ /dev/nvme* disappear in Linux 6

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

Title:
  /dev/nvme* disappear in Linux 6

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Upon installing linux-image-6.5.0-26-generic and linux-
  modules-6.5.0-26-generic and loading this version of the kernel, I see
  initrd.

  In initrd there are no /dev/nvme* devices. It leads to Linux being
  unable get past initrd stage and load the desktop.

  This is my system as it was before installing linux-image-6.5.0-26-generic:
  Linux victor 5.19.0-40-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 23 
21:39:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  $ sudo dmidecode

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: udisks2 2.10.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.skype.rules 70-snap.ipfs-desktop.rules 
70-snap.session-desktop.rules 70-snap.teams-for-linux.rules 
70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.g-assist.rules 
70-snap.snapd-desktop-integration.rules 70-snap.clickup.rules 
70-snap.obs-studio.rules 70-snap.canonical-livepatch.rules 
70-snap.postman.rules 70-snap.telegram-desktop.rules 70-snap.snapd.rules 
70-snap.cups.rules 70-snap.gimp.rules 70-snap.discord.rules 
70-snap.firefox.rules
  Date: Thu Mar 21 12:31:06 2024
  InstallationDate: Installed on 2022-01-18 (793 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qa6vun@/vmlinuz-5.19.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_qa6vun ro quiet splash
  SourcePackage: udisks2
  Symptom: storage
  Title: Internal hard disk partition cannot be mounted manually
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (139 days ago)
  dmi.bios.date: 07/22/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X515EA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515EA.303:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515EA_X515EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515EA_X515EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Desktop-packages] [Bug 2058635] Re: Internal hard disk partition cannot be mounted manually

[Victor Porton]

modprobe nvme
modprobe nvme_core

does not help (the devices don't appear in /dev/)

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

Title:
  Internal hard disk partition cannot be mounted manually

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Upon installing linux-image-6.5.0-26-generic and linux-
  modules-6.5.0-26-generic and loading this version of the kernel, I see
  initrd.

  In initrd there are no /dev/nvme* devices. It leads to Linux being
  unable get past initrd stage and load the desktop.

  This is my system as it was before installing linux-image-6.5.0-26-generic:
  Linux victor 5.19.0-40-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 23 
21:39:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  $ sudo dmidecode

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: udisks2 2.10.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.skype.rules 70-snap.ipfs-desktop.rules 
70-snap.session-desktop.rules 70-snap.teams-for-linux.rules 
70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.g-assist.rules 
70-snap.snapd-desktop-integration.rules 70-snap.clickup.rules 
70-snap.obs-studio.rules 70-snap.canonical-livepatch.rules 
70-snap.postman.rules 70-snap.telegram-desktop.rules 70-snap.snapd.rules 
70-snap.cups.rules 70-snap.gimp.rules 70-snap.discord.rules 
70-snap.firefox.rules
  Date: Thu Mar 21 12:31:06 2024
  InstallationDate: Installed on 2022-01-18 (793 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qa6vun@/vmlinuz-5.19.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_qa6vun ro quiet splash
  SourcePackage: udisks2
  Symptom: storage
  Title: Internal hard disk partition cannot be mounted manually
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (139 days ago)
  dmi.bios.date: 07/22/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X515EA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515EA.303:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515EA_X515EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515EA_X515EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Desktop-packages] [Bug 2058635] [NEW] Internal hard disk partition cannot be mounted manually

[Victor Porton]

Public bug reported:

Upon installing linux-image-6.5.0-26-generic and linux-
modules-6.5.0-26-generic and loading this version of the kernel, I see
initrd.

In initrd there are no /dev/nvme* devices. It leads to Linux being
unable get past initrd stage and load the desktop.

This is my system as it was before installing linux-image-6.5.0-26-generic:
Linux victor 5.19.0-40-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 23 
21:39:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10

$ sudo dmidecode

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: udisks2 2.10.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.skype.rules 70-snap.ipfs-desktop.rules 
70-snap.session-desktop.rules 70-snap.teams-for-linux.rules 
70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.g-assist.rules 
70-snap.snapd-desktop-integration.rules 70-snap.clickup.rules 
70-snap.obs-studio.rules 70-snap.canonical-livepatch.rules 
70-snap.postman.rules 70-snap.telegram-desktop.rules 70-snap.snapd.rules 
70-snap.cups.rules 70-snap.gimp.rules 70-snap.discord.rules 
70-snap.firefox.rules
Date: Thu Mar 21 12:31:06 2024
InstallationDate: Installed on 2022-01-18 (793 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qa6vun@/vmlinuz-5.19.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_qa6vun ro quiet splash
SourcePackage: udisks2
Symptom: storage
Title: Internal hard disk partition cannot be mounted manually
UpgradeStatus: Upgraded to mantic on 2023-11-03 (139 days ago)
dmi.bios.date: 07/22/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: X515EA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X515EA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515EA.303:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515EA_X515EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUSLaptop
dmi.product.name: VivoBook_ASUSLaptop X515EA_X515EA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug mantic

** Attachment added: "dmidecode output"
   https://bugs.launchpad.net/bugs/2058635/+attachment/5757867/+files/y.txt

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

Title:
  Internal hard disk partition cannot be mounted manually

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Upon installing linux-image-6.5.0-26-generic and linux-
  modules-6.5.0-26-generic and loading this version of the kernel, I see
  initrd.

  In initrd there are no /dev/nvme* devices. It leads to Linux being
  unable get past initrd stage and load the desktop.

  This is my system as it was before installing linux-image-6.5.0-26-generic:
  Linux victor 5.19.0-40-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 23 
21:39:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  $ sudo dmidecode

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: udisks2 2.10.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.skype.rules 70-snap.ipfs-desktop.rules 
70-snap.session-desktop.rules 70-snap.teams-for-linux.rules 
70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.g-assist.rules 
70-snap.snapd-desktop-integration.rules 70-snap.clickup.rules 
70-snap.obs-studio.rules 70-snap.canonical-livepatch.rules 
70-snap.postman.rules 70-snap.telegram-desktop.rules 70-snap.snapd.rules 
70-snap.cups.rules 70-snap.gimp.rules 70-snap.discord.rules 
70-snap.firefox.rules
  Date: Thu Mar 21 12:31:06 2024
  InstallationDate: Installed on 2022-01-18 (793 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: 

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Daniel van Vugt]

Thanks. It looks like the nautilus process isn't frozen at all:

https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus%3A6%3A__GI___poll%3Ag_main_context_poll_unlocked%3Ag_main_context_iterate_unlocked%3Ag_main_context_iteration%3Ag_application_run

Which makes sense because a properly frozen process wouldn't respond to
being asked to close. And so I suspect it has found a way to partly
freeze the compositor, maybe.

The only remaining ideas I have are:

 * Try scale 100% to see if it avoids the bug (not for your own sake, but for 
our information).
 * Try disabling fractional scaling briefly, for the same reason.
 * Try a different Nvidia driver version in the 'Additional Drivers' app.
 * Try Wayland.
 * If I get time in the coming weeks I may try to build a system with a similar 
configuration and try it.

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

[Desktop-packages] [Bug 1958019]

[thornley.david]

FYI, this looks to have been improved in Ubuntu's 6.8.1 mainline
(https://kernel.ubuntu.com/mainline/v6.8.1/).

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 2058468] Re: Login animation is missing since GNOME 45

[Daniel van Vugt]

Try this instead: https://github.com/micheleg/dash-to-dock/pull/2166

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

Title:
  Login animation is missing since GNOME 45

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Dock login animation is missing since GNOME 45

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


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

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Teh Kok How]

https://errors.ubuntu.com/user/b0e8093c7497f98ea1d6123f13650b77654510667f8c32cb9b7f39ed46e3c2533bcd265e527269b95a1cc6af2d15e3dc8625bb297ce66b2ecb65680ae6fb9b93

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

[Desktop-packages] [Bug 2058409] Re: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found

[Stefan Staeglich]

This worked at least until 13th of March

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

Title:
  Install of tevlive-full hangs:
  tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not
  found

Status in texlive-base package in Ubuntu:
  New

Bug description:
  Before 3 weeks at least it was possible to install texlive-full
  without any issues. Now this is not possible anymore. So the bug was
  probably introduced with one of the latest updates.

  How to reproduce:
  Install package texlive-full
  $ apt install texlive-full

  Install hangs:
  texlive-lang-japanese (2021.20220204-1) wird eingerichtet ...
  context (2021.03.05.20220211-1) wird eingerichtet ...
  Running mtxrun --generate. This may take some time... done.
  Pregenerating ConTeXt MarkIV format. This may take some time...

  Related running processes:
  root   18747  0.4  0.0  13936  7456 pts/2Ss+  17:47   0:01 
/usr/bin/dpkg --status-fd 43 --configure --pending
  root   20584  0.0  0.0   2892   960 pts/2S+   17:48   0:00 /bin/sh 
/var/lib/dpkg/info/context.postinst configure
  root   20592  0.0  0.0   2892  1064 pts/2S+   17:48   0:00 /bin/sh 
/usr/bin/luatools --make cont-en
  root   20593  0.1  0.9  92868 79952 pts/2S+   17:48   0:00 texlua 
/usr/bin/mtxrun --script base --make cont-en
  root   20596  0.0  0.0   2892  1004 pts/2S+   17:48   0:00 sh -c 
/usr/bin/luatex --ini  
--lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua 
/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv
  root   20597  0.0  0.3  40816 28684 pts/2S+   17:48   0:00 
/usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua 
/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv

  Run luatex manually:
  # /usr/bin/luatex --ini 
--lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua 
/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv
  This is LuaTeX, Version 1.14.0 (TeX Live 2022/dev/Debian)  (INITEX)
   system commands enabled.
  (/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv 
(/usr/share/texmf/tex/context/base/mkiv/context.mkiv 
(/usr/share/texmf/tex/context/base/mkiv/syst-ini.mkiv) 
(/usr/share/texmf/tex/context/base/mkiv/norm-ctx.mkiv) 
(/usr/share/texmf/tex/context/base/mkiv/syst-pln.mkiv) 
(/usr/share/texmf/tex/context/base/mkiv/syst-mes.mkiv) 
(/usr/share/texmf/tex/context/base/mkiv/luat-cod.mkiv<+ 
/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua>) 
(/usr/share/texmf/tex/context/base/mkiv/luat-bas.mkiv loading: ConTeXt Lua 
Macros / Basic Lua Libraries<+ 
/usr/share/texmf/tex/context/base/mkiv/l-bit32.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-lua.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-macro.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-package.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-lpeg.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-function.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-string.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-table.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-boolean.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-number.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-math.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-io.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-os.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-file.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-gzip.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-md5.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-sha.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-dir.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-unicode.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-url.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-set.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/l-macro-imp-optimize.lua>) 
(/usr/share/texmf/tex/context/base/mkiv/luat-lib.mkiv loading: ConTeXt Lua 
Macros / Libraries<+ /usr/share/texmf/tex/context/base/mkiv/util-str.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-tab.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-fil.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-sac.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-sto.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-pck.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-prs.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-fmt.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-dim.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/trac-set.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/luat-log.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/trac-inf.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-lua.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-deb.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-tpl.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-seq.lua><+ 
/usr/share/texmf/tex/context/base/mkiv/util-sta.lua><+ 

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Daniel van Vugt]

No there is no new file attached here. Also be careful not to attach
.crash files to bugs.

Please just tell us the new bug number, or your whoopsie-id.

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

Re: [Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Teh Kok How]

Can't you get it from the file attached?

On Thu, 21 Mar 2024, 17:17 Daniel van Vugt, <2058...@bugs.launchpad.net>
wrote:

> You will need to tell us the new bug number, or the user ID.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2058327
>
> Title:
>   Starting up Files app in external monitor freeze the entire monitor
>
> Status in nautilus package in Ubuntu:
>   New
>
> Bug description:
>   Starting up Files app in external monitor freeze the entire external
> monitor. I have to close the Files app in the primary monitor to get back
> to normalcy.
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.27.0-0ubuntu5
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 23.10
>   GsettingsChanges:
>b'org.gnome.nautilus.preferences' b'default-folder-viewer'
> b"'list-view'"
>b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
>b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
>b'org.gnome.nautilus.window-state' b'maximized' b'true'
>   InstallationDate: Installed on 2021-10-20 (881 days ago)
>   InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: nautilus 1:45~rc-1ubuntu1
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
>   Tags: mantic
>   Uname: Linux 6.5.0-26-generic x86_64
>   UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
>   UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root
> sambashare sudo syslog
>   _MarkForUpload: True
>   usr_lib_nautilus:
>file-roller   43.0-1
>nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
>nautilus-image-converter  0.4.0-2
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2058327/+subscriptions
>
>

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Daniel van Vugt]

You will need to tell us the new bug number, or the user ID.

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Teh Kok How]

Done

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Daniel van Vugt]

Let's analyse why the app is frozen... To do that you will need to kill
it while it's frozen:

  killall -ABRT nautilus

and then a new crash file is created in /var/crash/. Please then use the
ubuntu-bug command to upload the crash file like:

  ubuntu-bug /var/crash/_usr_bin_nautilus.1000.crash

If it doesn't tell you where the crash report went after that then have
a look at https://errors.ubuntu.com/user/ID where ID is the content of
file /var/lib/whoopsie/whoopsie-id on the machine.

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Teh Kok How]

It's on ONE app. I can start it in the primary window and move it to
external monitor.

One important thing to highlight though, sometimes the Files app starts
perfectly without this error, i.e, without this freezing the external
monitor thingy.

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Daniel van Vugt]

Usually because of the version of GTK or Cairo the app uses, based on
that previous bug. Or something else app-specific.

You might be able to select 'Ubuntu on Wayland' on the login screen as a
workaround, and use the same scaling factors as you do now. The only
catch is that may cause different bugs that some people might find more
annoying: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-
wayland

** Tags added: nvidia xrandr-scaling

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

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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

[Desktop-packages] [Bug 2058327] Re: Starting up Files app in external monitor freeze the entire monitor

[Teh Kok How]

Not changing the scale. Why it doesn't happen to other apps but only
Files?


** Attachment added: "xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2058327/+attachment/5757786/+files/xrandr.txt

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

Title:
  Starting up Files app in external monitor freeze the entire monitor

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Starting up Files app in external monitor freeze the entire external monitor. 
I have to close the Files app in the primary monitor to get back to normalcy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1039, 1177)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-10-20 (881 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nautilus 1:45~rc-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Tags: mantic
  Uname: Linux 6.5.0-26-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (136 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare 
sudo syslog
  _MarkForUpload: True
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2

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


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