[Desktop-packages] [Bug 1991494] Re: dark mode sometimes works

2022-10-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  dark mode sometimes works

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  the dark mode sometimes works and sometimes doesn't work. If i open
  Ubuntu Software store dark mode doesn't work and i have to go back to
  turn it back on again then it work's, its like it doesn't went to be
  in dark mode when i open Ubuntu Software store. it doesn't matter that
  must to me i just want you guys to know about it.

  this problem in on Ubuntu 22.10 Kinetic Kudu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  2 20:18:36 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e]
  InstallationDate: Installed on 2022-10-02 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  MachineType: ASUSTeK COMPUTER INC. X541UVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UVK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UVK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: X
  dmi.product.name: X541UVK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112-3ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  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/gnome-shell/+bug/1991494/+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 1987076] Re: Mouse cannot control windows after suspend and display change

2022-10-22 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Mouse cannot control windows after suspend and display change

Status in mutter package in Ubuntu:
  Expired

Bug description:
  My setup is this:

  Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
  Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
  Display: Lenovo T34w-20, connected via USB-C

  The problem started with upgrade to 22.04
  I have had the same exact problem with my previous laptop, a ThinkPad T14s. 
Both of these are AMD laptops, but I had no problem on 21.10.

  Way I can usually reproduce (always?)

  1. Suspend my laptop by yanking out the USB-C cable.
  2. Resume the laptop by connecting a different monitor (same make and model, 
but not the same physical one) and hit the keyboard a few times.

  Note: Resuming on the same physical display does not seem to result in
  the same problem.

  After this, I can no longer control the Windows on my desktop. The
  mouse cursor is active, but moves behind the open windows, and mouse
  click is not registered (at least not in a way that is useful).

  I can navigate the windows and use the applications, using the
  keyboard.

  Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the
  real session, mouse is still "broken".

  Ctrl+Alt+F2 to get to a TTY, and going back to the original session,
  mouse is still "broken".

  Only way I have found to reliably restore functionality is a reboot
  (which I have been doing a lot of the last few months).

  Please let me know what else I can provide you with, in order to get
  this fixed. :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Fri Aug 19 10:32:48 2022
  InstallationDate: Installed on 2022-05-20 (91 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+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 1987209] Re: gnome-shell (Wayland) crashes with SIGSEGV when screen locker activates (jj), immediately after meta_workspace_get_work_area_for_monitor: assertion 'logical_monito

2022-10-22 Thread 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/1987209

Title:
  gnome-shell (Wayland) crashes with SIGSEGV when screen locker
  activates (jj), immediately after
  meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor
  != NULL' failed

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Hi,

  On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a
  problem with the automatic lock screen which doesn't lock my session
  but closes it (and all opened applications in my session are closed
  too of course). In fact, I think the session is not really closed but
  there is some crash of gnome shell (see below).

  Maybe it's important, I have *2* monitors (more convenient for my
  tired eyes):

  * HP 24er (24")
  * ASUS MX279 (27")

  Theses 2 monitors are connected via a HDMI port, each on a dedicated
  card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model
  cards "Radeon Pro WX 3100").

  Here is my setting in "Privacy" > "Screen", to test quickly the
  automatic lock screen:

  ```
  Blank Screen Delay: 1 minute
  Automatic Screen Lock: 
  Automatic Screen Lock Delay: 30 seconds
  Lock Screen on Suspend: 
  Show Notifications on Lock Screen: 
  ```

  Note: I have tested with a fresh and new Unix account, just created
  for the test (by `sudo adduser foo`) and the problem is present too.

  Below, you can see the output of the `journalctl -eb` where:

  1. about ~13:02:50, screens begins to be blank,
  2. about ~13:03:20, the automatic lock screen should start.

  As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault":

  ```
  Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea 
from uid 1000 finished with success after 229ms
  Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd 
from uid 1000 finished with success after 235ms
  Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by 
gnome-shell.
  Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated 
successfully.
  Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Aug 21 13:03:19 flhpz4 gnome-shell[37898]: 
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) 
number < g_list_length (manager->logical_monitors)' failed
  Aug 21 13:03:19 flhpz4 gnome-shell[37898]: 
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' 
failed
  Aug 21 13:03:19 flhpz4 gnome-shell[37898]: 
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) 
number < g_list_length (manager->logical_monitors)' failed
  Aug 21 13:03:19 flhpz4 gnome-shell[37898]: 
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' 
failed
  Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 
ip 55a109404860 sp 7fff85039338 error 15
  Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 
65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 
00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00
  Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property 
match 'XRANDR_name'='DP-3' does not exist
  Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 
processes of 1 users.
  Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of 
process 37752 owned by '1000' RT at priority 5.
  Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 
processes of 1 users.
  Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from 
display: Broken pipe
  Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from 
display: Broken pipe
  Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: 
Broken pipe
  Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from 
display: Broken pipe
  Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from 
display: Broken pipe
  Aug 21 13:03:21 flhpz4 unknown[38050]: Error reading events from display: 
Broken pipe
  Aug 21 13:03:21 flhpz4 terminator[46053]: Error reading events from display: 
Connection reset by peer
  Aug 21 13:03:21 flhpz4 gsd-wacom[38078]: Error reading events from display: 
Broken pipe
  Aug 21 13:03:21 flhpz4 firefox[46499]: Error reading events from display: 
Broken pipe
  Aug 21 13:03:21 flhpz4 systemd[37743]: 
org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, 
status=1/FAILURE
  

[Desktop-packages] [Bug 1987360] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-10-22 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new
  firefox package pre-installation script subprocess returned error exit
  status 1

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Just received a message to report this issues

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Aug 22 20:16:49 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2022-02-06 (197 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  Snap: firefox 103.0.2-1 (stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   70   Error   2022-08-22T20:09:13-04:00  2022-08-22T20:16:49-04:00  Install 
"firefox" snap
   71   Done2022-08-22T20:20:35-04:00  2022-08-22T20:25:48-04:00  Install 
"firefox" snap
  Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new 
firefox package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987360/+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 1993874] Re: Settings and Quick Menu apply Dark style differently

2022-10-22 Thread Batwam
correct, and this issue occurs when the Appearance tab ob th Settings
app is activated (or Settings open with Appearance being the previous
section) so the issue is likely to sit within the init part of the code
of the Appearance tab which seems to be resetting (or do an action which
causing the reset) the theme.

Also, if you open Gnome Tweaks, you will see that when selecting Dark
via the quick menu, the themes are changed to *-dark". if you do the
same thing using Settings, the theme isn't changed at all.

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

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1989508]

2022-10-22 Thread updates
FEDORA-2022-027effed0e has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

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

Title:
  hp-plugin unable to load plugin.conf

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in hplip package in Fedora:
  Fix Released

Bug description:
  Linux hp-plugin fails on Fedora 35 with the error:

  error: Plugin download failed with error code = 8
  error:  file does not match its checksum. File may have been corrupted or 
altered

  When running "hp-plugin -l debug" the reason turns out to be that
  http://hplip.sourceforge.net/plugin.conf does not exist:

  hp-plugin[540794]: debug: wget returned: 0
  hp-plugin[540794]: debug: --2022-09-13 23:23:02--  
http://hplip.sf.net/plugin.conf
  Resolving hplip.sf.net (hplip.sf.net)... 204.68.111.100
  Connecting to hplip.sf.net (hplip.sf.net)|204.68.111.100|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: http://hplip.sourceforge.net/plugin.conf [following]
  --2022-09-13 23:23:02--  http://hplip.sourceforge.net/plugin.conf
  Resolving hplip.sourceforge.net (hplip.sourceforge.net)... 204.68.111.100
  Reusing existing connection to hplip.sf.net:80.
  HTTP request sent, awaiting response... 404 Not Found
  2022-09-13 23:23:02 ERROR 404: Not Found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1989508/+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 1993928] [NEW] Switching to new input method does nothing

2022-10-22 Thread O Gopal
Public bug reported:

I have ibus-m17n installed, but switching to a different input method
does nothing.

STR:
1. Make sure my 2nd input method (in my case, "Sanskrit (sa-IAST (m17n))" 
appears under "Settings-->Keyboard-->Input sources."
2. Use alt-space to switch to my second input method.
3. Notice on the top panel that the indicator shows that the input method has 
changed. 
4. Attempt to key in some special characters (using Gedit, LibreOffice, etc.). 

Expected result: 
The special characters will appear. 

Actual result:
The keyboard behaves as if the input method were my usual "English (US)."

No such problem with 22.04.

Removing and re-adding "Sanskrit (sa-IAST (m17n))" in Settings doesn't
solve the issue.

Hardware: IBM ThinkPad Carbon X-1, 5th generation.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: ibus 1.5.27-2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 23 08:44:46 2022
InstallationDate: Installed on 2017-12-08 (1779 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ibus
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

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


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

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

Title:
  Switching to new input method does nothing

Status in ibus package in Ubuntu:
  New

Bug description:
  I have ibus-m17n installed, but switching to a different input method
  does nothing.

  STR:
  1. Make sure my 2nd input method (in my case, "Sanskrit (sa-IAST (m17n))" 
appears under "Settings-->Keyboard-->Input sources."
  2. Use alt-space to switch to my second input method.
  3. Notice on the top panel that the indicator shows that the input method has 
changed. 
  4. Attempt to key in some special characters (using Gedit, LibreOffice, 
etc.). 

  Expected result: 
  The special characters will appear. 

  Actual result:
  The keyboard behaves as if the input method were my usual "English (US)."

  No such problem with 22.04.

  Removing and re-adding "Sanskrit (sa-IAST (m17n))" in Settings doesn't
  solve the issue.

  Hardware: IBM ThinkPad Carbon X-1, 5th generation.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 23 08:44:46 2022
  InstallationDate: Installed on 2017-12-08 (1779 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ibus
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1993928/+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 1993926] [NEW] No icon in tray and integration in menu when someone is connected

2022-10-22 Thread Jérôme
Public bug reported:

I'm running an up to date Ubuntu 22.04.1 LTS using X.

A friend of mine is having the same hardware and it's fully functional.
Just few extensions but even I I disable everything still no orange icon and no 
integration, got no info.

It's working perfectly, just a tiny bug.

Anything I can provide to help? ... if you can provide commands I can do
it.

OS: Ubuntu 22.04.1 LTS
Kernel: 5.15.0-52-generic
Package: 42.4-0ubuntu1
*** 42.4-0ubuntu1 500
500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 42.0-4ubuntu1 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

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

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

Title:
  No icon in tray and integration in menu when someone is connected

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  I'm running an up to date Ubuntu 22.04.1 LTS using X.

  A friend of mine is having the same hardware and it's fully functional.
  Just few extensions but even I I disable everything still no orange icon and 
no integration, got no info.

  It's working perfectly, just a tiny bug.

  Anything I can provide to help? ... if you can provide commands I can
  do it.

  OS: Ubuntu 22.04.1 LTS
  Kernel: 5.15.0-52-generic
  Package: 42.4-0ubuntu1
  *** 42.4-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-4ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1993926/+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 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor

2022-10-22 Thread Nathan Teodosio
Thanks for the report, Simon, I pushed a fix to Chromium in a feature
branch[1]. As per my tests, it solves the issue. Could you please
confirm it by downloading it and installing it with

  snap install --dangerous ./chromium*.snap

[1]: https://launchpad.net/~nteodosio/+snap/chromium-browser-beta-deny-
metrics/+build/1917882

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor,
  bios_version, board_name and board_vendor

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  When starting chromium's snap, those messages are logged:

  $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F 
snap.chromium.chromium
  audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  Chromium behaves OK but generates log pollution.

  Additional info:

  $ snap list chromium snapd
  Name  Version RevTracking   Publisher   Notes
  chromium  106.0.5249.119  2136   latest/stable  canonical✓  -
  snapd 2.57.4  17336  latest/stable  canonical✓  snapd

  $ uname -rm
  5.15.0-52-generic x86_64

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1993870] Re: WiFi setting has no visible networks

2022-10-22 Thread Changbin Du
** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  WiFi setting has no visible networks

Status in network-manager package in Ubuntu:
  New

Bug description:
  With ubuntu 22.10, I can not see any AP in WiFi setting. It's ok on
  previous versions. The driver is okay since I can scan with iwlist
  tool. Below are more details.

  $ sudo lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.10
  Release:  22.10
  Codename: kinetic

  $ ifconfig
  enx5e80011fa4e9: flags=4163  mtu 1500
  inet 192.168.42.116  netmask 255.255.255.0  broadcast 192.168.42.255
  inet6 fe80::cd60:eccc:f8d7:21e6  prefixlen 64  scopeid 0x20
  ether 5e:80:01:1f:a4:e9  txqueuelen 1000  (Ethernet)
  RX packets 432320  bytes 621981996 (621.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 186680  bytes 22769110 (22.7 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 11354  bytes 24889535 (24.8 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 11354  bytes 24889535 (24.8 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  wlp0s20f3: flags=4099  mtu 1500
  ether 18:1d:ea:ed:34:16  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  $ sudo iwlist wlp0s20f3 scan
  wlp0s20f3  Scan completed :
    Cell 01 - Address: D0:79:80:DA:4F:F3
  Channel:1
  Frequency:2.412 GHz (Channel 1)
  Quality=29/70  Signal level=-81 dBm
  Encryption key:on
  ESSID:"CMCC-7S6H"
  Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s
  Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
  Mode:Master
  Extra:tsf=00e793b8a899
  Extra: Last beacon: 2164ms ago
  IE: Unknown: 0009434D43432D37533648
  IE: Unknown: 010882848B962430486C
  IE: Unknown: 030101
  IE: Unknown: 23021100
  IE: Unknown: 2A0104
  IE: Unknown: 32040C121860
  IE: IEEE 802.11i/WPA2 Version 1
  Group Cipher : CCMP
  Pairwise Ciphers (1) : CCMP
  Authentication Suites (1) : PSK
  IE: Unknown: 0B0539
  IE: Unknown: 7F0804000840
  IE: Unknown: 
DD7E0050F204104A0001101044000102103B000103104700105D2DBCBB9D644948047E083B1A419A72102100094669626572686F6D65102300094669626572686F6D651024000631323334353610420004313233341054000800060050F20400011011000B4669626572686F6D6541501008000220081049000600372A000120
  IE: Unknown: DD0A001018020C01
  IE: WPA Version 1
  Group Cipher : CCMP
  Pairwise Ciphers (1) : CCMP
  Authentication Suites (1) : PSK
  IE: Unknown: 
DD180050F20201018C0003A227A442435E0062322F00
    Cell 02 - Address: FC:DD:65:2B:6B:52
  

  $ sudo dmesg | grep iwl
  [2.816274] iwlwifi :00:14.3: WRT: Overriding region id 0
  [2.816285] iwlwifi :00:14.3: WRT: Overriding region id 1
  [2.816289] iwlwifi :00:14.3: WRT: Overriding region id 2
  [2.816293] iwlwifi :00:14.3: WRT: Overriding region id 3
  [2.816297] iwlwifi :00:14.3: WRT: Overriding region id 4
  [2.816300] iwlwifi :00:14.3: WRT: Overriding region id 6
  [2.816304] iwlwifi :00:14.3: WRT: Overriding region id 8
  [2.816307] iwlwifi :00:14.3: WRT: Overriding region id 9
  [2.816311] iwlwifi :00:14.3: WRT: Overriding region id 10
  [2.816314] iwlwifi :00:14.3: WRT: Overriding region id 11
  [2.816318] iwlwifi :00:14.3: WRT: Overriding region id 15
  [2.816322] iwlwifi :00:14.3: WRT: Overriding region id 16
  [2.816326] iwlwifi :00:14.3: WRT: Overriding region id 18
  [2.816330] iwlwifi :00:14.3: WRT: Overriding region id 19
  [2.816333] iwlwifi :00:14.3: WRT: Overriding region id 20
  [2.816360] iwlwifi :00:14.3: WRT: Overriding region id 21
  [2.816363] 

[Desktop-packages] [Bug 1983181] Re: Cheese Internal data stream error

2022-10-22 Thread Danton Nunes
on my desktop (Ubuntu 22.10), when I run cheese as root, it works, but it does 
not as a regular user.
# lspci | fgrep -i vga
00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD 
Graphics 620] (rev 02)

on my noteboot (Ubuntu 22.04), it works fine.
# lspci | fgrep -i vga
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)

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

Title:
  Cheese Internal data stream error

Status in cheese package in Ubuntu:
  New

Bug description:
  corrado@corrado-n4-kk-0718:~$ cheese

  (cheese:12091): Gdk-WARNING **: 16:18:17.659: Native Windows taller
  than 65535 pixels are not supported

  (cheese:12091): cheese-WARNING **: 16:18:48.168: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: cheese 41.1-2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 30 16:21:11 2022
  InstallationDate: Installed on 2022-07-19 (11 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese41.1-2
   cheese-common 41.1-2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  corrado1757 F wireplumber
   /dev/snd/controlC0:  corrado1757 F wireplumber
   /dev/snd/seq:corrado1754 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-07-19 (11 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=2f8a8007-7685-4a68-85d3-46088d66849c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220711.gitdfa29317-0ubuntu1
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  wayland-session kinetic
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Desktop-packages] [Bug 1993870] [NEW] WiFi setting has no visible networks

2022-10-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

With ubuntu 22.10, I can not see any AP in WiFi setting. It's ok on
previous versions. The driver is okay since I can scan with iwlist tool.
Below are more details.

$ sudo lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.10
Release:22.10
Codename:   kinetic

$ ifconfig
enx5e80011fa4e9: flags=4163  mtu 1500
inet 192.168.42.116  netmask 255.255.255.0  broadcast 192.168.42.255
inet6 fe80::cd60:eccc:f8d7:21e6  prefixlen 64  scopeid 0x20
ether 5e:80:01:1f:a4:e9  txqueuelen 1000  (Ethernet)
RX packets 432320  bytes 621981996 (621.9 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 186680  bytes 22769110 (22.7 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 11354  bytes 24889535 (24.8 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 11354  bytes 24889535 (24.8 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s20f3: flags=4099  mtu 1500
ether 18:1d:ea:ed:34:16  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ sudo iwlist wlp0s20f3 scan
wlp0s20f3  Scan completed :
  Cell 01 - Address: D0:79:80:DA:4F:F3
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=29/70  Signal level=-81 dBm
Encryption key:on
ESSID:"CMCC-7S6H"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
  24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00e793b8a899
Extra: Last beacon: 2164ms ago
IE: Unknown: 0009434D43432D37533648
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 23021100
IE: Unknown: 2A0104
IE: Unknown: 32040C121860
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 0B0539
IE: Unknown: 7F0804000840
IE: Unknown: 
DD7E0050F204104A0001101044000102103B000103104700105D2DBCBB9D644948047E083B1A419A72102100094669626572686F6D65102300094669626572686F6D651024000631323334353610420004313233341054000800060050F20400011011000B4669626572686F6D6541501008000220081049000600372A000120
IE: Unknown: DD0A001018020C01
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 
DD180050F20201018C0003A227A442435E0062322F00
  Cell 02 - Address: FC:DD:65:2B:6B:52


$ sudo dmesg | grep iwl
[2.816274] iwlwifi :00:14.3: WRT: Overriding region id 0
[2.816285] iwlwifi :00:14.3: WRT: Overriding region id 1
[2.816289] iwlwifi :00:14.3: WRT: Overriding region id 2
[2.816293] iwlwifi :00:14.3: WRT: Overriding region id 3
[2.816297] iwlwifi :00:14.3: WRT: Overriding region id 4
[2.816300] iwlwifi :00:14.3: WRT: Overriding region id 6
[2.816304] iwlwifi :00:14.3: WRT: Overriding region id 8
[2.816307] iwlwifi :00:14.3: WRT: Overriding region id 9
[2.816311] iwlwifi :00:14.3: WRT: Overriding region id 10
[2.816314] iwlwifi :00:14.3: WRT: Overriding region id 11
[2.816318] iwlwifi :00:14.3: WRT: Overriding region id 15
[2.816322] iwlwifi :00:14.3: WRT: Overriding region id 16
[2.816326] iwlwifi :00:14.3: WRT: Overriding region id 18
[2.816330] iwlwifi :00:14.3: WRT: Overriding region id 19
[2.816333] iwlwifi :00:14.3: WRT: Overriding region id 20
[2.816360] iwlwifi :00:14.3: WRT: Overriding region id 21
[2.816363] iwlwifi :00:14.3: WRT: Overriding region id 28
[2.818423] iwlwifi :00:14.3: loaded firmware version 46.9d0122c0.0 
9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
[3.451691] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, 
REV=0x312
[3.514636] iwlwifi :00:14.3: base HW address: 18:1d:ea:ed:34:16, OTP 
minor version: 0x4
[3.584372] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[3.594287] iwlwifi :00:14.3 wlp0s20f3: 

[Desktop-packages] [Bug 1943752] Re: cheese does not work in Ubuntu 21.10+

2022-10-22 Thread warren
Workaround: Install Webcamoid then laptop webcam works on HP 840 G3 Elitebook. 
Remove Cheese because of non-working status with this laptop.
Tested with Ubuntu 22.10 from live-usb.

** Summary changed:

- cheese does not display image when first opened in Ubuntu 21.10
+ cheese does not work in Ubuntu 21.10+

** Summary changed:

- cheese does not work in Ubuntu 21.10+
+ cheese does not work with laptop webcam in Ubuntu 21.10+

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

Title:
  cheese does not work with laptop webcam in Ubuntu 21.10+

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 from live usb on a HP 840 G3 laptop
  1.Ubuntu Impish Indri (development branch)
  2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4
  version table:***3.38.0-4 500
  3.cheese should display an image from laptop camera after being opened.
  4.The error has reproduced by me on this hardware at least 4 times.
  When opening the cheese app no image is displayed until closing and reopening 
the app at least 3 times. The cheese app works as expected in both Ubuntu 18.04 
and Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-4
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 15 17:10:23 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-4
   cheese-common 3.38.0-4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: 2FZ00UP#ABA
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 5074 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-14-generic N/A
   linux-backports-modules-5.13.0-14-generic  N/A
   linux-firmware 1.199
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  impish
  Uname: Linux 5.13.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 

[Desktop-packages] [Bug 1801317] Re: Can't move/snap Nautilus window to occupy left or right half of the 1366x768 screen

2022-10-22 Thread Duke
I just upgraded from Ubuntu 20.04 LTS to 22.04.1 LTS. In 20.04 LTS this
worked as expected, but no longer in 22.04.1 LTS. My screen resolution
is 1366 x 768 (16:9). It does work when I disable or auto-hide the dock,
but this is more of a workaround than a solution in my opinion.

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

Title:
  Can't move/snap Nautilus window to occupy left or right half of the
  1366x768 screen

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 LTS with GNOME Shell.
  Nautilus does not want to occupy 50% (left or right) of the screen sized at 
1366x768.

  See screencast - https://i.stack.imgur.com/ainWP.gif .

  Other applications (such as GNOME Terminal, Eye of GNOME, Gedit) are
  normally snapping to the left/right half of the screen.

  But Nautilus can be resized to the width lower than half of screen (I
  can get 650 px, which is smaller than 1366/2 = 683 px).

  The first usable screen resolution seems to be 1400x1050, then goes
  1440x900. But large amount of [current
  devices](http://gs.statcounter.com/screen-resolution-
  stats/desktop/worldwide/#monthly-201709-201809-bar) are still using
  1366x768.

  
  Notes: 
  1. first seen on AskUbuntu ( https://askubuntu.com/q/1088630/66509 )
  2. disabling SideBar helps (by  or `gsettings set 
org.gnome.nautilus.window-state start-with-sidebar false` ), but it is hack and 
loss of usubility.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 12:21:05 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x549+268+38'"
  InstallationDate: Installed on 2018-04-28 (187 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1801317/+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 1993920] [NEW] Some windows overflow to other monitors whenever they're near to border and wider than main screen

2022-10-22 Thread Diogo Domanski de Souza
Public bug reported:

After upgrading to Ubuntu 22.10, some applications (for example, VSCode
and MySQL Workbench) are presenting weird behavior: if I move it to the
secondary monitor and maximize the window, it gets mirrored in the main
monitor.

I've made some tests and realized that this issue occurs if I place the
application window near to the divisor between the two monitors and this
window's width is greater than the main monitor's one.

Here is a link to a video that shows this issue:
https://youtu.be/FmYSgpwS6Bk

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 18:19:27 2022
DistUpgraded: 2022-10-20 20:40:37,319 DEBUG icon theme changed, re-reading
DistroCodename: kinetic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
 virtualbox/6.1.38, 5.19.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 
[VGA controller])
   Subsystem: Samsung Electronics Co Ltd Comet Lake UHD Graphics [144d:c834]
InstallationDate: Installed on 2022-10-15 (7 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic 
root=UUID=46adeab8-b7f5-472d-b479-38b045a695ff ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago)
dmi.bios.date: 02/23/2022
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P12RFH.054.220223.HC
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP550XCJ-KF1BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLA664A0C-C01-G002-S0001+10.0.19041
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP12RFH.054.220223.HC:bd02/23/2022:br5.16:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XCJ/550XCR:pvrP12RFH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XCJ-KF1BR:rvrSGLA664A0C-C01-G002-S0001+10.0.19041:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRFH:
dmi.product.family: Notebook 5 Series
dmi.product.name: 550XCJ/550XCR
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRFH
dmi.product.version: P12RFH
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
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

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


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

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

Title:
  Some windows overflow to other monitors whenever they're near to
  border and wider than main screen

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 22.10, some applications (for example,
  VSCode and MySQL Workbench) are presenting weird behavior: if I move
  it to the secondary monitor and maximize the window, it gets mirrored
  in the main monitor.

  I've made some tests and realized that this issue occurs if I place
  the application window near to the divisor between the two monitors
  and this window's width is greater than the main monitor's one.

  Here is a link to a video that shows this issue:
  https://youtu.be/FmYSgpwS6Bk

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 18:19:27 2022
  DistUpgraded: 2022-10-20 20:40:37,319 DEBUG icon theme changed, re-reading
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-21-generic, x86_64: installed
  

[Desktop-packages] [Bug 1993867] Re: Telegram sometimes start endless use 100% CPU

2022-10-22 Thread vodopad27
Added also libvpx to related package. Probably related with libvpx
package.I am not sure.

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

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

Title:
  Telegram sometimes start endless use 100% CPU

Status in libvpx package in Ubuntu:
  New
Status in telegram-desktop package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04 all was fine.

  After upgrade to Ubuntu 22.10 Telegram was also updated. And
  sometimes, randomly, TG starts to use 100% CPU.

  Nothing on logs. But in starce i see a lot of these messages:
  [pid 33581] poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, 
events=POLLIN}, {fd=14, events=POLLIN}, {fd=19, events=POLLIN}, {fd=51, 
events=POLLIN}], 6, 8) = 0 (Timeout)

  
  PSA. Thousand messages.

  In normal state, when TG use 0-2% CPU, i see same messages. So, not
  related with bug.

  Please, ask me additional information, i can provide any logs.

  Today this bug occurs two times.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: telegram-desktop 4.1.1+ds-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 01:53:36 2022
  InstallationDate: Installed on 2018-05-02 (1633 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: telegram-desktop
  UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1993867/+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 1969315] Re: text in torrent info tabs change after opening it to gibberish

2022-10-22 Thread Ian
Here, this issue comes and goes. It felt like having a brutal prune of
how many ISOs etc I was seeding got rid of it, but it's back again.

I did the grep above to see the messages in syslog.. ah, that's quite a
lot, isn't it? How many lines?

user@pc:~$ grep 'transmission' -c /var/log/syslog
5399493

!!! Ah, that's why syslog is so large... and that's just the number of
transmission-gtk messages in the past week.

Most are errors, repeated multiple times a second. Here's the output of
the grep piped into tail:

Oct 22 20:28:25 pc transmission-gt[22015]: gtk_spin_button_set_value: assertion 
'GTK_IS_SPIN_BUTTON (spin_button)' failed
Oct 22 20:28:25 pc transmission-gt[22015]: instance with invalid (NULL) class 
pointer
Oct 22 20:28:25 pc transmission-gt[22015]: g_signal_handler_unblock: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
Oct 22 20:28:25 pc transmission-gt[22015]: invalid unclassed pointer in cast to 
'GtkSpinButton'
Oct 22 20:28:25 pc transmission-gt[22015]: gtk_spin_button_get_value_as_int: 
assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed
Oct 22 20:28:25 pc transmission-gt[22015]: instance with invalid (NULL) class 
pointer
Oct 22 20:28:25 pc transmission-gt[22015]: g_signal_handler_block: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
Oct 22 20:28:25 pc transmission-gt[22015]: gtk_spin_button_set_value: assertion 
'GTK_IS_SPIN_BUTTON (spin_button)' failed
Oct 22 20:28:25 pc transmission-gt[22015]: instance with invalid (NULL) class 
pointer
Oct 22 20:28:25 pc transmission-gt[22015]: g_signal_handler_unblock: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed

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

Title:
  text in torrent info tabs change after opening it to gibberish

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  on transmission-gtk

  after opening the torrent's properties panel, the text at first it's showing 
ok, buy on mouse hover it changes to random text
  worked fine on 21.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 19:28:03 2022
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+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 1993912] [NEW] GNOME screen recorder drops vast majority of frames

2022-10-22 Thread Matthew D. Mower
Public bug reported:

I was trying to screen record for a different bug report, but I can't
seem to screen record properly and so find myself here reporting this
bug. When I try to record a region on my screen, after about 4 seconds
the frames stop updating. In the attached video, I am toggling between
the two visible windows every half second, roughly. The only frame
updates after 0:04 occur at 0:33, 1:07, and 1:40.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 12:13:30 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-05-01 (174 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screencast from 10-22-2022 12:09:45 PM.webm"
   
https://bugs.launchpad.net/bugs/1993912/+attachment/5626020/+files/Screencast%20from%2010-22-2022%2012%3A09%3A45%20PM.webm

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

Title:
  GNOME screen recorder drops vast majority of frames

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was trying to screen record for a different bug report, but I can't
  seem to screen record properly and so find myself here reporting this
  bug. When I try to record a region on my screen, after about 4 seconds
  the frames stop updating. In the attached video, I am toggling between
  the two visible windows every half second, roughly. The only frame
  updates after 0:04 occur at 0:33, 1:07, and 1:40.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 12:13:30 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-01 (174 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912/+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 1993907] [NEW] nautilus freezes randomly

2022-10-22 Thread enorrmann
Public bug reported:

nautilus becomes unresponsive and "files" is not responding sign appears
at random

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
Uname: Linux 5.19.0-1007-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 15:39:58 2022
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2022-05-13 (161 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: nautilus
UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
 python3-nautilus  4.0-1

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


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

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

Title:
  nautilus freezes randomly

Status in nautilus package in Ubuntu:
  New

Bug description:
  nautilus becomes unresponsive and "files" is not responding sign
  appears at random

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 15:39:58 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-05-13 (161 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993907/+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 1993904] Re: key binding to launch gnome-control-center doesn't work

2022-10-22 Thread Marius Gedminas
This was fixed upstream in version 42.beta:
https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/commit/371a1260630035724e20972ae5bda7098e2928a7

Ubuntu explicitly reverts that in debian/patches/ubuntu/Revert-media-
keys-fix-gnome-settings-desktop-file.patch with the rationale

> Ubuntu isn't getting the rename until gnome-control-center 42

Well, 22.10 now has gnome-control-center 43 with the .desktop file
rename, so this patch ought to be dropped.

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

Title:
  key binding to launch gnome-control-center doesn't work

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

Bug description:
  There's a default keybinding of XF86Tools to launch gnome-control-
  center.  On my ThinkPad X390's keyboard it is Fn-F9.  This keybinding
  no longer works in Ubuntu 22.10.  Instead I see this error in my
  journal:

  spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find
  application 'gnome-control-center.desktop' or '(null)'

  AFACT gnome-control-center 43 renamed the .desktop file to
  /usr/share/applications/org.gnome.Settings.desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-settings-daemon 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 20:29:29 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (1227 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1993904/+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 1993904] [NEW] key binding to launch gnome-control-center doesn't work

2022-10-22 Thread Marius Gedminas
Public bug reported:

There's a default keybinding of XF86Tools to launch gnome-control-
center.  On my ThinkPad X390's keyboard it is Fn-F9.  This keybinding no
longer works in Ubuntu 22.10.  Instead I see this error in my journal:

spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find
application 'gnome-control-center.desktop' or '(null)'

AFACT gnome-control-center 43 renamed the .desktop file to
/usr/share/applications/org.gnome.Settings.desktop

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-settings-daemon 43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 20:29:29 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1227 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

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


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

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

Title:
  key binding to launch gnome-control-center doesn't work

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

Bug description:
  There's a default keybinding of XF86Tools to launch gnome-control-
  center.  On my ThinkPad X390's keyboard it is Fn-F9.  This keybinding
  no longer works in Ubuntu 22.10.  Instead I see this error in my
  journal:

  spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find
  application 'gnome-control-center.desktop' or '(null)'

  AFACT gnome-control-center 43 renamed the .desktop file to
  /usr/share/applications/org.gnome.Settings.desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-settings-daemon 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 20:29:29 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (1227 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1993904/+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 1993902] [NEW] package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2022-10-22 Thread Md Najibul Islam
Public bug reported:

i cant not install wine in my ubuntu

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Oct 22 22:51:38 2022
DuplicateSignature:
 package:libgdk-pixbuf-2.0-0:i386:2.42.8+dfsg-1ubuntu0.1
 Setting up libopenal-data (1:1.19.1-2build3) ...
 dpkg: error processing package libgdk-pixbuf-2.0-0:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2022-10-21 (1 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: gdk-pixbuf
Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 jammy need-duplicate-check

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

Title:
  package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  i cant not install wine in my ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 22 22:51:38 2022
  DuplicateSignature:
   package:libgdk-pixbuf-2.0-0:i386:2.42.8+dfsg-1ubuntu0.1
   Setting up libopenal-data (1:1.19.1-2build3) ...
   dpkg: error processing package libgdk-pixbuf-2.0-0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2022-10-21 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993902/+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 1993900] Re: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse

2022-10-22 Thread Fedon Kadifeli
** Description changed:

  As far as I remember, this problem was not present in the previous
  versions of Ubuntu (Xorg):
  
  After selecting "Switch input sources individually for each window" at
  the "GNOME Settings" / "Keyboard / Input source switching" section, the
  keyboard layout can be changed for each window using the keyboard
  shortcut (Windows Key+Space), however when the selection is attempted
  using the mouse, nothing is changed and the current layout stays as is.
+ 
+ The problem is that I can use the keyboard shortcut on a local machine;
+ however, I have to use the mouse for a remote desktop, since the key
+ combination is captured by the local machine in this case.
  
  Wayland seems to work OK in this respect.
  
  Ref: https://askubuntu.com/questions/1436720/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Oct 22 19:02:15 2022
  InstallationDate: Installed on 2019-03-08 (1324 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (176 days ago)

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

Title:
  "Switch input sources individually for each window" does not work when
  a keyboard layout is selected using the mouse

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

Bug description:
  As far as I remember, this problem was not present in the previous
  versions of Ubuntu (Xorg):

  After selecting "Switch input sources individually for each window" at
  the "GNOME Settings" / "Keyboard / Input source switching" section,
  the keyboard layout can be changed for each window using the keyboard
  shortcut (Windows Key+Space), however when the selection is attempted
  using the mouse, nothing is changed and the current layout stays as
  is.

  The problem is that I can use the keyboard shortcut on a local
  machine; however, I have to use the mouse for a remote desktop, since
  the key combination is captured by the local machine in this case.

  Wayland seems to work OK in this respect.

  Ref: https://askubuntu.com/questions/1436720/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Oct 22 19:02:15 2022
  InstallationDate: Installed on 2019-03-08 (1324 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (176 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993900/+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 1993879] Re: "Settings" key fails to launch "Settings."

2022-10-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  "Settings" key fails to launch "Settings."

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

Bug description:
  Pressing the "settings" key fails to launch "Settings."

  STR:
  1. Press the "Settings" key (the key physically shared with F9).
  2. Nothing happens. 

  Expected result:
  The "Settings" app should appear (the same one accessed by the gear icon in 
"Quick Settings").

  Actual result: 
  Nothing happens. 

  The key worked fine in 22.04. 
  Pressing the gear icon in "Quick Settings" does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 11:55:00 2022
  InstallationDate: Installed on 2017-12-08 (1778 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993879/+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 1993892] Re: Window area is unusable

2022-10-22 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Window area is unusable

Status in xorg package in Ubuntu:
  New

Bug description:
  The window area becomes unusable without warning and the same visual
  artefacts are seen (see attached). The system taskbar is still
  responsive, so I can logout/login, which resolves the issues
  temporarily.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 16:10:38 2022
  DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081]
  InstallationDate: Installed on 2022-10-14 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Intel(R) Client Systems NUC10i5FNH
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)
  dmi.bios.date: 04/09/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0052.2021.0409.1144
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i5FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M38063-307
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.9
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN:
  dmi.product.family: FN
  dmi.product.name: NUC10i5FNH
  dmi.product.sku: BXNUC10i5FNHN
  dmi.product.version: M38014-308
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  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/xorg/+bug/1993892/+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 1993900] [NEW] "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse

2022-10-22 Thread Fedon Kadifeli
Public bug reported:

As far as I remember, this problem was not present in the previous
versions of Ubuntu (Xorg):

After selecting "Switch input sources individually for each window" at
the "GNOME Settings" / "Keyboard / Input source switching" section, the
keyboard layout can be changed for each window using the keyboard
shortcut (Windows Key+Space), however when the selection is attempted
using the mouse, nothing is changed and the current layout stays as is.

Wayland seems to work OK in this respect.

Ref: https://askubuntu.com/questions/1436720/

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Oct 22 19:02:15 2022
InstallationDate: Installed on 2019-03-08 (1324 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to jammy on 2022-04-29 (176 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  "Switch input sources individually for each window" does not work when
  a keyboard layout is selected using the mouse

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

Bug description:
  As far as I remember, this problem was not present in the previous
  versions of Ubuntu (Xorg):

  After selecting "Switch input sources individually for each window" at
  the "GNOME Settings" / "Keyboard / Input source switching" section,
  the keyboard layout can be changed for each window using the keyboard
  shortcut (Windows Key+Space), however when the selection is attempted
  using the mouse, nothing is changed and the current layout stays as
  is.

  Wayland seems to work OK in this respect.

  Ref: https://askubuntu.com/questions/1436720/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Oct 22 19:02:15 2022
  InstallationDate: Installed on 2019-03-08 (1324 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (176 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993900/+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 1993892] [NEW] Window area is unusable

2022-10-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The window area becomes unusable without warning and the same visual
artefacts are seen (see attached). The system taskbar is still
responsive, so I can logout/login, which resolves the issues
temporarily.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 16:10:38 2022
DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 
00 [VGA controller])
   Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081]
InstallationDate: Installed on 2022-10-14 (7 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Intel(R) Client Systems NUC10i5FNH
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)
dmi.bios.date: 04/09/2021
dmi.bios.release: 5.16
dmi.bios.vendor: Intel Corp.
dmi.bios.version: FNCML357.0052.2021.0409.1144
dmi.board.asset.tag: Default string
dmi.board.name: NUC10i5FNB
dmi.board.vendor: Intel Corporation
dmi.board.version: M38063-307
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.9
dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN:
dmi.product.family: FN
dmi.product.name: NUC10i5FNH
dmi.product.sku: BXNUC10i5FNHN
dmi.product.version: M38014-308
dmi.sys.vendor: Intel(R) Client Systems
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
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

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


** Tags: amd64 apport-bug corruption kinetic third-party-packages ubuntu 
wayland-session
-- 
Window area is unusable
https://bugs.launchpad.net/bugs/1993892
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
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 1993874] Re: Settings and Quick Menu apply Dark style differently

2022-10-22 Thread ABDELOUAHAB
There is a problem when changing the dark mode from the settings, the
top bar returns to the light mode

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

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1646665] Re: System becomes unstable on resume

2022-10-22 Thread Paul White
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Reporter says in comment #5 that issue has been fixed.
Sorry Mike, for not acknowledging your comment until now.
I'm closing this now as being fixed as there have been no further comments
for over five years now.

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

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

Title:
  System becomes unstable on resume

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  After I come back from suspend the system looks fine, then once
  launching the Unity dash the system becomes unstable. The graphics
  start to render incorrectly and eventually the system will crash.

  Once this problem starts it can be stopped by switching to TTY1 and
  back to 7. I experience many of the following errors in dmesg every
  second until I swap TTY.

  [   58.425802] NVRM: Xid (PCI::01:00): 56, CMDre 0001 00c0
  000100b2 0007 

  The machine has been tested with Ubuntu 16.04 and .10, running all of
  the nvidia 367, 370, and 375 drivers.

  SPEC:
  i7 6700 Skylake Processor
  nVidia 1060 Graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec  2 01:53:30 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-367, 367.57, 4.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:6a04]
  InstallationDate: Installed on 2016-12-02 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID 046d:c521 Logitech, Inc. Cordless Mouse Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65xRP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=289b4b8b-3286-44d0-8713-84abcf69afc4 ro quiet splash i8042.reset 
i8042.nomux vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.07
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.07:bd10/21/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Dec  2 01:51:08 2016
  xserver.configfile: default
  xserver.errors: evdev: Chicony USB 2.0 Camera: Unable to open evdev device 

[Desktop-packages] [Bug 1470980] Re: lightdm does not start in kvm with qxl graphics

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  lightdm does not start in kvm with qxl graphics

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  To do install a lubuntu installation in a kvm vm with qxl graphics.
  Then lightdm will not start after restarting the installation. Lightdm
  will not start.

  lightdm:
Installed: 1.15.0-0ubuntu1
Candidate: 1.15.0-0ubuntu1
Version table:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  I expected lightdm to start to a graphcial login screen. Instead
  lightdm did not start with qxl graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.15.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic i686
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  Date: Thu Jul  2 11:50:17 2015
  InstallationDate: Installed on 2015-07-02 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150702)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1470980/+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 1817666] Re: [nouveau] system hangs

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Invalid' as the reporter did not
respond to comment #2 after almost four years. If this bug report is
still relevant when using a currently maintained release of Ubuntu then
please feel free to tell us in which (current) release of Ubuntu is
affected.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  [nouveau] system hangs

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  i dont know

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-79.100~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Feb 26 12:19:26 2019
  DistUpgraded: 2016-11-14 14:16:19,712 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
  InstallationDate: Installed on 2016-11-12 (835 days ago)
  InstallationMedia: Edubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803.1)
  MachineType: LENOVO 20157
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic 
root=UUID=3006e45f-5f40-45c8-a376-3b9473cb4f8b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2016-11-14 (833 days ago)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 62CN44WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake 2
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr62CN44WW:bd02/01/2013:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: 20157
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Feb 26 09:04:52 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16978 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1817666/+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 1014475] Re: multiple logged in users causes X to be blank coming back from suspend

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Tags added: precise

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  multiple logged in users causes X to be blank coming back from suspend

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  With multiple people logged into my computer, when I come back from
  suspend I'm faced with a blank screen. There is a mouse present, and
  it moves... but I can't log in.

  I can go to a terminal (Ctrl Alt F1), log in, use ps to find the
  process id of X, use kill  on it, and I'm able to use Ctrl Alt F7 to
  get back. Ta Da, I can log in as normal. I don't know if it's X, or if
  killing X resets whatever is causing the problem. Sorry.

  This doesn't appear to happen until I've had more than one user logged
  in.

  I'm on Ubuntu 12.04.

  Tony

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1014475/+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 1376870] Re: Cannot access memory at address 0x7fff610d2ff8

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Invalid' as it's not seen any
activity in over eight years and there has been many changes in Ubuntu
since that time.

Should you experience similar crashes in the future then please follow
the correct procedure which is documented at
https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash


** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Cannot access memory at address 0x7fff610d2ff8

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Get this crash every day i start this machine.

  Bug Report is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1376870/+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 1699965] Re: java.lang.RuntimeException: cannot load system cursor: CopyDrop.32x32

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  java.lang.RuntimeException: cannot load system cursor: CopyDrop.32x32

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  User cache dir: /root/.gli/cache/
   Failed to successfully restart the GS3 server.
  AutoLoadConverters: PDFBox Extension to Greenstone detected for PDFPlugin
  java.lang.RuntimeException: cannot load system cursor: CopyDrop.32x32
  at sun.awt.X11.XToolkit.lazilyLoadDesktopProperty(XToolkit.java:1437)
  at java.awt.Toolkit.getDesktopProperty(Toolkit.java:1822)
  at java.awt.dnd.DragSource.load(DragSource.java:131)
  at java.awt.dnd.DragSource.(DragSource.java:147)
  at org.greenstone.gatherer.gui.tree.DragTree.init(DragTree.java:86)
  at org.greenstone.gatherer.gui.tree.DragTree.(DragTree.java:78)
  at 
org.greenstone.gatherer.file.WorkspaceTree.(WorkspaceTree.java:55)
  at org.greenstone.gatherer.gui.GatherPane.display(GatherPane.java:219)
  at org.greenstone.gatherer.gui.GUIManager.display(GUIManager.java:401)
  at org.greenstone.gatherer.Gatherer.openGUI(Gatherer.java:663)
  at org.greenstone.gatherer.GathererProg.main(GathererProg.java:81)
  Caused by: java.awt.AWTException: Exception: class 
java.lang.IllegalArgumentException Width (0) and height (0) must be non-zero 
occurred while creating cursor CopyDrop.32x32
  at java.awt.Cursor.getSystemCustomCursor(Cursor.java:362)
  at sun.awt.X11.XToolkit.lazilyLoadDesktopProperty(XToolkit.java:1435)
  ... 10 more
  Exception in thread "main" java.lang.ExceptionInInitializerError
  at org.greenstone.gatherer.gui.tree.DragTree.init(DragTree.java:86)
  at org.greenstone.gatherer.gui.tree.DragTree.(DragTree.java:78)
  at 
org.greenstone.gatherer.file.WorkspaceTree.(WorkspaceTree.java:55)
  at org.greenstone.gatherer.gui.GatherPane.display(GatherPane.java:219)
  at org.greenstone.gatherer.gui.GUIManager.display(GUIManager.java:401)
  at org.greenstone.gatherer.Gatherer.openGUI(Gatherer.java:663)
  at org.greenstone.gatherer.GathererProg.main(GathererProg.java:81)
  Caused by: java.lang.RuntimeException: failed to load system cursor: 
DnD.Cursor.CopyDrop : cannot load system cursor: CopyDrop.32x32
  at java.awt.dnd.DragSource.load(DragSource.java:135)
  at java.awt.dnd.DragSource.(DragSource.java:147)
  ... 7 more

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1699965/+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 666094] Re: package xserver-xorg-core 2:1.6.4-2ubuntu4.3 failed to install/upgrade:

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

12 years have passed since this issue was raised and there have been
many changes in Ubuntu since that time. I'm closing this as 'Invalid'.
Please raise a new bug report should you experience a similar issue so
that you current hardware and software configurations can be captured.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  package xserver-xorg-core 2:1.6.4-2ubuntu4.3 failed to
  install/upgrade:

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Upgrade process requested up send in information.

  ProblemType: Package
  Architecture: amd64
  Date: Mon Oct 25 11:42:10 2010
  DistroRelease: Ubuntu 10.04
  DkmsStatus: nvidia, 185.18.36, 2.6.31-22-server, x86_64: installed  (WARNING! 
Diff between built and installed module!)
  ErrorMessage:
   ErrorMessage: unable to create 
`/usr/lib/nvidia/libglx.so.xserver-xorg-core.dpkg-new' (while processing 
`./usr/lib/xorg/modules/extensions/libglx.so'): No such file or directory
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: xserver-xorg-core 2:1.6.4-2ubuntu4.3
  ProcCmdLine: root=UUID=3a5a082d-601f-4d59-ba73-e44e07749ab7 ro quiet splash
  ProcVersionSignature: Ubuntu 2.6.31-22.65-server
  SourcePackage: xorg-server
  Tags:  lucid
  Title: package xserver-xorg-core 2:1.6.4-2ubuntu4.3 failed to install/upgrade:
  Uname: Linux 2.6.31-22-server x86_64
  XsessionErrors:
   (gnome-settings-daemon:2048): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2048): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (nautilus:2131): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (polkit-gnome-authentication-agent-1:2160): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
  dmi.bios.date: 05/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   x86_64
   kernel: 2.6.31-22-server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/666094/+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 1382956] Re: cannot change hdmi monitor resolution anymore

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  cannot change hdmi monitor resolution anymore

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  since a few weeks cannot set resolution to 1360 x 768 anymore...didnt
  change anything...just updates..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Oct 19 12:38:27 2014
  InstallationDate: Installed on 2014-06-09 (131 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  LightdmConfig:
   [SeatDefaults]
   autologin-user=rolf
   autologin-user-timeout=0
   user-session=Lubuntu
   greeter-session=lightdm-gtk-greeter
  LightdmGreeterLog: ** (lightdm-gtk-greeter:30754): WARNING **: Failed to load 
user image: Failed to open file '/home/rolf/.face': No such file or directory
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1225): WARNING **: Failed to 
load user image: Failed to open file '/home/rolf/.face': No such file or 
directory
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1382956/+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 1268215] Re: 1002:9498 [Asus M4A77TD PRO] No screen after upgrade to Trusty

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this issue has any relevance when using a
currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Incomplete

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  1002:9498 [Asus M4A77TD PRO] No screen after upgrade to Trusty

Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Today I updated my desktop to test if a bug is still present in trusty and... 
It went very bad... AFter upgrade, I have no screen anymore (really not : none 
of my screens detect anything and continue searching on every possible source). 
My configuration is :
     - Graphic card : 01:00.0 VGA compatible controller: Advanced Micro 
Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650]
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV730 PRO [Radeon HD 4650]
     - Two screens connected : my computer screen on DVI, and an HD projector 
on HDMI
     - I was on latestest saucy then updated to Trusty.
     - The xord version after upgrade : 1:7.7+1ubuntu7

  I managed to start with failsafeX to report this bug, but in two
  times.

  I include in the bug report the xorg logs and syslogs

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.209
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.12.7-0ubuntu6
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Sat Jan 11 23:03:44 2014
  InstallationDate: Installed on 2013-08-05 (159 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130225)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashDB: ubuntu
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroRelease: Ubuntu 13.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.16, 3.11.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650] 
[1002:9498] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:0300]
  InstallationDate: Installed on 2014-01-12 (15 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=a5013f11-9304-4f8e-9a29-99697308d52f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Tags:  saucy dist-upgrade saucy ubuntu compiz-0.9
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77TD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77TDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 

[Desktop-packages] [Bug 1411375] Re: Xorg does not terminate at computer shutdown

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg does not terminate at computer shutdown

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Whenever I reboot the system, it seems to hang for a long time towards
  the end of the shutdown. I found out it's because of the
  /etc/init.d/sendsigs script's do_stop() function where it waits up to
  5 minutes for $(upstart_killed_jobs) to report that all the jobs have
  been killed.

  When the server comes back up there's a dialog box prompting me to
  report a bug that was detected. The bug "summary" above was filled in
  automatically. I'm a bit surprised to find out that it's Xorg that's
  preventing the shutdown, since I see X exit and the shutdown sequence
  displayed on a terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.125  Mon Dec  1 19:58:28 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  Date: Tue Jan 13 22:32:50 2015
  DistUpgraded: 2014-12-25 15:05:48,543 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0605] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:c981]
  InstallationDate: Installed on 2010-07-15 (1645 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MachineType: Gigabyte Technology Co., Ltd. GA-890FXA-UD5
  OmitPids: 16340 1775 16464 1810 1715 10716 1689 16485 1816 813 1719 2839 1587 
1775 16464 1810 1715 10716 1689 16485 1816 813 1719 2839 1587
  ProcCmdline: /usr/bin/X :2 -background none -verbose -auth 
/var/run/gdm/auth-for-gdm-SmYspb/database -seat seat0 -nolisten tcp
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=26ded80d-11df-4efd-80cb-57e0919395fd ro acpi=force
  SourcePackage: xorg-server
  Title: Xorg does not terminate at computer shutdown
  UpgradeStatus: Upgraded to trusty on 2014-12-25 (20 days ago)
  dmi.bios.date: 05/14/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-890FXA-UD5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd05/14/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890FXA-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890FXA-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-890FXA-UD5
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Jan 15 12:02:38 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   

[Desktop-packages] [Bug 1482684] Re: No keyboard / Mouse 50% of lightdm starts

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  No keyboard / Mouse 50% of lightdm starts

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  This is most prevalent when resuming from suspend, however it does
  occur on a few cold boot scenarios.

  When lightdm comes up, I see the mouse cursor, it disappears and then
  I cannot move the mouse. The system, however, is still responsive, I
  can press the power button to see the Unity shutdown menu and the
  mouse cursor on the default user session still animates.

  I however cannot tty down and cannot do anything other than force
  shutdown. Attached are the contents of lightdm.log.old on the next
  boot.

  This hasn't occured for me on 14.04.1 nor Freya. It started happening
  when I installed 15.04 and then 14.04.3 so I believe it's related to
  the 3.19 hardware stack or lightdm 1.10.5.

  I have a mostly intel system, a Lenovo u410. I'd prefer to fix the
  issue rather than avoid it since I cannot download 14.04.1 anymore.

  
  During the expected behavior, lightdm boots, the mouse dissappears and then 
reappears (why it's mounting and unmounting when plymouth closes is beyond me). 
And I should be able to use my mouse/kb when resuming or cold booting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  7 10:21:52 2015
  InstallationDate: Installed on 2015-08-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1482684/+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 1528860] Re: Screen freezes after 10 seconds. Mouse and keyboard not responding.

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Tags added: wily

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Screen freezes after 10 seconds. Mouse and keyboard not responding.

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi, I've experienced this bug randomly after rebooting my computer in
  Xubuntu 15.10.  This error is consistent even after multiple "disk
  format and reinstalls" of the operative system.

  PROBLEM: When i see the login screen, my mouse and keyboard turn off,
  and the cursos blinks in the password box for some seconds, and then
  it freezes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1528860/+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 1644488] Re: Resetting causes sometimes the wrong settings to be applied

2022-10-22 Thread Paul White
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Reporter's LP profile has been removed so will close as 'Invalid'
as cannot ask if there are any issues still relevant in 2022.

** Tags added: zesty

** Changed in: lxdm (Ubuntu)
   Status: New => Invalid

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Resetting causes sometimes the wrong settings to be applied

Status in lxdm package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 17.04 dev with lxdm 0.5.3-2 and xserver-xorg-core
  2:1.18.4-1ubuntu7 and I'm noticing that the reset option of lxdm seems
  to can't be disabled anymore and that the resetting makes troubles as
  sometimes on logging out of the desktop it causes lxdm to appear with
  the wrong resolution or the monitor is unsharp at some areas.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1644488/+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 1788991] Re: external screen blank

2022-10-22 Thread Paul White
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

Thanks for your comment pczaja. I'm sorry no-one responded to you over
four years ago. Will close as 'Invalid'.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  external screen blank

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Summary: On my dual screen setup, the external monitor doesn't work in
  X after the latest update.

  Tested this with the external monitor connected via VGA

  a) using docking station
  b) using X200s internal VGA output

  Booting up ubuntu works just normal. The boot screen and login prompt
  is mirrored on the internal and external monitors. So it does work
  technically and the cabling is correct.

  After logging in, X kicks in and the external monitor goes blank.
  System settings however shows the external monitor with correct dimensions.
  Hitting "recognize screen" doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 25 10:48:22 2018
  DistUpgraded: 2017-05-13 08:46:45,733 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:20e4]
 Subsystem: Lenovo Device [17aa:20e4]
  InstallationDate: Installed on 2015-03-03 (1270 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 7458WPW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=98fb4872-8b98-469b-9c96-acbc8e4eba17 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2017-05-13 (469 days ago)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET72WW (3.22 )
  dmi.board.name: 7458WPW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7458WPW:pvrThinkPadX200:rvnLENOVO:rn7458WPW:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7458WPW
  dmi.product.version: ThinkPad X200
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Aug 24 23:09:28 2018
  xserver.configfile: default
  xserver.errors: intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 
1, disabling CRTC:29
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16400 
   vendor LEN
  xserver.version: 2:1.18.4-0ubuntu0.2~trusty2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788991/+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 1641055] Re: startx, lightdm fail to start

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

Thank you for comment #3 Remi. I'm sorry no-one has responded until now.

With so many changes to Ubuntu in almost six years since you raised this
bug report and no comments from any other user I'll close this as being
'Invalid'.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  startx, lightdm fail to start

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  After updating from 16.04 to 16.10, lightdm doesn't start.

  Adding 'nomodeset' for booting allows it to start, but apparently
  lacks all acceleration.

  Trying different kernels doesn't help, including the one from 16.04.

  Sorry for brevity, I'm writing this on my phone...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.4-1ubuntu6
  Uname: Linux 4.8.7-040807-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog: /dev/sda1: clean, 2557730/15417344 files, 54003285/61639424 blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Fri Nov 11 09:07:35 2016
  DistUpgraded: 2016-11-10 20:42:28,744 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   acpi_call, 1.0, 3.2.0-21-generic, x86_64: built
   tp_smapi, 0.42, 4.4.0-47-generic, x86_64: installed
   tp_smapi, 0.42, 4.8.0-27-generic, x86_64: installed
   tp_smapi, 0.42, 4.8.7-040807-generic, x86_64: installed
   tp_smapi, 0.42, 4.8.7-040807-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2011-03-11 (2071 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 20BWS02D00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.7-040807-lowlatency 
root=UUID=45e540a8-fe2a-49e7-9c27-99725af4a6bd ro quiet splash 
i915.i915_enable_rc6=1 vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to yakkety on 2016-11-10 (0 days ago)
  dmi.bios.date: 12/09/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET39WW (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS02D00
  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.modalias: 
dmi:bvnLENOVO:bvrJBET39WW(1.04):bd12/09/2014:svnLENOVO:pn20BWS02D00:pvrThinkPadT450s:rvnLENOVO:rn20BWS02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS02D00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.71+git1611081830.670f1e~gd~y
  version.libgl1-mesa-dri: libgl1-mesa-dri 13.1~git1611101930.f500c3~gd~y
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 13.1~git1611101930.f500c3~gd~y
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Nov 11 09:06:56 2016
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+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 1369131] Re: package xserver-xorg-dev 2:1.15.1-0ubuntu9 failed to update on shell, found xserver-xorg-dev_2%3a1.16.0-1ubuntu1_amd64.deb on /var/cache/apt/archives/ exit 1 with

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

I'm setting the status of this bug to 'Invalid' as it's not seen any
activity since it was opened. Please feel free to reopen if it is
appropriate to do so.

** Description changed:

  En mode console, avec sudo apt-get dist-upgrade, le paquetage xserver-
  xorg-dev n'est pas trouvé et ressort avec une erreur de relais brisé car
  il y a un remplacement de certains caractère par un code de substitution
  qui serait généré lors du téléchargement.
+ 
+ Google translates as:
+ In console mode, with sudo apt-get dist-upgrade, the xserver-xorg-dev package 
is not found and comes out with a broken relay error because there is a 
replacement of some characters by a substitution code that would be generated 
when downloading.
  
  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-dev 2:1.15.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 13 19:22:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ErrorMessage: tentative de remplacement de « /usr/include/xorg/glamor.h », 
qui appartient aussi au paquet libglamor-dev:amd64 0.6.0-0ubuntu4
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
-  Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
-Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB 
DDR3 [174b:e164]
+  Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
+  Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
+    Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB 
DDR3 [174b:e164]
  InstallationDate: Installed on 2014-07-25 (50 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic 
root=UUID=898d3343-23e0-43ba-835c-bbc25142f4de ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  Title: package xserver-xorg-dev 2:1.15.1-0ubuntu9 failed to install/upgrade: 
tentative de remplacement de « /usr/include/xorg/glamor.h », qui appartient 
aussi au paquet libglamor-dev:amd64 0.6.0-0ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5401:bd11/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sat Sep 13 13:23:09 2014
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputEee PC WMI hotkeys   KEYBOARD, id 8
-  inputAT Translated Set 2 keyboard KEYBOARD, id 9
-  inputImPS/2 Logitech Wheel 

[Desktop-packages] [Bug 1400148] Re: Fullscreen causes screen blinks

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still relevant when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Fullscreen causes screen blinks

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Every fullscreen window program that have screensaver inhibiter option
  causes black blinks every few seconds, for example SMPlayer. If I turn
  off screensaver inhibit in SMPlayer screen doesn't blink. But not
  every fullscreen window program have that option.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
  Uname: Linux 3.17.1-031701-lowlatency i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Dec  7 22:16:52 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.20, 3.17.1-031701-lowlatency, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3ff3]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3ff3]
  InstallationDate: Installed on 2014-10-31 (37 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  MachineType: Micro-Star International MSI Notebook PR600
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.17.1-031701-lowlatency 
root=/dev/mapper/system-root ro rootflags=subvol=@ VERBOSE_INIT=yes splash 
crashkernel=384M-:128M vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1637IMS V1.7
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-1637
  dmi.board.vendor: MSI
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1637IMSV1.7:bd09/15/2008:svnMicro-StarInternational:pnMSINotebookPR600:pvrVer1.000:rvnMSI:rnMS-1637:rvrVer1.000:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: MSI Notebook PR600
  dmi.product.version: Ver 1.000
  dmi.sys.vendor: Micro-Star International
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Dec  7 22:15:50 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   
VGA-0
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1400148/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2022-10-22 Thread Jorge Pérez Lara
Same issue in 22.10. MUTTER_DEBUG_FORCE_KMS_MODE=simple doesn't work (it
gets stuck in the login screen, I can't actually login to my session).

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in GNOME Shell:
  New
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 952468] Re: package xserver-xorg 1:7.5+6ubuntu3.1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 1

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

I'm setting the status of this bug to 'Invalid' as it's not seen any
activity since it was opened. The nature of the problem suggests that
the many updates to the package since 2012 have rendered this bug report
irrelevant.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  package xserver-xorg 1:7.5+6ubuntu3.1 failed to install/upgrade:
  ErrorMessage: subprocess new pre-removal script returned error exit
  status 1

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  while doing a partial upgrade ...got this

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: xserver-xorg 1:7.5+6ubuntu3.1
  ProcVersionSignature: Ubuntu 2.6.35-32.67-generic 2.6.35.14
  Uname: Linux 2.6.35-32-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.agp.card:
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:8x 4x 
   Registers:0x1f000e1b:0x1f004302
  .proc.driver.nvidia.agp.host.bridge:
   Host Bridge:  PCI device 1039:0661
   Fast Writes:  Not Supported
   SBA:  Supported
   AGP Rates:8x 4x 
   Registers:0x1f004e0b:0x0f02
  .proc.driver.nvidia.agp.status:
   Status:   Enabled
   Driver:   AGPGART
   AGP Rate: 8x
   Fast Writes:  Disabled
   SBA:  Enabled
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  173.14.28  Wed Sep 29 09:47:25 
PDT 2010
   GCC version:  gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Mar 11 19:00:36 2012
  DistUpgraded: Log time: 2012-03-10 14:56:13.320469
  DistroCodename: natty
  DistroVariant: ubuntu
  ErrorMessage: ErrorMessage: subprocess new pre-removal script returned error 
exit status 1
  GraphicsCard:
   nVidia Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. MS-8911 (FX5200-TD128) 
[1462:9110]
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  MachineType: Advent Series Dreamsys
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-32-generic 
root=UUID=6ba7b561-aac0-47c3-9134-0ac8992501e4 ro quiet splash vt.handoff=7
  Renderer: Unknown
  SourcePackage: xorg
  Title: package xserver-xorg 1:7.5+6ubuntu3.1 failed to install/upgrade: 
ErrorMessage: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to natty on 2012-03-11 (0 days ago)
  dmi.bios.date: 10/21/2003
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: SiS-661
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/21/2003:svnAdventSeries:pnDreamsys:pvr:rvn:rnSiS-661:rvr:cvn:ct3:cvr:
  dmi.product.name: Dreamsys
  dmi.sys.vendor: Advent Series
  version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.5+6ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/952468/+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 1795285] Re: Mouse stopped working

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Mouse stopped working

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My mouse worked earlier today. I shut down the computer, rebooted, and
  the mouse no longer works.

  It functions with my Raspberry Pi. When I plug it into the laptop, the
  mouse lights up so it is connecting with the computer. I've plugged it
  into every USB port to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Sep 30 19:27:44 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-133-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-134-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2016-05-05 (878 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 5748
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic 
root=UUID=c0c46819-2fef-4174-b0e6-ebd2bbff3504 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0W73KF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron5748:pvrNotSpecified:rvnDellInc.:rn0W73KF:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5748
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Sep 30 19:17:48 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5940 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795285/+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 1805758] Re: error when install xserver-xorg-video-intel: unmet dependencies Depends: xorg-video-abi-20 Depends: xserver-xorg-core (>= 2:1.17.99.902)

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  error when install xserver-xorg-video-intel: unmet dependencies
  Depends: xorg-video-abi-20 Depends: xserver-xorg-core (>=
  2:1.17.99.902)

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-20
  Depends: xserver-xorg-core (>= 2:1.17.99.902)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Nov 29 09:56:24 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d7]
  InstallationDate: Installed on 2018-11-08 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Dell System Inspiron N4110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=820ff3ec-0d0c-400d-b14d-0ba206196997 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 05TM8C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rn05TM8C:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System Inspiron N4110
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1805758/+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 1306785] Re: closing window leaves a peristant box

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

** Tags added: trusty

** Summary changed:

- closing window leaves a peristant box 
+ Closing  a window leaves a persistent box

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Closing  a window leaves a persistent box

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have this issue with gnome-terminal or apport when closing the
  window.

  In order to reproduce I have to switch from docked to undocked on my
  laptop (with an external screen connected to the dock)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1306785/+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 1745963] Re: no displaY

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  no displaY

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  DISPLAY fades out after standby mode

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jan 29 08:19:44 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology Solutions 771/671 PCIE VGA Display Adapter 
[1734:1125]
  InstallationDate: Installed on 2018-01-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 15d9:0a4d Trust International B.V. Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5535
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=086e92bc-3d33-4968-a4b8-3a36e8a3e993 ro quiet plymouth:debug=1 splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/07
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.03
  dmi.board.name: Z17M2.0
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: User Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.03:bd11/30/07:svnFUJITSUSIEMENS:pnESPRIMOMobileV5535:pvrV1.02:rvnFUJITSUSIEMENS:rnZ17M2.0:rvrV1.02:cvnFUJITSUSIEMENS:ct1:cvrV1.02:
  dmi.product.name: ESPRIMO Mobile V5535
  dmi.product.version: V1.02
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Jan 28 23:35:43 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745963/+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 1772109] Re: Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot

2022-10-22 Thread Paul White
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
User was removed from Launchpad some time ago so closing.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Xorg consuming 50% CPU for no good reason, at-spi2-registr another
  20%, non-stop since boot

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I have booted the computer about half an hour ago. Since the very
  beginning, I noticed the fan spinning at high spin so I launched
  "top", and noticed that Xorg was consuming about 50% CPU and another
  process called "at-spi2-registr" is consuming another 20%.

  Since then, They have continued consuming that amount of CPU
  constantly, all the time, whether or not I was doing anything. The
  only applications I opened are a terminal where I'm running top and
  the browser where I've been browsing Facebook. Before I launched the
  browser and after I closed it, CPU usage by these processed has never
  gone below 50% and 20% respectively.

  This is fucking ridiculous.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 18 22:17:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (1680 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May 18 21:44:15 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7

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


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

[Desktop-packages] [Bug 1993889] Re: nautilus does not launch

2022-10-22 Thread Jan Morten Rausch
Nautilus works the first 3-5 minutes after booting, then it stops
working with this zombie process.

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

Title:
  nautilus does not launch

Status in nautilus package in Ubuntu:
  New

Bug description:
  Problem:
  nautilus does not launch after it was closed previously.

  Expectation:
  Close nautilus, start nautilus again -> new nautilus window spawns.

  What happens:
  nautilus does not launch a second time. The cursor spins, but no window opens.

  Observations:
  the nautilus process does not get terminated properly. There is a nautilus 
process remaining with almost no CPU consumption.

  Workarounds:
  Killing the process and starting nautilus again works. Starting it via 
console and exiting it via X button does not end the task in the terminal. 
CTRL+C terminates the process and it's restarting fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:03:06 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)'
  InstallationDate: Installed on 2022-10-22 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993889/+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 1723364] Re: Double clicking the title bar to maximise/unmaximise a window frequently does nothing or the wrong thing

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Double clicking the title bar to maximise/unmaximise a window
  frequently does nothing or the wrong thing

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Create a new window such as a gnome-terminal, and position it for you
  convenience against the top edge of the desktop. Double-click the
  title bar so that the window is maximised, then without moving the
  cursor, double click it again to unmaximise it, and so on. Frequently
  the double clicks will have no effect, sometimes requiring you to
  click elsewhere (on something that isn't a decoration) to reset the
  bug and get double clicks working again. Sometimes double clicking on
  the title bar will even do something completely unexpected, such as
  opening one of the application's pull-down menus (this happens in
  Transmission, for example).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,snap,vpswitch,wall,unitymtgrabhandles,animation,expo,ezoom,staticswitcher,workarounds,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Oct 13 19:57:03 2017
  DistUpgraded: 2017-10-13 08:53:41,683 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:183d]
  InstallationDate: Installed on 2016-12-02 (314 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: ASUSTeK COMPUTER INC. UX303LAB
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-15-generic 
root=UUID=795346fb-c6f2-478b-88c6-363f7317e849 ro rootflags=subvol=@ quiet 
splash acpi_osi= vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)
  dmi.bios.date: 08/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LAB.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LAB.210:bd08/25/2015:svnASUSTeKCOMPUTERINC.:pnUX303LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1723364/+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 1735962] Re: package xserver-common 2:1.18.4-0ubuntu0.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

"package is in a very bad inconsistent state" - usually caused by a bad
download and not a bug. No doubt resolved a long time ago as no comments
for almost five years.

Closing as 'Invalid'.


** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  package xserver-common 2:1.18.4-0ubuntu0.7 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  update issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xserver-common 2:1.18.4-0ubuntu0.7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Dec  2 23:58:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.10.0-40-generic, x86_64: installed
  DuplicateSignature:
   package:xserver-common:2:1.18.4-0ubuntu0.7
   Processing triggers for libc-bin (2.23-0ubuntu9) ...
   dpkg: error processing package xserver-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [106b:00a1]
 Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [106b:00a1]
  InstallationDate: Installed on 2017-06-23 (162 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Apple Inc. MacBook4,1
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=885ff842-af01-4f45-a0e0-d6e4acb8e4e5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: xorg-server
  Title: package xserver-common 2:1.18.4-0ubuntu0.7 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB41.88Z.00C1.B00.0802091535
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F22788A9
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22788A9
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
  dmi.product.name: MacBook4,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Nov 26 21:27:25 2017
  xserver.configfile: default
  xserver.errors:
   evdev: (unnamed): Unable to open evdev device "/dev/input/event12".
   PreInit returned 2 for "(unnamed)"
   evdev: (unnamed): Unable to open evdev device "/dev/input/event13".
   PreInit returned 2 for "(unnamed)"
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: modeset

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


-- 

[Desktop-packages] [Bug 1458865] Re: No Graphics on IGEL m300

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  No Graphics on IGEL m300

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  i cant start X on the IGEL m300. Installed LUBUNTU since the igel is
  not very vast.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic i686
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  Date: Tue May 26 14:41:48 2015
  LightdmGreeterLog:
   Activating service name='org.a11y.atspi.Registry'
   Successfully activated service 'org.a11y.atspi.Registry'
   
   ** (lightdm-gtk-greeter:1515): WARNING **: Failed to load user image: Failed 
to open file '/home/jaap/.face': Bestand of map bestaat niet
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to vivid on 2015-05-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1458865/+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 1553263] Re: Launchpad branches for xorg-server are not in sync with corresponding packages

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Launchpad branches for xorg-server are not in sync with corresponding
  packages

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  For example,

  https://code.launchpad.net/~ubuntu-branches/ubuntu/wily/xorg-
  server/wily

  is last tagged 2:1.14.2.901-2ubuntu1, although lasest wily release is
  2:1.17.2-1ubuntu9.1. Why are they not in sync?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1553263/+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 806505] Re: kubuntu upgrade to 11.04 produces error: cannot open theme file /usr/share/kde4/apps/kdm/themes/ethais

2022-10-22 Thread Paul White
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

Closing as 'Invalid' as KDE moved from KDE4 to Plasma 5 some time ago.


** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  kubuntu upgrade to 11.04 produces error: cannot open theme file
  /usr/share/kde4/apps/kdm/themes/ethais

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  kubuntu upgrade to 11.04 produces error: cannot open theme file
  /usr/share/kde4/apps/kdm/themes/ethais and then goes to command
  prompt, no kde desktop access, no gnome fall back or other desktop
  options @ login.

  It upgraded successfully (no reported issues) then upon reboot @ login
  error: cannot open theme file /usr/share/kde4/apps/kdm/themes/ethais
  and then only terminal access;

  - 'lsb_release -rd' produces Ubuntu 11.04
  - apt-cache policy pkgname produces N: Unable to locate package pkgname

  It appears that update manager held back vital packages without
  warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/806505/+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 935319] Re: xorg-server dependencies error - Impossible to install xorg, xserver-xorg, ...

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

This bug report is almost 11 years old and seems to have been caused by
the removal and reinstall of necessary packages. As so much time has
passed since this report was raised I'm closing this as 'Invalid'.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  xorg-server dependencies error - Impossible to install xorg, xserver-
  xorg, ...

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I removed the xserver-xorg and xorg and now i can't install anything
  neither fix broken dependencies... I've tried everything i found in
  internet, but nothing useful.

  I made apt-get update, upgrade, dpkg, apt-get -f install 

  Here there are the dependencies i can't solve:

  xorg : Depends: xserver-xorg (>= 1:7.6+7ubuntu7.1) but it is not going
  to be installed

  -
  xserver-xorg : Depends: xserver-xorg-core (>= 2:1.9.99.901+git20110131) but 
it is not going to be installed
  Depends: xserver-xorg-video-all but it is not going to be 
installed or
   xorg-driver-video
  Depends: xserver-xorg-input-all but it is not going to be 
installed or
   xorg-driver-input
  Depends: xserver-xorg-input-evdev but it is not going to be 
installed
  --
  xserver-xorg-core : Depends: libpciaccess0 (>= 0.12.902) but 0.12.1-2 is to 
be installed
  --
  xserver-xorg-input-evdev : Depends: xorg-input-abi-16
  Depends: xserver-xorg-core (>= 2:1.11.99) but it 
is not going to be installed
  ---
  xserver-xorg-input-all : Depends: xserver-xorg-input-evdev but it is not 
going to be installed
Depends: xserver-xorg-input-synaptics but it is not 
going to be installed
Depends: xserver-xorg-input-vmmouse but it is not 
going to be installed
Depends: xserver-xorg-input-wacom but it is not 
going to be installed
  -
  xserver-xorg-core : Depends: libpciaccess0 (>= 0.12.902) but 0.12.1-2 is to 
be installed
  --

  
  I think the "loop" ends with libpciaccess0, since is the only one i've 
already installed, but i can't purge/reinstall neither solve it.

  How can i fix the problem?

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/935319/+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 1993634] Re: network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no option to set suggested --data-ciphers flag instead

2022-10-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no
  option to set suggested --data-ciphers flag instead

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

Bug description:
  Latest network-manager-openvpn still uses the deprecated --cipher
  option, and offers no way to set the new --data-ciphers option.

  nm-openvpn[257279]: OPTIONS ERROR: failed to negotiate cipher with server.  
Add the server's cipher ('AES-256-CBC') to --data-ciphers (currently 
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to this 
server.
  nm-openvpn[257279]: ERROR: Failed to apply push options
  nm-openvpn[257279]: Failed to open tun/tap interface

  Using the command line and passing --data-ciphers option works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager-openvpn 1.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 20 09:50:10 2022
  InstallationDate: Installed on 2022-02-05 (256 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220119)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1993634/+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 1511876] Re: package xserver-xorg-core 2:1.17.2-1ubuntu9 failed to install/upgrade: dependency problems - leaving unconfigured

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

I'm closing this as after almost seven years without comment this bug
report in no longer useful.

** Description changed:

  Не знаю, почему одно обновление не хочет устанавливаться.
+ 
+ Google translate as:
+ I do not know why one update does not want to be installed.
  
  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-core 2:1.17.2-1ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct 31 01:21:02 2015
  DistUpgraded: 2015-10-31 01:21:46,039 ERROR got an error from dpkg for pkg: 
'console-setup': 'dependency problems - leaving unconfigured'
  DistroCodename: wily
  DistroVariant: ubuntu
  ErrorMessage: dependency problems - leaving unconfigured
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:3800]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:3800]
  InstallationDate: Installed on 2015-10-15 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20236
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=01122131-d8b3-4b94-8af3-b8227b9a3551 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  dpkg 1.18.2ubuntu5
-  apt  1.0.10.2ubuntu1
+  dpkg 1.18.2ubuntu5
+  apt  1.0.10.2ubuntu1
  SourcePackage: xorg-server
  Title: package xserver-xorg-core 2:1.17.2-1ubuntu9 failed to install/upgrade: 
dependency problems - leaving unconfigured
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-30 (0 days ago)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 78CN25WW(V2.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G500
  dmi.modalias: 
dmi:bvnLENOVO:bvr78CN25WW(V2.03):bd11/19/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500:
  dmi.product.name: 20236
  dmi.product.version: Lenovo G500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Oct 29 23:08:13 2015
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5543 
-  vendor CMO
+  product id5543
+  vendor CMO
  xserver.version: 2:1.17.1-0ubuntu3.1

** Description changed:

  Не знаю, почему одно обновление не хочет устанавливаться.
  
- Google translate as:
+ Google translates as:
  I do not know why one update does not want to be installed.
  
  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-core 2:1.17.2-1ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct 31 01:21:02 2015
  DistUpgraded: 2015-10-31 01:21:46,039 

[Desktop-packages] [Bug 709454] Re: package xserver-xorg-core 2:1.6.4-2ubuntu4.3 failed to install/upgrade:

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

This is an 11-year old bug report that refers to end-of-life releases
while upgrading. I'm closing this by changing the status to 'Invalid' as
this report is no longer useful.


** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  package xserver-xorg-core 2:1.6.4-2ubuntu4.3 failed to
  install/upgrade:

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  In the process of upgrading ubuntu 9.10 to 10.04.

  ProblemType: Package
  Architecture: amd64
  Date: Fri Jan 28 14:38:48 2011
  DistroRelease: Ubuntu 10.04
  DkmsStatus:
   nvidia, 185.18.36, 2.6.31-22-generic, x86_64: installed  (WARNING! Diff 
between built and installed module!)
   nvidia, 185.18.36, 2.6.28-19-generic, x86_64: installed
  ErrorMessage:
   ErrorMessage: unable to create 
`/usr/lib/nvidia/libglx.so.xserver-xorg-core.dpkg-new' (while processing 
`./usr/lib/xorg/modules/extensions/libglx.so'): No such file or directory
  MachineType: Dell Inc. Precision WorkStation T7500
  NonfreeKernelModules: nvidia
  Package: xserver-xorg-core 2:1.6.4-2ubuntu4.3
  ProcCmdLine: root=UUID=3cf66a6e-40cc-4f44-8790-380e52acc25a ro quiet splash
  ProcVersionSignature: Ubuntu 2.6.31-22.70-generic
  SourcePackage: xorg-server
  Tags:  lucid
  Title: package xserver-xorg-core 2:1.6.4-2ubuntu4.3 failed to install/upgrade:
  Uname: Linux 2.6.31-22-generic x86_64
  dmi.bios.date: 04/12/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 06FW8P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd04/12/2010:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   x86_64
   kernel: 2.6.31-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/709454/+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 1113223] Re: Help can't be showed because of missing permissions

2022-10-22 Thread Paul White
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Reporter's Launchpad account has been deleted.
Issue never confirmed by another use so closing as 'Invalid'


** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Help can't be showed because of missing permissions

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 13.04 dev with xserver-xorg-core 2:1.13.2-0ubuntu1.
  Normally using X -help works without a problem as user. If a non-
  existing option is used X will show the help too - but just if the
  user has enough permissions:

  sworddragon@ubuntu:~$ X -invalid_option
  X: user not authorized to run the X server, aborting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1113223/+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 713689] Re: package xserver-xorg-core 2:1.6.4-2ubuntu4 failed to install/upgrade on version upgrade from 9.10 to 10.04

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

This is an 11-year old bug report that refers to long forgotten end-of-
life releases when upgrading. I'm closing this as 'Invalid' as this bug
report is no longer useful.


** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  package xserver-xorg-core 2:1.6.4-2ubuntu4 failed to install/upgrade
  on version upgrade from 9.10 to 10.04

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Was upgrading from 9.10 to 10.04 LTS and got this error in the
  process. I have left to reboot, will see how it goes but I have this
  window "The upgrade is now aborted. Your system could be in an
  unusable state."

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: xserver-xorg-core 2:1.6.4-2ubuntu4
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  Uname: Linux 2.6.31-16-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sat Jan  1 14:54:23 2011
  DkmsStatus:
   nvidia-96, 96.43.17, 2.6.31-16-generic, i686: installed 
   nvidia-96, 96.43.17, 2.6.32-28-generic, i686: installed 
   nvidia-current, 195.36.24, 2.6.31-16-generic, i686: installed 
   nvidia-current, 195.36.24, 2.6.32-28-generic, i686: installed
  ErrorMessage:
   ErrorMessage: package xserver-xorg-core is already installed and configured
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Lsusb:
   Bus 002 Device 002: ID 046d:c012 Logitech, Inc. Mouseman Dual Optical
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-16-generic 
root=UUID=e09b3612-9a92-4165-af0b-2a501d71cc20 ro quiet splash
  SourcePackage: dpkg
  Title: package xserver-xorg-core 2:1.6.4-2ubuntu4 failed to install/upgrade:
  dmi.bios.date: 04/12/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7025
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/12/2005:svn:pn:pvr:rvn:rnMS-7025:rvr:cvn:ct3:cvr:
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.31-16-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/713689/+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 1686633] Re: Could not set the configuration for CRTC 64

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


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

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

Title:
  Could not set the configuration for CRTC 64

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am running on a dual screen installation with a razer blade laptop.
  At startup, I have a popup saying "Could not set the configuration for CRTC 
64".
  If I close the popup, I loose all of my screens.
  If I let the popup opened, everything works fine except that some ubuntu 
components doesn't show up with the usual visual style (i.e. no 3d effect and 
no fancy color for OS buttons).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr 27 10:27:02 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Razer USA Ltd. Skylake Integrated Graphics [1a58:674f]
   NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. Device [1a58:674f]
  InstallationDate: Installed on 2016-05-07 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Razer Blade
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=78c70b10-8984-4954-bb25-3d374dd77dd6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: Razer
  dmi.bios.version: E1.00
  dmi.board.name: Blade
  dmi.board.vendor: Razer
  dmi.board.version: Late 2016
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.chassis.version: Blade (Late 2016)
  dmi.modalias: 
dmi:bvnRazer:bvrE1.00:bd09/02/2016:svnRazer:pnBlade:pvr5.04:rvnRazer:rnBlade:rvrLate2016:cvnRazer:ct9:cvrBlade(Late2016):
  dmi.product.name: Blade
  dmi.product.version: 5.04
  dmi.sys.vendor: Razer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 27 10:22:39 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: modeset(G0): failed to set mode: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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

[Desktop-packages] [Bug 1373448] Re: [ASUS X202E] Unable to set third button emulation on Atmel touchscreen

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. Dies this bug report have any relevance when
using a currently maintained release of Ubuntu? If so,  then please let
us know which one(s) otherwise this bug report can be left to expire in
approximately 60 days time.


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

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

Title:
  [ASUS X202E] Unable to set third button emulation on Atmel touchscreen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My machine is ASUS X202E. It has an Atmel maXTouch Digitizer. I
  modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following
  options to the touchscreen section:

  Option "EmulateThirdButton" "1"
  Option "EmulateThirdButtonButton" "3"
  Option "EmulateThirdButtonTimeout" "750"
  Option "EmulateThirdButtonThreshold" "50"

  and restarted X. Running xinput list-props shows that these properties
  are indeed set for the Atmel touchscreen device. However, when I touch
  and hold my finger in the same spot on the screen, nothing happens!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep 24 16:09:59 2014
  DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:108d]
  InstallationDate: Installed on 2013-10-15 (343 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007)
  MachineType: ASUSTeK COMPUTER INC. X202E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (159 days ago)
  dmi.bios.date: 06/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X202E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X202E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X202E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Sep 24 16:08:42 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12380 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1373448/+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 1639581] Re: New_nvidia_driver.

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


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

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

Title:
  New_nvidia_driver.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  
  It has something to do with the NVIDIA driver that has just been updated.
  It starts in low resolution with startup.
  Can startup in recovery modus.
  My GPU is Nvidia GEFORCE GTX 970 desktop.
  If I disable bootloader graphics
  and disable VESA framebuffer driver
  and disable PAT memory I get a cursor and a blackscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Nov  6 15:07:37 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-45-generic, x86_64: installed
   nvidia-367, 367.57, 4.4.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Elitegroup Computer Systems GM204 [GeForce GTX 970] [1019:1029]
  InstallationDate: Installed on 2016-11-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: MEDION Akoya P5332 I/C124
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 110EMW0X.102
  dmi.board.name: H110H4-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 2.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr110EMW0X.102:bd03/04/2016:svnMEDION:pnAkoyaP5332I/C124:pvr1.0:rvnMEDION:rnH110H4-EM:rvr2.0:cvnMEDION:ct3:cvr:
  dmi.product.name: Akoya P5332 I/C124
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Nov  6 14:47:05 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639581/+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 1730469] Re: Display session freezes constitently on login after Win10 dual boot crash - Ubuntu 16.04

2022-10-22 Thread Paul White
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

Further to comment #10 I'm closing this as 'Invalid' as it doesn't
appear from the information given that an update fixed the problem.

Maxime, I'm sorry that it took someone almost five years to acknowledge
your comment. Thanks for reporting your issue though.

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

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

Title:
  Display session freezes constitently on login after Win10 dual boot
  crash - Ubuntu 16.04

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Hello,
  I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
  Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
  Windows recovered, but Ubuntu was corrupted it seems.
  Grub2 launches, Ubuntu boots. I reach lightdm greeter. Then I cannot input 
mouse nor keyboard, and after a few inputs login prompt hangs. The UI displays 
"connected to ethernet". I cannot Alt Gr Fx to other ttys.
  I can REISUB, I can launch a recovery mode and get a root shell. I can SSH 
after normal boot from an external Debian system.
  Filesystem looks OK. Not sure but for some reason directories seems to have 
appeared in /root (git..)

  My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of
  debug info.

  Best regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Nov  6 18:38:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:14f7]
  InstallationDate: Installed on 2017-03-04 (247 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. X301A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=84fd9c9d-fdb2-4ebf-a754-115d068500e0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X301A1.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X301A1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX301A1.204:bd05/02/2012:svnASUSTeKCOMPUTERINC.:pnX301A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX301A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X301A1
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Nov  6 18:33:32 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730469/+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 1604742] Re: Black screen when booting without nomodeset

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Black screen when booting without nomodeset

Status in Ubuntu:
  Incomplete

Bug description:
  It happens intermittently. Some times after a kernel upgrade it boots
  fine, but immediately after the screensaver turns on the screen gets
  black with the backlight on. After a good boot it returns to booting
  to a black screen.

  The system is working while the black screen is on. I am able to log
  in and shutdown via console (blindly)

  I have tried to write dmesg to a file while it is in this mode and I
  got this:

  [ 1835.947242] cfg80211:   (5815000 KHz - 585 KHz @ 35000 KHz), (N/A, 
3301 mBm), (0 s)
  [ 1835.947243] cfg80211:   (1710 KHz - 1730 KHz @ 20 KHz), (N/A, 
2000 mBm), (N/A)
  [ 1835.947244] cfg80211:   (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 
4000 mBm), (N/A)
  [ 1835.952825] wlp3s0: Limiting TX power to 18 dBm as advertised by 
04:da:d2:fd:7d:0e
  [ 1998.759411] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* 
too many full retries, give up
  [ 1998.770230] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* 
too many full retries, give up
  [ 1998.781095] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* 
too many full retries, give up
  [ 1998.791896] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* 
too many full retries, give up
  [ 1998.802880] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* 
too many full retries, give up
  [ 1998.813780] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* 
too many full retries, give up
  [ 1998.824569] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* 
too many full retries, give up
  [ 1998.824747] [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to 
train DP, aborting

  This was after a boot failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.35  Mon Jul 11 23:14:21 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jul 20 11:41:21 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-367, 367.35, 4.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:1501]
   NVIDIA Corporation Device [10de:1667] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1503]
  InstallationDate: Installed on 2016-07-09 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc.
   Bus 001 Device 003: ID 5986:066d Acer, Inc
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N15_N17RF1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=32802ab4-59f5-434e-a6a4-8ee988bf7e24 ro nomodeset quiet splash 
vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Desktop-packages] [Bug 1985089] Re: Resizing two edge tiled windows is laggy

2022-10-22 Thread Ubuntu Foundations Team Bug Bot
The attachment "tiling--Skip-the-resize-effect-for-tiled-windows-during-
user-grabs.diff" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Resizing two edge tiled windows is laggy

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

Bug description:
  Just to report an issue that other people have reported to GNOME and
  in Reddit, that seems to also affect Ubuntu 22.04.

  If you snap 2 windows side-by-side in Wayland and then try to resize
  them, it's very slow and uses a lot of memory.

  Check here for more details:
  - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246
  - 
https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1985089/+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 1993889] [NEW] nautilus does not launch

2022-10-22 Thread Jan Morten Rausch
Public bug reported:

Problem:
nautilus does not launch after it was closed previously.

Expectation:
Close nautilus, start nautilus again -> new nautilus window spawns.

What happens:
nautilus does not launch a second time. The cursor spins, but no window opens.

Observations:
the nautilus process does not get terminated properly. There is a nautilus 
process remaining with almost no CPU consumption.

Workarounds:
Killing the process and starting nautilus again works. Starting it via console 
and exiting it via X button does not end the task in the terminal. CTRL+C 
terminates the process and it's restarting fine.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 14:03:06 2022
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)'
InstallationDate: Installed on 2022-10-22 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
 python3-nautilus  4.0-1

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


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

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

Title:
  nautilus does not launch

Status in nautilus package in Ubuntu:
  New

Bug description:
  Problem:
  nautilus does not launch after it was closed previously.

  Expectation:
  Close nautilus, start nautilus again -> new nautilus window spawns.

  What happens:
  nautilus does not launch a second time. The cursor spins, but no window opens.

  Observations:
  the nautilus process does not get terminated properly. There is a nautilus 
process remaining with almost no CPU consumption.

  Workarounds:
  Killing the process and starting nautilus again works. Starting it via 
console and exiting it via X button does not end the task in the terminal. 
CTRL+C terminates the process and it's restarting fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:03:06 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)'
  InstallationDate: Installed on 2022-10-22 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993889/+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 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment

2022-10-22 Thread SzySzySzy
What happened that it broken so many ppl things? wtf ubuntu
My gpu stopped detecting other two displays and one display has limited 
resolution. It was working!!! Stopped working few days ago
3080TI if that helps.. I think it's for nvidia only, but someone messed 
something pretty badly..

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

Title:
  UnboundLocalError: local variable 'version' referenced before
  assignment

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Hello, we received a drive-by complaint about the ubuntu-drivers
  autoinstall tool:

  < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
  < Fhazal> this error appear when i try to auto install recommended driver
  < Fhazal> https://pastebin.com/ydZVFT24

  The contents of the pastebin:

  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment

  
  Skimming the version on my system it sure feels plausible:

  def nvidia_desktop_pre_installation_hook(to_install):
  '''Applies changes that need to happen before installing the NVIDIA 
drivers'''
  with_nvidia_kms = False

  # Enable KMS if nvidia >= 470
  for package_name in to_install:
  if package_name.startswith('nvidia-driver-'):
  try:
  version = int(package_name.split('-')[-1])
  except ValueError:
  pass
  finally:
  with_nvidia_kms = version >= 470

  if with_nvidia_kms:
  set_nvidia_kms(1)


  If there was an exception splitting, indexing, or converting to an
  int, that 'version' variable may not have a value.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+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 1993880] Re: package firefox 106.0.1+build1-0ubuntu0.22.04.1~mt1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-10-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

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

Title:
  package firefox 106.0.1+build1-0ubuntu0.22.04.1~mt1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I was upgrading Ubuntu 22.04.01 to 22.10 because I was having some
  problems with the Fan and the system unable to sleep. The other major
  problem was updating the system because Firefox was in this extremely
  slow snap. So I removed it from snap and installed it via apt and it
  was functioning normally until the release upgrade.

  It kept asking me to WAIT or FORCE QUIT. After like 30 times being
  prompted I had to FORCE QUIT it.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: firefox 106.0.1+build1-0ubuntu0.22.04.1~mt1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  captain1951 F pulseaudio
   /dev/snd/controlC0:  captain1951 F pulseaudio
   /dev/snd/controlC1:  captain1951 F pulseaudio
   /dev/snd/controlC3:  captain1951 F pulseaudio
  BuildID: 20221019185550
  CasperMD5CheckResult: pass
  Channel: Unavailable
  Date: Sat Oct 22 09:14:11 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-09-30 (21 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.1.1 dev wlp4s0 proto dhcp src 192.168.1.4 metric 20600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.4 metric 600
  NoProfiles: True
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=bee0f08f-e2c4-45a4-90cd-d13bd409e007 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 106.0.1+build1-0ubuntu0.22.04.1~mt1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to kinetic on 2022-10-22 (0 days ago)
  dmi.bios.date: 04/07/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E15CKAMS.106
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-15CK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.106:bd04/07/2022:br1.6:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1:
  dmi.product.family: Delta
  dmi.product.name: Delta 15 A5EFK
  dmi.product.sku: 15CK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1993880/+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 1683271] Re: webGLSL: "return" ignored in "if"

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

This bug seems to have been fixed some time ago as I'm not seeing an
issue when using Chrome and Firefox in both Ubuntu 20.04 and 22.04.
Comments in the link above imply that is the case.

Without any version information being given for Ubuntu, Firefox or
Chrome I'm closing this as probably being fixed in updates since this
bug report was raised.


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

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

Title:
  webGLSL: "return" ignored in "if"

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  This bug occurs in web GLSL ES since WebGl2.0 , on firefox and chrome.

  in some configurations (probably: divergent branches with only some having a 
"return"), "return" in "if" is ignored.
  see simple proof case here: https://www.shadertoy.com/view/MsScDm
  (this is also the cause of several existing shaders no longer working since 
WebGl2.0 ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1683271/+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 1732116] Re: HDMI device is not working / not found

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.


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

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

Title:
  HDMI  device is not working / not found

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  after conecting TV over HDMI, Ubuntu doenst find the external display

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov 14 10:29:17 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec]
  InstallationDate: Installed on 2017-09-10 (64 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 8730w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=95c3f524-8551-407a-91a0-65632f3854b3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PAD Ver. F.13
  dmi.board.name: 30EC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.25
  dmi.chassis.asset.tag: CNU911000L
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8730w
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Nov 14 09:58:47 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732116/+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 1993874] Re: Settings and Quick Menu apply Dark style differently

2022-10-22 Thread Steven Mordarski
I had this issue since gnome-control-center 43 came out in the
development release of Ubuntu 22.10. I found another post for the same
bug and made it a duplicate so it's linked here.

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

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error

2022-10-22 Thread Robin Sheat
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563

Totem works in 22.10

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

Title:
  Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush
  Wayland connection | Gdk-Message: Error flushing display: Protocol
  error

Status in NVIDIA / egl-wayland:
  Unknown
Status in egl-wayland package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  If I launch totem, it crashes pretty much immediately. I resolved this
  by deleting .config/totem. I had moved some video files that had been
  previously opened within it recently, so possibly it was trying to
  reference them (for thumbnails or whatever) and that broke it.

  robin@malik:~$ totem

  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush
  Wayland connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  Gdk-Message: 18:00:17.844: Error flushing display: Protocol error
  robin@malik:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 18:00:39 2022
  InstallationDate: Installed on 2022-03-23 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1966787/+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 1682941] Re: graphics connection and resolution

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s) and
give us full details of any problem that you are seeing. Otherwise this
bug report can be left to expire in approximately 60 days time.

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

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

Title:
  graphics connection and resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Please see bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr 14 17:22:54 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122] (prog-if 00 
[VGA controller])
 Subsystem: VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122]
  InstallationDate: Installed on 2017-04-14 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  MachineType: Hewlett-Packard HP t5565z Thin Client
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=6ed5fed6-7449-44ca-b3be-da8be55b0514 ro quiet vesafb.invalid=1 splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 786R9 v1.04
  dmi.board.asset.tag: Astronaut
  dmi.board.name: 158Ch
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL2150RT5
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr786R9v1.04:bd11/10/2011:svnHewlett-Packard:pnHPt5565zThinClient:pvr:rvnHewlett-Packard:rn158Ch:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP t5565z Thin Client
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Apr 14 16:18:30 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSleep Button KEYBOARD, id 8
   inputLogitech K400KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682941/+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 1993883] Re: problems with dark mode

2022-10-22 Thread Steven Mordarski
*** This bug is a duplicate of bug 1993874 ***
https://bugs.launchpad.net/bugs/1993874

** This bug has been marked a duplicate of bug 1993874
   Settings and Quick Menu apply Dark style differently

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

Title:
  problems with dark mode

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

Bug description:
  when going to appearance settings my dark panels become white, though
  settings are not changed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 12:01:14 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-27 (267 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-02-07T09:04:41.555461

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993883/+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 1659140] Re: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever)

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. Does this bug report have any relevance when
using a currently maintained release of Ubuntu? If so, please let us
know which one(s) otherwise this bug report can be left to expire in
approximately 60 days time.

** Tags removed: security startx tty
** Tags added: xenial

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

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

Title:
  x crashes when I log in and back out of a tty (console, cntrl-alt-F2
  thing, whatever)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Observed behavior:

  When I get an alternate tty, or whatever it's called, with cntrl-alt-
  FN, where N is any digit, 2-6, inclusive; log in as the same user on
  the console; do stuff; and then log out with "exit":

  I'm suddenly back in tty1 and X has crashed. There is no x on any
  console. I can start it again with startx.

  Expected behavior:

  As it does in 14.04, I should just get a login prompt and stay in the
  same console. X running in tty1 should be unaffected, like x in tty7
  would be unaffected in Trusty.

  
  This is 64 bit Xenial with a minimalist Openbox environment, built from the 
mini.iso. I start X with "startx".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659140/+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 1703129] Re: VCE init error and much more in my lappy please see it

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

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

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

Title:
  VCE init error and much more in my lappy please see it

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  more errors see it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  NonfreeKernelModules: openafs wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jul  8 20:48:24 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-81-generic, x86_64: installed
   openafs, 1.6.15, 4.4.0-79-generic, x86_64: installed
   openafs, 1.6.15, 4.4.0-81-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80c2]
  InstallationDate: Installed on 2016-11-24 (225 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Notebook
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic.efi.signed 
root=UUID=f110cba6-8b9c-4548-8ed4-f543954307e6 ro splash quiet vesafb.invalid=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.47
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd05/17/2016:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.47:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jul  8 17:29:30 2017
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20049 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1703129/+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 1708829] Re: Unable to detect correct resolution of external monitor

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

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

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

Title:
  Unable to detect correct resolution of external monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system is unable to detect the correct resolution of the monitor.
  This problem is not consistent and happens randomly. I think its a
  driver issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Aug  5 17:51:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-87-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-89-generic, x86_64: installed
   nvidia-375, 375.66, 4.4.0-87-generic, x86_64: installed
   nvidia-375, 375.66, 4.4.0-89-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:380a]
 Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:380a]
  InstallationDate: Installed on 2015-12-21 (593 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20287
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed 
root=UUID=b2b670cf-975c-444c-b9be-75df78fb9323 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z510
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DCN40WW:bd10/24/2014:svnLENOVO:pn20287:pvrLenovoIdeaPadZ510:rvnLENOVO:rnVIUU4:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoIdeaPadZ510:
  dmi.product.name: 20287
  dmi.product.version: Lenovo IdeaPad Z510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Aug  4 23:58:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5565 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1708829/+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 1993883] Re: problems with dark mode

2022-10-22 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1993874 ***
https://bugs.launchpad.net/bugs/1993874

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  problems with dark mode

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

Bug description:
  when going to appearance settings my dark panels become white, though
  settings are not changed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 12:01:14 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-27 (267 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-02-07T09:04:41.555461

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993883/+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 1655436] Re: HDMI-display not working

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

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

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

Title:
  HDMI-display not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  Since I upgraded to Ubuntu 16.04 my HDMI-display is not recognized.
  I'm on an HP laptop (dv7-1095) with an Nvidia 9600M GT graphics card.
  Does anyone know what might cause this problem? :)

  Regards
  Emil

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.134  Fri Dec  9 11:30:02 
PST 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan 10 20:31:47 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
   nvidia-304, 304.134, 4.4.0-59-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4]
  InstallationDate: Installed on 2017-01-08 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.55
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jan 10 20:26:54 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1655436/+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 1665853] Re: HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen)

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

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

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

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

Title:
  HWE 16.04.2: Login Screen goes partially black after upgrade (Dual
  Screen)

Status in gnome-flashback package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.

  On dual screen setup, during system login, the first screen stretches
  over a part of the second screen (about 25% of it), whereas the rest
  of the second screen is black. Like this:

  
   
  #  # #<<|...#
  # Login# #<<|.Black.#
  #  # #<<|...#
   

  The part marked with "<<" is the rightest part of the background image
  of the first screen. I've seen this after updating to xorg/xserver-
  hwe-16.04, whereas installing the hwe kernel alone did not make this
  happen.

  Nevertheless, I can login and everything is fine again. Both screens
  look as they should. (I had to reconfigure monitors once after
  updating to xorg/xserver-hwe-16.04).

  sylog shows:

  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-flashback 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Feb 18 07:46:46 2017
  InstallationDate: Installed on 2014-11-29 (812 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-flashback
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1665853/+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 1321426] Re: x11-apps -> Should be recommends?

2022-10-22 Thread Paul White
** Changed in: xorg (Ubuntu)
   Status: New => Opinion

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

Title:
  x11-apps -> Should be recommends?

Status in xorg package in Ubuntu:
  Opinion

Bug description:
  Smells like bloat to me. Who actually uses any of those programs
  outside of a few minimalist WMs that depend on it explicitly... not to
  mention that recommends are installed by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1321426/+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 1645352] Re: No HDMI output after upgrade to 16.04!

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.

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

** Tags added: xenial

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

Title:
  No HDMI output after upgrade to 16.04!

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell 
graphics card and using i915 driver. After upgrade there is no HDMI output to 
the external screen that I use daily. 
  I did the following:
  - Upgraded to  4.4.8 Kernel hoping that the issue would be resolved.
  - Checked for other reports of this issue and followed advise to use NVIDIA 
364 drivers. 
  - Checked Intel for the most recent driver which is already packaged with 
16.04;  it is the i915 driver which is in use.
  - Used Intel driver update tool to ensure that update is correct.
  - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 
is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2)
  - Someone has assisted and has confirmed that there seems to be no hardware 
issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645352/+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 1490255] Re: changes in /etc/default/keyboard not loaded

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this issue is still relevant when using a
currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.

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

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

Title:
  changes in /etc/default/keyboard not loaded

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 15.04
  Release:  15.04
  Variant:Xubuntu

  What you expected to happen:
  Changes in /etc/default/keyboard to be effective.

  What happened instead:
  Nothing.

  ex: 
   
  File : /etc/default/keyboard

  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="fr"
  XKBVARIANT="latin9"
  XKBOPTIONS="altwin:ctrl_alt_win"

  BACKSPACE="guess"

  
  Nothing happens after boot.

  (but setxkbmap -option alt win:ctrl_alt_win does works)

  Suggestion : 
  -Remove /etc/default/keyboard as it doesn't seems to serve any purpose other 
than misleading people.
  -Make somehow working as it should.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1490255/+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 1716184] Re: failure of xrandr to find any outputs

2022-10-22 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner. I'm sorry that it took
almost five years for someone to acknowledge your comment.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

As this bug report was never confirmed by another user and seems to have
been fixed by a change to the system hardware I'm closing this by
changing the status to 'Invalid'.

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

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

Title:
  failure of xrandr to find any outputs

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I have a very new Lenovo X1 Yoga 2nd edition, with oled display.
  The exact model is 20JECTO1WW.
  The BIOS is N1NET27W.  I am running a vanilla Ubuntu 16.04

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  uname -a
  Linux gjs-yoga 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Until recently things worked quite well.  But on August 26 I got an update 
from Ubuntu and
  things began to decay.

  In particular, I can no longer display except on the built-in display:  For 
example, xrandr
  cannot find any outputs, even though this laptop has a (working) HDMI output 
port.

  xrandr --verbose
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440
  default connected primary 2560x1440+0+0 (0x272) normal (normal) 0mm x 0mm
   Identifier: 0x271
   Timestamp:  33974
   Subpixel:   unknown
   Clones:
   CRTC:   0
   CRTCs:  0
   Transform:  1.00 0.00 0.00
   0.00 1.00 0.00
   0.00 0.00 1.00
  filter:
   _GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0
    2560x1440 (0x272) 342.835MHz *current
  h: width  2560 start0 end0 total 2560 skew0 clock 
133.92KHz
  v: height 1440 start0 end0 total 1440   clock  93.00Hz

  Notice there are no (even disconnected) outputs other than default.

  Another symptom is that system restart always turns off the power
  rather than rebooting.

  I looked at the manifest of the update that seems to have caused trouble and 
the only
  suspicious entry is a microcode update from Intel.
  Here is the entry from the apt history log:

  Start-Date: 2017-08-26  17:54:05
  Commandline: aptdaemon role='role-commit-packages' sender=':1.87'
  Upgrade: intel-microcode:amd64 (3.20151106.1, 3.20170707.1~ubuntu16.04.0),

  I hope that someone knows what is the problem here.  I am stumped.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Uname: Linux 4.11.0-14-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Sep  9 18:54:56 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:224e]
  InstallationDate: Installed on 2017-07-27 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20JECTO1WW
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET27W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1NET27W(1.14):bd07/12/2017:svnLENOVO:pn20JECTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JECTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.name: 20JECTO1WW
  dmi.product.version: ThinkPad X1 Yoga 2nd
  dmi.sys.vendor: LENOVO
  

[Desktop-packages] [Bug 1909695] Re: Software application hasn't been installed

2022-10-22 Thread Paul White
This issue has sat without a response to comment #1 for almost two years
so it is being closed as 'Invalid'. The reporter gave us no indication
as to which 'LTS' release was being installed.

Please feel free to re-open this bug report if this issue has any
relevance when using a currently supported release of Ubuntu but please
make sure you tell us in which release you still experience this issue.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Invalid

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

Title:
  Software application hasn't been installed

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  I installed Ubuntu LTS with mini.iso. After choosing ubuntu-desktop in
  task selection gnome-software was not installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1909695/+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 1985089] Re: Resizing two edge tiled windows is laggy

2022-10-22 Thread xalt7x
This bug is still present with Ubuntu's Mutter 42.5-0ubuntu1 package.
And aforementioned patch still applies and fixes the problem.
Dear maintainers, please consider including it in the next update.

** Patch added: "https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2579;
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985089/+attachment/5625902/+files/tiling--Skip-the-resize-effect-for-tiled-windows-during-user-grabs.diff

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

Title:
  Resizing two edge tiled windows is laggy

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

Bug description:
  Just to report an issue that other people have reported to GNOME and
  in Reddit, that seems to also affect Ubuntu 22.04.

  If you snap 2 windows side-by-side in Wayland and then try to resize
  them, it's very slow and uses a lot of memory.

  Check here for more details:
  - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246
  - 
https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1985089/+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 882535] Re: LibreOffice Writer regularly suddenly crashes in a working session.

2022-10-22 Thread Paul White
This issue has sat with a status of 'Incomplete' for over eight years
now without a response to comment #26 so it is being closed as
'Invalid'.

Please feel free to re-open this bug report if this is still an issue
when using a currently supported release of Ubuntu and tell us in which
release you still experience this issue.

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  LibreOffice Writer regularly suddenly crashes in a working session.

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  WHAT EXACTLY HAPPENS
  When editing a document in LibreOffice Writer, this package or the whole 
system suddenly crashes sometimes. I cannot reconstruct exactly under which 
circumstances this happens - it happens always in the middle of an intense 
working session. After the crash, the system automatically restarts.
  I have been experiencing this problem ever since the latest versions of 
OpenOffice before the transit to LibreOffice. Recently, I found at least an 
effective workaround - as explained here below.

  WORKAROUND
  The workaround I have found, consist of preventive and curative measures.

  WORKAROUND - PREVENTIVE MEASURES
  When editing the document, I save it after each phrase via the command 
CONTROL-S.
  Each +/- 5 minutes, I go back to the folder where the document is: via 
Dolphin. First I refresh the document list via F5. Than I copy the document 
into a backup-document under another name.

  WORKAROUND - CURATIVE MEASURES
  After coming in the system again after such a crash, I go back to the 
document in which I have been working just before the crash: via Dolphin.  
After clicking at the document, the LibreOffice document recovery dialogue 
starts. I choose the option "Open the read-only document". After opening this 
document, I save the same document under another name, after which I can 
continue the working session. 
  By doing so, I manage to recover the document in 9 out of 10 cases.
  In about 1 out of 10 cases, I do NOT manage to recover the document. In such 
a case, I continue the working session in the lastest backup document.

  ANSWERS TO SOME OTHER RELEVANT QUESTIONS:
  Release of the OS I am using: Kubuntu 11.04.

  Version of the package I am using:
  LibreOffice 3.3.4 
  OOO330m19 (Build:401)
  tag libreoffice-3.3.3.1, Ubuntu package 1:3.3.4-0ubuntu1

  What I expected to happen: being able to continue the working session
  without any unexpected and non-sollicitated interruption.

  What happened instead: suddenly LibreOffice crashed and the whole
  system restarted automatically, without me consciously provoking this
  course of events.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.4-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic i686
  Architecture: i386
  Date: Thu Oct 27 13:14:40 2011
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  ProcEnviron:
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
   LC_MESSAGES=en_GB.UTF-8
   SHELL=/bin/usernameh
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroRelease: Ubuntu 11.04
  DistroVariant: kubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GME Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
 Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  MachineType: ASUSTeK Computer INC. 1001HA
  Package: xorg-server (not installed)
  ProcEnviron:
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
   LC_MESSAGES=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-12-generic 
root=UUID=30263ac8-c75d-45b3-b0d9-97060b9d3f53 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Renderer: Unknown
  Tags:  natty kubuntu patch
  Uname: Linux 2.6.38-12-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 02/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1005HA
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 

[Desktop-packages] [Bug 1164876] Re: update xserver to fix broken XResetScreenSaver

2022-10-22 Thread Paul White
This issue has sat with a status of 'Incomplete' for more than eight
years without a response to comment #2 so it is being closed as
'Invalid' although it may well have been fixed.

Please feel free to re-open this bug report if this is still an issue
when using a currently supported release of Ubuntu and tell us in which
release you still experience this issue.

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  update xserver to fix broken XResetScreenSaver

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I reported the bug at http://bugs.kde.org/  [1]. They asked me to file
  a bug here in order to suggest to update the X server "to a recent
  1.13.x point release or at least pull in the fix for
  https://bugs.freedesktop.org/show_bug.cgi?id=56649; (see comment #9).

  [1] https://bugs.kde.org/show_bug.cgi?id=315379

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1164876/+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 1002788] Re: Using the touchscreen breaks normal device left clicking

2022-10-22 Thread Paul White
This issue has sat with a status of 'Incomplete' for over nine years now
without any response so it is being closed as 'Invalid' as it only
refers to long time 'EOL' releases.

Please feel free to re-open this bug report if this is still an issue
when using a currently supported release of Ubuntu and tell us in which
release you still experience this issue.


** Changed in: xorg-server (Ubuntu)
 Assignee: Canonical X.org (canonical-x) => (unassigned)

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Using the touchscreen breaks normal device left clicking

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Shortly after reboot, the problem starts occurring.

  Haven't been able to find a trigger for the issue.

  When opening the home folder, using the left Unity menu, we are unable to 
open files or folders by left clicking on them.
  When right clicking, the menu contains no open option 

  Same problem with files on the desktop.

  We have installed the 'open in terminal' right click menu addon from
  repos.

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  nautilus:
Installed: 1:3.4.1-0ubuntu1
Candidate: 1:3.4.1-0ubuntu1
Version table:
   *** 1:3.4.1-0ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  nautilus-open-terminal:
Installed: 0.19-2build1
Candidate: 0.19-2build1
Version table:
   *** 0.19-2build1 0
  500 http://za.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages
  100 /var/lib/dpkg/status

  
  We would appreciate your help.

  Kind regards,
  Charles & Tresor

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: wl fglrx
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Tue May 22 12:07:42 2012
  GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+1076+157'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_ZA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1002788/+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 1200866] Re: multi-touch screen functions break when using chromium

2022-10-22 Thread Paul White
This issue has sat with a status of 'Incomplete' for almost nine years
without any response so it is being closed as 'Invalid' although the bug
may well have been fixed.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

Please feel free to re-open this bug report if this is still an issue
when using a currently supported release of Ubuntu and tell us in which
release you still experience this issue.

** Changed in: xorg-server (Ubuntu)
 Assignee: Maarten Lankhorst (mlankhorst) => (unassigned)

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  multi-touch screen functions break when using chromium

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Steps:
  1. Have a multi-touch monitor
  2. run terminal
  3. use 3 finger swipe to put it into resize and resposition window, note that 
it works using multi-touch on the screen
  4. run chromium
  5. go to http://reddpics.com/r/cats (or similar)
  6. click 3 cat pictures with your finger on touch screen
  7. use your finger on the screen to click between the open tabs

  Result:
  After a few clicks the taps stop working

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu5
  ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jul 13 09:26:27 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3903]
  InstallationDate: Installed on 2013-06-18 (25 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130617)
  MachineType: LENOVO Lenovo IdeaPad U310 Touch
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic.efi.signed 
root=UUID=f26c50a8-eb98-479c-ad80-1906e5d1e626 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 65CN97WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad U310 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr65CN97WW:bd01/29/2013:svnLENOVO:pnLenovoIdeaPadU310Touch:pvrLenovoIdeaPadU310Touch:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadU310Touch:
  dmi.product.name: Lenovo IdeaPad U310 Touch
  dmi.product.version: Lenovo IdeaPad U310 Touch
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.45-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu1.1
  xserver.bootTime: Sat Jul 13 09:25:12 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.1-0ubuntu1
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1200866/+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 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-22 Thread Eliyahu Basa
Is there a temporal solution? or a way to fix it without resetting the
computer?

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993284/+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 1993883] [NEW] problems with dark mode

2022-10-22 Thread Dmytro Holovchenko
Public bug reported:

when going to appearance settings my dark panels become white, though
settings are not changed

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 12:01:14 2022
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2022-01-27 (267 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2022-02-07T09:04:41.555461

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


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

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

Title:
  problems with dark mode

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

Bug description:
  when going to appearance settings my dark panels become white, though
  settings are not changed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 12:01:14 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-27 (267 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-02-07T09:04:41.555461

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993883/+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 1993879] Re: "Settings" key fails to launch "Settings."

2022-10-22 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => gnome-control-center (Ubuntu)

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

Title:
  "Settings" key fails to launch "Settings."

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

Bug description:
  Pressing the "settings" key fails to launch "Settings."

  STR:
  1. Press the "Settings" key (the key physically shared with F9).
  2. Nothing happens. 

  Expected result:
  The "Settings" app should appear (the same one accessed by the gear icon in 
"Quick Settings").

  Actual result: 
  Nothing happens. 

  The key worked fine in 22.04. 
  Pressing the gear icon in "Quick Settings" does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 11:55:00 2022
  InstallationDate: Installed on 2017-12-08 (1778 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993879/+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 1993879] [NEW] "Settings" key fails to launch "Settings."

2022-10-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Pressing the "settings" key fails to launch "Settings."

STR:
1. Press the "Settings" key (the key physically shared with F9).
2. Nothing happens. 

Expected result:
The "Settings" app should appear (the same one accessed by the gear icon in 
"Quick Settings").

Actual result: 
Nothing happens. 

The key worked fine in 22.04. 
Pressing the gear icon in "Quick Settings" does work.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 11:55:00 2022
InstallationDate: Installed on 2017-12-08 (1778 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)

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


** Tags: amd64 apport-bug kinetic third-party-packages wayland-session
-- 
"Settings" key fails to launch "Settings."
https://bugs.launchpad.net/bugs/1993879
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-control-center in Ubuntu.

-- 
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 1993881] [NEW] shotwell does not support file format WebP

2022-10-22 Thread corrado venturini
Public bug reported:

Try open a file in WebP format: shotwell displays a small window with a message 
stating:
Shotwell does not support the file format of .webp 

corrado@corrado-n7-kinetic:~$ apt policy shotwell
shotwell:
  Installed: 0.30.16-1ubuntu2
  Candidate: 0.30.16-1ubuntu2
  Version table:
 *** 0.30.16-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-n7-kinetic:~$ inxi -Sx
System:
  Host: corrado-n7-kinetic Kernel: 5.19.0-21-generic arch: x86_64 bits: 64
compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
corrado@corrado-n7-kinetic:~$

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: shotwell 0.30.16-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 09:14:18 2022
InstallationDate: Installed on 2022-10-21 (1 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  shotwell does not support file format WebP

Status in shotwell package in Ubuntu:
  New

Bug description:
  Try open a file in WebP format: shotwell displays a small window with a 
message stating:
  Shotwell does not support the file format of .webp 

  corrado@corrado-n7-kinetic:~$ apt policy shotwell
  shotwell:
Installed: 0.30.16-1ubuntu2
Candidate: 0.30.16-1ubuntu2
Version table:
   *** 0.30.16-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n7-kinetic:~$ inxi -Sx
  System:
Host: corrado-n7-kinetic Kernel: 5.19.0-21-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  corrado@corrado-n7-kinetic:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: shotwell 0.30.16-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 09:14:18 2022
  InstallationDate: Installed on 2022-10-21 (1 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


  1   2   >