[Touch-packages] [Bug 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart

2024-03-17 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: ubuntu-meta (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1721763

Title:
  ubuntu is stuck with black screen and blinking cursos at top left on
  all shutdown or restart

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  I really do not know which package to assign this incident, please
  excuse me.

  Any way, the release candidates is near, and this problem continues to
  occur since linux kernel was updated from 4.11 to 4.12 ... and now
  with version 4.13 the problem continues.

  I noticed that this problem does not occur with my other two older
  notebooks (one Sony Vaio and the other a generic one integrated by me)
  both old notes use NVIDIA video card in versions of more than 5 years
  ago.

  My new Dell notebook has a GTX 1050 video card ... but I also do not
  know if the cause of this problem may be linked to the video card and
  the fact that Nouveau driver and linux Kernel have received recent
  implementations for compatibilities with this new NVIDIA technology.

  The fact is that Ubuntu 17.10 has potential to be distributed with
  this problem and I think this may not be interesting, so I am
  reporting this case.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-desktop 1.402
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 08:25:20 2017
  InstallationDate: Installed on 2017-09-29 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2057605] Re: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1

2024-03-12 Thread Paul White
** Package changed: ubuntu => initramfs-tools (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2057605

Title:
  update-initramfs fails:  /usr/share/initramfs-tools/hooks/fsck failed
  with return 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04

  initramfs-tools:
Installed: 0.136ubuntu6.7
Candidate: 0.136ubuntu6.7
Version table:
   *** 0.136ubuntu6.7 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   0.136ubuntu6 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 
Packages

  
  sudo apt-get install linux-image-5.4.0-173-generic
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
linux-modules-5.4.0-173-generic
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-173-generic
  The following NEW packages will be installed:
linux-image-5.4.0-173-generic linux-modules-5.4.0-173-generic
  0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
  Need to get 25.5 MB of archives.
  After this operation, 92.5 MB of additional disk space will be used.
  Do you want to continue? [Y/n]
  Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-modules-5.4.0-173-generic amd64 5.4.0-173.191 [15.0 MB]
  Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-image-5.4.0-173-generic amd64 5.4.0-173.191 [10.5 MB]
  Fetched 25.5 MB in 2s (12.1 MB/s)
  Selecting previously unselected package linux-modules-5.4.0-173-generic.
  (Reading database ... 77620 files and directories currently installed.)
  Preparing to unpack 
.../linux-modules-5.4.0-173-generic_5.4.0-173.191_amd64.deb ...
  Unpacking linux-modules-5.4.0-173-generic (5.4.0-173.191) ...
  Selecting previously unselected package linux-image-5.4.0-173-generic.
  Preparing to unpack .../linux-image-5.4.0-173-generic_5.4.0-173.191_amd64.deb 
...
  Unpacking linux-image-5.4.0-173-generic (5.4.0-173.191) ...
  Setting up linux-modules-5.4.0-173-generic (5.4.0-173.191) ...
  Setting up linux-image-5.4.0-173-generic (5.4.0-173.191) ...
  I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-173-generic
  I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-173-generic
  Processing triggers for linux-image-5.4.0-173-generic (5.4.0-173.191) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.4.0-173-generic
  + PREREQ=
  + prereqs
  + echo
  + exit 0
  + PREREQ=
  + [ ! -x /sbin/fsck ]
  + . /usr/share/initramfs-tools/scripts/functions
  + . /usr/share/initramfs-tools/hook-functions
  + + sort
  get_fsck_types
  + get_fsck_type_fstab / root
  + uniq
  + _read_fstab_entry /
  + echo MNT_FSNAME=
  + echo MNT_DIR=
  + echo MNT_TYPE=
  + [ -f /etc/fstab ]
  + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ / = / ]
  + [ -n  ]
  + echo MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72"
  + echo MNT_DIR=/
  + echo MNT_TYPE=ext4
  + echo MNT_PASS=0
  + break 2
  + eval MNT_FSNAME=
  MNT_DIR=
  MNT_TYPE=
  MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72"
  MNT_DIR=/
  MNT_TYPE=ext4
  MNT_PASS=0
  + MNT_FSNAME=
  + MNT_DIR=
  + MNT_TYPE=
  + MNT_FSNAME=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72
  + MNT_DIR=/
  + MNT_TYPE=ext4
  + MNT_PASS=0
  + [ / = / ]
  + [ / = / ]
  + resolve_device UUID=d4148b00-3426-4e12-a89c-1eab09c29b72
  + DEV=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72
  + local orig=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72
  + blkid -l -t UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 -o device
  + DEV=/dev/md127
  + [ -e /dev/md127 ]
  + echo /dev/md127
  + MNT_FSNAME=/dev/md127
  + get_fstype /dev/md127
  + local FS FSTYPE
  + FS=/dev/md127
  + blkid -o value -s TYPE /dev/md127
  + FSTYPE=ext4
  + echo ext4
  + return 0
  + get_fsck_type_fstab /usr /usr
  + _read_fstab_entry /usr
  + echo MNT_FSNAME=
  + echo MNT_DIR=
  + echo MNT_TYPE=
  + [ -f /etc/fstab ]
  + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ / = /usr ]
  + MNT_DIR=
  + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ /var = /usr ]
  + MNT_DIR=
  + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ /home = /usr ]
  + MNT_DIR=
  + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ swap = /usr ]
  + MNT_DIR=
  + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ swap = /usr ]
  + MNT_DIR=
  + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ /boot/efi = /usr ]
  + MNT_DIR=
  + read -r 

[Touch-packages] [Bug 1499899] Re: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL

2024-02-08 Thread Paul White
Closing as both other tasks are 'Expired'

** Changed in: unity
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1499899

Title:
  Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Expired
Status in vim package in Ubuntu:
  Expired

Bug description:
  When launched from a terminal the widely used text editor gvim
  displays lots WARNING and CRITICAL messages such as:

  ** (gvim:3608): WARNING **: (../../../lib/unity-gtk-menu-
  shell.c:176):unity_gtk_menu_shell_show_item: code should not be
  reached

  ** (gvim:3608): CRITICAL **: unity_gtk_menu_shell_handle_item_notify:
  assertion 'UNITY_GTK_IS_MENU_SHELL (shell)' failed

  This did not happen in 15.04. It is a most embarrassing bug. Gvim is
  an essential tool for many users.

  I am using Ubuntu 15.10 Beta 2.

  $ lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  $ apt-cache policy vim-gnome
  vim-gnome:
Installed: 2:7.4.712-2ubuntu3
Candidate: 2:7.4.712-2ubuntu3
Version table:
   *** 2:7.4.712-2ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy vim-gtk
  vim-gtk:
Installed: 2:7.4.712-2ubuntu3
Candidate: 2:7.4.712-2ubuntu3
Version table:
   *** 2:7.4.712-2ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected to be able to use Gvim. Now Gvim pollutes the terminal with
  scary messages, and disturbs the messages shown by other programs
  running in the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: vim-gnome 2:7.4.712-2ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 26 00:40:37 2015
  InstallationDate: Installed on 2015-09-25 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2047727] Re: display backlight

2024-01-20 Thread Paul White
Moving to 'xorg' so that this bug report reaches Ubuntu's Desktop Team
Please explain in further detail 'display backlight' and  'bridness backlight'
What exactly is the problem that you are seeing while using Ubuntu?

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2047727

Title:
  display backlight

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  bridness backlight

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 20:15:41 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0214]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0214]
  InstallationDate: Installed on 2023-12-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: emachines emachines D725
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-26-generic root=/dev/sda2 ro 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.12
  dmi.board.name: HM40
  dmi.board.vendor: emachines
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.12:bd08/10/2009:svnemachines:pnemachinesD725:pvr0100:rvnemachines:rnHM40:rvrRev:cvnAcer:ct10:cvrN/A:sku:
  dmi.product.name: emachines D725
  dmi.product.version: 0100
  dmi.sys.vendor: emachines
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/2047727/+subscriptions


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


[Touch-packages] [Bug 2046574] Re: Printer grey scale/bw option is not available

2023-12-31 Thread Paul White
** Package changed: ubuntu => gtk+3.0 (Ubuntu)

** Tags added: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2046574

Title:
  Printer grey scale/bw option is not available

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I was using 22.04 LTS until last week(8 Dec 2023). I upgraded to 23.10
  and noticed a difference with the printing options.

  In 22.04 (as far as I remember),
  There was Monochrome, Grey scale and Color. I used to print using grey scale 
and it used to print in grey scale.

  After upgrade to 23.10,
  There is no grey scale option. Instead there is Color, Auto Monochrome, 
Monochrome and process Monochrome. I tried all the monochrome options and all 
of them printed with color. Even when I checked preview it was showing color 
with these options selected. I think the monochrome options are not selected at 
all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2046574/+subscriptions


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


[Touch-packages] [Bug 2047595] Re: sound control panel security

2023-12-28 Thread Paul White
** Package changed: ubuntu => ubuntu-meta (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2047595

Title:
  sound control panel security

Status in ubuntu-meta package in Ubuntu:
  New

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

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


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


[Touch-packages] [Bug 2043314] Re: The 'Settings >> Multitasking >> Active Screen Edges' option status never been saved.

2023-12-19 Thread Paul White
** Package changed: ubuntu-settings (Ubuntu) => gnome-settings-daemon
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2043314

Title:
  The 'Settings >> Multitasking >> Active Screen Edges' option status
  never been saved.

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

Bug description:
  Hello, Our Toilsome Maintainers, The 'Settings >> Multitasking >> Active 
Screen Edges' option status never been saved. The 'Active Screen Edges' option 
is off when I turned it on and restarted my laptop. Hope it been fixed soon.
  Regards,
  larryw3i

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-settings 23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 21:31:49 2023
  InstallationDate: Installed on 2023-05-04 (192 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 886450] Re: Gvim hangs with blank window if not maximized

2023-12-05 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.10 (oneiric) reached end-of-life on May 9, 2013.

The bug description implies that this isn't a vim bug as emacs is also
affected and and comment #16 implies the issue is theme related.

As almost 12 years have passed without any comment I'll close this as
'Invalid'.

** Changed in: vim (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/886450

Title:
  Gvim hangs with blank window if not maximized

Status in vim package in Ubuntu:
  Invalid

Bug description:
  If gvim is opened not maximized, it simply hangs without showing any
  content of the file (or the standard content ~s for new file).
  However, if it is maximized, it works. Again if gvim is unmaximized,
  it freezes the window content. I tried with removing .vimrc file and
  .vim directory. Same behavior persists. I tried with removing
  .gnome2/Vim file and calling /usr/bin/gvim -f. But same problem.

  However, I think it may not be a problem in Gvim because the same
  frozen window behavior happens for emacs. However, this problem is not
  there with gedit.

  I did not know how to file bug with the window management software, so
  i invoked "ubuntu-bug vim" from command window.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: vim (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Nov  5 11:18:16 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to oneiric on 2011-10-18 (18 days ago)

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


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


[Touch-packages] [Bug 1417978] Re: vim improperly displaying text when loaded in gnome-terminal with altered geometry

2023-12-05 Thread Paul White
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
Issue never confirmed by another user.
Reporter's account has been deactivated so closing.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1417978

Title:
  vim improperly displaying text when loaded in gnome-terminal with
  altered geometry

Status in vim package in Ubuntu:
  Invalid

Bug description:
  I use the following command to load vi(m) in a new gnome-terminal
  window with altered geometry:

  gnome-terminal --geometry 156x48+80+50 -e "/usr/bin/vi .bashrc"

  About 60% of the time, when I do this, it loads the text within vim as
  follows:

  1.  The top line of text seems to be the next line after the line of text 
that would have been displayed as the last line had I started vim in the 
default sized gnome-terminal window
  2.  After what seems to be the text normally displayed below that offset, 
after what seems to be the number of lines displayed as if it were in a default 
sized gnome-terminal window, the remaining lines are blank
  3.  The only way to correct the display is to scroll down until a full screen 
of text is normally displayed in vi(m), then everything starts working normally

  Note that this behavior happens only around 60-70% of the time -
  sometimes, issuing the command will work correctly, sometimes as
  described above.  It is very repeatable though on my machine.

  This behavior happens on my native Ubuntu 14.04 box as well as on my
  14.04.1 box within a virtual machine under Windows 8.1 (both for
  hyper-v and vmware)

  The reason I think it may be vim, not gnome-terminal, is that nano,
  irssi and the man pages all work fine every time when I issue the same
  command but substitute them inside the quotes above.

  * EDIT 
  Further investigation may seem to point to vte3 (libvte).

  Looking at vte.c in the Gnome vte3 (libvte) source code from their git repo, 
the default number of lines for a terminal is hardcoded to be 24 lines and the 
terminal widget appears to be set to this size during the call to 
vte_terminal_init().  This is the same number of lines displayed before 
starting the blank lines going to the bottom of vim within the gnome-terminal
  ** End EDIT *

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: vim-tiny 2:7.4.052-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  4 02:35:03 2015
  ExecutablePath: /usr/bin/vim.tiny
  InstallationDate: Installed on 2015-02-02 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1179722] Re: :help word[CTRL-D] doesn't search help

2023-12-05 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.

Looking at this bug report in 2023 I can't reproduce the reported
problem using either Ubuntu 20.04 or 22.04. As the issue was never
confirmed by another user and there have been no comments for over 10
years I'll mark it as being 'Invalid'. A local configuration problem?

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1179722

Title:
  :help word[CTRL-D] doesn't search help

Status in vim package in Ubuntu:
  Invalid

Bug description:
  I launch vim by typing it's name. Inside vim I type :help word[CTRL-D]

  EXPECTED RESULT: search the vim documentation

  ACTUAL RESULT: I get the : command history

  The CTRL-D sequence is described in the :help help file. This is a
  very important feature for me and I suspect other vim users. This
  problem does not exist on 10.04.

  WORKAROUND: tab key instead of CTRL-D, but this isn't mentioned in the
  documentation.

  I can start vim either in a gnome-terminal with or without byobu
  running screen, I can also start via a virtual terminal by pressing
  ctrl-alt-F2 and I get the same result. All three entries of vim :set
  term?. vim :echo $TERM and vim :!echo $TERM are consistent in both
  cases, as screen in the first case and linux in the second case. With
  all three in agreement there is only the vim configuration left for
  interpreting the following command, right?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: vim 2:7.3.429-2ubuntu2.1
  ProcVersionSignature: Ubuntu 3.2.0-41.66-generic 3.2.42
  Uname: Linux 3.2.0-41-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: amd64
  Date: Mon May 13 16:10:08 2013
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120315)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1772050] Re: 't' and 'T' command used in vi editor is not working its working only for first occurrence of character.

2023-12-05 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 while 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: vim (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1772050

Title:
  't' and 'T' command used in vi editor is not working its working only
  for first occurrence of character.

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  't' and 'T' command used in vi editor is not working its working only
  for first occurrence of character.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri May 18 20:28:09 2018
  InstallationDate: Installed on 2018-05-17 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1393596] Re: Extreme slow syntax highlighting for Windows Registry Files

2023-12-05 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.

However, no Ubuntu version or flavour information has been given and as
there has been no comment on the bug report for over nine years I'm
closing this as being an invalid report.

If this is still an issue while using a currently supported release of
Ubuntu then please revert the bug status to 'New' and run the following
command in a terminal:

  apport-collect 1393596

Thank you.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1393596

Title:
  Extreme slow syntax highlighting for Windows Registry Files

Status in vim package in Ubuntu:
  Invalid

Bug description:
  If exported Windows Registry Information is opened in vim, an very
  simple, but apropriate syntax highlighting is enabled.

  However, on any longer block of ASCII hex representation (and usual
  Registry data has a lot of that trash) the text rendering gets
  extremely slow, hugging CPU and make scrolling almost impossible.

  The simple scheme of marking keys and there values should not need
  such complex parsing.

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


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


[Touch-packages] [Bug 1745902] Re: gvim will freeze when partial window is out of current desktop using Wayland

2023-12-05 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 while 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: vim (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1745902

Title:
  gvim will freeze when partial window is out of current desktop using
  Wayland

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Reproduce Steps:
  0. Login ubuntu 17.10 using Wayland
  1. Open Gvim
  2. Move Gvim window to partially out of current desktop
  3. Press i to change current mode to insert mode <- problem
  4. Input some chars and new lines
  5. Press ESC to return to normal mode
  6. Press j or k to move cursor <- problem

  
  The problem is:
  gvim window will freeze unless:
  1. you move your mouse
  2. wait a few seconds

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: vim-gtk 2:8.0.0197-4ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 10:43:36 2018
  InstallationDate: Installed on 2016-04-24 (644 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: vim
  UpgradeStatus: Upgraded to artful on 2017-10-23 (98 days ago)

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


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


[Touch-packages] [Bug 1499899] Re: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL

2023-12-05 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 while 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: vim (Ubuntu)
 Assignee: Lee moonhyoung (eobeauti2) => (unassigned)

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1499899

Title:
  Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete
Status in vim package in Ubuntu:
  Incomplete

Bug description:
  When launched from a terminal the widely used text editor gvim
  displays lots WARNING and CRITICAL messages such as:

  ** (gvim:3608): WARNING **: (../../../lib/unity-gtk-menu-
  shell.c:176):unity_gtk_menu_shell_show_item: code should not be
  reached

  ** (gvim:3608): CRITICAL **: unity_gtk_menu_shell_handle_item_notify:
  assertion 'UNITY_GTK_IS_MENU_SHELL (shell)' failed

  This did not happen in 15.04. It is a most embarrassing bug. Gvim is
  an essential tool for many users.

  I am using Ubuntu 15.10 Beta 2.

  $ lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  $ apt-cache policy vim-gnome
  vim-gnome:
Installed: 2:7.4.712-2ubuntu3
Candidate: 2:7.4.712-2ubuntu3
Version table:
   *** 2:7.4.712-2ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy vim-gtk
  vim-gtk:
Installed: 2:7.4.712-2ubuntu3
Candidate: 2:7.4.712-2ubuntu3
Version table:
   *** 2:7.4.712-2ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected to be able to use Gvim. Now Gvim pollutes the terminal with
  scary messages, and disturbs the messages shown by other programs
  running in the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: vim-gnome 2:7.4.712-2ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 26 00:40:37 2015
  InstallationDate: Installed on 2015-09-25 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1721280] Re: vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()

2023-12-05 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 while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1721280

Title:
  vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Might be related to one of my extensions

  camelcasemotion  lightline.vim  vim-fetch
  inorirust.vim   validator.vim  vim-fugitive

  
  Please also double check that it's not a duplicate of #96263 "vim crashed 
with sigsegv"

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: vim-gtk3 2:8.0.0197-4ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct  4 16:13:33 2017
  ExecutablePath: /usr/bin/vim.gtk3
  InstallationDate: Installed on 2017-05-30 (127 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: vim update_test_projects.sh
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   mch_exit ()
   getout ()
() at /lib/x86_64-linux-gnu/libpthread.so.0
   __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135
  Title: vim.gtk3 crashed with SIGSEGV in kill()
  UpgradeStatus: Upgraded to artful on 2017-09-25 (8 days ago)
  UserGroups: dialout plugdev sudo wireshark

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


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


[Touch-packages] [Bug 293331] Re: vim-gnome mousewheel/scrollbar strange behavior

2023-12-05 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 8.04 (hardy) reached end-of-life on May 12, 2011.

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 while 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: vim (Ubuntu)
   Status: New => Incomplete

** Tags added: hardy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/293331

Title:
  vim-gnome mousewheel/scrollbar strange behavior

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim-gnome

  8.04 x86 and amd64 under gnome, run gvim and open a file or create
  text that has more lines than are shown.  when hovering the mouse over
  the up and down buttons on the scrollbar and using the mouse scroll
  wheel, the bar moves according to the scroll wheel but the text moves
  as if you had pressed the scroll button with a left mouse click.  i
  expect it to scroll as it would if i had the mouse over the text and
  used the mouse scroll wheel.

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


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


[Touch-packages] [Bug 560157] Re: vim-gtk, vim-gnome menu_bar error

2023-12-05 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.

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 while 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: vim (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/560157

Title:
  vim-gtk,vim-gnome menu_bar error

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim

  vim-gtk,vim-gnome menu_bar error,

  only the  item was show in the menu bar. Others have no context.

  but,
  export LANG=xxx can solve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: vim-gnome 2:7.2.330-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sun Apr 11 01:12:41 2010
  ExecutablePath: /usr/bin/vim.gnome
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=zh_CN.utf8
   LANGUAGE=zh_CN:zh
  SourcePackage: vim

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


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


[Touch-packages] [Bug 627332] Re: Scroll bars do not appear correctly on new splits

2023-12-05 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.

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 while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/627332

Title:
  Scroll bars do not appear correctly on new splits

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim-gnome

  vim-gnome 2:7.2.330-1ubuntu3
  ubuntu 10.04.1 LTS

  Easiest steps to reproduce:

  - Open gvim
  - Maximise (currently reproduced under Compiz - not tried without)
  - Open a file with more lines than available.
  - :vsp

  Expected behaviour: New split has a scrollbar on the right
  Actual behaviour: Scrollbar exists, but appears to be attached to the outside 
of the maximised window, and thus not visible.
  Workaround: Restore gvim and maximise again. This is how it should originally 
have displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: vim-gnome 2:7.2.330-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Tue Aug 31 11:06:43 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: vim

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


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


[Touch-packages] [Bug 778485] Re: Add nginx syntax to the default vim package

2023-12-05 Thread Paul White
Looking at my 'jammy' installation I see that nginx.vim is installed in 
  /usr/share/vim/vim82/syntax
so I'm closing this report as being fixed.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/778485

Title:
  Add nginx syntax to the default vim package

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: vim

  Could you add the nginx.vim into the syntax directory and add the appropriate 
line into the filetype.vim ?
  Here are all you need :
  http://www.vim.org/scripts/script.php?script_id=1886

  Thank you,

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: vim-runtime 2:7.3.035+hg~8fdc1210-1ubuntu7
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Fri May  6 14:56:45 2011
  Dependencies:
   
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to natty on 2011-04-29 (7 days ago)

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


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


[Touch-packages] [Bug 1785813] Re: gvim crashes when clicking on manager to shade the window

2023-12-05 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 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
  and the Xubuntu flavour around two years earlier in 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 while using a
currently maintained release of Xubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1785813

Title:
  gvim crashes when clicking on manager to shade the window

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  I am running xubuntu 18.04 and when I click the "shade" button of gvim
  frame the window disappears with gvim crashing. It happens only to
  gvim all other windows I've tested are ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim-gtk3 2:8.0.1453-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug  7 14:08:10 2018
  InstallationDate: Installed on 2017-11-02 (278 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: vim
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (99 days ago)

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


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


[Touch-packages] [Bug 1144487] Re: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2

2023-12-05 Thread Paul White
*** This bug is a duplicate of bug 1144486 ***
https://bugs.launchpad.net/bugs/1144486

** This bug has been marked a duplicate of bug 1144486
   package vim-gnome 2:7.3.429-2ubuntu2.1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1144487

Title:
  package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 2

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  2013-04-03
  No install vim packege and failed update.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: vim 2:7.3.429-2ubuntu2.1
  ProcVersionSignature: Ubuntu 3.0.0-31.48-generic 3.0.61
  Uname: Linux 3.0.0-31-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Mon Mar  4 11:15:45 2013
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 2
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: vim
  Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
  UpgradeStatus: Upgraded to precise on 2013-03-04 (0 days ago)

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


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


[Touch-packages] [Bug 1394891] Re: evim search fails with message: "E486: Pattern not found: \\/\c" followed by the string searched for

2023-12-05 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 while 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: vim (Ubuntu)
   Status: New => Incomplete

** Tags added: trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1394891

Title:
  evim search fails with message: "E486: Pattern not found: \\/\c"
  followed by the string searched for

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Trusty 64 bit system built from the mini.iso with Openbox as the WM 
and sole DE as well.  Vim version 2:7.4.052-1ubuntu3.  Recently, search has 
started failing about half the time.  In Evim, if I search for "some string 
that IS there somewhere" I'll get the following message:
  E486: Pattern not found: \\/\csome string that IS there somewhere
  as if it had prepended some stuff to what I what I wanted to search for and 
searched for that instead. Whenever it does this it is always the same string
  that gets prepended:
  \\/\c
  Seems the longer the string the more likely it is to happen.

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


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


[Touch-packages] [Bug 253576] Re: Buffer content is lost when opening file over network that doesn't exsist

2023-12-05 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 8.04 (hardy) reached end-of-life on May 12, 2011.

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 while 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: hardy

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/253576

Title:
  Buffer content is lost when opening file over network that doesn't
  exsist

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim

  I'm using VIM 7.1.138 (netrw v109) on Ubuntu 8.04.
  The fastest way to see this bug happening seems to be this:
  1) Start vim, type :e ftp://u...@domain.xxx//path/to/existing/file
  2) Enter the password - file content appears in the buffer.
  3) Type :w
  4) Type :sp ftp://u...@domain.xxx//path/to/NOT/existing/file

  What happens after this is:
  1) 2 new buffers are opened: the first one says '/path/to/NOT/existing/file: 
No such file or directory', and the second is the buffer for that file. You can 
edit that buffer and save it, so a new file is created on the server.
  2) The old buffer which had the contents of 
ftp://u...@domain.xxx//path/to/existing/file is empty.

  I expect that the second consequence above is a bug. If I was in a
  middle of editing in one buffer and opened another which would create
  a new file, all my work on the first one is lost - it's impossible to
  undo any changes, it says 'Already at oldest change', and the old
  buffer is cleared and not saved on the server.

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


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


[Touch-packages] [Bug 808941] Re: gvim in ubuntu is slow when switching tabs or navigating lines

2023-12-05 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 'Incomplete' as it's not seen any
activity for some time. If this is still an issue while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/808941

Title:
  gvim in ubuntu is slow when switching tabs or navigating lines

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  It's been like this forever really. Because I worked both on Ubuntu
  and MacOSX interchangeably I didn't care as much. Now I think maybe
  it's time to finally find out what is wrong with it.

  THE PROBLEM: when I switch tabs or navigate the lines with arrows or
  J,K keys and when I do it repeatedly (as if when trying to find the
  right tab holding Ctrl and hitting Tab) it seems to be delaying the
  action. When I stop hitting the keys gvim may still be finishing the
  operations (for instance, I stop hitting Ctrl+Tab, gvim may switch 5
  more tabs - the number depends on how long I've been hitting Ctrl+Tab
  - before it stops).

  MacVim with similar settings in .vimrc works just fine. The delays are
  present both when Compiz is turned off and turned on. Any ideas?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: vim-gnome 2:7.3.035+hg~8fdc1210-1ubuntu7
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Jul 11 22:24:32 2011
  ExecutablePath: /usr/bin/vim.gnome
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to natty on 2011-06-05 (36 days ago)

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


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


[Touch-packages] [Bug 320700] Re: gvim rendering is slow

2023-12-05 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 while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/320700

Title:
  gvim rendering is slow

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim

  Rendering in gvim is very slow compared to previous Ubuntu releases.
  It's usable, but takes patience. I'm using vim/gvim 7.1.314-3ubuntu3.1
  on Ubuntu 8.10.

  Others have reported this same issue on a thread from the vim mailing list. 
Many solutions have been tried w/o success:
  http://groups.google.com/group/vim_use/browse_thread/thread/dd1d8d9a799adf4a

  From the thread, someone provided this benchmark script:
  -- -- --
  " Benchmark vim's redrawing speed
  let i = 0
  while i < 2000
1
redraw
$
redraw
let i = i + 1
  endwhile
  qa!
  -- -- --

  I've run it with /etc/init.d/README as an input file (just to pick
  something consistent across Ubuntu machines):

  $ time vim -u NONE -U NONE  -S test-redraw-speed.vim /etc/init.d/README 
  real  0m5.407s
  user  0m0.568s
  sys   0m0.048s

  $ time gvim -u NONE -U NONE -f -S test-redraw-speed.vim /etc/init.d/README 
  real  3m27.614s
  user  0m11.685s
  sys   0m0.312s

  As you can see gvim is almost 40x slower then vim (running in gnome-
  terminal). You'd expect gvim to be slower then vim, but not by this
  much. Note, from the thread, not all users experience this huge
  difference. Some only report 2-3x slowdown, which I'd be very happy
  with at this point :)

  I'm using the radeon X11 driver (open source) on a ThinkPad T42p, and
  do _not_ experience slow rendering in other apps (for example, gedit).

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


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


[Touch-packages] [Bug 788481] Re: Unity can't handle two GVIM's at the same time

2023-12-05 Thread Paul White
** Changed in: vim (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/788481

Title:
  Unity can't handle two GVIM's at the same time

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim

  When I open two gvim's at the same time (from the command prompt),
  only one of them has a global menu, the other does not.

  This is not a duplicate of:
  https://bugs.launchpad.net/ubuntu/+source/vim/+bug/781180
  As I see no warnings. Just the first menu works, and the second GVIM has no 
menu. 
  Which also means copy & paste between gvims using menu shortcuts is broken :(
  SInce only one instance has a menu... 
  Alt+E 'C' is probably one of the most common things I do with two gvims 
open...

  Take care,
-stu

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


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


[Touch-packages] [Bug 617841] Re: Gvim 7.2 paste into OpenOffice 3.2.0 fails

2023-12-05 Thread Paul White
Thank you for reporting this bug to Ubuntu.  We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.

Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

This issue may well have been fixed sometime during the 12+ years since
it was reported but as OpenOffice is no longer part of the Ubuntu
distribution I'm closing this as 'Invalid'.

FWIW, I can copy from GVim 8.2 and paste into LibreOffice Writer 7.3 (in
Ubuntu 22.04).



** Changed in: vim (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/617841

Title:
  Gvim 7.2 paste into OpenOffice 3.2.0 fails

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: vim

  Copying something from Gvim, either using the X clipboard or the menu
  commands, and then pasting it into OpenOffice, fails with the error
  "Requested clipboard format is not available". This behavior also
  happens with other programs such as Lotus Notes.

  As a workaround, using Paste Special and selecting plain text format
  (not HTML) will successfully paste the text. Alternatively, setting
  the following option in vim/vimrc prior to copying will also work:

  :set cb=autoselect,html,exclude:cons\|linux

  This bug was introduced in vim 7.2.201 and corrected in 7.2.442 (see
  http://ftp.vim.org/pub/vim/patches/7.2/README)

  Given the LTS status of Ubuntu 10.04 this fix should be trickled down
  to it since it affects basic functionality of Gvim.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: vim-common 2:7.2.330-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Aug 14 14:53:03 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/zsh
  SourcePackage: vim

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


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


[Touch-packages] [Bug 876262] Re: Gvim launcher doesn't appear in dash; appears in launcher with bad icon

2023-12-05 Thread Paul White
In 2023, does this bug have any relevance in a currently supported
release?

** Tags added: natty oneiric trusty

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/876262

Title:
  Gvim launcher doesn't appear in dash; appears in launcher with bad
  icon

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  After installing vim-gnome a shortcut to Gvim text editor is not
  available in the dash. After starting it (e.g. Alt-F2 -> 'gvim') the
  icon it appears with in the launcher is not pretty. This is a
  regression from Ubuntu 11.04.

  /usr/share/applications/gvim.desktop exists in 11.10 and the only
  difference between this and the same file in 11.04 is:

  $ diff 11.10/gvim.desktop 11.04/gvim.desktop 
  75c75
  < Icon=/usr/share/pixmaps/vim.svg
  ---
  > Icon=vim

  Furthermore, the icon used in 11.04 also exists in 11.10.

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


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


[Touch-packages] [Bug 919735] Re: vim.gnome crashed with SIGABRT in raise()

2023-12-05 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.10 (oneiric) reached end-of-life on May 9, 2013.

An almost 11 year old bug report against an Ubuntu release than has been
'end of life' for over 10 years is no longer useful so I'm closing this
as being 'Invalid'.

Please do report any further bugs that you might find while using
Ubuntu.

** Changed in: vim (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/919735

Title:
  vim.gnome crashed with SIGABRT in raise()

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Not sure what caused this: i was editing some files, and don't recall
  doing something particularly unusual.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: vim-gnome 2:7.3.154+hg~74503f6ee649-2ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Jan 20 23:49:27 2012
  ExecutablePath: /usr/bin/vim.gnome
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: vim campaigns/workers/base.py
  Signal: 6
  SourcePackage: vim
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   free () from /lib/x86_64-linux-gnu/libc.so.6
  Title: vim.gnome crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: admin

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


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


[Touch-packages] [Bug 967084] Re: vim.gtk crashed with SIGSEGV in update_screen()

2023-12-05 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 closing this as 'Invalid' as neither the Ubuntu release or Vim
release are currently supported.

Please create a new bug report if you still see the reported problem in
a currently supported release of Ubuntu.



** Changed in: vim (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/967084

Title:
  vim.gtk crashed with SIGSEGV in update_screen()

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Vim crashed when I tried to quit.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: vim-gtk 2:7.3.429-2ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar 28 14:10:55 2012
  ExecutablePath: /usr/bin/vim.gtk
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: vim comm.c
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   TERM=screen-256color
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   update_screen ()
   main_loop ()
   main ()
  Title: vim.gtk crashed with SIGSEGV in update_screen()
  UpgradeStatus: Upgraded to precise on 2012-02-14 (43 days ago)
  UserGroups: adm admin cdrom dialout disk libvirtd lpadmin plugdev sambashare

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


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


[Touch-packages] [Bug 1065264] Re: gview does not display scrollbars where gvim does

2023-12-05 Thread Paul White
Using Ubuntu 20.04 and 22.04 I'm not seeing the reported issue.

There have been no comments supporting the reported bug for over 11
years so as the status is 'Confirmed' I'm closing this as being fixed.

** Tags added: precise

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1065264

Title:
  gview does not display scrollbars where gvim does

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  $lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  $ apt-cache policy vim-gnome
  vim-gnome:
Installed: 2:7.3.429-2ubuntu2.1
Candidate: 2:7.3.429-2ubuntu2.1

  Expected:
  Opening files in gview/gvimdiff (both /etc/alternatives point at vim.gnome) 
that do not fit in the window should result in scrollbars the same way they do 
in gvim.

  Instead:
  No visable scrollbars. Clicking and holding in the area where I would expect 
a scrollbar sometimes produced the scrollbar that is present in Gnome Terminal. 
 This is not the same scrollbar as present in gvim and it is only visible while 
you click and hold.

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


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


[Touch-packages] [Bug 793703] Re: Format string bug in shtags.pl

2023-12-05 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 closing this bug report as 'Invalid' as no version information was
given for either Vim or Ubuntu and as over twelve years have passed
without comment it is unlikely that an Ubuntu developer will even look
at a bug report which probably needs to be fixed upstream by a Vim
developer.


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/793703

Title:
  Format string bug in shtags.pl

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: vim-runtime

  vim/vim73/tools/shtags.pl have format string bug .

  test case :
  emanuel@emanuel-desktop:~$ echo 1 > '/tmp/a%n'
  emanuel@emanuel-desktop:~$ /usr/share/vim/vim73/tools/shtags.pl '/tmp/a%n'
  Modification of a read-only value attempted at 
/usr/share/vim/vim73/tools/shtags.pl line 142, <> line 1.

  the bug can be found at :
  printf "Using $shell for $ARGV\n";

  fix : use %s for $shell and $ARGV
  printf "Using %s for %s\n" , $shell , $ARGV ;

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


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


[Touch-packages] [Bug 1282345] Re: vim crashes on ruby files with very long lines

2023-12-05 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 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 is still an issue while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1282345

Title:
  vim crashes on ruby files with very long lines

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  1.  edit a file to be called test in vim:  vi test.
  2.  Insert the following line:
  vln = 
"Nowisthetimeforareallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyr
 
eallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallreallyreallyreallyreallyreallyy"
  3.  Play with the file to reassure you have no problem editing it.
  4.  Exit vi and mv test test.rb.
  5.  vi test.rb.  Note that now the file freezes up.  You can exit the 
terminal, and try going back and forth.  It is 100%.  When the file is called 
test.rb, it freezes up, apparently from formatting for ruby.  When it is called 
just test, it is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: vim 2:7.4.000-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed Feb 19 17:37:36 2014
  InstallationDate: Installed on 2013-10-25 (117 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (117 days ago)

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


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


[Touch-packages] [Bug 1305778] Re: Misinterpretation of key sequence

2023-12-05 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 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 is still an issue while 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: vim (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1305778

Title:
  Misinterpretation of key sequence

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.10
  Vim:   Installed: 2:7.4.000-1ubuntu2

  Entering the commands to leave insert mode & insert a new line above
  the current one, beginning with certain letters, results in
  punctuation on the current line instead.

  To reproduce:
  Start vim, *quickly* type the keys: iOm

  Expected result:
  New line created above the current one with the letter 'm' in it

  Actual result:
  Hyphen inserted on current line

  Also affects:
  Letters j,k,n,o
  j gives *, k gives +, m gives -, n gives ., o gives /

  Vim version: 7.4 (as installed by Ubuntu 13.10)
  Happens on my machine, my co-worker's machine, several VMs and to some (not 
all) of the people I asked about it on IRC. Definitely requires that the typing 
is done quickly. Causes me problems very frequently because I write a lot of 
Perl and when I go to declare a variable, I get "-y $foo" on the current line 
instead of "my $foo" on the previous line.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: vim 2:7.4.000-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Apr 10 11:51:03 2014
  InstallationDate: Installed on 2013-11-27 (134 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1314238] Re: Account logged off when gvim is started from terminal

2023-12-05 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 while 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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1314238

Title:
  Account logged off when gvim is started from terminal

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  The issue:

  When I open a terminal and start gvim with gvim command, I'm
  immediately logged off. Before the login dialog appears, a text-only
  framebuffer appears briefly with nothing but cursor blinking on the
  first line, which leads me to believe it's an Unity or X crash.

  I have just installed a fresh copy of 14.04.

  unity version 7.2.0+14.04.20140416-0ubuntu1
  vim-runtime version 2:7.4.052-1ubuntu3

  This happens with both vim-gtk and vim-gnome packages.

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


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


[Touch-packages] [Bug 1380110] Re: comments inside parentheses mess up the syntax coloring of shell script

2023-12-05 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.

No version information has been given and with no comments for over nine
years I'm closing this as 'Invalid'. If this issue is still relevant in
a currently supported release of Ubuntu then please let us know which
one(s) so that the Ubuntu developers can focus their attention on
specific Ubuntu releases.

You should also then change the status of the bug report back to 'New'.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1380110

Title:
  comments inside parentheses mess up the syntax coloring of shell
  script

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I've found the following bug with syntax coloring of shell scripts in vi and 
vim.
  If you add comments outside parenthesis, it works fine.
  But if you add comments inside parenthesis, or worse comments with quotes, 
the syntax coloring is totally messed up.

  I join a sample shell script to demonstrate the bug.

  Best regards,
 Laurent Lyaudet

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


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


[Touch-packages] [Bug 1334168] Re: vim defaults for tm and ttm are wrong

2023-12-05 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 while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1334168

Title:
  vim defaults for tm and ttm are wrong

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  While scouring the net for info on curious lag in vim that can eat keystrokes
  (devastating over a laggy link, which is one of the primary situations where
  vim is useful), every conversation pointed me to `:help ttm`, which says:

  A useful setting would be 
  :set timeout timeoutlen=3000 ttimeoutlen=100
  (time out on mapping after three seconds, time out on key codes after a
  tenth of a second).

  So it appears that insead of putting the correct defaults in as the defaults,
  vim chose to bury the information deep inside the documentation.

  As a distro packaging vim, we have an opportunity to fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: vim 2:7.4.052-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 25 10:01:05 2014
  InstallationDate: Installed on 2014-05-29 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1647771] Re: Undefined variable in vim netrw when netrw_browse_split = 3

2023-12-05 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 while 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: xenial

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1647771

Title:
  Undefined variable in vim netrw when netrw_browse_split = 3

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  To reproduce, open the netrw explorer in a new tab, and set opened
  files to go to a new tab:

  :let g:netrw_browse_split = 3
  :Texplore

  When the user selects a file from the explorer with Enter, this error
  appears:

  Error detected while processing function 20_NetrwBrowseChgDir:
  line  135:
  E121: Undefined variable: b:netrw_curdir

  And this is displayed for a second:

  Invalid arguments for function SetRexDir

  Saw this after upgrade to Ubuntu 16.04 (vim 7.4.1689-3ubuntu1.2). The
  error didn't show with vim 7.4.052-1ubuntu3.1 on Ubuntu-14.04.

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


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


[Touch-packages] [Bug 1756418] Re: Error detected while processing /usr/share/vim/vim80/debian.vim

2023-12-05 Thread Paul White
*** This bug is a duplicate of bug 1754999 ***
https://bugs.launchpad.net/bugs/1754999

** This bug has been marked a duplicate of bug 1754999
   Error detected while processing /usr/share/vim/vim80/debian.vim:

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1756418

Title:
  Error detected while processing /usr/share/vim/vim80/debian.vim

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  Just after virsh edit domain:

   Error detected while processing /usr/share/vim/vim80/debian.vim:
  line   29:
  E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
  line   30:
  E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
  line   34:
  E319: Sorry, the command is not available in this version:   endfor
  line   35:
  E319: Sorry, the command is not available in this version:   return 0
  line   36:
  E319: Sorry, the command is not available in this version: endfunction
  Press ENTER or type command to continue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim-common 2:8.0.1401-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 19:34:33 2018
  InstallationDate: Installed on 2018-02-27 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227)
  PackageArchitecture: all
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 560217] Re: vim-gnome omnicompletion mousewheel bug

2023-12-05 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 9.10 (karmic) reached end-of-life on April 30, 2011.

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 while 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: karmic

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/560217

Title:
  vim-gnome omnicompletion mousewheel bug

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim-gnome

  Huge version with GTK2-GNOME GUI version has the mousewheel broken on
  the omni complete popup.

  It works on the command version in gnome-terminal.

  9.10 / vim 7.2

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


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


[Touch-packages] [Bug 96263] Re: vim crashed with sigsegv

2023-12-05 Thread Paul White
Thank you for reporting this bug to Ubuntu.  We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.

Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

A sixteen year old bug report with few subsequent comments is of little
use to Ubuntu's developers in 2023 so I'm closing this as 'Invalid'.

If you're still using Ubuntu them please do continue to report any bugs
that you might find.

** Changed in: vim (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/96263

Title:
  vim crashed with sigsegv

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Vim crashes on my feisty machine; it's reproducible at least twice.  I
  have a core file which shows this traceback:

(gdb) bt
  #0  0xe410 in __kernel_vsyscall ()
  #1  0xb712c226 in kill () from /lib/tls/i686/cmov/libc.so.6
  #2  0x08149da7 in may_core_dump () at os_unix.c:2900
  #3  0x0814be18 in mch_exit (r=1) at os_unix.c:2865
  #4  0x0810fa60 in preserve_exit () at misc1.c:8277
  #5  
  #6  do_highlight (line=0x81f20dc "", forceit=0, init=1) at syntax.c:6752
  #7  0x0818f227 in init_highlight (both=1, reset=0) at syntax.c:6336
  #8  0x080f9ec3 in main (argc=Cannot access memory at address 0x4
  ) at main.c:546

  I don't know what changed to break this, it was working a moment ago
  and I didn't upgrade it.

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


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


[Touch-packages] [Bug 84735] Re: [apport] package vim-tiny failed to install/upgrade:

2023-12-05 Thread Paul White
Thank you for reporting this bug to Ubuntu.  We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.

I'm closing this as 'Invalid' as no version information has been
provided and there has been no comments for over sixteen years.

** Changed in: vim (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/84735

Title:
  [apport] package vim-tiny failed to install/upgrade:

Status in vim package in Ubuntu:
  Invalid

Bug description:
  [apport] package ubuntu-minimal failed to install/upgrade:

  ProblemType: Package
  Date: Mon Feb 12 13:20:01 2007
  ErrorMessage:
   ErrorMessage: dependency problems - leaving unconfigured
  Package: ubuntu-minimal
  SourcePackage: ubuntu-meta

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


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


[Touch-packages] [Bug 472082] Re: gvim corrupts text after Jaunty -> karmic upgrade

2023-12-05 Thread Paul White
Thank you for reporting this bug to Ubuntu.  We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.

A fourteen year old bug report which details an upgrade between releases
which were both 'end of life' over twelve years ago is not useful in
2023 so I'm closing this as 'Invalid'.

Please *do* report any problems that you might see when upgrading
currently supported Ubuntu releases.


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/472082

Title:
  gvim corrupts text after Jaunty -> karmic upgrade

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: vim

  The installed gvim application was running fine under Jaunty (on an
  IBM T30). Now, having upgraded to Karmic (but booted into 2.6.28-14 -
  owing to consistent failure to boot to 2.6.31-14 documented
  elsewhere), the application opens showing an initial screen on which
  all text is corrupted and wholly unreadable. On entering insert mode,
  all text entered text is displayed in corrupt fashion. If the gvim
  window is minimised and then subsequently recovered, any text is
  rendered readable ... any new text inserted is unreadable until such
  time as the window undergoes another minimise/maximise cycle.

  The fault isn't, AFAICT, related to the font selected in the window -
  the same behaviour is exhibited irrespective of the selected font.

  The attached screen shot shows the state of the app after some text
  had been entered, a minimise/maximise cycle undergone, followed by
  further text entry.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Nov  3 02:35:30 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/vim.gnome
  Package: vim-gnome 2:7.2.245-2ubuntu2
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.28-14.47-generic
  SourcePackage: vim
  Uname: Linux 2.6.28-14-generic i686

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


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


[Touch-packages] [Bug 788481] Re: Unity can't handle two GVIM's at the same time

2023-12-05 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 'Incomplete' as it's not seen any
activity for some time. If this is still an issue while 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: natty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/788481

Title:
  Unity can't handle two GVIM's at the same time

Status in vim package in Ubuntu:
  New

Bug description:
  Binary package hint: vim

  When I open two gvim's at the same time (from the command prompt),
  only one of them has a global menu, the other does not.

  This is not a duplicate of:
  https://bugs.launchpad.net/ubuntu/+source/vim/+bug/781180
  As I see no warnings. Just the first menu works, and the second GVIM has no 
menu. 
  Which also means copy & paste between gvims using menu shortcuts is broken :(
  SInce only one instance has a menu... 
  Alt+E 'C' is probably one of the most common things I do with two gvims 
open...

  Take care,
-stu

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


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


[Touch-packages] [Bug 751726] Re: gvim icon is low-res and blurry in Unity

2023-12-05 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 'Incomplete' as it's not seen any
activity for some time. If this is still an issue while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/751726

Title:
  gvim icon is low-res and blurry in Unity

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim

  The icon used for gvim in Unity is a low-res bitmap.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: vim-gnome 2:7.3.035+hg~8fdc1210-1ubuntu7
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Tue Apr  5 20:48:39 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1768026] Re: echo message hides cursor

2023-12-05 Thread Paul White
Further to comment #3:

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

All currently supported releases as of today's date, that is focal and
later, include this patch so I'm closing this bug report as being fixed.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1768026

Title:
  echo message hides cursor

Status in vim:
  Fix Released
Status in vim package in Ubuntu:
  Fix Released

Bug description:
  https://github.com/w0rp/ale/issues/1536#issuecomment-385056702
  upstream bug https://github.com/vim/vim/issues/2612

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim 2:8.0.1453-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 14:16:35 2018
  InstallationDate: Installed on 2017-05-17 (347 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: vim
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago)

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


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


[Touch-packages] [Bug 1454016] Re: "c{motion}" temporary cancels 'linebreak' option for current line

2023-12-05 Thread Paul White
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Patch will be included in all currently supported releases of Ubuntu so closing 
as being fixed.


** Tags added: vivid

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

** Also affects: vim via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774492
   Importance: Unknown
   Status: Unknown

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

** No longer affects: vim

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1454016

Title:
  "c{motion}" temporary cancels 'linebreak' option for current line

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  When editing long text using the c command, vim seems to temporarily
  disable the "linebreak" option. This can be very annoying when editing
  long lines of text.

  A thorough discussion of this bug can be found in the Debian BTS
  774492 (http://bugs.debian.org/774492)

  I am encountering this bug on Ubuntu 15.04 running vim
  2:7.4.488-3ubuntu2.

  Debian fixed this issue by backporting patch 7.4.576 into the vim
  package 2:7.4.488-7. It would be great if Ubuntu could backport/sync.

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


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


[Touch-packages] [Bug 1195448] Re: Gvim problem

2023-12-05 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.
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 while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1195448

Title:
  Gvim problem

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Upon lauchaing GVIM to update a shell file I get
  (gvim:335): GLib-GObject-WARNING **: cannot retrieve class for invalid 
(unclassed) type `'
  The file is loaded without problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: vim-gnome 2:7.3.429-2ubuntu2.1
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic-pae 3.2.46
  Uname: Linux 3.2.0-48-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: i386
  Date: Thu Jun 27 12:54:21 2013
  ExecutablePath: /usr/bin/vim.gnome
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1570393] Re: vim 'autochdir' doesn't work for the first file

2023-12-05 Thread Paul White
No version information given as to which Ubuntu release was affected by
the reported issue.

I'm closing this as 'Fixed Released' as in 2023 all currently supported
releases of Ubuntu will include the Vim patch referred to in the bug
description.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1570393

Title:
  vim 'autochdir' doesn't work for the first file

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  Please, update at least to version 7.4.1716 that fixes this issue with
  `autochdir`.

  https://github.com/vim/vim/releases/tag/v7.4.1716

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


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


[Touch-packages] [Bug 938469] Re: vim cannot regain control of mouse

2023-12-05 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 while 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: vim (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/938469

Title:
  vim cannot regain control of mouse

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  In Precise, vim is unable to reassert control of the mouse once it has
  started. The mouse works normally upon starting vim. If it loses
  control of the mouse in the pseudo-terminal, however, perhaps due to
  being suspended with ^Z, or turning the mouse off with ':set mouse=',
  then vim becomes unable to regain control of the mouse when it should,
  such as being resumed or ':set mouse=a'.

  The expected behavior is that suspending should have no effect on the
  mouse within vim, and clearing and resetting the mouse variable should
  also have no effect on the mouse.

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


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


[Touch-packages] [Bug 1074454] Re: resize during insert problem

2023-12-05 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.10 (quantal) reached end-of-life on May 16, 2014.

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 while 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: quantal

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1074454

Title:
  resize during insert problem

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  resize during insert seems to cause a problem.  to reproduce:
  create a textfile using the 21 lines of text given below.
  resize an xterm to 12 lines long and 80 characters wide.
  in the xterm, edit (vim) the textfile.
  position the cursor on the / preceeding "vmlinuz", and type
  cB/
  (with no escape)(still in insert mode)
  resize the xterm to 10 lines by 80 characters.
  vim is now in an inconsistent state.
  the first visible cue is the disappearance of text following the cursor.
  further inserted characters appear to insert on the wrong line.
  as things progress it may recover itself, or it may ABRT or SEGV.
  for example if at this point i
  hit  (end the insert)
  type :ls (with no CR)
  enlarge the window
  i get
  Vim: Caught deadly signal SEGV
  Vim: preserving files...
  and it hangs thus.

  
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 uuid  
960c92bd-69d3-415f-93b6-2242187e3557
 kernel/SL-60-i386/Install-DVD/vmlinuz quiet panic=30 method=hd:sda7: 
ksdevice=
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
 initrd/SL-60-i386/Install-DVD/initrd.img
  

  $  lsb_release -rd
  Description:Ubuntu 12.10
  Release:12.10
  $  apt-cache policy vim
  vim:
Installed: 2:7.3.547-4ubuntu1
Candidate: 2:7.3.547-4ubuntu1
Version table:
   *** 2:7.3.547-4ubuntu1 0
  500 http://ie.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
  100 /var/lib/dpkg/status

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


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


[Touch-packages] [Bug 1157538] Re: vim.basic crashed with SIGSEGV in modify_fname()

2023-12-05 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 13.10 (saucy) reached end-of-life on July 17, 2014.

I'm setting the status of this bug to 'Invalid' as it's not seen any
activity for some time and no-one has confirmed the issue.

If this is still an problem while using a currently maintained release
of Ubuntu then please let us know which one(s) and revert the status
back to 'New'.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1157538

Title:
  vim.basic crashed with SIGSEGV in modify_fname()

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  creating a desktop launcher

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: vim 2:7.3.547-6ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
  Uname: Linux 3.8.0-12-generic i686
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Wed Mar 20 04:49:43 2013
  ExecutablePath: /usr/bin/vim.basic
  InstallationDate: Installed on 2013-03-15 (4 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130314)
  MarkForUpload: True
  ProcCmdline: vim
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   modify_fname ()
   _r_debug ()
   ?? ()
   ?? ()
  Title: vim.basic crashed with SIGSEGV in modify_fname()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


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


[Touch-packages] [Bug 616858] Re: Mouse cursor in gvim is sometimes invisible

2023-12-05 Thread Paul White
Thank you for reporting this bug to Ubuntu.  We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.

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

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 while 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: lucid quantal

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/616858

Title:
  Mouse cursor in gvim is sometimes invisible

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim-gnome

  In some cases the mouse cursor within a gvim window disappears.  It is
  still there, just not visible, or under the window.  Left clicking and
  selecting text will make it reappear.  Searching within gvim for
  matching text can (sometimes) make the cursor disappear again.  This
  doesn't happen with every gvim window opened up, but even if it didn't
  happen when first opened, searching will cause it to disappear again.

  
  [opiet@doodle ~] --> lsb_release -rd
  Description:  Ubuntu 10.04.1 LTS
  Release:  10.04
  [opiet@doodle ~] --> 

  [opiet@doodle ~] --> apt-cache policy vim-gnome
  vim-gnome:
Installed: 2:7.2.330-1ubuntu3
Candidate: 2:7.2.330-1ubuntu3
Version table:
   *** 2:7.2.330-1ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
  100 /var/lib/dpkg/status
  [opiet@doodle ~] -->

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


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


[Touch-packages] [Bug 1069413] Re: Remove vim-tiny from install media

2023-12-05 Thread Paul White
** Package changed: vim (Ubuntu) => ubuntu-seeds

** Project changed: ubuntu-seeds => ubuntu-meta (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1069413

Title:
  Remove vim-tiny from install media

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Finally with Ubuntu 12.10 the full VIM is installed by default.
  However, the package vim-tiny is _also_ installed, and frustratingly
  it is the vim-tiny binary that is used when typing 'vim' on the CLI.
  Please remove the vim-tiny package from the default install as it is
  1) redundant now that full VIM is installed by default, and 2) harmful
  in the fact that it masks the VIM binary.

  Note that there was a request to remove vim-tiny back in 2007, but it was 
(rightfully) rejected at the time due to space considerations in the install 
media. Now, removing vim-tiny will actually save space due to full VIM being 
installed by default anyway:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/100029

  Thanks.:wq

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


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


[Touch-packages] [Bug 1584539] Re: 16.04 regression: exceptions in ruby code in plugins have started causing vim to segfault

2023-12-05 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 while 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: vim (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1584539

Title:
  16.04 regression: exceptions in ruby code in plugins have started
  causing vim to segfault

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  In 14.04, an exception in the ruby code of a plugin caused the error
  to be printed to stderr, after which vim would launch, skipping the
  offending plugin:

Error detected while processing 
/mnt/terra/home/simon/dev/vim-livecoding/plugin/livecoding.vim:
line   37:
NameError: undefined local variable or method 
`undefined_method_causing_an_exception' for main:Object
Press ENTER or type command to continue

  But in 16.04, the same thing causes vim to segfault:

Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped)

  ---

  Vim version in 14.04:
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan  2 2014 19:39:59)
Included patches: 1-52
Modified by pkg-vim-maintain...@lists.alioth.debian.org
Compiled by buildd@
Huge version with GTK2 GUI. 

  Vim version in 16.04:
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28)
Included patches: 1-1689
Modified by pkg-vim-maintain...@lists.alioth.debian.org
Compiled by pkg-vim-maintain...@lists.alioth.debian.org
Huge version with GTK2 GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vim-gtk 2:7.4.1689-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun May 22 22:33:45 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-04-25 (392 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (0 days ago)

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


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


[Touch-packages] [Bug 1971090] Re: OS fully crashes when I exit an app folder.

2023-12-05 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 has been filed against 'vim' but the bug description says that 
vim is not installed.
You say 'When I leave a app folder in a specific place' but what does that 
mean? Which app?

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 while 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: vim (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1971090

Title:
  OS fully crashes when I exit an app folder.

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  When I leave a app folder in a specific place, the OS crashes and I
  need to do a force shut down to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vim (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  1 10:17:57 2022
  InstallationDate: Installed on 2021-05-31 (334 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1903057] Re: vim confused by \~/

2023-12-05 Thread Paul White
** Also affects: vim via
   https://github.com/vim/vim/issues/8015
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1903057

Title:
  vim confused by \~/

Status in vim:
  Unknown
Status in vim package in Ubuntu:
  New

Bug description:
   $ cd
   $ mkdir \~
   $ echo content a>\~/a
   $ echo content b>b
   $ less \~/a b
  :n
  :e#
  :q
   $ vim \~/a b
  :n
  :e#

  less is not confused, but vim has forgotten where the first file was.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim 2:8.0.1453-1ubuntu1.3
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Nov  5 08:50:54 2020
  InstallationDate: Installed on 2019-11-16 (354 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1230374] Re: vi editor for loop syntax problem

2023-12-05 Thread Paul White
Closing as 'Invalid' as a 10 year old bug report with no version
information and no comments for some time is of little use to the
developers of currently supported releases of Ubuntu.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1230374

Title:
  vi editor for loop syntax problem

Status in vim package in Ubuntu:
  Invalid

Bug description:
  for (( i=0; i<=5; i++ ))
  do
  echo "$i Echoed"
  done

  this is what wrote in "bubble.sh" with vi editor and it gave me this error 
"bubble.sh: 1: bubble.sh: Syntax error: Bad for loop variable
  "
  i don't seem to understand why this is happening..please help

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


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


[Touch-packages] [Bug 1745889] Re: Cron overloading system since update to 17.10

2023-12-05 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 while 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: artful

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1745889

Title:
  Cron overloading system since update to 17.10

Status in Ubuntu:
  Incomplete

Bug description:
  Prior to updating to 17.10 this issue did not exist.
  Since the update pam_unix(cron:session): session opened for user root by 
(uid=0)
  Happens after a short time of being logged in through webmin.
  None of the cron systems prior to hand were edited.
  Whatever is going on is nearly maxing out CPU usage and if you are one webmin 
you get a message the connection was lost.

  pam_unix(cron:session): session opened for user root by (uid=0)
  Fills up the log file once it starts.

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


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


[Touch-packages] [Bug 320478] Re: Backport fix for bug 270386 to 8.04 LTS?

2023-12-05 Thread Paul White
Closing as 'Invalid' but should be 'Wont Fix' as Ubuntu 8.04 was EOL in
2011.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/320478

Title:
  Backport fix for bug 270386 to 8.04 LTS?

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: vim

  There is a reproducible bug in vim, bug #270386, which was marked as
  closed because it appears fixed in Ubuntu 8.10.  Are there any plans
  on fixing this bug in 8.04 LTS?

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


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


[Touch-packages] [Bug 1822688] Re: it does not print on printer

2023-12-05 Thread Paul White
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

This bug report has been filed against the 'vim' package but according
to the bug description vim is not installed so I'm closing this as
'Invalid'.

If the reported problem is still an issue while using a currently
supported release of Ubuntu then please create a new bug report fully
describing the bug that you are seeing and confirm the application that
is being used.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1822688

Title:
  it does not print on printer

Status in vim package in Ubuntu:
  Invalid

Bug description:
  os: ubuntu 18.04.2  ,trying to print with Canon Imageclass MF 6530
  .message says: printing completed, but it does not print the
  document.dell computer xps 8930

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 15:50:56 2019
  InstallationDate: Installed on 2019-03-29 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1535809] Re: Segfaults in current vim in xenial (16.04)

2023-12-05 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 while 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: xenial

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1535809

Title:
  Segfaults in current vim in xenial (16.04)

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Version: 2:7.4.826-1ubuntu2

  I can't tell what causes it, but i haven't gotten such segfaults in
  14.04 and my vimrc was the same. From vims changelog i see some
  segfaulting has been fixed in newer revisions.

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


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


[Touch-packages] [Bug 1659542] Re: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

2023-12-05 Thread Paul White
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

Probably just a bad package download for which:
  apt-get clean, apt-get update, apt-get install vim-common
would have fixed the issue.


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1659542

Title:
  package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Cannot run package manager

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vim-common 2:7.4.1689-3ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   vim-common: Configure
   vim-tiny: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jan 26 04:17:45 2017
  DpkgTerminalLog:
   dpkg: error processing package vim-common (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-01-13 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.15ubuntu0.2
  SourcePackage: vim
  Title: package vim-common 2:7.4.1689-3ubuntu1.2 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/vim/+bug/1659542/+subscriptions


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


[Touch-packages] [Bug 2044130] Re: "Ubuntu Software" keeps telling me "an important update has been made" for the same "UEFI dbx" at every boot.

2023-11-21 Thread Paul White
*** This bug is a duplicate of bug 2024392 ***
https://bugs.launchpad.net/bugs/2024392

** This bug has been marked a duplicate of bug 2024392
   Gnome-software displays notification about OS upgrade on each boot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2044130

Title:
  "Ubuntu Software" keeps telling me "an important update has been made"
  for the same "UEFI dbx" at every boot.

Status in apport package in Ubuntu:
  New

Bug description:
  At every boot (maybe also every new login, haven't tried that),
  "Ubuntu Software" pops up and tells me it updated an important
  component, and when clicking to review for more information, it's
  always "UEFI dbx".

  I dont think that this thing is always updated (I also didn run and
  updates with apt or the GUI), it looks like a bug in "Ubuntu
  software".

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


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


[Touch-packages] [Bug 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

2023-11-14 Thread Paul White
** Tags added: mantic

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2043442

Title:
  /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

Status in ibus package in Ubuntu:
  New

Bug description:
  Apport captured a system freeze [crash] which required a hard reboot.
  However I could not confirm that the report was successfully uploaded.

  The /var/log/apport.log entry is as follows.
  
  ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable already 
crashed 2 times, ignoring
  INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report 
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
  INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  Note:The last line may explain why I could not verify the file
  upload when I performed the following proceedure per:
  https://help.ubuntu.com/community/ReportingBugs

  ---
  luigi@l-g905:~$ ubuntu-bug /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash

  luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
  
7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80

  
https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
 No such file or directory
  -

  
  This upload fialure seemed confirmed when in: 
https://answers.launchpad.net/ubuntu/+questions?
  a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
  "ibus-ui-gtk3" is not mentioned in the release notes bugs section.

  In
  https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
  text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above both 
returned "phrase not found"

  I reproduced the executable failure using Terminal with these results
  --
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  Returns:
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  ** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global

  Trace/breakpoint trap (core dumped)
  -

  I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file
  /var/crash/ _ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines
  - modified on 11/13/23 9:07 PM - US-ASCII)

  Platform Information 
  Operating System: Ubuntu Studio 23.10
  KDE Plasma Version:   5.27.8
  KDE Frameworks Version:   5.110.0
  Qt Version:   5.15.10
  Kernel Version:   6.5.0-10-lowlatency (64-bit)
  Graphics Platform:Wayland
  Processors:   24 × AMD Ryzen 9 7900X 12-Core Processor
  Memory:   31.0 GiB of RAM
  Graphics Processor:   NV172
  Manufacturer: MicroElectronics
  Product Name: G905
  System Version:   1.0

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


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


[Touch-packages] [Bug 2043321] Re: intel ekran kartı çalışmıyor

2023-11-13 Thread Paul White
** Description changed:

  intel ekran kartı çalışmıyor hatalı sürücüler var
+ 
+ Google translates as:
+ Intel graphics card is not working, there are faulty drivers
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 18:43:17 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) 
(prog-if 00 [VGA controller])
-Subsystem: Dell Iris Plus Graphics G1 (Ice Lake) [1028:09e8]
+  Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) 
(prog-if 00 [VGA controller])
+    Subsystem: Dell Iris Plus Graphics G1 (Ice Lake) [1028:09e8]
  InstallationDate: Installed on 2023-11-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Inspiron 14 5401
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=tr_TR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=tr_TR.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.25.0
  dmi.board.name: 06DNFY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.0:bd09/19/2023:br1.25:svnDellInc.:pnInspiron145401:pvr:rvnDellInc.:rn06DNFY:rvrA02:cvnDellInc.:ct10:cvr:sku09E8:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 14 5401
  dmi.product.sku: 09E8
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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

** Summary changed:

- intel ekran kartı çalışmıyor
+ intel ekran kartı çalışmıyor (Intel graphics card not working)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2043321

Title:
  intel ekran kartı çalışmıyor (Intel graphics card not working)

Status in xorg package in Ubuntu:
  New

Bug description:
  intel ekran kartı çalışmıyor hatalı sürücüler var

  Google translates as:
  Intel graphics card is not working, there are faulty drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 18:43:17 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Iris Plus Graphics G1 (Ice Lake) [1028:09e8]
  InstallationDate: Installed on 2023-11-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Inspiron 14 5401
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.25.0
  dmi.board.name: 06DNFY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 2043255] Re: Wayland user session terminates when screen is disabled on inactivity

2023-11-13 Thread Paul White
** Package changed: xorg (Ubuntu) => wayland (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2043255

Title:
  Wayland user session terminates when screen is disabled on inactivity

Status in wayland package in Ubuntu:
  New

Bug description:
  Reproducibly, the user is logged out the moment the screen gets
  disabled due to inactivity. Can be worked around by disabling the
  "screen disabling on inactivity" feature in the system settings.

  Issue started after upgrade from 23.04 to 23.10. Wayland is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 09:21:02 2023
  DistUpgraded: 2023-11-03 18:23:57,803 DEBUG icon theme changed, re-reading
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Lucienne [17aa:5097]
  InstallationDate: Installed on 2021-08-27 (806 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=86fa7801-2441-4de0-bdff-28c460a157ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (8 days ago)
  dmi.bios.date: 05/17/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1OET27W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20YHS00A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1OET27W(1.06):bd05/17/2021:br1.6:efr1.6:svnLENOVO:pn20YHS00A00:pvrThinkPadE15Gen3:rvnLENOVO:rn20YHS00A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YH_BU_Think_FM_ThinkPadE15Gen3:
  dmi.product.family: ThinkPad E15 Gen 3
  dmi.product.name: 20YHS00A00
  dmi.product.sku: LENOVO_MT_20YH_BU_Think_FM_ThinkPad E15 Gen 3
  dmi.product.version: ThinkPad E15 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  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/wayland/+bug/2043255/+subscriptions


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


[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

2023-11-13 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

Comments #50 and #51 suggest that this issue may have been fixed in a
recent release of Ubuntu.

Does anyone when using the hardware that was being used when making the
initial report still experience the reported issue?


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Once every couple hours, the internal laptop display goes black for a
  few seconds.

  This was reproducible:
  + With the laptop connected to a port replicator and the external display 
connected into the port replicator DP port via DP-DVI adapter. The external 
display remains on during this time.
  + With the laptop not connected into a port replicator but connected to an 
external display. The external display remains on during this time.
  + With the laptop not connected to either a port replicator or an external 
display.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1. The problem started immediately
  after the drive move.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  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.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 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

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


-- 
Mailing list: 

[Touch-packages] [Bug 1592544] Re: ubuntu is using gallium graphics instead of intel graphics

2023-11-13 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

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

Do you still see a problem related to the one that was reported when
using a currently supported version of  Ubuntu?

If so, please let us know which currently supported releases(s) are
affected otherwise this bug report can be left to expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1592544

Title:
  ubuntu is using gallium graphics instead of intel graphics

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  xorg file empty, I tried to uninstall the gallium drivers but it
  didn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.27  Thu Jun  9 18:53:27 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.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: Tue Jun 14 21:50:15 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   nvidia-367, 367.27, 4.4.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05fe]
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe]
  InstallationDate: Installed on 2016-04-25 (50 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 15 9530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=f565161c-e76f-4b59-b989-60ea2a0b51a6 ro nomodeset nomodeset 
nouveau.modeset=0
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-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: Tue Jun 14 21:48:10 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

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


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


[Touch-packages] [Bug 2042987] Re: The settings of different Wi-Fi adapters do NOT work separately.

2023-11-08 Thread Paul White
** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2042987

Title:
   The settings of different Wi-Fi adapters do NOT work separately.

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

Bug description:
  The settings of different Wi-Fi adapters do NOT work separately.

  The Wi-Fi switch triggers all Wi-Fi adapters, and the Saved Networks lists do 
NOT be saved separately.
  Hope this bug can be fixed soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-settings 23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 08:54:37 2023
  InstallationDate: Installed on 2023-07-29 (101 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: Upgraded to mantic on 2023-08-16 (83 days ago)

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


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


[Touch-packages] [Bug 2033142] Re: ubuntu-bug doesn't work for snap-store

2023-10-22 Thread Paul White
** Also affects: apport (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2033142

Title:
  ubuntu-bug doesn't work for snap-store

Status in snap-store-desktop:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  When I run ubuntu-bug with snap-store's PID,

  ```
  ubuntu-bug $(pgrep snap-store)
  ```

  it errors out with:

  > The problem cannot be reported:
  > This package does not seem to be installed correctly

  and another message box:

  > The problem cannot be reported:
  > snap-store is provided by a snap published by canonical. No contact
  > address has been provided; visit the forum at ... for help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/2033142/+subscriptions


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


[Touch-packages] [Bug 2039660] Re: wayland application not inputting accentuated caps characters after upgrade to 23.10

2023-10-18 Thread Paul White
** Package changed: ubuntu => wayland (Ubuntu)

** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2039660

Title:
  wayland application not inputting accentuated caps characters after
  upgrade to 23.10

Status in mutter package in Ubuntu:
  New
Status in Fedora:
  Unknown

Bug description:
  After upgrading to 23.10 from 23.04, I am unable to input accentuated
  caps chars like « É ».

  STR:
   - Configure keyboard input as french (any variant does the job it seems)
   - Make sure you are in caps lock mode
   - Type the "2 é" char on the keyboard

  Expected:
   - « É » is produced

  Actual:
   - « é » in produced

  Fun fact:
   When reproducing in the GNOME Settings app, there is an interesting behavior:
   - if you try to input « É » WITHOUT focusing first in the search field of 
the app, then the first char will be correctly produced as « É » but subsequent 
will not
   - obviously, if you try the same WITH focusing first in the search field, 
you end up in the first case

  Facts:
   - xev shows proper data arriving
   - reproduced on several wayland app (gnome-text-editor, firefox, 
gnome-settings, gedit)
   - not reproduced on xwayland (hexchat, GDB_BACKEND=x11 gedit)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.10
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 11:57:45 2023
  InstallationDate: Installed on 2022-07-04 (471 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (2 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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


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


[Touch-packages] [Bug 2039289] Re: add-apt-repository ppa:rock-core/qt4 fails

2023-10-13 Thread Paul White
** Package changed: ubuntu => software-properties (Ubuntu)

** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2039289

Title:
  add-apt-repository ppa:rock-core/qt4 fails

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64
  x86_64 x86_64 GNU/Linux

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu-Server 20.04.3 LTS amd64

  sudo add-apt-repository ppa:rock-core/qt4
  Cannot add PPA: 'ppa:~rock-core/ubuntu/qt4'.
  The team named '~rock-core' has no PPA named 'ubuntu/qt4'
  Please choose from the following available PPAs:
   * 'qt4':  Qt4 for Ubuntu 20.04

  This used to work until sometime on Monday.

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


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


[Touch-packages] [Bug 2038095] Re: gnome save dialog -> no reaction to thumb buttons of mouse

2023-10-02 Thread Paul White
** Package changed: ubuntu => gtk+3.0 (Ubuntu)

** Tags added: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2038095

Title:
  gnome save dialog -> no reaction to thumb buttons of mouse

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Bug related to: #1891739

  While "saving" documents in programs like LO, firefox, gedit,
  filezilla, ... the thumb mouse-buttons don't react to browse in the
  menu structure as usual e.g. in a filebrowser like nautilus or in
  using firefox going back from the current page.

  I'd expect to go back and forth in the "file-browser of the saving-
  dialog" with the thumb buttons (4. and 5. button) of my mouse:

  cherry DW5100

  
  ~$ inxi -Fxxxz
  System:
Kernel: 6.2.0-33-generic x86_64 bits: 64 compiler: N/A Desktop: GNOME 42.9
  tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 42.0
  Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2038095/+subscriptions


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


[Touch-packages] [Bug 1922686] Re: Can't log in every time lightdm Xubuntu 20.04.2.1

2023-10-01 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu flavour releases are only supported for three years, so in this
case until April, 2023.

Do you still see a problem related to the one that you reported when using a 
currently supported version of Ubuntu? Please let us know if you do otherwise 
this report can be left to expire in approximately 60 days time. If you do then 
please tell us which release is affected and assign the bug report to a package.
Thank you for helping make Ubuntu better.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1922686

Title:
  Can't log in every time lightdm Xubuntu 20.04.2.1

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I select my username on the login screen, enter my password, the password 
field becomes inactive and nothing happens. If I try a second time by switching 
to "other user" and then back to myself, filling in the password again, it 
sometimes logs in and other times prints a message saying login failed. Then I 
have to restart via the console, which also takes an unreasonable amount of 
time.
  Also, there is a mysterious "Guest" account that I didn't create, which is 
not in the user list, and also requires a password, which I couldn't find 
anywhere on the internet.

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


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


[Touch-packages] [Bug 2037349] Re: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1

2023-09-27 Thread Paul White
** Package changed: ubuntu => cups (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2037349

Title:
  package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed
  cups package post-installation script subprocess returned error exit
  status 1

Status in cups package in Ubuntu:
  New

Bug description:
  DOnt know, but crome always cras, i migt be infected

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   
  Date: Thu Sep 21 06:28:18 2023
  DuplicateSignature:
   package:cups:2.4.1op1-1ubuntu4.7
   Setting up cups (2.4.1op1-1ubuntu4.7) ...
   debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
another process: Resource temporarily unavailable
   dpkg: error processing package cups (--configure):
installed cups package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed cups package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-04-06 (172 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Camera
   Bus 001 Device 002: ID 145f:02d7 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Power Laptop 15-cb0xx
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  Snap: cups 2.4.6-4 (stable)
  Snap.Changes: no changes found
  Title: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed 
cups package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2020
  dmi.bios.release: 15.41
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 836B
  dmi.board.vendor: HP
  dmi.board.version: 46.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 46.24
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd12/01/2020:br15.41:efr46.24:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.24:cvnHP:ct10:cvrChassisVersion:sku2CK98EA#ABE:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Power Laptop 15-cb0xx
  dmi.product.sku: 2CK98EA#ABE
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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


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


[Touch-packages] [Bug 2036887] Re: package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1

2023-09-21 Thread Paul White
** Package changed: ubuntu => cups (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2036887

Title:
  package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso
  instalado paquete cups script post-installation devolvió el código de
  salida de error 1

Status in cups package in Ubuntu:
  New

Bug description:
  No details.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-84-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   
  Date: Thu Sep 21 11:59:31 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  ErrorMessage: el subproceso instalado paquete cups script post-installation 
devolvió el código de salida de error 1
  InstallationDate: Installed on 2021-12-21 (639 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6d1a Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4G Mouse
   Bus 001 Device 004: ID 0bda:c829 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 3511
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=53ec6836-3cb0-4e0d-b3b3-346372cfdc51 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=53ec6836-3cb0-4e0d-b3b3-346372cfdc51 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  Snap: cups 2.4.6-4 (latest/stable)
  Title: package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso 
instalado paquete cups script post-installation devolvió el código de salida de 
error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 06F315
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd10/07/2021:br1.6:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn06F315:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 3511
  dmi.product.sku: 0AB0
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 2036261] Re: Outdated alsa-ucm-conf with fresh install

2023-09-15 Thread Paul White
** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Outdated alsa-ucm-conf with fresh install

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  With a fresh install of Ubuntu 22.04 or 23.04 audio on the front panel
  of PC doesn't work. However if an aux cord is plugged in to "Line In"
  port on the motherboard, the front panel audio is rerouted to that
  port. I fixed it by downloading the updated alsa-ucm-conf and copying
  ucm and ucm2 folders from said directory into "/usr/share/alsa ".
  However, audio through the front panel is quieter than it should be.
  It seems Ubuntu uses an outdated version of alsa-ucm-conf with a fresh
  install.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 10:54:49 2023
  InstallationDate: Installed on 2023-09-15 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: H.70
  dmi.board.asset.tag: Default string
  dmi.board.name: MAG Z690 TOMAHAWK WIFI (MS-7D32)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.70:bd07/04/2022:br5.25:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D32:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGZ690TOMAHAWKWIFI(MS-7D32):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D32
  dmi.product.sku: Default string
  dmi.product.version: 3.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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


[Touch-packages] [Bug 2034763] Re: Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2

2023-09-07 Thread Paul White
** Package changed: ubuntu => glib2.0 (Ubuntu)

** Also affects: xdg-desktop-portal (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: mantic

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

Title:
  Flatpak applications ignore appearance settings with glib2.0 2.77.3
  and xdg-desktop-portal 1.17.2

Status in glib2.0 package in Ubuntu:
  New
Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  I use Plasma desktop in Mantic. With the latest versions of glib2.0
  and xdg-desktop-portal all Flatpak applications ignore host settings
  like GTK theme, cursor theme and window controls position. I can get
  proper appearance only in the following state:

  > sudo apt list --upgradable 
  Listing... Done
  libglib2.0-0/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1]
  libglib2.0-bin/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1]
  libglib2.0-data/mantic,mantic 2.77.3-1 all [upgradable from: 2.77.1-1]
  xdg-desktop-portal/mantic 1.17.2-1ubuntu1 amd64 [upgradable from: 
1.16.0-3ubuntu1]

  Upgrading either glib2.0 or xdg-desktop-portal causes the problem, so
  I don't know exactly which package causes this incompatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2034763/+subscriptions


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


[Touch-packages] [Bug 1737046] Re: Razer Naga Chroma wheel tilt being remapped to vertical scroll

2023-09-04 Thread Paul White
Bug report won't expire due to bug watch
Upstream issue was closed "RESOLVED NOTOURBUG"over 5 years ago
No response to comment #14 after almost two months
So closing as 'Invalid' as this report no longer refers to a currently 
supported release of Ubuntu.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1737046

Title:
  Razer Naga Chroma wheel tilt being remapped to vertical scroll

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  My Razer Naga Chroma's wheel tilt right and left (buttons 6, and 7)
  are being remapped to scroll up and down (buttons 4, and 5) as per
  xev.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems

   Ubuntu: clean, 394556/11829248 files, 20977988/47286784 blocks
  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 Dec  7 14:25:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1303]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 5986: Acer, Inc
   Bus 001 Device 004: ID 1532:0053 Razer USA, Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=4bf03301-9454-4893-8590-722b1fa2efa7 ro quiet splash 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04nRSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04nRSA:bd04/26/2017:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.version: galp2
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.80-1~xenial
  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: Thu Dec  7 14:21:19 2017
  xserver.configfile: default
  xserver.errors:

  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/+bug/1737046/+subscriptions


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


[Touch-packages] [Bug 2028187] Re: Bluetooth audio locked to device disallows other devices to use Bluetooth speaker

2023-07-26 Thread Paul White
** Package changed: ubuntu => bluez (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2028187

Title:
  Bluetooth audio locked to device disallows other devices to use
  Bluetooth speaker

Status in bluez package in Ubuntu:
  New

Bug description:
  Not sure which layer is causing this. I switch bluetooth audio sources
  going to my AVR frequently throughout the day. After an update, Ubuntu
  seems to continue sending something like a keepalive to the bluetooth
  receiver despite no audio being played on the computer. This prohibits
  switching to my phone as the audio source. For example if I play a
  youtube video in Chrome, and then stop the video and then play Amazon
  Music or Spotify, the device is connected but I get no audio. If I
  close Chrome, no change. If I disconnect Ubuntu from that bluetooth
  device, audio starts coming through. No change to bluetooth receiver,
  but there was a Samsung update the other day.

  Interestingly, I disconnected Ubuntu from my BT device. Connected my
  phone, played some audio, then disconnected my phone from the BT
  device. Ubuntu then automatically connected back to that BT device and
  prohibits my phone from using it. This was clearly a change to the
  bluetooth stack that doesn't release the BT device when audio is
  stopped by the application.

  Linux gnosis 5.15.0-76-generic #83

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


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


[Touch-packages] [Bug 1737046] Re: Razer Naga Chroma wheel tilt being remapped to vertical scroll

2023-07-15 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.

Further to comments #12 and #13 the upstream issue has been closed as
"RESOLVED NOTOURBUG".

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

These releases of Ubuntu are no longer receiving maintenance updates. If
this is still an issue when using a currently supported release of
Ubuntu then please let us know otherwise this report can be left to
expire in approximately 60 days time.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1737046

Title:
  Razer Naga Chroma wheel tilt being remapped to vertical scroll

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My Razer Naga Chroma's wheel tilt right and left (buttons 6, and 7)
  are being remapped to scroll up and down (buttons 4, and 5) as per
  xev.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems

   Ubuntu: clean, 394556/11829248 files, 20977988/47286784 blocks
  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 Dec  7 14:25:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1303]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 5986: Acer, Inc
   Bus 001 Device 004: ID 1532:0053 Razer USA, Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=4bf03301-9454-4893-8590-722b1fa2efa7 ro quiet splash 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04nRSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04nRSA:bd04/26/2017:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.version: galp2
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.80-1~xenial
  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: Thu Dec  7 14:21:19 2017
  xserver.configfile: default
  xserver.errors:

  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/+bug/1737046/+subscriptions


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


[Touch-packages] [Bug 1623339] Re: The system is running in low-graphics mode (Ubuntu 16.04, ARM64 platform, AST2400 VGA chip)

2023-06-29 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: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1623339

Title:
  The system is running in low-graphics mode  (Ubuntu 16.04, ARM64
  platform, AST2400 VGA chip)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I use netboot to install Ubuntu 16.04 in Cavium ThunderX 8800 platform
  (ARM64 core) with AST2400 VGA chip and I see "The system is running in
  low graphics mode". How can I fix this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Sep 14 14:02:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000]
  MachineType: Cavium ThunderX CRB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=513a25ac-9bd5-49b5-a6cb-4298036c6abd ro splash quiet vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  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: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  8 09:56:09 2016
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3

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


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


[Touch-packages] [Bug 1444880] Re: xrandr report inverted gamma values

2023-06-29 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 (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1444880

Title:
  xrandr report inverted gamma values

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  $ xrandr --output VGA1  --gamma 1:1:1.7
  $ xrandr --verbose | grep -iE '(gamma|bright)'
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0
  Gamma:  1.0:1.0:0.59
  Brightness: 1.0
  $ xrandr --output VGA1  --gamma 1:1:.6
  $ xrandr --verbose | grep -iE '(gamma|bright)'
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0

  As you can see in output of commands above, "Gamma" values printed by
  xrandr --verbose are exactly the invert of the values set: 1/... Appart for value 1.0 which is correct.

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


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


[Touch-packages] [Bug 1662042] Re: Black screen after resuming from sleep with nvidia drivers on 16.04

2023-06-29 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: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1662042

Title:
  Black screen after resuming from sleep with nvidia drivers on 16.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This happens on an ASUS ZenBook UX303UB, with nvidia-375 installed.
  I'm able to connect to the host through SSH. I have run the apport-bug tool 
when the display was black.

  The problem is not present when I switch back to using the Intel GPU
  using Nvidia's tool (through nvidia-prime).

  So far, I have done the following tests, following reports from other users:
  - Switched to kernel 4.8
  - Tried with both nvidia-370 and nvidia-375
  - Tried with fix to backlight 
(http://askubuntu.com/questions/820955/blank-screen-after-resume-dell-m5510-ubuntu-16-04/823523)
  - Configured ligthdm idle-timeout to 3 seconds and see if the display came 
back  (due to an old bug affecting older versions)

  Bumblebee is not installed.

  I have seen several issues / questions that seems similar to this one,
  but I couldn't find a solution / workaround, other than disabling
  Nvidia's GPU.

  I appreciate any help to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-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  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Feb  5 22:16:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1b1d]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1b1d]
  InstallationDate: Installed on 2016-08-18 (172 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 005: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 03eb:8b0d Atmel Corp. 
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303UB
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=none acpi_osi= 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303UB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303UB.206:bd03/02/2016:svnASUSTeKCOMPUTERINC.:pnUX303UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303UB
  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.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 

[Touch-packages] [Bug 1715633] Re: nvidia drivers...

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715633

Title:
  nvidia drivers...

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to install the nvidia driver since days. I'm afraid that
  one of the "displays" (the intel VGA one) is not working anymore. At
  least it appears unclaimed with or without the nvidia driver.

  
  *** ANY HELP IS HIGHLY APPREACIATED, THANK YOU ***


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-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  381.26.13  Wed Aug 16 
04:02:47 PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Sep  7 14:54:16 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
   nvidia-381, 381.26.13, 4.4.0-93-generic, x86_64: installed
   webcamstudio, 0.73, 3.13.0-101-generic, x86_64: installed
   webcamstudio, 0.73, 4.4.0-92-generic, x86_64: installed
   webcamstudio, 0.73, 4.4.0-93-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GconfCompiz:
   /apps/compiz-1/plugins:
     /apps/compiz-1/plugins/unityshell:
  /apps/compiz-1/plugins/unityshell/screen0:
   /apps/compiz-1/plugins/unityshell/screen0/options:
    devices_option = 0
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1113]
     Subsystem: Micro-Star International Co., Ltd. [MSI] GM108M [GeForce 840M] 
[1462:1113]
  InstallationDate: Installed on 2015-01-23 (958 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Micro-Star International Co., Ltd. GP60 2PE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=da904324-ef1b-4408-8fe7-543a661e7464 ro nomodeset=1 splash quiet
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Error: GLX is not available on the system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GHIMS.10B
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GH
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  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.:bvrE16GHIMS.10B:bd10/23/2014:svnMicro-StarInternationalCo.,Ltd.:pnGP602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GH:rvrREV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GP60 2PE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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
  

[Touch-packages] [Bug 1584238] Re: RADEON(G0): [XvMC] Failed to initialize extension. AND CRTC 64

2023-06-29 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: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1584238

Title:
  RADEON(G0): [XvMC] Failed to initialize extension. AND CRTC 64

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  **UPDATED AS REQUESTED**

  7/02: The display setting commands are to change the display
  orientation (I want to rotate the display 90' clockwise). Two
  displays, on the same graphics card, the primary card as listed in the
  BIOS, will respond to those commands. However, the displays on the
  secondary card will not respond. And if I try to select those displays
  the system crashes or is unable to make the change.

  I have had consistent issues in both 14.04 (even with FGLRX installed)
  and 16.04 with the graphics card labeled as secondary in the BIOS
  correctly displaying or even responding to display setting commands in
  Unity.

  LSPCI Info
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series Chipset 
Family KT Controller (rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM 
(rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d4)
  00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #5 (rev d4)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Q87 Express LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 04)
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos XTX [Radeon HD 8490 / R5 235X OEM]
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI 
Audio [Radeon HD 6400 Series]
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos XTX [Radeon HD 8490 / R5 235X OEM]
  03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI 
Audio [Radeon HD 6400 Series]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-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
  CurrentDesktop: Unity
  Date: Fri May 20 18:22:07 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  InstallationDate: Installed on 2016-05-05 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex 9020
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=baa78b6c-e47e-4119-af45-1c2ee756768a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2013
  

[Touch-packages] [Bug 1716104] Re: can't get nvidia to work

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1716104

Title:
  can't get nvidia to work

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can't get the nvidia driver to work.

  When I type "prime-select intel" the system works.

  When I type "prime-select nvidia" glxinfo breaks.

  
  lsmod | grep nvidia
  nvidia_uvm688128  0
  nvidia_drm 49152  0
  nvidia_modeset843776  1 nvidia_drm
  nvidia  12984320  2 nvidia_modeset,nvidia_uvm
  drm_kms_helper155648  2 i915,nvidia_drm
  drm   364544  4 i915,drm_kms_helper,nvidia_drm

  
  > BUT: Xorg.0.log has the following errors:

  [   478.562] (EE) Failed to load module "nvidia" (module does not exist, 0)
  [   478.562] (EE) Failed to load module "nouveau" (module does not exist, 0)
  [   478.563] (EE) Failed to load module "nvidia" (module does not exist, 0)
  [   478.563] (EE) Failed to load module "nouveau" (module does not exist, 0)
  [   478.572] (EE) open /dev/fb0: No such file or directory
  [   478.572] (EE) open /dev/fb0: No such file or directory
  [   478.572] (EE) open /dev/fb0: No such file or directory
  [   478.572] (EE) open /dev/fb0: No such file or directory
  [   478.572] (EE) Screen 0 deleted because of no matching config section.
  [   478.572] (EE) Screen 0 deleted because of no matching config section.
  [   478.572] (EE) Screen 0 deleted because of no matching config section.
  [   478.572] (EE) Screen 0 deleted because of no matching config section.
  [   478.699] (EE) AIGLX: reverting to software rendering


  > I think I need to generate a valid xorg.conf file

  
  > BUT: when I execute sudo X -configure I get the following error at the 
end:

  
  List of video drivers:
amdgpu
ati
cirrus
intel
mach64
mga
neomagic
openchrome
qxl
r128
radeon
savage
siliconmotion
sisusb
trident
vmware
vesa
modesetting
fbdev
tdfx
  (++) Using config file: "/home/jccb/xorg.conf.new"
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  Number of created screens does not match number of detected devices.
Configuration failed.
  (EE) Server terminated with error (2). Closing log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-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  384.69  Wed Aug 16 19:34:54 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Sep  9 11:25:06 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
   nvidia-384, 384.69, 4.4.0-93-generic, x86_64: installed
   webcamstudio, 0.73, 3.13.0-101-generic, x86_64: installed
   webcamstudio, 0.73, 4.4.0-92-generic, x86_64: installed
   webcamstudio, 0.73, 4.4.0-93-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1113]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM108M [GeForce 840M] 
[1462:1113]
  InstallationDate: Installed on 2015-01-23 (960 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Micro-Star International Co., Ltd. GP60 2PE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 

[Touch-packages] [Bug 1703098] Re: No X if resuming when "Configure new displays when connected" unchecked

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1703098

Title:
  No X if resuming when "Configure new displays when connected"
  unchecked

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This system normally has two displays connected which are always on.
  This problem arose when a TV was connected as a third display. It was
  preferred to have the TV left "disabled" by unchecking "Use this
  display" when it was not needed, but leaving its cable connected.
  However at each startup a GUI will be presented asking for display
  configuration because the option in Display settings for "Configure
  new displays when connected" is checked.

  If the option for "Connfigure new displays when connected" is then
  unchecked and the system is hibernated, then on resume X will not
  start. The only thing that can be done is to start a new terminal
  session and then startx will bring up a desktop. However the
  applications that were restored in the resume aren't accessible from
  this desktop session that has been manually started.

  The following were tried until the system was found to be resuming:
  1. Disconnected the third display
  2. Checked the option for "Configure new displays when connected"
  Not until both options had been tried would the system resume after 
hibernation and start X.

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://nz.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  xrandr
  Screen 0: minimum 8 x 8, current 3600 x 1080, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 510mm x 287mm
 1920x1080 60.00*+
 1280x1024 75.0260.02  
 1152x864  75.00  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected 1680x1050+1920+0 (normal left inverted right x axis y axis) 
474mm x 296mm
 1680x1050 59.88*+  59.95  
 1280x1024 75.0260.02  
 1152x864  75.00  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)

  $ cat xorg.conf
  # nvidia-settings: X configuration file generated by nvidia-settings
  # nvidia-settings:  version 361.42  (buildd@lgw01-18)  Tue Apr  5 14:33:28 
UTC 2016

  Section "ServerLayout"
  Identifier "Layout0"
  Screen  0  "Screen0" 0 0
  InputDevice"Keyboard0" "CoreKeyboard"
  InputDevice"Mouse0" "CorePointer"
  Option "Xinerama" "0"
  EndSection

  Section "Files"
  EndSection

  Section "Module"
  Load   "dbe"
  Load   "extmod"
  Load   "type1"
  Load   "freetype"
  Load   "glx"
  EndSection

  Section "InputDevice"
  # generated from default
  Identifier "Mouse0"
  Driver "mouse"
  Option "Protocol" "auto"
  Option "Device" "/dev/psaux"
  Option "Emulate3Buttons" "no"
  Option "ZAxisMapping" "4 5"
  EndSection

  Section "InputDevice"
  # generated from default
  Identifier "Keyboard0"
  Driver "kbd"
  EndSection

  Section "Monitor"
  # HorizSync source: edid, VertRefresh source: edid
  Identifier "Monitor0"
  VendorName "Unknown"
  ModelName  "DELL P2210"
  HorizSync   30.0 - 83.0
  VertRefresh 56.0 - 75.0
  Option "DPMS"
  EndSection

  Section "Device"
  Identifier "Device0"
  Driver "nvidia"
  VendorName "NVIDIA Corporation"
  BoardName  "GeForce GTX 750"
  EndSection

  Section "Screen"
  Identifier "Screen0"
  Device "Device0"
  Monitor"Monitor0"
  DefaultDepth24
  Option 

[Touch-packages] [Bug 1592519] Re: [radeon] sumo2 locks up and fails to train displayport during boot (panel turns off)

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1592519

Title:
  [radeon] sumo2 locks up and fails to train displayport during boot
  (panel turns off)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Problem: Laptop panel turns off during boot, which makes the laptop
  unusable.

  Expected Results: Laptop panel is ON when I boot without "nomodeset",
  and I can use graphical UI.

  Guys from #radeon channel on "irc.freenode.net" said:
   radeon :00:01.0 is the sumo2 and it locks up
   radeon :01:00.0 is the caicos but there seems to be no problem 
with it
   the problem is the sumo crashing and failing to train displayport
   as it's the travis bridge it's trying to modeset which is the panel
   fixing the travis bridge is the first problem

  I also tried the latest (v4.7-rc3) manually installed kernel,
  confirmed that the bug remains, and submitted the bug here
  https://bugs.freedesktop.org/show_bug.cgi?id=96527 .

  WORKAORUND: Use kernel parameter nomodeset when booting. UI works with
  this kernel parameter but it's not usable as it's very slow.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jun 14 21:33:48 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6380G] [1002:9643] 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6380G] [103c:168c]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-06-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP ProBook 4535s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=74aa7181-639e-464e-b1e1-2af72c4b6e35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CPC Ver. F.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 168B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.1D
  dmi.chassis.asset.tag: CNU13746LQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CPCVer.F.60:bd03/11/2015:svnHewlett-Packard:pnHPProBook4535s:pvrA402:rvnHewlett-Packard:rn168B:rvrKBCVersion32.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4535s
  dmi.product.version: A402
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-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.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: Tue Jun 14 21:32:36 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: radeon

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


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


[Touch-packages] [Bug 1707394] Re: DVI-I being read as DVI-D and i have no picture

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1707394

Title:
  DVI-I being read as DVI-D and i have no picture

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  I'm using Radeon R9 380X graphics card with two monitors. Before
  installing the radeon drivers, each of the monitors work properly. But
  after this, the DVI-D output is being read as DVI-I, and monitor
  attached to this port says "No signal". It only has a d-sub VGA input.
  The other monitors works fine.

  Here are the outputs of the xrandr command:

  Before installing the drivers:

  Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
  DisplayPort-0 connected 1920x1080+1920+0 (normal left inverted right x axis y 
ax
  is) 477mm x 268mm
 1920x1080 60.00*+
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  74.9859.89  
 1280x960  60.00  
 1280x800  59.81  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DVI-D-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axi
  s) 477mm x 268mm
 1920x1080 60.00*+
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08 

  After the installation:

  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
  DisplayPort-0 connected primary 1920x1080+0+0 (normal left inverted right x 
axis
   y axis) 477mm x 268mm
 1920x1080 60.00*+
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  74.9859.89  
 1280x960  60.00  
 1280x800  59.81  
 1152x864  75.00  
 1280x720  60.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DVI-D-0 disconnected (normal left inverted right x axis y axis)
  DVI-D-1 connected (normal left inverted right x axis y axis)
 1920x1080 60.00 +
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1280x800  60.00  
 1152x864  75.00  
 1280x720  60.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  

  By the way in practice, tho physycaly port itself is REALY a dual link DVI-D.
  Any solution?

  Thank you for the help!

  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-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: Sat Jul 29 15:09:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: amdgpu-pro, 17.30-458935, 4.8.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Tonga PRO [Radeon R9 
285/380] [174b:e306]
  

[Touch-packages] [Bug 1556452] Re: 4K@60Hz DisplayPort 1.2 loses output modes

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1556452

Title:
  4K@60Hz DisplayPort 1.2 loses output modes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell UP2414Q 24" 4K display panel. The only way to achieve
  60Hz refresh on it, is to use DisplayPort 1.2 MST.

  Due to MST, this results in two screens with 1920x2160 resolution
  being exposed to X. In order to get back to a proper rendering where
  it looks like a single display, one must either use Xinerama (with
  NVidia) or Xorg 3.18 and the new xrandr with support for configuring
  monitors in RandR 1.5 (with Intel). In both of these configurations,
  if the monitor itself is powered off, the output modes will disappear
  from xrandr, and when the monitor is powered back on, it behaves as
  though no output is being sent to it over the DisplayPort connection.
  When connecting with ssh to debug, running DISPLAY=:0 xrandr says that
  the two outputs exist, but no modes are configured, and indeed it does
  not list any. If however, instead of powering the monitor off, it is
  left on while away, this does not occur upon return, and the display
  works normally as when it was left.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  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 Mar 12 12:26:16 2016
  DistUpgraded: 2016-03-10 16:26:10,719 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-lowlatency, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-lowlatency, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7919]
  InstallationDate: Installed on 2012-10-21 (1237 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: MSI MS-7919
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=167bf6e1-727f-4db1-b2f9-c496700b301b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-10 (1 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M GAMING (MS-7919)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/30/2014:svnMSI:pnMS-7919:pvr1.0:rvnMSI:rnZ97MGAMING(MS-7919):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7919
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 11:07:14 2016
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
 

[Touch-packages] [Bug 1607966] Re: X doesn't start with r128 driver with PM 3, 1 PPC ATI Rage

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1607966

Title:
  X doesn't start with r128 driver with PM 3,1 PPC ATI Rage

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I was working on bug #1541082 which was reporting "blotchy" graphics
  images on my PowerMac3,1 with Rage ATI Pro 128 card . . . and got the
  suggestion to try to add the "r128" driver, which I did.  After that
  the display went black.  After fiddling around with it, I removed the
  r128 driver, made an xorg.conf file . . . and after numerous attempts
  to get the display back, today I got "fbdev" and mode "1920 x 1200" to
  bring the GUI back online . . . but, there was another "xorg" crash on
  reboot, which I reported, along with filing this bug against the r128
  module for this PPC machine.

  F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13
  Uname: Linux 4.4.0-31-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jul 29 14:34:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (179 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0201 Apple, Inc. USB Keyboard [Alps or Logitech, 
M2452]
   Bus 002 Device 002: ID 05ac:1001 Apple, Inc. Keyboard Hub [ALPS]
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  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.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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jul 29 14:15:13 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputAlps Electric Apple USB Keyboard KEYBOARD, id 6
   inputKensington  USB/PS2 Wheel Mouse MOUSE, id 7
   inputPMU  KEYBOARD, id 8
  xserver.errors: AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

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


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


[Touch-packages] [Bug 1665629] Re: external HDMI doesnt function properly

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1665629

Title:
  external HDMI doesnt function properly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  New clean install of 16.04 on dell Inspiron N5110 laptop,when External HDMI 
Monitor plugged in
   display randomly switches from laptop screen to hdmi screen ,
   changing resolution, 
  changing display mode,
  display positioning,
  whether the internal or external display is enabled or not, 
  and other things all display settings related, ie size of iconts, font and 
title bars.
  All this happens AUTOMATICALLY and without notice.
  This does not stop, it makes it look like the computer is Haunted.
   How do I fix this???

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


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


[Touch-packages] [Bug 1694109] Re: X server freezes with all NVIDIA open source driver releases (340.102, 375.66, 381.22)

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1694109

Title:
  X server freezes with all NVIDIA open source driver releases (340.102,
  375.66, 381.22)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have Dell XPX L502X with Nvidia GT 540M card i.e. 6 years old
  hardware whose driver is still not working, this is amazing :(

  The X server freezes with all NVIDIA open source driver releases
  (340.102, 375.66, 381.22). This report is for NVIDIA driver version
  340.102.

  X Server freezes at any time keyboard and mouse hangs and last resort
  used to be to power down with power key forcefully which may destroy
  HDD also :(

  I even tried proprietary NVIDIA drivers also but they had shown the
  same behaviour.

  Without the NVIDIA drivers in place I can't use CUDA toolkit.

  Please let me know if someone need any further info apart from attached file.
  Thanks

  Br
  aksgaur

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-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.102  Mon Jan 16 13:06:29 
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.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun May 28 11:42:45 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-36-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed
   nvidia-340, 340.102, 4.8.0-36-generic, x86_64: installed
   nvidia-340, 340.102, 4.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:050e]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 540M] [1028:050e]
  InstallationDate: Installed on 2017-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e35ef27e-882a-4ccf-9430-7246671359cb ro rootflags=subvol=@ quiet 
splash
  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: 0NJT03
  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.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell 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.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 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:

[Touch-packages] [Bug 1718868] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1718868

Title:
  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  SO: Lubuntu 16.04 Xenial

  :~$ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:Ubuntu 16.04
  Release:  16.04
  Codename: xenial

  
  :~$ uname -r
  4.4.0-96-generic

  
  below is a sample command where the error is displayed:

  ~$ dpkg-reconfigure keyboard-configuration
  [./ply-boot-client.c:183]   ply_boot_client_connect:could 
not connect to /org/freedesktop/plymouthd: Connection refused
  [./ply-boot-client.c:184]   
ply_boot_client_connect:trying old fallback path /ply-boot-protocol
  [./ply-boot-client.c:190]   ply_boot_client_connect:could 
not connect to /ply-boot-protocol: Connection refused
  [./plymouth.c:1121]  main:daemon not 
running
  [./plymouth.c:1124]  main:ping failed
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  update-initramfs: deferring update (trigger activated)
  Elaborazione dei trigger per initramfs-tools (0.122ubuntu8.8)...
  update-initramfs: Generating /boot/initrd.img-4.4.0-96-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: x11-common 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep 22 09:43:50 2017
  Dependencies: lsb-base 9.20160110ubuntu0.2
  InstallationDate: Installed on 2016-11-19 (306 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-11-20 (305 days ago)

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


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


[Touch-packages] [Bug 1590457] Re: Switching to proprietary nvidia driver prevents compiz from starting

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1590457

Title:
  Switching to proprietary nvidia driver prevents compiz from starting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After enabling proprietary driver nvidia 361.42 in unity-control-
  center and rebooting, compiz fails to start.  I'm able to login.  I
  see my wallpaper and desktop icons, but there's no window manager or
  panel.

  A manual fix that worked in the past was
  right-click, open terminal
  enter commands:
  dconf reset -f /org/compiz/
  setsid unity

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .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: Wed Jun  8 09:06:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Skylake Integrated Graphics 
[144d:c12b]
 Subsystem: Samsung Electronics Co Ltd GM107M [GeForce GTX 950M] [144d:c12b]
  InstallationDate: Installed on 2015-12-22 (168 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 940Z5L
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=24c27814-5135-4a80-9ce1-b932e2513949 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06AFC.091.160311.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP940Z5L-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8554A1H-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06AFC.091.160311.SH:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn940Z5L:pvrP06AFC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940Z5L-X01US:rvrSGL8554A1H-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 940Z5L
  dmi.product.version: P06AFC
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-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.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: Wed Jun  8 09:04:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16714 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.2

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


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


[Touch-packages] [Bug 1672566] Re: Extra carriage return in 20x11-common_process-args

2023-06-29 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 'Invalid' as it's not seen any activity 
for some time and there was no reference to the release of Ubuntu being used.


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1672566

Title:
  Extra carriage return in 20x11-common_process-args

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Hi there,

  I believe there is an axtra carriage return in the function
  has_option() in the file /etc/X11/Xsession.d/20x11-common_process-
  args.  The function is defined as:

  has_option() {
if [ "${OPTIONS#*
  $1}" != "$OPTIONS" ]; then
  return 0
else
  return 1
fi
  }

  however it looks like there is an extra carriage return after the *.
  I believe the function should look like this:

  has_option() {
if [ "${OPTIONS#*$1}" != "$OPTIONS" ]; then
  return 0
else
  return 1
fi
  }

  Thanks.

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


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


[Touch-packages] [Bug 1694254] Re: Requested size (2944, 1080) exceeds 3D hardware limit

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1694254

Title:
  Requested size (2944, 1080) exceeds 3D hardware limit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  IBM T60 laptop (1024x768), and an external monitor, Benq E2200HDA
  (1920x1080) connected.

  Displays with expected resolutions only if one above/below the other,
  not left or right.

  Xrandr say:
  Screen 0: minimum 8 x 8, current 1920 x 1848, maximum 32767 x 32767
  LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 286mm x 214mm
 1024x768  60.00*+  50.00  
 800x600   60.3256.25  
 640x480   60.0059.94  
 512x384   60.00  
  DVI1 disconnected (normal left inverted right x axis y axis)
  VGA1 connected 1920x1080+0+768 (normal left inverted right x axis y axis) 
476mm x 268mm
 1920x1080 59.96*+
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  74.9859.89  
 1280x960  60.00  
 1280x800  59.81  
 1152x864  75.00  
 1152x720  59.97  
 1024x768  75.0860.00  
 832x624   74.55  
 800x600   75.0060.32  
 640x480   75.0060.00  
 720x400   70.08  
 1920x1080_60.00  59.96  
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  Forcing fitting any screen left/right of the other results in black
  screen with xrandr.

  Trying to fit them left/right with System Settings > Screen Display says:
   
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code3: 
Requested size (2944, 1080) exceeds 3D hardware limit (2048, 2048). You must 
either rearrange the displays so that they fit within a (2048, 2048) square.

  System:
  - Ubuntu 16.04.2 LTS 
  - expected to happen: built up screen and VGA1 fits left/right as it works 
with XP.
  - what happenes: see above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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: Mon May 29 12:06:57 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
  InstallationDate: Installed on 2017-05-23 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: LENOVO 19524TC
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=f2865c0e-961d-4c45-8734-4152a94446fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE7WW (2.27 )
  dmi.board.name: 19524TC
  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:bvr79ETE7WW(2.27):bd03/21/2011:svnLENOVO:pn19524TC:pvrThinkPadT60:rvnLENOVO:rn19524TC:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 19524TC
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  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
  

[Touch-packages] [Bug 1657903] Re: XRandR failed: XRandR returned error code 1: X Error of failed request: BadValue (integer parameter out of range for operation)

2023-06-29 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1657903

Title:
  XRandR failed: XRandR returned error code 1: X Error of failed
  request: BadValue (integer parameter out of range for operation)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  What happens when using a StarTech device (Product ID: USB3SDOCKDD)
  with either the DisplayLink driver from StarTech's website (1.1.62),
  or the latest from DisplayLink's website (1.2.65), is when I attach
  the USB 3.0 cord to the USB 3.0 port on my laptop for the first time
  after a reboot, open arandr, open the attached StarTech.sh file, and
  click Apply, the Dell E2414Ht monitor VGA connected on the left is the
  primary and the laptop display is the secondary on the right.

  However, if I disconnect the USB cord, then reconnect, and then re-apply the 
file, I get a pop up noting:
  
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1657903/+attachment/4806499/+files/screenshot.png

  XRandR failed: XRandR returned error code 1: X Error of failed request:
  BadValue (integer parameter out of range for operation)
   Major opcode of failed request: 140 (RANDR)
   Minor opcode of failed request: 7 (RRSetScreenSize)
   Value in failed request: 0x0
   Serial number of failed request: 42
   Current serial number in output stream: 43

  The two DisplayLink driver versions tested:
  sudo displaylink-installer
  DisplayLink Linux Software 1.1.62 install script called:
  Distribution discovered: Ubuntu 16.04.1 LTS

  sudo displaylink-installer
  DisplayLink Linux Software 1.2.65 install script called:
  Distribution discovered: Ubuntu 16.04.1 LTS

  WORKAROUND: Restart the computer after disconnecting the USB cord.

  WORKAROUND: Go to Applications > System Tools > System Settings >
  Displays and make only the Dell monitor as On > click Apply > then
  make the Built-in Display On > click Apply. This is the only way to
  make the Dell monitor the primary, and the laptop the secondary as
  there are no general options, and the app makes the Built-in Display
  the primary by default, with no General options to change this.

  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
  .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
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Jan 19 16:17:34 2017
  DistUpgraded: 2016-01-20 03:32:27,395 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated 
Graphics Controller [1179:f840]
  InstallationDate: Installed on 2015-12-18 (398 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA Satellite S55-C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/ubuntu--vg-root ro ipv6.disable=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (365 days ago)
  dmi.bios.date: 10/14/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 5.10
  dmi.board.name: 06F1
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.10:bd10/14/2015:svnTOSHIBA:pnSatelliteS55-C:pvrPSPTJU-006005:rvnFF50:rn06F1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-C
  dmi.product.version: PSPTJU-006005
  dmi.sys.vendor: TOSHIBA
  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 

  1   2   3   4   5   6   7   8   9   10   >