[Bug 1906294] Re: systemd-journal hang after chromium is closed

2020-12-01 Thread Per-Inge
Has been fixed after updates. Probably one of these
Start-Date: 2020-12-01  19:43:08
Commandline: aptdaemon role='role-commit-packages' sender=':1.241'
Upgrade: xserver-common:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), 
xserver-xorg-core:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), 
xserver-xorg-legacy:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), 
xserver-xephyr:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), xwayland:amd64 
(2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1)
End-Date: 2020-12-01  19:43:10

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

Title:
  systemd-journal hang after chromium is closed

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

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

[Bug 1905946] Re: Mouse stop moving after few seconds. restart at click

2020-11-30 Thread Per-Inge
I installed all the updates in proposed (main repository) and now have
libfprint-2-2 1:1.90.3tod1-0ubuntu3 installed
This fixed the problem on my computer

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

Title:
  Mouse stop moving after few seconds. restart at click

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

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

[Bug 1906294] [NEW] systemd-journal hang after chromium is closed

2020-11-30 Thread Per-Inge
Public bug reported:

CPU usage after close of Chromium is 98,7% by systemd-jounal after these
updates

Start-Date: 2020-11-30  18:39:16
Commandline: packagekit role='update-packages'
Upgrade: gir1.2-mutter-7:amd64 (3.38.1-1ubuntu1, 3.38.1-2ubuntu1), snapd:amd64 
(2.47.1+20.10.1, 2.48+20.10), libmutter-7-0:amd64 (3.38.1-1ubuntu1, 
3.38.1-2ubuntu1), mutter-common:amd64 (3.38.1-1ubuntu1, 3.38.1-2ubuntu1), 
gir1.2-snapd-1:amd64 (1.57-0ubuntu4, 1.58-0ubuntu0.20.10.0), 
libsnapd-glib1:amd64 (1.57-0ubuntu4, 1.58-0ubuntu0.20.10.0)
End-Date: 2020-11-30  18:39:25

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Uname: Linux 5.10.0-051000rc3-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 30 19:20:00 2020
InstallationDate: Installed on 2020-11-14 (16 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Snap: chromium 87.0.4280.66 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy snap

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

Title:
  systemd-journal hang after chromium is closed

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

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

[Bug 1905946] Re: Mouse stop moving after few seconds. restart at click

2020-11-27 Thread Per-Inge
Same problem mouse is Steeleries Rival 110
My configuration is
p-i@pi-TUF-Gaming-B550M:~$ inxi -Fz
System:Kernel: 5.8.0-25-generic x86_64 bits: 64 Desktop: GNOME 3.38.1 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial:  
   Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1212 
   date: 11/04/2020 
CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3072 KiB 
   Speed: 2196 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 2198 2: 
2198 3: 2199 4: 2200 5: 2199 6: 2194 7: 2198 
   8: 2201 9: 2193 10: 2195 11: 2194 12: 2192 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
   v: kernel 
   Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: 
fbdev,modesetting,radeon,vesa 
   resolution: 2560x1440~60Hz 
   OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.38.0 
5.8.0-25-generic LLVM 11.0.0) v: 4.6 Mesa 20.2.2 
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel 
   Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel 
   Sound Server: ALSA v: k5.8.0-25-generic 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
   IF: wlp6s0 state: up mac:  
   Device-2: Realtek RTL8125 2.5GbE driver: N/A 
Drives:Local Storage: total: 1.36 TiB used: 24.03 GiB (1.7%) 
   ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 
465.76 GiB 
   ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 465.76 
GiB 
   ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 
GiB 
Partition: ID-1: / size: 456.96 GiB used: 24.00 GiB (5.3%) fs: ext4 dev: 
/dev/sda2 
Swap:  ID-1: swap-1 type: file size: 2.00 GiB used: 0 KiB (0.0%) file: 
/swapfile 
Sensors:   System Temperatures: cpu: 0.0 C mobo: N/A gpu: amdgpu temp: 46.0 C 
   Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
Info:  Processes: 362 Uptime: 2m Memory: 15.54 GiB used: 2.20 GiB (14.2%) 
Shell: Bash inxi: 3.1.09 
p-i@pi-TUF-Gaming-B550M:~$

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

Title:
  Mouse stop moving after few seconds. restart at click

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

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

[Bug 1904382] Re: Always crash when opened

2020-11-22 Thread Per-Inge
Fixed in this update
Start-Date: 2020-11-22  09:54:35
Commandline: apt upgrade
Requested-By: p-i (1000)
Upgrade: libc-ares2:amd64 (1.16.1-1ubuntu1, 1.17.1-1), libkrb5-3:amd64 
(1.17-10, 1.17-10ubuntu1), libgssapi-krb5-2:amd64 (1.17-10, 1.17-10ubuntu1), 
mscompress:amd64 (0.4-7, 0.4-8), libcurl4:amd64 (7.68.0-1ubuntu4, 
7.72.0-1ubuntu1), libk5crypto3:amd64 (1.17-10, 1.17-10ubuntu1), 
ubuntu-drivers-common:amd64 (1:0.8.6.1, 1:0.8.6.2), libkrb5support0:amd64 
(1.17-10, 1.17-10ubuntu1), python3-dbus:amd64 (1.2.16-3, 1.2.16-4), 
libcurl3-gnutls:amd64 (7.68.0-1ubuntu4, 7.72.0-1ubuntu1)
End-Date: 2020-11-22  09:54:37

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

Title:
  Always crash when opened

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

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

[Bug 1904878] Re: update-manager crashed with dbus.exceptions.DBusException in update(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

2020-11-22 Thread Per-Inge
Fixed in this update

Start-Date: 2020-11-22  09:54:35
Commandline: apt upgrade
Requested-By: p-i (1000)
Upgrade: libc-ares2:amd64 (1.16.1-1ubuntu1, 1.17.1-1), libkrb5-3:amd64 
(1.17-10, 1.17-10ubuntu1), libgssapi-krb5-2:amd64 (1.17-10, 1.17-10ubuntu1), 
mscompress:amd64 (0.4-7, 0.4-8), libcurl4:amd64 (7.68.0-1ubuntu4, 
7.72.0-1ubuntu1), libk5crypto3:amd64 (1.17-10, 1.17-10ubuntu1), 
ubuntu-drivers-common:amd64 (1:0.8.6.1, 1:0.8.6.2), libkrb5support0:amd64 
(1.17-10, 1.17-10ubuntu1), python3-dbus:amd64 (1.2.16-3, 1.2.16-4), 
libcurl3-gnutls:amd64 (7.68.0-1ubuntu4, 7.72.0-1ubuntu1)
End-Date: 2020-11-22  09:54:37

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

Title:
  update-manager crashed with dbus.exceptions.DBusException in update():
  org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited
  with unknown return code 1

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

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

[Bug 1904878] Re: update-manager crashed with dbus.exceptions.DBusException in update(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

2020-11-19 Thread Per-Inge
** Information type changed from Private to Public

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

Title:
  update-manager crashed with dbus.exceptions.DBusException in update():
  org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited
  with unknown return code 1

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

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

[Bug 1904866] Re: Software updater fails to update with errors

2020-11-19 Thread Per-Inge
I got the bug on Ubuntu with the ubuntu-desktop

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

Title:
  Software updater fails to update with errors

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

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

Re: [Bug 1904382] Re: Always crash when opened

2020-11-16 Thread Per-Inge
I think the bug is reported in
https://bugs.launchpad.net/bugs/1904217
When I tried to report the crash I got the message that it already is
reported, but I don't have permission to open the bug.

Den mån 16 nov. 2020 kl 10:56 skrev Julian Andres Klode <
1904...@bugs.launchpad.net>:

> Thanks for your bug report. Unfortunately, you have not included any
> error messages like the stacktrace from such a crash, and the bug cannot
> be analyzed further without them.
>
> ** Changed in: update-manager (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1904382
>
> Title:
>   Always crash when opened
>
> Status in update-manager package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Crash when opened on a new hirsute installation.
>   sudo apt update and sudo apt upgrade work OK
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: update-manager 1:20.10.1
>   ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
>   Uname: Linux 5.8.0-25-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu51
>   Aptdaemon:
>
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Nov 16 09:16:05 2020
>   GsettingsChanges:
>b'com.ubuntu.update-manager' b'launch-count' b'4'
>b'com.ubuntu.update-manager' b'launch-time' b'int64 1605513900'
>   InstallationDate: Installed on 2020-11-15 (0 days ago)
>   InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201115)
>   PackageArchitecture: all
>   SourcePackage: update-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1904382/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  Always crash when opened

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

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

[Bug 1904382] [NEW] Always crash when opened

2020-11-16 Thread Per-Inge
Public bug reported:

Crash when opened on a new hirsute installation.
sudo apt update and sudo apt upgrade work OK

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: update-manager 1:20.10.1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu51
Aptdaemon:
 
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 16 09:16:05 2020
GsettingsChanges:
 b'com.ubuntu.update-manager' b'launch-count' b'4'
 b'com.ubuntu.update-manager' b'launch-time' b'int64 1605513900'
InstallationDate: Installed on 2020-11-15 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201115)
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  Always crash when opened

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

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

Re: [Bug 1900998] Re: ubiquity graphic problems

2020-10-22 Thread Per-Inge
Installed the 20201022 ISO.
This worked better and the 2:nd time the installation worked without
graphic issues
The 1:st time I got a system hang, when I used the mouse to scroll down to
find the keyboard layout. Had to do a hard reset of the computer.

Den tors 22 okt. 2020 kl 15:38 skrev Per-Inge Hallin <
peringe.hal...@gmail.com>:

> A screenshot looks OK. But this time I got a gnome-shell crash and I
> uploaded this. Probably it's a gnome-shell problem and not ubiquity.
>
> Den tors 22 okt. 2020 kl 14:01 skrev Jean-Baptiste Lallement <
> 1900...@bugs.launchpad.net>:
>
>> Thanks for your report. Can you please attach a screenshot of the issue?
>>
>> ** Changed in: ubiquity (Ubuntu)
>>Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1900998
>>
>> Title:
>>   ubiquity graphic problems
>>
>> Status in ubiquity package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   USB booted OK, graphic problem started when selecting keyboard and
>> continued during the installation with unreadable text and slide show with
>> graphic problems.
>>   Hard to select keyboard, had to guess the right keyboard was selected.
>>   Installation is OK with Nvidia driver.
>>   UEFI install
>>   GPU: Nvidia GEFORCE GTX 660
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.10
>>   Package: ubiquity (not installed)
>>   ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
>>   Uname: Linux 5.8.0-25-generic x86_64
>>   NonfreeKernelModules: nvidia_modeset nvidia
>>   ApportVersion: 2.20.11-0ubuntu50
>>   Architecture: amd64
>>   CasperMD5CheckResult: skip
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Thu Oct 22 12:41:51 2020
>>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
>> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
>>   InstallationDate: Installed on 2020-10-22 (0 days ago)
>>   InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64
>> (20201021.2)
>>   SourcePackage: ubiquity
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900998/+subscriptions
>>
>
>
> --
> Skickat från min nya mailadress
>


-- 
Skickat från min nya mailadress

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

Title:
  ubiquity graphic problems

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

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

Re: [Bug 1900998] Re: ubiquity graphic problems

2020-10-22 Thread Per-Inge
A screenshot looks OK. But this time I got a gnome-shell crash and I
uploaded this. Probably it's a gnome-shell problem and not ubiquity.

Den tors 22 okt. 2020 kl 14:01 skrev Jean-Baptiste Lallement <
1900...@bugs.launchpad.net>:

> Thanks for your report. Can you please attach a screenshot of the issue?
>
> ** Changed in: ubiquity (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1900998
>
> Title:
>   ubiquity graphic problems
>
> Status in ubiquity package in Ubuntu:
>   Incomplete
>
> Bug description:
>   USB booted OK, graphic problem started when selecting keyboard and
> continued during the installation with unreadable text and slide show with
> graphic problems.
>   Hard to select keyboard, had to guess the right keyboard was selected.
>   Installation is OK with Nvidia driver.
>   UEFI install
>   GPU: Nvidia GEFORCE GTX 660
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.10
>   Package: ubiquity (not installed)
>   ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
>   Uname: Linux 5.8.0-25-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu50
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Oct 22 12:41:51 2020
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
>   InstallationDate: Installed on 2020-10-22 (0 days ago)
>   InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64
> (20201021.2)
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900998/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  ubiquity graphic problems

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

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

[Bug 1900998] [NEW] ubiquity graphic problems

2020-10-22 Thread Per-Inge
Public bug reported:

USB booted OK, graphic problem started when selecting keyboard and continued 
during the installation with unreadable text and slide show with graphic 
problems.
Hard to select keyboard, had to guess the right keyboard was selected.
Installation is OK with Nvidia driver.
UEFI install
GPU: Nvidia GEFORCE GTX 660

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 22 12:41:51 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2020-10-22 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201021.2)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy ubiquity-20.10.13

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

Title:
  ubiquity graphic problems

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

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

Re: [Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist(

2020-07-14 Thread Per-Inge
I don't have problems with suspend any longer. I think this bug is
fixed.

However I'm not using the standard kernel.  I'm using Kernel:
5.7.7-050707-generic x86_64.
I had a problem with Chrome freezing the computer and this kernel fixed
that problem.

Den tis 14 juli 2020 kl 16:01 skrev Martin Wimpress <
1868...@bugs.launchpad.net>:

> ** Changed in: gnome-shell (Ubuntu Focal)
>  Assignee: (unassigned) => Daniel van Vugt (vanvugt)
>
> ** Changed in: gnome-shell (Ubuntu)
>  Assignee: (unassigned) => Daniel van Vugt (vanvugt)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868660
>
> Title:
>   gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
>   from st_texture_cache_load_gicon() from st_icon_update() from
>   _g_closure_invoke_va() from g_signal_emit_valist()
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding gnome-shell.  This problem was most recently seen with package
> version 3.35.91-1ubuntu2, the problem page at
> https://errors.ubuntu.com/problem/f48b96bcfbbd221faf772da51dae29be310cbd9c
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker and are a software
> developer, you can request it at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868660/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

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

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

[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda

2020-07-09 Thread Per-Inge
Made an USB boot disk with mkusb and tested the Groovy Ubuntu Desktop
amd64 version 20200709.

Worked with MBR/BIOS mode on a desktop computer with an AMD Bulldozer CPU and 
Nvidia 1660 GPU. There were however some peculiar things
- Graphical artifacts during the installation. Perhaps "Safe graphics mode" is 
needed.
- Had to power off after the installation to boot the computer
- At boot you get the message: BootOrder not found. Initializing default. 
Creating boot entry "Boot002" with label "ubuntu" for file 
\EFI\ubuntu\shimx64.efi

Worked as expected on a newer computer with Ryzen CPU and Radeon GPU.

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

Title:
  on flavours ubiquity: bootloader failed on /dev/vda

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

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

[Bug 1885414] Re: ubiquity: bootloader failed on /dev/vda

2020-07-08 Thread Per-Inge
Tested installation in VirtualBox of Ubuntu desktop amd64 version
20200707.1 in both MBR and EFI mode. Both worked OK.

Tested to install from USB in MBR mode on a computer with Nvidia GPU.
Doesn't work. get an error message about /DEV/SR0 No media found

Tested on another computer in EFI mode. Doesn't work. Error message
"Unable to find a medium container a live file system"

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

Title:
  ubiquity: bootloader failed on /dev/vda

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

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

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

2020-06-19 Thread Per-Inge
p-i@asus-b450-f:~$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.36.3-1ubuntu1~20.04.2
  Candidate: 3.36.3-1ubuntu1~20.04.2
  Version table:
 *** 3.36.3-1ubuntu1~20.04.2 500
500 http://se.archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
100 /var/lib/dpkg/status
 3.36.2-1ubuntu1~20.04.1 500
500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
 3.36.1-5ubuntu1 500
500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages
p-i@asus-b450-f:~

Den fre 19 juni 2020 kl 16:05 skrev Marco Trevisan (Treviño) <
1877...@bugs.launchpad.net>:

> Please, ensure the version with the command I gave to you
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1877760
>
> Title:
>   gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
>   g_str_has_prefix() from _st_theme_node_ensure_background() from
>   st_theme_node_paint_equal
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   GNOME shell crashes on extensions loading / updates
>
>   [ Test case ]
>- No clear test case, normally may happen during screen
> locking/unlocking
>- But crashes should be monitored at
>
> https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3
>
>   [ Regression potential ]
>
>   Stylesheet memory could be leaked
>
>   ---
>
>   Started the computer from suspend. Started Gmail from Dash to Panel.
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.10
>   Package: gnome-shell 3.36.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu33
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May  9 18:30:48 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-04-16 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200415.2)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu
> (%rdi),%ymm1
>PC (0x7fe9fdcc3e41) ok
>source "(%rdi)" (0xf0250) not located in a known VMA region (needed
> readable region)!
>destination "%ymm1" ok
>   SegvReason: reading unknown VMA
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
>g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>_st_theme_node_ensure_background () from /usr/lib/gnome-shell/
> libst-1.0.so
>st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>   Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

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

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

2020-06-19 Thread Per-Inge
No, this is noy groovy. I have downloaded Focal Daily from
http://iso.qa.ubuntu.com/qatracker/milestones/408/builds some days ago and
updates regularly and I think the developer option is set.
After an update today the Gnome version is " Desktop: Gnome 3.36.3". I have
made a couple of suspends and there is no crash..

Den fre 19 juni 2020 kl 12:30 skrev Marco Trevisan (Treviño) <
1877...@bugs.launchpad.net>:

> > I'm now using the development version of 20.04.1. Will this fix be
> included?
>
> What do you mean by that? Are you using groovy?
>
> However, to check, just look what version of gnome-shell you're running via
>  - apt-cache policy gnome-shell
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1877760
>
> Title:
>   gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
>   g_str_has_prefix() from _st_theme_node_ensure_background() from
>   st_theme_node_paint_equal
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   GNOME shell crashes on extensions loading / updates
>
>   [ Test case ]
>- No clear test case, normally may happen during screen
> locking/unlocking
>- But crashes should be monitored at
>
> https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3
>
>   [ Regression potential ]
>
>   Stylesheet memory could be leaked
>
>   ---
>
>   Started the computer from suspend. Started Gmail from Dash to Panel.
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.10
>   Package: gnome-shell 3.36.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu33
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May  9 18:30:48 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-04-16 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200415.2)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu
> (%rdi),%ymm1
>PC (0x7fe9fdcc3e41) ok
>source "(%rdi)" (0xf0250) not located in a known VMA region (needed
> readable region)!
>destination "%ymm1" ok
>   SegvReason: reading unknown VMA
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
>g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>_st_theme_node_ensure_background () from /usr/lib/gnome-shell/
> libst-1.0.so
>st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>   Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

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

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

2020-06-19 Thread Per-Inge
I'm now using the development version of 20.04.1. Will this fix be
included?

Den fre 19 juni 2020 kl 07:55 skrev Timo Aaltonen <
1877...@bugs.launchpad.net>:

> Hello Per-Inge, or anyone else affected,
>
> Accepted gnome-shell into focal-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/gnome-
> shell/3.36.3-1ubuntu1~20.04.2 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> focal to verification-done-focal. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-focal. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: gnome-shell (Ubuntu Focal)
>Status: Fix Released => Fix Committed
>
> ** Tags added: verification-needed verification-needed-focal
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1877760
>
> Title:
>   gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
>   g_str_has_prefix() from _st_theme_node_ensure_background() from
>   st_theme_node_paint_equal
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   GNOME shell crashes on extensions loading / updates
>
>   [ Test case ]
>- No clear test case, normally may happen during screen
> locking/unlocking
>- But crashes should be monitored at
>
> https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3
>
>   [ Regression potential ]
>
>   Stylesheet memory could be leaked
>
>   ---
>
>   Started the computer from suspend. Started Gmail from Dash to Panel.
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.10
>   Package: gnome-shell 3.36.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu33
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May  9 18:30:48 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-04-16 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200415.2)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu
> (%rdi),%ymm1
>PC (0x7fe9fdcc3e41) ok
>source "(%rdi)" (0xf0250) not located in a known VMA region (needed
> readable region)!
>destination "%ymm1" ok
>   SegvReason: reading unknown VMA
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
>g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>_st_theme_node_ensure_background () from /usr/lib/gnome-shell/
> libst-1.0.so
>st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>   Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

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

Re: [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() when using dash-to-panel

2020-05-21 Thread Per-Inge
Started Groovy Gorilla today and update. Suspend don't crash gnome-shell.
Perhaps "gnome-shell-extension-desktop-icons:amd64 (20.04.0-1, 20.04.0-2)"
fixed the problem.

Den ons 20 maj 2020 kl 19:30 skrev Per-Inge
<1877...@bugs.launchpad.net>:

> Used apport-cli to report and that worked. Marked the report as bug
> 184.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/184
>
> Title:
>   gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
>   when using dash-to-panel
>
> Status in GNOME Shell:
>   Unknown
> Status in Gnome Shell Extension Dash To Panel:
>   Fix Released
> Status in gnome-shell package in Ubuntu:
>   Fix Committed
>
> Bug description:
>   Seems to be reproducible
>   Suspend the computer
>   Start the computer from suspend
>   Start chrome gmail.
>   Has happened two times
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 20.10
>   Package: gnome-shell 3.36.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu33
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May  9 20:00:47 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-04-16 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200415.2)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7fe1b40c4252
> <_st_theme_node_ensure_background+226>: mov(%rax),%r12
>PC (0x7fe1b40c4252) ok
>source "(%rax)" (0x) not located in a known VMA region (needed
> readable region)!
>destination "%r12" ok
>   SegvReason: reading NULL VMA
>   Signal: 11
>   SourcePackage: gnome-shell
>   StacktraceTop:
>_st_theme_node_ensure_background () from /usr/lib/gnome-shell/
> libst-1.0.so
>st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>   Title: gnome-shell crashed with SIGSEGV in
> _st_theme_node_ensure_background()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/184/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  when using dash-to-panel

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

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

[Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() when using dash-to-panel

2020-05-20 Thread Per-Inge
Used apport-cli to report and that worked. Marked the report as bug
184.

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  when using dash-to-panel

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

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

Re: [Bug 1879043] Re: gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

2020-05-18 Thread Per-Inge
*** This bug is a duplicate of bug 184 ***
https://bugs.launchpad.net/bugs/184

OK,
when I send the crash report launchpad isn't opened. Might be because the
crash file _usr_bin_gnome.shell.1000.crash is 45 MB, the
file  _usr_bin_gnome.shell.1000.upload is 0 bytes and
the _usr_bin_gnome.shell.1000.uploaded is only 37 bytes.

Den mån 18 maj 2020 kl 08:55 skrev Daniel van Vugt <
daniel.van.v...@canonical.com>:

> *** This bug is a duplicate of bug 184 ***
> https://bugs.launchpad.net/bugs/184
>
> Without more information we will assume this is bug 184.
>
> In future please follow these steps to report crashes:
>
>
> https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
>
> ** This bug has been marked a duplicate of bug 184
>gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
> when using dash-to-panel
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1879043
>
> Title:
>   gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   It might be bug 184.
>   This is a new installation. During the installation After each change I
> made Suspend and restarted the computer and checked if gnome-shell had
> crashed.
>   Installed: Printer, Flatpaks, Sensory Perceptions, AlternateTab,
> Applications Menu, OpenWeather and Dash to Panel without crash.
>   The last thing I did before the crash was to "install" Gmail and Google
> Calender and put all my favorite applications in the panel. Left the
> computer to suspend, after 15 minutes, and restarted the computer.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>   Uname: Linux 5.4.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May 16 11:11:09 2020
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-05-16 (0 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879043/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

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

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

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

2020-05-16 Thread Per-Inge
I reinstalled and got a crash after suspend. It might be bug 184, but I
made a new one.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879043

Den fre 15 maj 2020 kl 22:41 skrev Marco Trevisan (Treviño) :

> No error reported for the SRU or groovy version for this crash at
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
> ** Tags removed: verification-needed verification-needed-focal
> ** Tags added: verification-done verification-done-focal
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868440
>
> Title:
>   gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
>   from _st_set_text_from_style()
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   gnome-shell crashes in st_theme_node_get_font_features()
>
>   [ Test case ]
>
>   No single reproducer, but try clicking multiple times in appindicators
>   in the system tray
>
>   [ Regression potential ]
>
>   Extensions are not correctly styled
>
>   ---
>
>
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
>   ---
>
>   This happened when I closed Chrome and moved the curser to "Power
>   Off/Log Out, Settings .."
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.35.91-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 22 11:22:08 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-03-15 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200315)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>st_theme_node_get_font_features () from /usr/lib/gnome-shell/
> libst-1.0.so
>_st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gnome-shell crashed with SIGSEGV in
> st_theme_node_get_font_features()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
  from _st_set_text_from_style()

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

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

[Bug 1879043] [NEW] gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

2020-05-16 Thread Per-Inge
Public bug reported:

It might be bug 184.
This is a new installation. During the installation After each change I made 
Suspend and restarted the computer and checked if gnome-shell had crashed.
Installed: Printer, Flatpaks, Sensory Perceptions, AlternateTab, Applications 
Menu, OpenWeather and Dash to Panel without crash.
The last thing I did before the crash was to "install" Gmail and Google 
Calender and put all my favorite applications in the panel. Left the computer 
to suspend, after 15 minutes, and restarted the computer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 11:11:09 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal package-from-proposed

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

Title:
  gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

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

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

[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()

2020-05-15 Thread Per-Inge
I don't know if this is related. It seems I always get a crash either when I 
start suspend or when I return from suspend. When I send the crash report 
launchpad don't open. The crash is in gnome-shell and the crash message is 
"gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()".
It might be related to my installation and I will reinstall Focal later today.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

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

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

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

2020-05-13 Thread Per-Inge
I installed the gnome related components from proposed, but this isn't on a
standard installation I'm using the oibaf ppa (4.6 Mesa 20.2.0-devel
(git-d510974 2020-05-06 focal-oibaf-ppa) and kernel 5.6.7-050607-generic
x86_64. After the update the Gnome desktop is Gnome 3.36.2.
This problem doesn't happen often, but I will use this configuration for
some time. Alternatively I also use a system on other hardware with Groovy
Gorilla. This system don't have any kernel or graphic driver changes.

Den tis 12 maj 2020 kl 22:21 skrev Brian Murray :

> Hello Per-Inge, or anyone else affected,
>
> Accepted gnome-shell into focal-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/gnome-
> shell/3.36.2-1ubuntu1~20.04.1 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> focal to verification-done-focal. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-focal. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: gnome-shell (Ubuntu Focal)
>Status: New => Fix Committed
>
> ** Tags added: verification-needed verification-needed-focal
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868440
>
> Title:
>   gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
>   from _st_set_text_from_style()
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   gnome-shell crashes in st_theme_node_get_font_features()
>
>   [ Test case ]
>
>   No single reproducer, but try clicking multiple times in appindicators
>   in the system tray
>
>   [ Regression potential ]
>
>   Extensions are not correctly styled
>
>   ---
>
>
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
>   ---
>
>   This happened when I closed Chrome and moved the curser to "Power
>   Off/Log Out, Settings .."
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.35.91-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 22 11:22:08 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-03-15 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200315)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>st_theme_node_get_font_features () from /usr/lib/gnome-shell/
> libst-1.0.so
>_st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gnome-shell crashed with SIGSEGV in
> st_theme_node_get_font_features()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
  from _st_set_text_from_style()

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

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

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

2020-05-07 Thread Per-Inge
I don't have a standard installation of Ubuntu 20.04 any longer. It's now
updated with kernel 5.6.7-050607-generic x86_64 and I'm also using
the oibaf-ppa.
I tried clicking multiple times in appindicators  in the system tray, but I
didn't get any error.
I run Fedora 32 on this computer too and I think I got this error also on
Fedora 32 before it was upgraded to gnome-shell 3.36.2.
I have these extensions installed: AlternateTab, Dash to Panel, OpenWeather
and Sensory Perception


Den tors 7 maj 2020 kl 18:41 skrev Marco Trevisan (Treviño) :

> ** Description changed:
>
> + [ Impact ]
> +
> + gnome-shell crashes in st_theme_node_get_font_features()
> +
> + [ Test case ]
> +
> + No single reproducer, but try clicking multiple times in appindicators
> + in the system tray
> +
> + [ Regression potential ]
> +
> + Extensions are not correctly styled
> +
> + ---
> +
>
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
>   ---
>
>   This happened when I closed Chrome and moved the curser to "Power
>   Off/Log Out, Settings .."
>
> - ProblemType: Crash
> - DistroRelease: Ubuntu 20.04
> + ProblemType: CrashDistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.35.91-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 22 11:22:08 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-03-15 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200315)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
> - Signal: 11
> - SourcePackage: gnome-shell
> + Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>st_theme_node_get_font_features () from /usr/lib/gnome-shell/
> libst-1.0.so
>_st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gnome-shell crashed with SIGSEGV in
> st_theme_node_get_font_features()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> ** Changed in: gnome-shell (Ubuntu)
>  Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
>
> ** Also affects: gnome-shell (Ubuntu Focal)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868440
>
> Title:
>   gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
>   from _st_set_text_from_style()
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   New
>
> Bug description:
>   [ Impact ]
>
>   gnome-shell crashes in st_theme_node_get_font_features()
>
>   [ Test case ]
>
>   No single reproducer, but try clicking multiple times in appindicators
>   in the system tray
>
>   [ Regression potential ]
>
>   Extensions are not correctly styled
>
>   ---
>
>
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
>   ---
>
>   This happened when I closed Chrome and moved the curser to "Power
>   Off/Log Out, Settings .."
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.35.91-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 22 11:22:08 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-03-15 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200315)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>st_theme_node_get_font_features () from /usr/lib/gnome-shell/
> libst-1.0.so
>_st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gnome-shell crashed with SIGSEGV in
> st_theme_node_get_font_features()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions
>


-- 
Skickat från min nya mailadress

-- 
You received 

[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

2020-04-08 Thread Per-Inge
No, I'm not using gTile. To Lock the screen and log in also works OK. My
gnome-shell crashes don't happen that often and I haven't found a way to
reproduce the crash.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

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

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

[Bug 1835660] Re: initramfs unpacking failed

2020-04-02 Thread Per-Inge
I added the fix in comment #33 on two computers and this fixed the
initramfs problem.

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

Title:
  initramfs unpacking failed

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

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

[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()

2020-03-27 Thread Per-Inge
Thought this was fixed with gnome 3.36, but I got it when I 1:st closed
Gmail and then Chrome.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

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

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

[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

2020-03-23 Thread Per-Inge
Happened again, but now it refers to icon instead of font.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

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

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

Re: [Bug 1862792] Re: gnome-shell always crash after boot

2020-02-12 Thread Per-Inge
This is the result:

Error reports sent from this system
Occurred Received Problem Type Program
2020-02-11 19:02 2020-02-11 18:02 UTC Crash gnome-shell
2020-02-11 06:02 2020-02-11 05:02 UTC Crash gnome-shell
2020-02-10 11:02 2020-02-10 11:02 UTC Crash gnome-shell
2020-02-09 12:02 2020-02-09 12:02 UTC Crash gnome-shell
2020-02-08 09:02 2020-02-08 08:02 UTC Crash gnome-shell
2020-02-03 17:02 2020-02-03 16:02 UTC Crash /usr/lib/xorg/Xorg
2020-02-03 07:02 2020-02-03 07:02 UTC Crash /usr/lib/xorg/Xorg
2020-01-24 15:01 2020-01-24 14:01 UTC Crash google-chrome-stable
2020-01-17 21:01 2020-01-17 20:01 UTC Crash gnome-shell
2020-01-13 18:01 2020-01-13 17:01 UTC Crash cups-browsed
2019-12-30 21:12 2019-12-30 20:12 UTC Crash google-chrome-stable
2019-12-27 19:12 2019-12-27 18:12 UTC Crash google-chrome-stable
2019-12-27 12:12 2019-12-27 13:12 UTC Crash cups-browsed

These are the links:
https://errors.ubuntu.com/oops/31013d32-4cfd-11ea-a96b-fa163e983629
https://errors.ubuntu.com/oops/8269e776-4c91-11ea-a07a-fa163e6cac46
https://errors.ubuntu.com/oops/e4e4e6ec-4bfa-11ea-a95c-fa163e983629
https://errors.ubuntu.com/oops/5f9cd9b2-4b3b-11ea-a957-fa163e983629
https://errors.ubuntu.com/oops/650b32dc-4a4e-11ea-a953-fa163e983629
https://errors.ubuntu.com/oops/234b0822-46a3-11ea-aa47-fa163e6cac46
https://errors.ubuntu.com/oops/b2bebda8-4655-11ea-b902-fa163e102db1
https://errors.ubuntu.com/oops/65f83450-3eb8-11ea-a7c8-fa163ee63de6
https://errors.ubuntu.com/oops/a46d4394-3966-11ea-b219-fa163e983629
https://errors.ubuntu.com/oops/cb2e2fc2-3626-11ea-b89d-fa163e102db1
https://errors.ubuntu.com/oops/e2494484-2b44-11ea-a75f-fa163ee63de6
https://errors.ubuntu.com/oops/b45882ec-28d8-11ea-b84d-fa163e102db1
https://errors.ubuntu.com/oops/70a7627c-28b0-11ea-b1c1-fa163e983629

Den ons 12 feb. 2020 kl 03:20 skrev Daniel van Vugt <
daniel.van.v...@canonical.com>:

> It sounds like the main issue is that Xwayland has crashed first:
>
> [   31.095070] pi-asus-b450f-gaming gnome-shell[1400]: Connection to
> xwayland lost
>
> Please follow the steps in comment #2 to help us diagnose the problem
> further.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1862792
>
> Title:
>   gnome-shell always crash after boot
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   gnome-shell always crash after boot with an UnreportableReason. This is
> in a Wayland session.
>   There are no stability issues after boot.
>
>   I get this information in the terminal after the command ubuntu-bug
>
>   p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
>   p-i@pi-asus-b450f-gaming:~$
> [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID
> data: manufacturer id
>   [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)]
> InitializeSandbox() called with multiple threads in process gpu-process.
>
> [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)]
> GetVSyncParametersIfAvailable() failed for 1 times!
>
>   ERROR:gl goes from 1 to 19.
>
>   In Settings the Display is named Microstep 27"
>   The problem might be hardware related:
>   Mobo: ASUSTeK model: ROG STRIX B450-F GAMING
>   GPU: AMD Navi 10 Radeon RX 5700
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.34.3-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
>   Uname: Linux 5.4.0-12-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu16
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Feb 11 16:43:08 2020
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-02-08 (3 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200207.2)
>   RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862792/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell always crash after boot

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

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

[Bug 1862792] [NEW] gnome-shell always crash after boot

2020-02-11 Thread Per-Inge
Public bug reported:

gnome-shell always crash after boot with an UnreportableReason. This is in a 
Wayland session. 
There are no stability issues after boot. 

I get this information in the terminal after the command ubuntu-bug

p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
p-i@pi-asus-b450f-gaming:~$ 
[8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: 
manufacturer id
[8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] 
GetVSyncParametersIfAvailable() failed for 1 times!

ERROR:gl goes from 1 to 19.

In Settings the Display is named Microstep 27"
The problem might be hardware related:
Mobo: ASUSTeK model: ROG STRIX B450-F GAMING
GPU: AMD Navi 10 Radeon RX 5700

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 11 16:43:08 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-02-08 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2)
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-shell always crash after boot

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

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

[Bug 1835660] Re: initramfs unpacking failed

2020-01-16 Thread Per-Inge
I get different behavior depending on how I boot the computer using the BIOS 
boot menu
- When I select sda with Ubuntu 20.04, I don't get the error message
- When I select sdc with Fedora 31 and select Ubuntu from Fedora's boot menu I 
get the error message

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

Title:
  initramfs unpacking failed

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

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

[Bug 1835660] Re: initramfs unpacking failed

2020-01-16 Thread Per-Inge
Added Fedora 31 and made a triple boot system with Ubuntu 20.04, Windows 10 and 
Fedora 31.
Fedora stored the boot record in /dev/sdc1 and I had to change boot disk to sdc 
in BIOS.
Fedora provides a boot menu with
Fedora
Ubuntu
Windows
When I start Ubuntu via the Fedora boot menu I get this error message.

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

Title:
  initramfs unpacking failed

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

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

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-12-28 Thread Per-Inge
I don't know if this is related but it fixed my problem with wake up from 
suspend.
This is on a desktop with an Asus Rog Strix B450-F Gaming motherboard and Focal 
Fossa.

I have changed these settings in BIOS
- Used DOCP settings on the memory
- USB power delivery in SoftOff is set to Disable
- PSS support is set to enable
- Serial Port is set to OFF
In AMD CBS
- IOMMU is set to Disabled
- Global C-state control is set to enable
- Power Supply Idle Control is set to Low Current Idle

I think the most important setting is to disable IOMMU. Instead I have
added "iommu=soft" in GRUB_CMDLINE_LINUX="" in /etc/default/grub

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

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

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

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

2019-12-15 Thread Per-Inge
On computers with HDA or SDA drives it is possible to disconnect all drives 
except the installation drive to install grub on the wanted drive.
This is however not a practical solution with NVme drives.
As I want to use the development version of Ubuntu early this is normally the 
last installation and will provide the used grub. To have to use grub of the 
development version gives a high risk to crash the whole computer.
I suppose this also is the case when you want to use IOS, Fedora or Windows as 
your "master" version in a computer and clearly separate the different 
installations.

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

Title:
  installer uses first EFI system partition found even when directed
  otherwise

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

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

[Bug 1846318] [NEW] Placement set to Left

2019-10-02 Thread Per-Inge
Public bug reported:

When Placement in Windows Titlebars is set to Left, gnome-tweaks opens in a too 
small window and the menu to select view isn't shown.
Test case:
Set placement to Left
Open gnome-tweaks
Enlarge the window and the menu is shown.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-tweaks 3.34.0-2
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  2 11:53:07 2019
InstallationDate: Installed on 2019-08-02 (60 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
PackageArchitecture: all
SourcePackage: gnome-tweaks
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Placement set to Left

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

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

Re: [Bug 1842022] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

2019-09-17 Thread Per-Inge
I haven't seen this bug for some time and the test case: log in, start
Gnome Gmail open a mail and click a link that opens Chrome works fine.
This is on ibus 1.5.19-4ubuntu2.

Den tis 17 sep. 2019 kl 21:50 skrev Gunnar Hjalmarsson <
1842...@bugs.launchpad.net>:

> IBus has just been updated in eoan. Can those of you who were hit by
> crashes please upgrade to ibus 1.5.21-1~exp2ubuntu1 and let us know if
> you notice any difference.
>
> ** Information type changed from Private to Public
>
> ** Changed in: ibus (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1842022
>
> Title:
>   ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()
>
> Status in ibus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Didn't do anything special. Logged out and checked if "Ubuntu" or
>   Ubuntu on Wayland" was set and "Ubuntu" was set.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 19.10
>   Package: ibus 1.5.19-4ubuntu2
>   ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
>   Uname: Linux 5.2.0-15-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Aug 30 08:47:18 2019
>   ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
>   InstallationDate: Installed on 2019-08-02 (27 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
>   ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
>   SegvAnalysis:
>Segfault happened at: 0x7fd6131738ce <__vfprintf_internal+30>:
>  mov%rsi,-0x4b8(%rbp)
>PC (0x7fd6131738ce) ok
>source "%rsi" ok
>destination "-0x4b8(%rbp)" (0x7ffdb5e52bf8) not located in a known VMA
> region (needed writable region)!
>Stack memory exhausted (SP below stack segment)
>   SegvReason: writing unknown VMA
>   Signal: 11
>   SourcePackage: ibus
>   StacktraceTop:
>?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
>ibus_bus_get_engines_by_names () from
> /lib/x86_64-linux-gnu/libibus-1.0.so.5
>?? ()
>?? ()
>g_cclosure_marshal_VOID__STRINGv () from
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: ibus-ui-gtk3 crashed with SIGSEGV in
> ibus_bus_get_engines_by_names()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1842022/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

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

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

Re: [Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

2019-09-16 Thread Per-Inge
Test case
Start Text Editor, Minimize and right click Text Editor in the Dock works
fine.

Den mån 16 sep. 2019 kl 17:50 skrev Launchpad Bug Tracker <
1843...@bugs.launchpad.net>:

> This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
> 66ubuntu19.10.2
>
> ---
> gnome-shell-extension-ubuntu-dock (66ubuntu19.10.2) eoan; urgency=medium
>
>   [ Marco Trevisan (Treviño) ]
>   * windowPreview: Use the window actor as Clone source (LP: #1843520)
>   * appIcons: Don't warn if variable is undefined
>   * appIcons: Enable scroll handler if enabled on construction
>   * docking: Don't warn if variable is undefined
>   * ubuntu-gschema.override: Enable fixed transparency with opacity at 70%
>
>  -- Marco Trevisan (Treviño)   Mon, 16 Sep 2019
> 14:28:09 +0200
>
> ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
>Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1843520
>
> Title:
>   ubuntu-dock right-click menu appears at the top-left corner of the
>   desktop (which in some cases is the wrong monitor) and is permanent
>
> Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Very recently the ubuntu-dock has started displaying some right-click
>   menus for pinned apps on the wrong monitor. It doesn't happen for all
>   the apps, but when it does, the menu is permanent but you can't click
>   on it and you have to restart gnome-shell with ALT-F2 'r' (which now
>   always kills some apps like firefox).
>
>   See attached screenshot where the menu for gnome-tweaks has appeared
>   at the top left of the top monitor.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1
>   Uname: Linux 5.3.0-050300rc8-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Sep 11 11:42:07 2019
>   InstallationDate: Installed on 2019-07-01 (71 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
>   PackageArchitecture: all
>   SourcePackage: gnome-shell-extension-ubuntu-dock
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1843520/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

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

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

[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

2019-09-11 Thread Per-Inge
One more problem.
After Log Out and Log In, Windows Titlebars are move from Left to Right. It is 
not possible to change them back to Left in Tweaks.

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

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

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

[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

2019-09-11 Thread Per-Inge
This also happens in this usecase.
Open an application for example text editor
Minimize the application
Right click the application in Ubuntu Dock

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

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

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

[Bug 1834957] [NEW] Automatic generated printer in CUPS

2019-07-01 Thread Per-Inge
Public bug reported:

The automatic generated printer don't work. It is possible to use Settings and 
add the printer.
It is possible to delete the faulty printer in Setting, but every time the 
printer is turned on the faulty printer is generated again.
It is also possible to use Settings to block the printer, but after login the 
printer is activated again.
There is also notifications about the printout until the printout is canceled.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.10-6ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  1 19:23:17 2019
InstallationDate: Installed on 2019-07-01 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190701)
Lpstat: device for Brother_HL_3140CW_series: 
implicitclass://Brother_HL_3140CW_series/
MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_HL_3140CW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Brother_HL_3140CW_series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=27f650c7-e62f-48f9-acce-c3c8e92f109e ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/13/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-990FXA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug eoan

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

Title:
  Automatic generated printer in CUPS

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

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

[Bug 1809936] Re: Installing GNOME shell extensions

2019-07-01 Thread Per-Inge
In a new installation of EOAN it's not possible to install gnome extensions in 
Chromium.
You get this error message
"Although GNOME Shell integration extension is running, native host connector 
is not detected." Refer documentation for instructions about installing 
connector."
The method advised in the instruction "GNOME Shell integration for Chrome 
Installation Guide"
$ sudo apt-get install chrome-gnome-shell
isn't working.

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

Title:
  Installing GNOME shell extensions

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

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

Re: [Bug 1821435] [NEW] nautilus crashed with SIGABRT in g_assertion_message()

2019-05-23 Thread Per-Inge
I set the developer option and updated. Got the nautilus update among other
updates.
Copied a file from the server to Documents and starred the file. Worked OK
and got no crash.
Copied another file from the server to Documents and starred it. Got no
crash, but the file didn't show up in Starred.
Restarted Nautilus, but this didn't help.
Logged out and logged in again. Open Documents and starred the file again.
This time the file showed up in Starred.

Did the same in Eoan with the same result.


Den lör 23 mars 2019 kl 08:15 skrev Per-Inge :

> Private bug reported:
>
> Copied a file from a server to ~/Documents and used the Star function.
> Got this crash two times with different files.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 19.04
> Package: nautilus 1:3.32.0-0ubuntu1
> ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
> Uname: Linux 5.0.0-8-generic x86_64
> ApportVersion: 2.20.10-0ubuntu23
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Mar 23 07:53:09 2019
> ExecutablePath: /usr/bin/nautilus
> InstallationDate: Installed on 2018-11-24 (118 days ago)
> InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124)
> ProcCmdline: /usr/bin/nautilus --gapplication-service
> Signal: 6
> SourcePackage: nautilus
> StacktraceTop:
>  ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>  g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>  nautilus_window_slot_get_location ()
>  ?? ()
>  g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> separator:
>
> usr_lib_nautilus:
>
> ** Affects: nautilus (Ubuntu)
>  Importance: Medium
>  Status: New
>
>
> ** Tags: amd64 apport-crash disco third-party-packages
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821435
>
> Title:
>   nautilus crashed with SIGABRT in g_assertion_message()
>
> Status in nautilus package in Ubuntu:
>   New
>
> Bug description:
>   Copied a file from a server to ~/Documents and used the Star function.
>   Got this crash two times with different files.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 19.04
>   Package: nautilus 1:3.32.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
>   Uname: Linux 5.0.0-8-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu23
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Mar 23 07:53:09 2019
>   ExecutablePath: /usr/bin/nautilus
>   InstallationDate: Installed on 2018-11-24 (118 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124)
>   ProcCmdline: /usr/bin/nautilus --gapplication-service
>   Signal: 6
>   SourcePackage: nautilus
>   StacktraceTop:
>?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>nautilus_window_slot_get_location ()
>?? ()
>g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   separator:
>
>   usr_lib_nautilus:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1821435/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

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

Re: [Bug 1821435] Re: nautilus crashed with SIGABRT in g_assertion_message()

2019-05-20 Thread Per-Inge
Will test om thursday

Den mån 20 maj 2019 16:30Łukasz Zemczak <1821...@bugs.launchpad.net>
skrev:

> Hello Per-Inge, or anyone else affected,
>
> Accepted nautilus into disco-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/nautilus/1:3.32.1-0ubuntu0.19.04.0
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-disco to verification-done-disco. If it does not fix
> the bug for you, please add a comment stating that, and change the tag
> to verification-failed-disco. In either case, without details of your
> testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: nautilus (Ubuntu Disco)
>Status: New => Fix Committed
>
> ** Tags added: verification-needed verification-needed-disco
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821435
>
> Title:
>   nautilus crashed with SIGABRT in g_assertion_message()
>
> Status in Nautilus:
>   Fix Released
> Status in nautilus package in Ubuntu:
>   Fix Released
> Status in nautilus source package in Disco:
>   Fix Committed
>
> Bug description:
>   Copied a file from a server to ~/Documents and used the Star function.
>   Got this crash two times with different files.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 19.04
>   Package: nautilus 1:3.32.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
>   Uname: Linux 5.0.0-8-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu23
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Mar 23 07:53:09 2019
>   ExecutablePath: /usr/bin/nautilus
>   InstallationDate: Installed on 2018-11-24 (118 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124)
>   ProcCmdline: /usr/bin/nautilus --gapplication-service
>   Signal: 6
>   SourcePackage: nautilus
>   StacktraceTop:
>?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>nautilus_window_slot_get_location ()
>?? ()
>g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   separator:
>
>   usr_lib_nautilus:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/1821435/+subscriptions
>

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

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

[Bug 1723760] Re: No restart after installation

2019-03-28 Thread Per-Inge
I haven't seen this when I have followed the 18.10 and 19.04
development.

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

Title:
  No restart after installation

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

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

Re: [Bug 1793249] Re: nautilus crashed with SIGABRT in g_assertion_message()

2019-01-15 Thread Per-Inge
I don't get that crash any longer.
I'm using Nautilus 3.26.4.

Den tis 15 jan. 2019 kl 18:35 skrev Sebastien Bacher
:

> The error tracker has a few report for that issue on
> https://errors.ubuntu.com/problem/82ca773a06c225419be734599e500c5f4b2100ac
>
> ** Information type changed from Private to Public
>
> ** Changed in: nautilus (Ubuntu)
>Importance: Medium => Low
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1793249
>
> Title:
>   nautilus crashed with SIGABRT in g_assertion_message()
>
> Status in nautilus package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This is a second crash when I searched for it87. Nautilus crashed after
> typing "i".
>   Related to bug report 1793248. Before I rebooted.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.10
>   Package: nautilus 1:3.26.4-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
>   Uname: Linux 4.18.0-7-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu11
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Sep 19 06:49:11 2018
>   ExecutablePath: /usr/bin/nautilus
>   GsettingsChanges:
>b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
>b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
>b'org.gnome.nautilus.window-state' b'sidebar-width' b'222'
>b'org.gnome.nautilus.window-state' b'geometry' b"'1108x849+1308+138'"
>b'org.gnome.nautilus.list-view' b'default-column-order' b"['name',
> 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where',
> 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']"
>   InstallationDate: Installed on 2018-08-09 (40 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64
> (20180809)
>   ProcCmdline: /usr/bin/nautilus --gapplication-service
>   Signal: 6
>   SourcePackage: nautilus
>   StacktraceTop:
>?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_assertion_message_expr () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
>?? ()
>?? ()
>?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>   Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   usr_lib_nautilus:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793249/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

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

[Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

2018-11-15 Thread Per-Inge
Thanks a lot.
This worked OK. I used kernel 4.19.1, but now I have removed it and I have also 
removed the "proposed package" setting. 
The power draw from the wall outlet at idle is now back to the normal 63W-65W.

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

Title:
  High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

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

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

[Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

2018-11-15 Thread Per-Inge
This kernel update didn't fix the the high power consumption on my
Radeon RX580 GPU.

Start-Date: 2018-11-14  06:51:30
Commandline: /usr/bin/unattended-upgrade
Install: linux-headers-4.18.0-11:amd64 (4.18.0-11.12, automatic), 
linux-image-4.18.0-11-generic:amd64 (4.18.0-11.12, automatic), 
linux-modules-extra-4.18.0-11-generic:amd64 (4.18.0-11.12, automatic), 
linux-modules-4.18.0-11-generic:amd64 (4.18.0-11.12, automatic), 
linux-headers-4.18.0-11-generic:amd64 (4.18.0-11.12, automatic)
Upgrade: linux-headers-generic:amd64 (4.18.0.10.11, 4.18.0.11.12), 
linux-image-generic:amd64 (4.18.0.10.11, 4.18.0.11.12), linux-generic:amd64 
(4.18.0.10.11, 4.18.0.11.12)
End-Date: 2018-11-14  06:52:01

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

Title:
  High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

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

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

Re: [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

2018-10-24 Thread Per-Inge
I followed the [Test Case] and got the expected result
  "Please note that the upstream fix reverts a new behaviour and as a
  result, when opening again gnome-software at step 6, the application
  opens on the home screen instead of resuming the last open page."
These are the updates I installed:
"Start-Date: 2018-10-24  20:07:00
Commandline: aptdaemon role='role-commit-packages' sender=':1.749'
Upgrade: gnome-software-plugin-snap:amd64 (3.30.2-0ubuntu5,
3.30.2-0ubuntu8), gnome-software:amd64 (3.30.2-0ubuntu5, 3.30.2-0ubuntu8),
ubuntu-software:amd64 (3.30.2-0ubuntu5, 3.30.2-0ubuntu8),
gnome-software-common:amd64 (3.30.2-0ubuntu5, 3.30.2-0ubuntu8)
End-Date: 2018-10-24  20:07:04"

Den ons 24 okt. 2018 kl 21:51 skrev Edson José dos Santos <
1798...@bugs.launchpad.net>:

> Ultima versão do Software Ubuntu Instalada vide anexo.
>
> Latest version of Ubuntu Software Installed see attachment
>
>
>
> ** Attachment added: "Captura de tela de 2018-10-24 16-29-16.png"
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+attachment/5205022/+files/Captura%20de%20tela%20de%202018-10-24%2016-29-16.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1798053
>
> Title:
>   [SRU] Click on the back icon in gnome-software doesn't work
>
> Status in gnome-software package in Ubuntu:
>   Fix Committed
> Status in gnome-software source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Test Case]
>
>   1. Open gnome-software
>   2. Press Ctrl+F and type "firefox" or any string that will return results
>   3. Click any result in the list (snap package or deb, already installed
> or not, it doesn't matter)
>   4. Observe that a new page is open showing details about the application
>   5. Close gnome-software
>   6. Open gnome-software again
>   7. Observe that the application is open on the last open page (details
> view about the application)
>   8. Click the back button (top-left corner)
>
>   Expected result: the application goes back to the list of search
>   results (or perhaps to the home screen)
>
>   Current result: nothing happens
>
>   Please note that the upstream fix reverts a new behaviour and as a
>   result, when opening again gnome-software at step 6, the application
>   opens on the home screen instead of resuming the last open page. This
>   is consistent with how gnome-software behaves in bionic. So after
>   applying the patch, steps 7 and 8 can be folded into one single step:
>   "Observe that the application is open on the home screen".
>
>
>   [Regression Potential]
>
>   Low. This is a cherry-pick of a self-contained trivial upstream commit
> that is already released in gnome-software 3.30.3 (
> https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774
> ).
>   As noted above, it does change the behaviour of re-opening the
> application after closing it, but it reverts it to the behaviour it had in
> bionic, so I don't think it should be considered a regression.
>
>   Re-opening the application after closing it in a number of different
>   situations should be thoroughly exercised to make sure that this
>   doesn't introduce any functional regression.
>
>
>   [Original Description]
>
>   Searched for Chromium, installed Chromium (snap version), clicked
> Launched and used chromium.
>   Went back to gnome-software and clicked the back button. Nothing
> happened. Restarted gnome-software and clicked the back button. Nothing
> happened.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: gnome-software 3.30.2-0ubuntu3 [modified:
> usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini]
>   ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
>   Uname: Linux 4.18.0-10-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu13
>   Architecture: amd64
>   CasperVersion: 1.399
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Oct 16 11:22:16 2018
>   InstalledPlugins:
>gnome-software-plugin-flatpak N/A
>gnome-software-plugin-limba   N/A
>gnome-software-plugin-snap3.30.2-0ubuntu3
>   LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181016)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-software
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   modified.conffile..etc.xdg.autostart.gnome-software-service.desktop:
> [deleted]
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  [SRU] Click on the back icon in gnome-software doesn't work

To manage notifications about this bug go to:

Re: [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

2018-10-24 Thread Per-Inge
To get the new version of ubuntu/gnome-software you have to enable
"Pre-released updates" in "Developer Options" and allow all updates of
ubuntu-software.

Den ons 24 okt. 2018 kl 20:50 skrev Edson José dos Santos <
1798...@bugs.launchpad.net>:

> Se abrir a loja novamente volta para mesma tela e continua travado.
>
> Vide anexo
>
> ***
>
> If you open the store again back to the same screen and still locked.
>
> See attachment
>
> ** Attachment added: "Captura de tela de 2018-10-24 15-32-47.png"
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+attachment/5205007/+files/Captura%20de%20tela%20de%202018-10-24%2015-32-47.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1798053
>
> Title:
>   [SRU] Click on the back icon in gnome-software doesn't work
>
> Status in gnome-software package in Ubuntu:
>   Fix Committed
> Status in gnome-software source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Test Case]
>
>   1. Open gnome-software
>   2. Press Ctrl+F and type "firefox" or any string that will return results
>   3. Click any result in the list (snap package or deb, already installed
> or not, it doesn't matter)
>   4. Observe that a new page is open showing details about the application
>   5. Close gnome-software
>   6. Open gnome-software again
>   7. Observe that the application is open on the last open page (details
> view about the application)
>   8. Click the back button (top-left corner)
>
>   Expected result: the application goes back to the list of search
>   results (or perhaps to the home screen)
>
>   Current result: nothing happens
>
>   Please note that the upstream fix reverts a new behaviour and as a
>   result, when opening again gnome-software at step 6, the application
>   opens on the home screen instead of resuming the last open page. This
>   is consistent with how gnome-software behaves in bionic. So after
>   applying the patch, steps 7 and 8 can be folded into one single step:
>   "Observe that the application is open on the home screen".
>
>
>   [Regression Potential]
>
>   Low. This is a cherry-pick of a self-contained trivial upstream commit
> that is already released in gnome-software 3.30.3 (
> https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774
> ).
>   As noted above, it does change the behaviour of re-opening the
> application after closing it, but it reverts it to the behaviour it had in
> bionic, so I don't think it should be considered a regression.
>
>   Re-opening the application after closing it in a number of different
>   situations should be thoroughly exercised to make sure that this
>   doesn't introduce any functional regression.
>
>
>   [Original Description]
>
>   Searched for Chromium, installed Chromium (snap version), clicked
> Launched and used chromium.
>   Went back to gnome-software and clicked the back button. Nothing
> happened. Restarted gnome-software and clicked the back button. Nothing
> happened.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: gnome-software 3.30.2-0ubuntu3 [modified:
> usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini]
>   ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
>   Uname: Linux 4.18.0-10-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu13
>   Architecture: amd64
>   CasperVersion: 1.399
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Oct 16 11:22:16 2018
>   InstalledPlugins:
>gnome-software-plugin-flatpak N/A
>gnome-software-plugin-limba   N/A
>gnome-software-plugin-snap3.30.2-0ubuntu3
>   LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181016)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-software
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   modified.conffile..etc.xdg.autostart.gnome-software-service.desktop:
> [deleted]
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  [SRU] Click on the back icon in gnome-software doesn't work

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

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

Re: [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

2018-10-24 Thread Per-Inge
Tested and behaves as expected. When gnome-software is started again the
home screen is shown.

Den ons 24 okt. 2018 kl 00:41 skrev Brian Murray :

> Hello Per-Inge, or anyone else affected,
>
> Accepted gnome-software into cosmic-proposed. The package will build now
> and be available at https://launchpad.net/ubuntu/+source/gnome-
> software/3.30.2-0ubuntu8 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-cosmic to verification-done-cosmic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-cosmic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: gnome-software (Ubuntu Cosmic)
>Status: In Progress => Fix Committed
>
> ** Tags added: verification-needed verification-needed-cosmic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1798053
>
> Title:
>   [SRU] Click on the back icon in gnome-software doesn't work
>
> Status in gnome-software package in Ubuntu:
>   Fix Committed
> Status in gnome-software source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Test Case]
>
>   1. Open gnome-software
>   2. Press Ctrl+F and type "firefox" or any string that will return results
>   3. Click any result in the list (snap package or deb, already installed
> or not, it doesn't matter)
>   4. Observe that a new page is open showing details about the application
>   5. Close gnome-software
>   6. Open gnome-software again
>   7. Observe that the application is open on the last open page (details
> view about the application)
>   8. Click the back button (top-left corner)
>
>   Expected result: the application goes back to the list of search
>   results (or perhaps to the home screen)
>
>   Current result: nothing happens
>
>   Please note that the upstream fix reverts a new behaviour and as a
>   result, when opening again gnome-software at step 6, the application
>   opens on the home screen instead of resuming the last open page. This
>   is consistent with how gnome-software behaves in bionic. So after
>   applying the patch, steps 7 and 8 can be folded into one single step:
>   "Observe that the application is open on the home screen".
>
>
>   [Regression Potential]
>
>   Low. This is a cherry-pick of a self-contained trivial upstream commit
> that is already released in gnome-software 3.30.3 (
> https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774
> ).
>   As noted above, it does change the behaviour of re-opening the
> application after closing it, but it reverts it to the behaviour it had in
> bionic, so I don't think it should be considered a regression.
>
>   Re-opening the application after closing it in a number of different
>   situations should be thoroughly exercised to make sure that this
>   doesn't introduce any functional regression.
>
>
>   [Original Description]
>
>   Searched for Chromium, installed Chromium (snap version), clicked
> Launched and used chromium.
>   Went back to gnome-software and clicked the back button. Nothing
> happened. Restarted gnome-software and clicked the back button. Nothing
> happened.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: gnome-software 3.30.2-0ubuntu3 [modified:
> usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini]
>   ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
>   Uname: Linux 4.18.0-10-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu13
>   Architecture: amd64
>   CasperVersion: 1.399
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Oct 16 11:22:16 2018
>   InstalledPlugins:
>gnome-software-plugin-flatpak N/A
>gnome-software-plugin-limba   N/A
>gnome-software-plugin-snap3.30.2-0ubuntu3
>   LiveMediaBuild: Ubuntu 18

[Bug 1798053] [NEW] Click on the back icon in gnome-software don't work

2018-10-16 Thread Per-Inge
Public bug reported:

Searched for Chromium, installed Chromium (snap version), clicked Launched and 
used chromium.
Went back to gnome-software and clicked the back button. Nothing happened. 
Restarted gnome-software and clicked the back button. Nothing happened.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-software 3.30.2-0ubuntu3 [modified: 
usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini]
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CasperVersion: 1.399
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 16 11:22:16 2018
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.30.2-0ubuntu3
LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181016)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

** Affects: gnome-software (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/1798053

Title:
  Click on the back icon in gnome-software don't work

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

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

[Bug 1798050] [NEW] Installation crashed after Continue clicked after presentation of the time Zone

2018-10-16 Thread Per-Inge
Public bug reported:

Followed the test case Install (auto-resize)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.10
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CasperVersion: 1.399
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 16 10:59:51 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181016)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic ubiquity-18.10.10 ubuntu

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

Title:
  Installation crashed after Continue clicked after presentation of the
  time Zone

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

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

[Bug 1797198] Re: [nvidia] After login the screen goes black

2018-10-14 Thread Per-Inge
This bug was fixed in the http://cdimage.ubuntu.com/daily-
live/20181013.1/cosmic-desktop-amd64.iso

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

Title:
  [nvidia] After login the screen goes black

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

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

[Bug 1797198] [NEW] Oct 10 18:22:28 pi-GA-990FXA-UD3 /usr/lib/gdm3/gdm-x-session[1676]: Fatal server error:

2018-10-10 Thread Per-Inge
Public bug reported:

When I boot Cosmic, grub is working OK and login screen is presented OK, but 
after login the screen goes black.
When I boot in Recovery Mode" and "Resume" all is working OK and Nvidia driver 
390 is used.
These bugs my be related
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748656
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192

See attachment for syslog info.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gdm3 3.30.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 10 20:12:32 2018
InstallationDate: Installed on 2018-10-10 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181010.1)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

** Attachment added: "nvidia-problem-3"
   
https://bugs.launchpad.net/bugs/1797198/+attachment/5199647/+files/nvidia-problem-3

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

Title:
  Oct 10 18:22:28 pi-GA-990FXA-UD3 /usr/lib/gdm3/gdm-x-session[1676]:
  Fatal server error:

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

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

[Bug 1794923] Re: Corrupt sreen in CIV VI

2018-10-09 Thread Per-Inge
Tested.
Works OK

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

Title:
  Corrupt sreen in CIV VI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-7/+bug/1794923/+subscriptions

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

[Bug 1795210] [NEW] nautilus crashed with SIGABRT in g_assertion_message_expr()

2018-09-30 Thread Per-Inge
Public bug reported:

Search in Computer with åäö. Nautilus kept searching. Canceled the search, 
which worked OK. Edited the search with backspace. Removed ö and removed ä. 
Nautilus crashed when å was the only character in the search field.
I suppose this is related to bug#1795136.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: nautilus 1:3.26.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 30 10:19:08 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
 b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'268'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1108x849+1425+107'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
InstallationDate: Installed on 2018-08-09 (51 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180809)
ProcCmdline: /usr/bin/nautilus --gapplication-service
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 nautilus_directory_add_file ()
 ?? ()
Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

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


** Tags: amd64 apport-crash cosmic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message_expr()

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

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

[Bug 1794923] [NEW] Corrupt sreen in CIV VI

2018-09-28 Thread Per-Inge
Public bug reported:

After the upgrade of MESA to 18.2.1, CIV VI has corrupt picture elements
in full screen mode, e.g the buttons to the right in the upper panel are
corrupt. The intro picture when starting a game is not displayed
correctly. See the attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 28 07:39:24 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1462:3417]
InstallationDate: Installed on 2018-08-09 (49 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180809)
MachineType: Micro-Star International Co., Ltd. MS-7A34
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=2a36b13d-f333-477e-b902-ea7322f6b566 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/02/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.H0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 TOMAHAWK (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.H0:bd05/02/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.94-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug corruption cosmic ubuntu

** Attachment added: "Screenshot from 2018-09-28 07-42-00.png"
   
https://bugs.launchpad.net/bugs/1794923/+attachment/5193921/+files/Screenshot%20from%202018-09-28%2007-42-00.png

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

Title:
  Corrupt sreen in CIV VI

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

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

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-09-08 Thread Per-Inge
Still not fixed in the ISO from 8/9
Not able to run gnome-calculator.

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

Title:
  snapd didn't initialize all the seeded snaps

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

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

[Bug 1759591] Re: gnome-control-center assert failure: corrupted size vs. prev_size

2018-05-26 Thread Per-Inge
This is on "Ubuntu 18.10" with 4.17.0-041700rc6.
Opened settings/device/printers clicked on the cog, selected Printing Options 
and clicked Test Page.
The page was printed, but I wasn't able to close the window and settings 
crashed.

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

Title:
  gnome-control-center assert failure: corrupted size vs. prev_size

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

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

Re: [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

2018-04-25 Thread Per-Inge
Yes every time. I changed method and used Power/Automatic suspend instead,
which actually is more convenient.

2018-04-24 23:12 GMT+02:00 Marco Trevisan (Treviño) :

> Great to hear, were you getting this regularly?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1760485).
> https://bugs.launchpad.net/bugs/1724439
>
> Title:
>   gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
>   ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
>   function_call()
>
> Status in Mutter:
>   In Progress
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Bionic:
>   Fix Released
> Status in mutter source package in Bionic:
>   Fix Released
>
> Bug description:
>   https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f
> 429e44c854
>
>   ---
>
>   left virtual box to update win10 came back and got error message
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.10
>   Package: gnome-shell 3.26.1-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Oct 17 23:37:32 2017
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2017-04-18 (182 days ago)
>   InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64
> (20170412)
>   ProcCmdline: /usr/bin/gnome-shell
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SegvAnalysis:
>Segfault happened at: 0x7feb2ed42d94 :
> mov0x18(%rax),%eax
>PC (0x7feb2ed42d94) ok
>source "0x18(%rax)" (0x0018) not located in a known VMA region
> (needed readable region)!
>destination "%eax" ok
>   SegvReason: reading NULL VMA
>   Signal: 11
>   SourcePackage: gnome-shell
>   StacktraceTop:
>meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/
> libmutter-1.so.0
>ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>?? () from /usr/lib/libgjs.so.0
>?? () from /usr/lib/libgjs.so.0
>   Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
>   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/mutter/+bug/1724439/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

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

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

Re: [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

2018-04-24 Thread Per-Inge
I checked and I don't get this bug any longer

2018-04-18 23:41 GMT+02:00 Launchpad Bug Tracker <1724...@bugs.launchpad.net
>:

> This bug was fixed in the package mutter - 3.28.1-1
>
> ---
> mutter (3.28.1-1) unstable; urgency=medium
>
>   [ Jeremy Bicha ]
>   * New upstream release
> - Fix window button spacing when display is scaled (LP: #1725133)
>   * Bump Standards-Version to 4.1.4
>
>   [ Marco Trevisan (Treviño) ]
>   * Add patches proposed upstream:
>   * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch:
> - theme, frames: Use surface device scale instead of cairo_scale
>   (LP: #1764554)
>   * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch:
> - theme: use gtk_render_icon_suface to paint button icon
>   (LP: #1764558)
>   * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch:
> - theme: load icons as Gtk does with fallback and RTL support
>   * clutter-Smooth-out-master-clock-to-smooth-visuals.patch:
> - clutter: Smooth out master clock to smooth visuals
>   * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch:
> - core: Return -1 if meta_window_get_monitor is called on an
>   unmanaged window (LP: #1724439)
>   * backends-Move-MetaOutput-crtc-field-into-private-struct.patch:
> - backends: Move MetaOutput::crtc field into private struct
>   (LP: #1703668)
>   * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch:
> - backends: Add logical monitor -> monitor -> output -> crtc ref
>   chain (LP: #1703668)
>
>  -- Jeremy Bicha   Mon, 16 Apr 2018 22:35:14 -0400
>
> ** Changed in: mutter (Ubuntu Bionic)
>Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1761149).
> https://bugs.launchpad.net/bugs/1724439
>
> Title:
>   gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
>   ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
>   function_call()
>
> Status in Mutter:
>   In Progress
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Bionic:
>   Fix Released
> Status in mutter source package in Bionic:
>   Fix Released
>
> Bug description:
>   https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f
> 429e44c854
>
>   ---
>
>   left virtual box to update win10 came back and got error message
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.10
>   Package: gnome-shell 3.26.1-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Oct 17 23:37:32 2017
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2017-04-18 (182 days ago)
>   InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64
> (20170412)
>   ProcCmdline: /usr/bin/gnome-shell
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SegvAnalysis:
>Segfault happened at: 0x7feb2ed42d94 :
> mov0x18(%rax),%eax
>PC (0x7feb2ed42d94) ok
>source "0x18(%rax)" (0x0018) not located in a known VMA region
> (needed readable region)!
>destination "%eax" ok
>   SegvReason: reading NULL VMA
>   Signal: 11
>   SourcePackage: gnome-shell
>   StacktraceTop:
>meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/
> libmutter-1.so.0
>ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>?? () from /usr/lib/libgjs.so.0
>?? () from /usr/lib/libgjs.so.0
>   Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
>   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/mutter/+bug/1724439/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

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

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

[Bug 1765593] [NEW] Cannot start synaptic from Ubuntu-dock

2018-04-19 Thread Per-Inge
Public bug reported:

To reproduce the bug:
- click the Synaptic icon in Ubuntu-dock
- when Synaptic starts click cancel
- click the Synaptic icon in Ubuntu-dock
Synaptic will not start
It's possible to start Synaptic from the terminal

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Fri Apr 20 07:08:47 2018
InstallationDate: Installed on 2018-04-01 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Cannot start synaptic from Ubuntu-dock

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

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

[Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

2018-04-14 Thread Per-Inge
I always get this bug when I start with an Xorg session. I started with
a Wayland session and didn't get the bug.

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

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

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

[Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

2018-04-07 Thread Per-Inge
I have earlier reported a private bug #1761149 and bug #1761973
According to information it is a duplicate this bug. When I'm asked to report 
the bug, this bug number or my earlier reported bugs isn't among the suggested 
bugs.
I am used to turn of the monitor, when I'm not going to use the computer for 
some time. When I turn on the monitor I most of get this crash, but I have also 
got a problem where Ubuntu dock is replaced with the "standard Gnome dock" and 
I have to click Activities to see the favorite applications.
My monitor is a MSI Optix MAG27CQ which is set to 144 MHz refresh rate.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

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

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

Re: [Bug 1761149] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

2018-04-05 Thread Per-Inge
*** This bug is a duplicate of bug 1724439 ***
https://bugs.launchpad.net/bugs/1724439

It's a little better now. There is no crash, but Ubuntu dock isn't working.
To see the favorite applications you have to click activities.

2018-04-04 14:43 GMT+02:00 Apport retracing service <
1761...@bugs.launchpad.net>:

> *** This bug is a duplicate of bug 1724439 ***
> https://bugs.launchpad.net/bugs/1724439
>
> Thank you for taking the time to report this crash and helping to make
> this software better.  This particular crash has already been reported
> and is a duplicate of bug #1724439, so is being marked as such.  Please
> look at the other bug report to see if there is any missing information
> that you can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report.  Please continue to report any other bugs you may
> find.
>
> ** Attachment removed: "CoreDump.gz"
>https://bugs.launchpad.net/bugs/1761149/+attachment/
> 5101234/+files/CoreDump.gz
>
> ** Attachment removed: "Disassembly.txt"
>https://bugs.launchpad.net/bugs/1761149/+attachment/
> 5101236/+files/Disassembly.txt
>
> ** Attachment removed: "ProcMaps.txt"
>https://bugs.launchpad.net/bugs/1761149/+attachment/
> 5101241/+files/ProcMaps.txt
>
> ** Attachment removed: "ProcStatus.txt"
>https://bugs.launchpad.net/bugs/1761149/+attachment/
> 5101242/+files/ProcStatus.txt
>
> ** Attachment removed: "Registers.txt"
>https://bugs.launchpad.net/bugs/1761149/+attachment/
> 5101243/+files/Registers.txt
>
> ** Attachment removed: "Stacktrace.txt"
>https://bugs.launchpad.net/bugs/1761149/+attachment/
> 5101244/+files/Stacktrace.txt
>
> ** Attachment removed: "ThreadStacktrace.txt"
>https://bugs.launchpad.net/bugs/1761149/+attachment/5101245/+files/
> ThreadStacktrace.txt
>
> ** This bug has been marked a duplicate of bug 1724439
>gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
> ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
> function_call()
>
> ** Information type changed from Private to Public
>
> ** Tags removed: need-amd64-retrace
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1761149
>
> Title:
>   gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   This crash happens always when I turn off and on the monitor.
>   According to information it is a duplicate of bug #1724439, but when I'm
> asked to report the bug, this bug number or my earlier reported bug isn't
> among the suggested bugs.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.28.0-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
>   Uname: Linux 4.15.0-13-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu2
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
>   Date: Wed Apr  4 13:37:33 2018
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2018-04-01 (2 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180330)
>   ProcCmdline: /usr/bin/gnome-shell
>   SegvAnalysis:
>Segfault happened at: 0x7f68c98ebc24 :
> mov0x18(%rax),%eax
>PC (0x7f68c98ebc24) ok
>source "0x18(%rax)" (0x0018) not located in a known VMA region
> (needed readable region)!
>destination "%eax" ok
>   SegvReason: reading NULL VMA
>   Signal: 11
>   SourcePackage: gnome-shell
>   StacktraceTop:
>meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/
> libmutter-2.so.0
>ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>?? () from /usr/lib/libgjs.so.0
>?? () from /usr/lib/libgjs.so.0
>   Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
>   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/gnome-shell/+
> bug/1761149/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

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

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

Re: [Bug 897842] Re: The alternative Try Ubuntu failed

2018-04-02 Thread Per-Inge
You may clear this bug. It's not happening any longer.

2018-04-03 2:32 GMT+02:00 Simon Quigley :

> 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 look
> at all reported bugs in a timely manner. There have been many changes in
> Ubuntu since that time you reported the bug and your problem may have been
> fixed with some of the updates. It would help us a lot if you could test it
> on a currently supported Ubuntu version. When you test it and it is still
> an issue, kindly upload the updated logs by running only once:
> apport-collect 897842
>
> and any other logs that are relevant for this particular issue.
>
> ** Changed in: ubiquity (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/897842
>
> Title:
>   The alternative Try Ubuntu failed
>
> Status in ubiquity package in Ubuntu:
>   Incomplete
>
> Bug description:
>   During ISO-testing of Precise Alpha1 the Try Ubuntu alternative ended
>   with a purple screen. The desktop screen was never presented.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 12.04
>   Package: ubiquity (not installed)
>   ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
>   Uname: Linux 3.2.0-2-generic x86_64
>   ApportVersion: 1.90-0ubuntu1
>   Architecture: amd64
>   Date: Tue Nov 29 20:56:02 2011
>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64
> (2029.1)
>   ProcEnviron:
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> 897842/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  The alternative Try Ubuntu failed

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

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

Re: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

2018-04-02 Thread Per-Inge
I also get this in Xorg.
My duplicate is #Bug 1760448

2018-04-03 5:40 GMT+02:00 swadesh Parasher <1748...@bugs.launchpad.net>:

> Yes, at least the bug I reported was from Ubuntu 18.04 which doesn't use
> Wayland by default.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1760448).
> https://bugs.launchpad.net/bugs/1748450
>
> Title:
>   gnome-shell crashed with SIGTRAP in _g_log_abort() from
>   g_log_default_handler() from default_log_handler(message="Connection
>   to xwayland lost") from g_logv() from g_log() from 
>
> Status in gnome-shell package in Ubuntu:
>   Triaged
>
> Bug description:
>   *** This is a duplicate of bug 1505409, but is being kept separate so
>   as to automatically collect duplicate reports since the stacktrace
>   signature has changed recently. Any resolution and discussion should
>   occur in bug 1505409. ***
>
>   See also:
>   https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988
> f78ecd0f95
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.26.2-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>   Uname: Linux 4.13.0-33-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu8
>   Architecture: amd64
>   CurrentDesktop: GNOME-Greeter:GNOME
>   Date: Thu Feb  8 23:50:23 2018
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2016-03-21 (690 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160307)
>   ProcCmdline: /usr/bin/gnome-shell
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/false
>   Signal: 5
>   SourcePackage: gnome-shell
>   StacktraceTop:
>() at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>_XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>_XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>() at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>   Title: gnome-shell crashed with signal 5
>   UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>   UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1748450/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

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

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

[Bug 1752950] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

2018-03-04 Thread Per-Inge
Have crashed a couple of times. Updated Bionic Beaver with oibaf ppa.

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

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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

[Bug 1630218] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

2017-12-23 Thread Per-Inge
I suppose it's this bug even if I'm on Ubuntu 18.04 with kernel 4.15-RC3

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

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

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

[Bug 1738749] Re: vlc 3 fails to start under wayland: vlc crashed with SIGABRT in qt_message_fatal()

2017-12-20 Thread Per-Inge
VLC is working on my system after today's updates, but I had to change
Video Settings/Output from "Automatic" to "OpenGL video output".

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

Title:
  vlc 3 fails to start under wayland: vlc crashed with SIGABRT in
  qt_message_fatal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1738749/+subscriptions

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

[Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

2017-11-10 Thread Per-Inge
Installed "Bionic Beaver" from 2017-11-09.
Used "Install Ubuntu", which worked OK
Used "Try Ubuntu", made the installation, got the error message and not the 
expected "Remove the installation Media and press Return". Used Ctrl+C to stop 
the script and the system restarted. The Installation worked OK.

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions

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

[Bug 1723760] [NEW] No restart after installation

2017-10-15 Thread Per-Inge
Public bug reported:

New installation of Ubuntu 17.10 with ISO from 20171015.

After the message that ends with Restart Now. There is a system hang after this 
information:
7.616392 sd 3:0:0:0:0 [sdd] No cashing mode page found
7.616393 sd 3:0:0:0:0 [sdd] Assuming cash: write through

When Ctrl+C is entered the system restarts.
The Installation is OK.

Installation from the "live session" is working OK.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 15 18:46:40 2017
InstallationDate: Installed on 2017-10-15 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  No restart after installation

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

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

Re: [Bug 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:... error: void value not ignored as it ought to be ... seq_printf]

2017-10-01 Thread Per-Inge
This is a very old bug.
As far as I know support of fglrx is cancelled and replaced with amdgpu-pro.
I'm using amdgpu now and have no problems.
Additional drivers don't offers on the Ubuntu 17.10 beta I'm using now.

2017-10-01 21:44 GMT+02:00 Launchpad Bug Tracker <1502...@bugs.launchpad.net
>:

> Status changed to 'Confirmed' because the bug affects multiple users.
>
> ** Changed in: fglrx-installer-updates (Ubuntu Trusty)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1502978
>
> Title:
>   fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
>   against kernel 4.3 [firegl_public.c:... error: void value not ignored
>   as it ought to be ... seq_printf]
>
> Status in fglrx-installer package in Ubuntu:
>   Invalid
> Status in fglrx-installer-updates package in Ubuntu:
>   Invalid
> Status in software-properties package in Ubuntu:
>   Invalid
> Status in fglrx-installer source package in Trusty:
>   Confirmed
> Status in fglrx-installer-updates source package in Trusty:
>   Confirmed
> Status in software-properties source package in Trusty:
>   Triaged
>
> Bug description:
>   Probably fglrx-installer.
>   However I am not using fglrx , I am using xserver-xorg-video-ati and
> xserver-xorg-video-amdgpu.
>   This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily
> Werewolf.
>   Graphic card Radeon R9 380
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 15.10
>   Package: fglrx-core 2:15.201-0ubuntu1
>   Uname: Linux 4.3.0-040300rc4-generic x86_64
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.19-0ubuntu1
>   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
>   DKMSKernelVersion: 4.3.0-040300rc4-generic
>   Date: Mon Oct  5 18:33:50 2015
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroVariant: ubuntu
>   DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
>   DuplicateSignature: dkms:fglrx-core:2:15.201-
> 0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
> error: void value not ignored as it ought to be
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380]
> [1002:6939] (rev f1) (prog-if 00 [VGA controller])
>  Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
>   InstallationDate: Installed on 2015-02-01 (246 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
>   MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
>   PackageVersion: 2:15.201-0ubuntu1
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic
> root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.2ubuntu4
>apt  1.0.9.10ubuntu7
>   SourcePackage: fglrx-installer
>   Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to
> build
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/09/2009
>   dmi.bios.vendor: Award Software International, Inc.
>   dmi.bios.version: FA
>   dmi.board.name: GA-MA770-UD3
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:
> svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:
> rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:
> cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
>   dmi.product.name: GA-MA770-UD3
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>   version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.64-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.9.2-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati
> 1:7.5.0+git20150819-0ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20150808-0ubuntu2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.11-1ubuntu3
>   xserver.bootTime: Mon Oct  5 18:37:05 2015
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.17.2-1ubuntu9
>   xserver.video_driver: amdgpu
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1502978/+
> subscriptions
>


-- 
Skickat från min nya mailadress

-- 
You received this bug notification 

Re: [Bug 1720510] Re: No results after search

2017-09-30 Thread Per-Inge
No I don't get any errors.
Tested again.on two installations on the same hardware.
- Restarted the the computer.
 - Started Ubuntu Software from the doc
- Search for "soft" and the result was presented
- Closed Ubuntu Software
- Started Ubuntu Software from the doc
- Search for "soft" and the result wasn't presented
- Clicked outside the Ubuntu Software window and the result was shown.

Will check on a new installation with other hardware later.

2017-10-01 2:24 GMT+02:00 Sebastien Bacher :

> thank you for your bug report, do you get any error displayed in the ui?
> trying here it works unless the snap query timeouts which blocks it to
> return other results but that's indicated in a notification
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1720510
>
> Title:
>   No results after search
>
> Status in gnome-software package in Ubuntu:
>   New
>
> Bug description:
>   Test case:
>   Open a new version of gnome-software/Ubuntu Software
>   Search for soft
>   No results are shown
>   Do something outside the gnome-software window, e.g mouse click or focus
> on another window, and the results are shown.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: gnome-software 3.26.0-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
>   Uname: Linux 4.13.0-12-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Sep 30 09:28:37 2017
>   InstallationDate: Installed on 2017-09-15 (14 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170915)
>   InstalledPlugins:
>gnome-software-plugin-flatpak N/A
>gnome-software-plugin-limba   N/A
>gnome-software-plugin-snap3.26.0-0ubuntu3
>   SourcePackage: gnome-software
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/
> +bug/1720510/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  No results after search

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

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

[Bug 1720510] [NEW] No results after search

2017-09-30 Thread Per-Inge
Public bug reported:

Test case:
Open a new version of gnome-software/Ubuntu Software
Search for soft
No results are shown
Do something outside the gnome-software window, e.g mouse click or focus on 
another window, and the results are shown.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.26.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 30 09:28:37 2017
InstallationDate: Installed on 2017-09-15 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.0-0ubuntu3
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  No results after search

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

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

[Bug 1702078] Re: Boot to blank screen

2017-09-27 Thread Per-Inge
Installed the Daily Build from 2917-09-27.
This version works OK

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

Title:
  Boot to blank screen

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

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

Re: [Bug 1713249] Re: gnome-software don't install e.g gnome-tweak tool

2017-09-02 Thread Per-Inge
I get the problem after a new install. I have my configurations file in
Dropbox and my bookmarks in Chrome/Chromium. It's essential to me that it's
easy to install these packages.

Today I used the 2/9 daily and  Software provided this message both at
installation of Dropbox and Chromium.
"Enable Third-party Software Source? Dropbox is provided by
"ubuntu-artful-universe". This software source must be enabled to continue
installation. Cancel Enable and Install."
When I use Enable and Install I get the message
"Unable to install Dropbox
[system/packages/ubuntu-artful-universe/desktop/dropbox.desktop/*] E:Could
not find the repository"

However GNOME Packages installs OK and both Dropbox and Chromium install OK
with GNOME Packages.

When I search for Chromium after the installation with Packages, Software
provides no results, but if I click on the desktop outside of Software the
result is provided.

When I click on All in Software Dropbox and Chromium are not shown as
installed. "Install..." is shown instead of the expected  "Remove."


2017-08-30 9:50 GMT+02:00 Sebastien Bacher :

> thank you for your bug report, the universe message has already been
> reported as bug #1709657
>
> I can't confirm the search bug, do you get it every time? is it a
> rendering issue? could you make a small screencast showing the problem?
>
> ** Changed in: gnome-software (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: gnome-software (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1713249
>
> Title:
>   gnome-software don't install e.g gnome-tweak tool
>
> Status in gnome-software package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When installing gnome-tweak-tool and also chromium, gnome-tweak-tool
>   provides the error message "Enable Third-party Software Source? GNOME
>   Tweaks is provided by "ubuntu-artful-universe". This software source
>   must be enabled to continue installation. Cancel Enable to continue
>   installation"
>
>   However this source is already enabled and Packages will install
>   gnome-tweak-tool.
>
>   There is also problems with the search function. When you start gnome-
>   software and search for e.g tweak no results are presented. However if
>   you click on the desktop outside of gnome-software results are
>   presented.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: gnome-software 3.25.91-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
>   Uname: Linux 4.12.0-11-generic x86_64
>   ApportVersion: 2.20.6-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Aug 26 18:33:58 2017
>   InstallationDate: Installed on 2017-08-26 (0 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170826)
>   InstalledPlugins:
>gnome-software-plugin-flatpak N/A
>gnome-software-plugin-limba   N/A
>gnome-software-plugin-snap3.25.91-1ubuntu1
>   SourcePackage: gnome-software
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/
> +bug/1713249/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-software don't install e.g gnome-tweak tool

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

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

[Bug 1713249] [NEW] gnome-software don't install e.g gnome-tweak tool

2017-08-26 Thread Per-Inge
Public bug reported:

When installing gnome-tweak-tool and also chromium, gnome-tweak-tool
provides the error message "Enable Third-party Software Source? GNOME
Tweaks is provided by "ubuntu-artful-universe". This software source
must be enabled to continue installation. Cancel Enable to continue
installation"

However this source is already enabled and Packages will install gnome-
tweak-tool.

There is also problems with the search function. When you start gnome-
software and search for e.g tweak no results are presented. However if
you click on the desktop outside of gnome-software results are
presented.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.25.91-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 26 18:33:58 2017
InstallationDate: Installed on 2017-08-26 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170826)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.25.91-1ubuntu1
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-software don't install e.g gnome-tweak tool

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

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


Re: [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]

2017-07-26 Thread Per-Inge
I get the bug notification directly after boot, but only after an upgrade.
It's strange that there is No reference to the known bug. I am useing the
Ubuntu login.
Regards Per-inge

Den 26 juli 2017 9:25 fm skrev "Daniel van Vugt" <
daniel.van.v...@canonical.com>:

> Weirdly there are practically no crashes reported for Xwayland:
>   https://errors.ubuntu.com/?package=xwayland=year
>
> This makes me suspect that gnome-shell might be managing the Xwayland
> process and possibly hiding its crashes (including the root cause of
> this bug) from errors.ubuntu.com.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1696904).
> https://bugs.launchpad.net/bugs/1505409
>
> Title:
>   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
>   _XEventsQueued() from XPending() from gdk_check_xpending()
>   ["Connection to xwayland lost"]
>
> Status in GNOME Shell:
>   Confirmed
> Status in Ubuntu GNOME:
>   Confirmed
> Status in gdm3 package in Ubuntu:
>   Confirmed
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   Confirmed
>
> Bug description:
>   https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31
> 681e2b2742
>
>   ---
>
>   Occurred during start-up, before I did anything special...
>
>   1 Ubuntu Wily Werewolf (development branch) 15.10
>   2 3.16.3-1ubuntu6
>   3&4 not applicable
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 15.10
>   Package: gnome-shell 3.16.3-1ubuntu6
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>   Uname: Linux 4.2.0-16-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.19.1-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Mon Oct 12 19:22:07 2015
>   DisplayManager: gdm
>   ExecutablePath: /usr/bin/gnome-shell
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2015-10-08 (4 days ago)
>   InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64
> (20150924)
>   ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
>   ProcEnviron:
>SHELL=/bin/false
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=nl_NL.UTF-8
>   Signal: 5
>   SourcePackage: gnome-shell
>   StacktraceTop:
>?? () from /usr/lib/libmutter.so.0
>_XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>   Title: gnome-shell crashed with signal 5 in _XIOError()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
  _XEventsQueued() from XPending() from gdk_check_xpending()
  ["Connection to xwayland lost"]

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

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


[Bug 1702077] [NEW] Boot to blank screen

2017-07-03 Thread Per-Inge
Public bug reported:

Made the test case Install (entire disk) in Ubuntu Desktop amd64 in Artful Daily
Installation went OK.
At boot the grub menu is shown.
After selection of Ubuntu the screen gets blank. The plymouth screen isn't 
shown.
When I press Ctrl repeatedly the plymouth screen is shown and then the login 
screen.
The installation is set to use the swedish keyboard, but the english keyboard 
is used.
Except for that the installation behaves OK.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
BootLog: /dev/sdc1: clean, 153910/39075840 files, 4226467/156282624 blocks
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Jul  3 13:56:41 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] 
(prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:e174]
InstallationDate: Installed on 2017-07-03 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170703)
MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=e83ef1bc-3743-4dde-a4e8-b774b544ef66 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/13/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-990FXA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.81-2
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Jul  3 15:28:22 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputCHICONY Compaq USB Keyboard KEYBOARD, id 8
 inputCHICONY Compaq USB Keyboard KEYBOARD, id 9
 inputMicrosoft Corporation Microsoft ® Laser Mouse 6000 MOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug artful reproducible ubuntu

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

Title:
  Boot to blank screen

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

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

[Bug 1702078] [NEW] Boot to blank screen

2017-07-03 Thread Per-Inge
Public bug reported:

Made the test case Install (entire disk) in Ubuntu Desktop amd64 in Artful Daily
Installation went OK.
At boot the grub menu is shown.
After selection of Ubuntu the screen gets blank. The plymouth screen isn't 
shown.
When I press Ctrl repeatedly the plymouth screen is shown and then the login 
screen.
The installation is set to use the swedish keyboard, but the english keyboard 
is used.
Except for that the installation behaves OK.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
BootLog: /dev/sdc1: clean, 153910/39075840 files, 4226467/156282624 blocks
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Jul  3 13:56:41 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] 
(prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:e174]
InstallationDate: Installed on 2017-07-03 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170703)
MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=e83ef1bc-3743-4dde-a4e8-b774b544ef66 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/13/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-990FXA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.81-2
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Jul  3 15:28:22 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputCHICONY Compaq USB Keyboard KEYBOARD, id 8
 inputCHICONY Compaq USB Keyboard KEYBOARD, id 9
 inputMicrosoft Corporation Microsoft ® Laser Mouse 6000 MOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug artful reproducible ubuntu

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

Title:
  Boot to blank screen

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

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

[Bug 1695600] [NEW] package grub-efi-amd64-signed 1.83+2.02~beta3-4ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-06-03 Thread Per-Inge
Public bug reported:

The computer has 3 boot-disks
sda with Ubuntu artful efi boot
sdb with W10 non efi boot
sdc with Ubuntu artful non efi boot

Problems earlier with grub on sda as sudo update-grub don't find the W10
installation.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: grub-efi-amd64-signed 1.83+2.02~beta3-4ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
Date: Sat Jun  3 12:53:17 2017
DuplicateSignature:
 package:grub-efi-amd64-signed:1.83+2.02~beta3-4ubuntu5
 Setting up grub-efi-amd64-signed (1.83+2.02~beta3-4ubuntu5) ...
 grub-install: error: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist. Please 
specify --target or --directory.
 dpkg: error processing package grub-efi-amd64-signed (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-04-29 (35 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170428)
RelatedPackageVersions:
 dpkg 1.18.23ubuntu7
 apt  1.4.5
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.83+2.02~beta3-4ubuntu5 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package grub-efi-amd64-signed 1.83+2.02~beta3-4ubuntu5 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

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

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


[Bug 1693101] [NEW] gnome-shell crashed with signal 5 in _XIOError()

2017-05-23 Thread Per-Inge
Public bug reported:

Happened directly after boot. No usability issue.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed May 24 00:38:27 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2017-05-20 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170519)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

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

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


[Bug 1692309] [NEW] nautilus crashed with SIGSEGV

2017-05-21 Thread Per-Inge
Public bug reported:

Happened directly after boot. The only activities was a bug report about
plymouth and start of Chrome.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.24.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.5-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun May 21 12:05:04 2017
Disassembly: No registers.
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-05-20 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170519)
ProcCmdline: /usr/bin/nautilus --gapplication-service
Registers: The program has no registers now.
SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
Signal: 11
SourcePackage: nautilus
Stacktrace: No stack.
StacktraceTop:
 
ThreadStacktrace:
 
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV

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

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


[Bug 1692293] [NEW] gnome-shell crashed with signal 5 in _XIOError()

2017-05-21 Thread Per-Inge
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409

Public bug reported:

Happend directly after boot.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.5-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun May 21 09:13:39 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2017-05-20 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170519)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash artful

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

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

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


[Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 ***

2017-05-20 Thread Per-Inge
Happend on a new install of Artful after installation of gnome-shell and
ubuntu-gnome-desktop, logout and login. Crashed during "Welcome to
Gnome"

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 ***

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

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


[Bug 1442728] Re: Chromium fullscreen should be unredirected by default

2016-01-17 Thread Per-Inge
The suggestion in post #6 fixed the issue on my system, when playing a C More 
Channel in Chrome Version 47.0.2526.111 (64-bit).
Ubuntu Xenial Xerus
Radeon R9 380
AMD FX -8120

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

Title:
  Chromium fullscreen should be unredirected by default

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

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


Re: [Bug 1504989] Re: package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other instances of pa

2015-12-15 Thread Per-Inge
After an update of Wily before 14/12 Unity Tweak Tool didn't start, but
after installation of these packages Unity Tweak Tool started OK.
Installed the following packages:
libunity-webapps0 (2.5.0~+15.10.20151002-0ubuntu1)
qtdeclarative5-ubuntu-web-plugin (0.23+16.04.20151204-0ubuntu1)
unity-webapps-common (2.4.17+15.10.20150616-0ubuntu1)
unity-webapps-service (2.5.0~+15.10.20151002-0ubuntu1)
webapp-container (0.23+16.04.20151204-0ubuntu1)
webbrowser-app (0.23+16.04.20151204-0ubuntu1)

2015-12-15 11:14 GMT+01:00 Marco Trevisan (Treviño) :

> ** Changed in: libunity
>Importance: Undecided => High
>
> ** Changed in: libunity
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1504989
>
> Title:
>   package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to
>   install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
>   loader', which is different from other instances of package
>   libunity9:i386
>
> Status in libunity:
>   Confirmed
> Status in libunity package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This happened when I tried to install unity-webapps-service after a
>   forced an upgrade to Wily with sudo do-release-upgrade -d
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 15.10
>   Package: libunity9 7.1.4+15.10.20151002-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>   Uname: Linux 4.2.0-16-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.19.1-0ubuntu2
>   Architecture: amd64
>   Date: Sun Oct 11 19:54:49 2015
>   DuplicateSignature:
> package:libunity9:7.1.4+15.10.20151002-0ubuntu1:trying to overwrite shared
> '/usr/bin/unity-scope-loader', which is different from other instances of
> package libunity9:i386
>   ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader',
> which is different from other instances of package libunity9:i386
>   InstallationDate: Installed on 2013-05-04 (890 days ago)
>   InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64
> (20130424)
>   RelatedPackageVersions:
>dpkg 1.18.2ubuntu4
>apt  1.0.10.2ubuntu1
>   SourcePackage: libunity
>   Title: package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to
> install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader',
> which is different from other instances of package libunity9:i386
>   UpgradeStatus: Upgraded to wily on 2015-10-11 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/libunity/+bug/1504989/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

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

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

Re: [Bug 1504989] Re: package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other instances of pa

2015-10-24 Thread Per-Inge
Unity Tweak Tool required unity-webapps-service to start.
unity-webapps-service wasn't possible to install as there was a dependency
on libunity9:i386. However libunity9:i386 wasn't possible to install as the
version was different from the installed libunity9.
I fixed the problem by downloading the correct version
(libunity9_7.1.4+15.10.20151002-0ubuntu1_i386.deb),  from launchpad
and installed it.

2015-10-24 15:47 GMT+02:00 Launchpad Bug Tracker <1504...@bugs.launchpad.net
>:

> Status changed to 'Confirmed' because the bug affects multiple users.
>
> ** Changed in: libunity (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1504989
>
> Title:
>   package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to
>   install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
>   loader', which is different from other instances of package
>   libunity9:i386
>
> Status in libunity package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This happened when I tried to install unity-webapps-service after a
>   forced an upgrade to Wily with sudo do-release-upgrade -d
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 15.10
>   Package: libunity9 7.1.4+15.10.20151002-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>   Uname: Linux 4.2.0-16-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.19.1-0ubuntu2
>   Architecture: amd64
>   Date: Sun Oct 11 19:54:49 2015
>   DuplicateSignature:
> package:libunity9:7.1.4+15.10.20151002-0ubuntu1:trying to overwrite shared
> '/usr/bin/unity-scope-loader', which is different from other instances of
> package libunity9:i386
>   ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader',
> which is different from other instances of package libunity9:i386
>   InstallationDate: Installed on 2013-05-04 (890 days ago)
>   InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64
> (20130424)
>   RelatedPackageVersions:
>dpkg 1.18.2ubuntu4
>apt  1.0.10.2ubuntu1
>   SourcePackage: libunity
>   Title: package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to
> install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader',
> which is different from other instances of package libunity9:i386
>   UpgradeStatus: Upgraded to wily on 2015-10-11 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1504989/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

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

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

Re: [Bug 1501894] Re: Xorg crashed with SIGABRT

2015-10-21 Thread Per-Inge
This bug seems to be fixed now.
Running kernel 4.3.0-rc6
xserver-xorg-video-amdgpu 0.0.01~git20150807-0ubuntu1
mesa 11.0.2-ubuntu4

2015-10-21 10:46 GMT+02:00 Timo Aaltonen :

> ** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-amdgpu
> (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1501894
>
> Title:
>   Xorg crashed with SIGABRT
>
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   New
>
> Bug description:
>   Happened when I was running Kodi in full screen mode.
>   Kernel 4.3 rc3
>   graphic card Radeon R9 380.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 15.10
>   Package: xserver-xorg-core 2:1.17.2-1ubuntu9
>   Uname: Linux 4.3.0-040300rc3-generic x86_64
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.19-0ubuntu1
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Thu Oct  1 21:59:21 2015
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroVariant: ubuntu
>   ExecutablePath: /usr/bin/Xorg
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380]
> [1002:6939] (rev f1) (prog-if 00 [VGA controller])
>  Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
>   InstallationDate: Installed on 2015-02-01 (242 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
>   MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
>   ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth
> /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
>   ProcEnviron:
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc3-generic
> root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
>   Signal: 6
>   SourcePackage: xorg-server
>   StacktraceTop:
>?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so
>?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so
>?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so
>?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so
>?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so
>   Title: Xorg crashed with SIGABRT
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   dmi.bios.date: 04/09/2009
>   dmi.bios.vendor: Award Software International, Inc.
>   dmi.bios.version: FA
>   dmi.board.name: GA-MA770-UD3
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.modalias:
> dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
>   dmi.product.name: GA-MA770-UD3
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>   version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.64-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.9.2-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati
> 1:7.5.0+git20150819-0ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20150808-0ubuntu2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.11-1ubuntu3
>   xserver.bootTime: Thu Oct  1 21:59:28 2015
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.17.2-1ubuntu9
>   xserver.video_driver: amdgpu
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1501894/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  Xorg crashed with SIGABRT

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

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

[Bug 1476178] Re: Installer tries to install grub on the wrong disk

2015-10-15 Thread Per-Inge
I have the same problem but on wily

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

Title:
  Installer tries to install grub on the wrong disk

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

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


[Bug 1504989] [NEW] package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other instances of pack

2015-10-11 Thread Per-Inge
Public bug reported:

This happened when I tried to install unity-webapps-service after a
forced an upgrade to Wily with sudo do-release-upgrade -d

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libunity9 7.1.4+15.10.20151002-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Sun Oct 11 19:54:49 2015
DuplicateSignature: package:libunity9:7.1.4+15.10.20151002-0ubuntu1:trying to 
overwrite shared '/usr/bin/unity-scope-loader', which is different from other 
instances of package libunity9:i386
ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
InstallationDate: Installed on 2013-05-04 (890 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu4
 apt  1.0.10.2ubuntu1
SourcePackage: libunity
Title: package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
UpgradeStatus: Upgraded to wily on 2015-10-11 (0 days ago)

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


** Tags: amd64 apport-package package-conflict wily

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

Title:
  package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

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

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


[Bug 1501894] Re: Xorg crashed with SIGABRT

2015-10-06 Thread Per-Inge
** Information type changed from Private to Public

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

Title:
  Xorg crashed with SIGABRT

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

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


Re: [Bug 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build [firegl_public.c:639:9: error: void value not ignored as it ought to be]

2015-10-06 Thread Per-Inge
When I got the crash fglrx-core was installed. I removed fglrx-core,
removed the Linux 4.3 RC4 kernel and installed it again. This time there
was no crash.

2015-10-06 3:18 GMT+02:00 Daniel van Vugt
:

> ** Summary changed:
>
> - fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
> + fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
> [firegl_public.c:639:9: error: void value not ignored as it ought to be]
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1502978
>
> Title:
>   fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
>   [firegl_public.c:639:9: error: void value not ignored as it ought to
>   be]
>
> Status in fglrx-installer package in Ubuntu:
>   New
>
> Bug description:
>   Probably fglrx-installer.
>   However I am not using fglrx , I am using xserver-xorg-video-ati and
> xserver-xorg-video-amdgpu.
>   This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily
> Werewolf.
>   Graphic card Radeon R9 380
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 15.10
>   Package: fglrx-core 2:15.201-0ubuntu1
>   Uname: Linux 4.3.0-040300rc4-generic x86_64
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.19-0ubuntu1
>   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
>   DKMSKernelVersion: 4.3.0-040300rc4-generic
>   Date: Mon Oct  5 18:33:50 2015
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroVariant: ubuntu
>   DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
>   DuplicateSignature:
> dkms:fglrx-core:2:15.201-0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
> error: void value not ignored as it ought to be
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380]
> [1002:6939] (rev f1) (prog-if 00 [VGA controller])
>  Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
>   InstallationDate: Installed on 2015-02-01 (246 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
>   MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
>   PackageVersion: 2:15.201-0ubuntu1
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic
> root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.2ubuntu4
>apt  1.0.9.10ubuntu7
>   SourcePackage: fglrx-installer
>   Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to
> build
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/09/2009
>   dmi.bios.vendor: Award Software International, Inc.
>   dmi.bios.version: FA
>   dmi.board.name: GA-MA770-UD3
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.modalias:
> dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
>   dmi.product.name: GA-MA770-UD3
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>   version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.64-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.9.2-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati
> 1:7.5.0+git20150819-0ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20150808-0ubuntu2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.11-1ubuntu3
>   xserver.bootTime: Mon Oct  5 18:37:05 2015
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.17.2-1ubuntu9
>   xserver.video_driver: amdgpu
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1502978/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  [firegl_public.c:639:9: error: void value not ignored as it ought to
  be]

To manage notifications about this bug go to:

[Bug 1502978] [NEW] fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build

2015-10-05 Thread Per-Inge
Public bug reported:

Probably fglrx-installer. 
However I am not using fglrx , I am using xserver-xorg-video-ati and 
xserver-xorg-video-amdgpu.
This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily Werewolf.
Graphic card Radeon R9 380

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: fglrx-core 2:15.201-0ubuntu1
Uname: Linux 4.3.0-040300rc4-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19-0ubuntu1
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
DKMSKernelVersion: 4.3.0-040300rc4-generic
Date: Mon Oct  5 18:33:50 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
DuplicateSignature: 
dkms:fglrx-core:2:15.201-0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
 error: void value not ignored as it ought to be
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
InstallationDate: Installed on 2015-02-01 (246 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
PackageVersion: 2:15.201-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic 
root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.2ubuntu4
 apt  1.0.9.10ubuntu7
SourcePackage: fglrx-installer
Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FA
dmi.board.name: GA-MA770-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA770-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Mon Oct  5 18:37:05 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9
xserver.video_driver: amdgpu

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 need-duplicate-check 
third-party-packages ubuntu wily

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

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build

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

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


Re: [Bug 953368] Re: gtk-window-decorator crashed with SIGSEGV in update_event_windows()

2015-09-16 Thread Per-Inge
No problem. This was a long time back.

2015-09-16 20:46 GMT+02:00 Will Cooke <953...@bugs.launchpad.net>:

> As part of the big bug clear up for 16.04 LTS I am marking this bug as
> Wont Fix.
> These types of crasher are better handled by errors.ubutnu.com which can
> collate similar crash reports to help us identify persitent bugs rather
> than one-off crashes.
> Sorry we are not able to help with this specific issue. If you are still
> experiencing this crash, please re-open the bug and add the tag
> "desktop-bugscrub-reopened". See
> https://wiki.ubuntu.com/BigDesktopBugScrub for more information.
>
> ** Changed in: compiz (Ubuntu)
>Status: Confirmed => Won't Fix
>
> ** Tags added: desktop-bugscrub-autoclosed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/953368
>
> Title:
>   gtk-window-decorator crashed with SIGSEGV in update_event_windows()
>
> Status in compiz package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   Happened when I closed Steam and opened Filemanager
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 12.04
>   Package: compiz-gnome 1:0.9.7.0~bzr2995-0ubuntu5
>   ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
>   Uname: Linux 3.2.0-18-generic x86_64
>   NonfreeKernelModules: nvidia
>   .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
> '/proc/driver/nvidia/gpus/0'
>   .proc.driver.nvidia.registry: Binary: ""
>   .proc.driver.nvidia.version:
>NVRM version: NVIDIA UNIX x86_64 Kernel Module  295.20  Mon Feb  6
> 21:07:30 PST 2012
>GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu2)
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 1.94.1-0ubuntu2
>   Architecture: amd64
>   CompizPlugins:
> [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
>   CompositorRunning: compiz
>   Date: Mon Mar 12 21:06:26 2012
>   DistUpgraded: Fresh install
>   DistroCodename: precise
>   DistroVariant: ubuntu
>   DkmsStatus: nvidia-current, 295.20, 3.2.0-18-generic, x86_64: installed
>   ExecutablePath: /usr/bin/gtk-window-decorator
>   GraphicsCard:
>NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if
> 00 [VGA controller])
>  Subsystem: Giga-byte Technology Device [1458:34c7]
>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64
> (20120306)
>   JockeyStatus:
>firmware:dvb_usb - Firmware for DVB cards (Proprietary, Enabled, In use)
>xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary,
> Enabled, In use)
>xorg:nvidia_current_updates - NVIDIA accelerated graphics driver
> (post-release updates) (Proprietary, Disabled, Not in use)
>   MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
>   ProcCmdline: /usr/bin/gtk-window-decorator
>   ProcEnviron:
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic
> root=UUID=a88d8e77-62ff-4c47-b528-d659a44515fe ro quiet splash vt.handoff=7
>   SegvAnalysis:
>Segfault happened at: 0x4194c4 :   cmpq
>  $0x0,0x2d8(%rax)
>PC (0x004194c4) ok
>source "$0x0" ok
>destination "0x2d8(%rax)" (0x02d8) not located in a known VMA
> region (needed writable region)!
>   SegvReason: writing NULL VMA
>   Signal: 11
>   SourcePackage: compiz
>   StacktraceTop:
>max_window_name_width ()
>update_window_decoration_size ()
>?? ()
>g_cclosure_marshal_VOID__OBJECTv () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
>?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gtk-window-decorator crashed with SIGSEGV in
> max_window_name_width()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   XorgConf:
>Section "Device"
> Identifier  "Default Device"
> Option  "NoLogo""True"
>EndSection
>   dmi.bios.date: 07/08/2010
>   dmi.bios.vendor: Award Software International, Inc.
>   dmi.bios.version: FKb
>   dmi.board.name: GA-MA770-UD3
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: x.x
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.modalias:
> dmi:bvnAwardSoftwareInternational,Inc.:bvrFKb:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
>   dmi.product.name: GA-MA770-UD3
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>   version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.30-1ubuntu1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: 

Re: [Bug 1196189] Re: compiz crashed with SIGABRT in __libc_message()

2015-09-16 Thread Per-Inge
OK

2015-09-16 11:35 GMT+02:00 Will Cooke <1196...@bugs.launchpad.net>:

> As part of the big bug clear up for 16.04 LTS I am marking this bug as
> Wont Fix. These types of crasher are better handled by errors.ubutnu.com
> which can collate similar crash reports to help us identify persitent
> bugs rather than one-off crashes. Sorry we are not able to help with
> this specific issue. If you are still experiencing this crash, please
> re-open the bug and add the tag “desktop-bugscrub-reopen”. See
> https://wiki.ubuntu.com/BigDesktopBugScrub for more information.
>
> ** Changed in: unity
>Status: New => Won't Fix
>
> ** Changed in: unity (Ubuntu)
>Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1196189
>
> Title:
>   compiz crashed with SIGABRT in __libc_message()
>
> Status in Unity:
>   Won't Fix
> Status in unity package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   Nautilus and a terminal window was open. I searched for disks in Dash
>   and started disks. Clicked a USB drive in disks. Nothing happend in
>   disks. Compiz crashed and restarted.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 13.10
>   Package: unity 7.0.0daily13.06.24-0ubuntu2
>   ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
>   Uname: Linux 3.10.0-1-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.10.2-0ubuntu3
>   Architecture: amd64
>   Date: Sun Jun 30 09:01:53 2013
>   ExecutablePath: /usr/bin/compiz
>   InstallationDate: Installed on 2013-05-04 (56 days ago)
>   InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64
> (20130424)
>   MarkForUpload: True
>   ProcCmdline: compiz
>   Signal: 6
>   SourcePackage: unity
>   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
>sigc::internal::signal_emit1 sigc::nil>::emit(sigc::internal::signal_impl*, double const&) () from
> /usr/lib/compiz/libunityshell.so
>   Title: compiz crashed with SIGABRT in raise()
>   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/unity/+bug/1196189/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  compiz crashed with SIGABRT in __libc_message()

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

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

  1   2   3   >