date:20181229

[Bug 1810072] [NEW] Dependency Browser window is empty

2018-12-29 Thread Victor Porton

Public bug reported:

When I open Tools / Browsers / Dependency in GNAT GPS menu, I see an
empty window (no graph).

Compiling the library before showing it does not help.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnat-gps 17.0.2017-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 30 09:15:06 2018
InstallationDate: Installed on 2018-06-23 (189 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IL
 SHELL=/bin/bash
SourcePackage: gnat-gps
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (70 days ago)

** Affects: gnat-gps (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic

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

Title:
  Dependency Browser window is empty

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

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

ubuntu-bugs@lists.ubuntu.com

2018-12-29 Thread Bug Watch Updater

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.xfce.org/show_bug.cgi?id=13537.

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


On 2017-04-29T00:24:58+00:00 Andreldm-2 wrote:

There are some bugs reported to xfce4-screenshooter about copy to clipboard not 
working for large resolutions:
https://bugzilla.xfce.org/show_bug.cgi?id=13342
https://bugzilla.xfce.org/show_bug.cgi?id=13395
https://bugzilla.xfce.org/show_bug.cgi?id=10426
https://bugzilla.xfce.org/show_bug.cgi?id=12704

gnome-screenshot is also affected if started with -c flag or in interactive 
mode if you press the copy to clipboard button then close the app before 
pasting.
At first I thought it was something related to gtk_clipboard_set_image, but 
this problem doesn't happen when running 
/usr/lib/gnome-settings-daemon/gsd-clipboard instead of xfsettingsd.

Reply at:
https://bugs.launchpad.net/xfce4-settings/+bug/1655398/comments/3


On 2018-12-29T16:20:42+00:00 Kristiana2000 wrote:

This issue doesnt seem to be limited to just images but generally very
large buffers. Copying some very large pieces of text data fails as
well.

I looked through the gnome clipboard and xfce source. Unsure which one
of the two is the fork, but they obviously share the same codebase. I
suggest the changes from gnome-settings-daemon get picked into the
xfsettingsd clipboardmanager.

Reply at:
https://bugs.launchpad.net/xfce4-settings/+bug/1655398/comments/6


** Changed in: xfce4-settings
   Status: Unknown => Confirmed

** Changed in: xfce4-settings
   Importance: Unknown => Medium

** Bug watch added: Xfce Bugzilla #13342
   https://bugzilla.xfce.org/show_bug.cgi?id=13342

** Bug watch added: Xfce Bugzilla #13395
   https://bugzilla.xfce.org/show_bug.cgi?id=13395

** Bug watch added: Xfce Bugzilla #12704
   https://bugzilla.xfce.org/show_bug.cgi?id=12704

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

Title:
  1920x1080 screenshot hangs & fails on clipboard insert (GIMP&lowriter)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1655398/+subscriptions

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

[Bug 1810070] Re: 18.04.1 Live CD fails to boot with EFI errors

2018-12-29 Thread Shepherd King

** Description changed:

  System Information:
- Fujitsu T901, 16GB Ram, i5-2520M CPU 
+ Fujitsu T901, 16GB Ram, i5-2520M CPU
+ BIOS version: 1.15 (latest)
  (laptop manufactured 2011)
  Laptop does not support UEFI
  
  The MD5 sums were verified for the live cd image.
  
  The laptop is currently dual booted with Windows 10, Ubuntu 16.04 with
  separate hard drives.  The live cd (a live USB) was intended to be used
  to install 18.04.
  
  The error message at boot is:
  Could not get fio for li->DeviceHandle: Invalid Parameter
  Failed to find fs: Invalid Parameter
  Failed to load image \EFI\BOOT\grubx64.efi: Invalid Parameter
  start_image() returned Invalid Parameter
  
  The laptop was verified to be BIOS-only.  Under Windows 10,
  C:\Windows\Panther\setupact.log reports "Detected boot environment:
  BIOS".  Under Ubuntu 16.04, "sudo efibootmgr" reports that "EFI
  variables are not supported on this system."
  
  The system will successfully boot into a live cd environment using Knoppix 
8.2, though it does report an error at boot time before proceeding with startup:
  ERROR
  Failed to start loader.efi: (14) Not Found

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

Title:
  18.04.1 Live CD fails to boot with EFI errors

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

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

[Bug 1807056] Re: Occasional Keyboard freeze

2018-12-29 Thread Dilip

What I have noticed is that the freeze occurred only once in Cinnamon.
Nothing since it happened first. I will update here if some progress
happens.

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

Title:
  Occasional Keyboard freeze

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-29 Thread Ben

The UX391UA fix is not in 4.20 as it was already a release candidate.
To get sound working on this model you'll need to download the 4.20
source, apply the patch to sound/pci/hda/patch_realtek.c then compile
and install the kernel.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1588009] Re: "libinput bug: timer offset negative" keeps coming up in syslog

2018-12-29 Thread Bug Watch Updater

Launchpad has imported 10 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=96312.

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


On 2016-06-01T17:48:16+00:00 Wise Melon wrote:

I have just recently looked in my syslog and discovered that the
following message shows up a lot daily so I thought I should report it:

/usr/lib/gdm3/gdm-x-session[1707]: (EE) libinput bug: timer offset
negative

I am running Ubuntu GNOME 16.04 with GNOME 3.20, more information (logs
and other system information etc) can be found in my LaunchPad bug
report that I made through apport: https://bugs.launchpad.net/ubuntu-
gnome/+bug/1588009

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/2


On 2016-06-01T22:29:56+00:00 Peter Hutterer wrote:

is this reproducible? the most common cause of this is a slow
compositor/X server busy with rendering. libinput does timer setups
based on event timestamps from the kernel and relies on the caller to
keep calling libinput_dispatch() often enough, if that isn't the case
then a 150ms timer may be set for an event from 500ms ago - resulting in
an offset of -350ms from the current time.

Unless you can reproduce this reliably with a specific interaction there
is not much we can do here.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/3


On 2016-06-17T00:57:24+00:00 Peter Hutterer wrote:

any updates here?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/4


On 2016-07-13T00:47:55+00:00 Peter Hutterer wrote:

Closing after almost a month of no updates

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/5


On 2016-08-15T16:49:55+00:00 termite wrote:

I've been getting a lot of this since switching to using Gnome on
Wayland (from X). My system freezes completely, and I need to hard
restart. Looking at /var/log/messages, I see a lot of these errors just
before the freeze, plus:

org.gnome.Shell.desktop[2961]: libinput error: kernel bug: Touch jump detected 
and discarded.
debian-x1yoga org.gnome.Shell.desktop[2961]: See 
https://wayland.freedesktop.org/libinput/doc/1.4.0/touchpad_jumping_cursor.html 
for details

I'd be happy to help if you let me know how.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/6


On 2016-08-18T05:44:21+00:00 Peter Hutterer wrote:

The jumping touch is unrelated and can be ignored for this bug.

But comment #1 still stands, this is almost always a slow compositor.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/7


On 2017-07-01T04:55:00+00:00 Bahodir wrote:

I have the same issue and would like to help with consistent steps to
reproduce the bug. Please let me know what information I can share.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/8


On 2017-07-03T03:54:14+00:00 Peter Hutterer wrote:

Here's a patch that'll make tracking things down a bit easier:
https://lists.freedesktop.org/archives/wayland-
devel/2017-July/034396.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/9


On 2018-04-03T19:06:17+00:00 Nils Kaiser wrote:

I can confirm I have this on Arch Kernel 4.15.14-1-ARCH Gnome 3.28 on
Wayland on Thinkpad X1 Carbon 2017 model. Libinput version is 1.10.3

Here some sample logs:

libinput error: client bug: timer event17 debounce short: offset negative 
(-42ms)
libinput error: client bug: timer event15 trackpoint: offset negative (-1720ms)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/11


On 2018-12-28T17:29:05+00:00 Thommen wrote:

Hi,
@Nils Kaiser I have KDE, but I have same problem on Arch Linux 
(4.19.12-arch1-1-ARCH)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/14


** Changed in: libinput
   Status: Invalid => Confirmed

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

Title:
  "libinput b

[Bug 1299007] Re: [ASUS Z87-PRO] suspend/resume failure

2018-12-29 Thread Sam

Debug info for Kernel 4.20.0-042000

https://wiki.ubuntu.com/DebuggingKernelSuspend
Debugging information to provide in the bug report


Kernel 4.20.0-042000
=

1. Issue occurs with resume from 'Suspend to ram' (not hibernate).

2. Suspend action initiated by clicking Suspend in the GUI.

3. Resume initiated by pressing power button on PC case.

4. Attached.

5. (echo freezer > /sys/power/pm_test) UI froze for few seconds. System
returned to normal operation.

6. (echo devices > /sys/power/pm_test) Display switched off for few
seconds. Standby flashing LED on PC case not observed (remained in solid
'ON' state). System returned to normal operation after few seconds.

7. (echo platform > /sys/power/pm_test) Display switched off for few
seconds. Standby flashing LED on PC case not observed (remained in solid
'ON' state). System returned to normal operation after few seconds.

8. (echo processors > /sys/power/pm_test) Display switched off for few
seconds. Standby flashing LED on PC case not observed (remained in solid
'ON' state). System returned to normal operation after few seconds.

9. (echo core > /sys/power/pm_test) Display switched off for few
seconds. Standby flashing LED on PC case not observed (remained in solid
'ON' state). System returned to normal operation after few seconds.

10. (echo none > /sys/power/pm_test) Display switched off. All fans
powered off (CPU fan, PSU fan). Standby LED flashing on PC case. Resume
initiated by pressing power button on PC case. Display remained off -
LCD monitor standby LED flashing. System not responsive. Caps-lock
button not responding; USB keyboard remove-reattach not effective.
Rebooted manually (cycled power).

11. suspend_stats output after successful restore at step 6 (devices)
provided.

Notably, on this kernel version system returns to normal operation at step 6 
(echo devices > /sys/power/pm_test). On kernel 4.15.0.20.21, system does not 
restore.
However, system still does not restore from step 10 (echo none > 
/sys/power/pm_test).


** Attachment added: "Debug files kernel 4.20.0-042000.zip"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299007/+attachment/5225769/+files/Debug%20files%20kernel%204.20.0-042000.zip

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

Title:
  [ASUS Z87-PRO] suspend/resume failure

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

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

[Bug 1299007] Re: [ASUS Z87-PRO] suspend/resume failure

2018-12-29 Thread Sam

Debug info for Kernel 4.15.0.20.21

https://wiki.ubuntu.com/DebuggingKernelSuspend
Debugging information to provide in the bug report

Kernel 4.15.0.20.21
=

1. Issue occurs with resume from 'Suspend to ram' (not hibernate).

2. Suspend action initiated by clicking Suspend in the GUI.

3. Resume initiated by pressing power button on PC case.

4. Attached.

5. (echo freezer > /sys/power/pm_test) UI froze for few seconds. System
returned to normal operation after few seconds.

6. (echo devices > /sys/power/pm_test) Display switched off for few seconds.
Standby flashing LED on PC case not observed (remained in solid 'ON' state).
Display switched on again - showed Gnome UI in the same state as immediately
before suspend. System not responsive. Caps-lock button not responding; USB
keyboard remove-reattach not effective. Rebooted manually (cycled power).
After display switched on again; system started to respond to ping from
network. Could not connect via ssh, despite being able to ping.

7. (echo platform > /sys/power/pm_test) Display switched off for few
seconds. Standby flashing LED on PC case not observed (remained in solid
'ON' state). Display switched on again - showed Gnome UI in the same
state as immediately before suspend. System not responsive. Caps-lock
button not responding; USB keyboard remove-reattach not effective.
Rebooted manually (cycled power).

8. (echo processors > /sys/power/pm_test) Display switched off for few
seconds. Standby flashing LED on PC case not observed (remained in solid
'ON' state). Display switched on again - showed Gnome UI in the same
state as immediately before suspend. System not responsive. Caps-lock
button not responding; USB keyboard remove-reattach not effective.
Rebooted manually (cycled power).

9. (echo core > /sys/power/pm_test) Display switched off for few
seconds. Standby flashing LED on PC case not observed (remained in solid
'ON' state). Display switched on again - showed Gnome UI in the same
state as immediately before suspend. System not responsive. Caps-lock
button not responding; USB keyboard remove-reattach not effective.
Rebooted manually (cycled power).

10. (echo none > /sys/power/pm_test) Display switched off. All fans
powered off (CPU fan, PSU fan). Standby LED flashing on PC case. Resume
initiated by pressing power button on PC case. Display remained off -
LCD monitor standby LED flashing. System not responsive. Caps-lock
button not responding; USB keyboard remove-reattach not effective.
Rebooted manually (cycled power).

1 2 >

1 - 100 of 112 matches

Mail list logo