Updated and tested.
There is no crash at logout or restart
Den tis 5 okt. 2021 kl 17:05 skrev Launchpad Bug Tracker <
1943...@bugs.launchpad.net>:
> This bug was fixed in the package gnome-shell - 40.5-1ubuntu2
>
> ---
> gnome-shell (40.5-1ubuntu2) impish; urgency=medium
>
> [ Danie
Now I get a problem that cannot be reported
** Attachment added: "Screenshot from 2021-09-28 16-27-45.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943406/+attachment/5528718/+files/Screenshot%20from%202021-09-28%2016-27-45.png
--
You received this bug notification becaus
Don't get the crash any longer.
Den tors 22 apr. 2021 kl 16:41 skrev Launchpad Bug Tracker <
1820...@bugs.launchpad.net>:
> This bug was fixed in the package nautilus - 1:3.38.2-1ubuntu2
>
> ---
> nautilus (1:3.38.2-1ubuntu2) hirsute; urgency=medium
>
> * d/p/19_unity_open_location_
Public bug reported:
Get this error message when trying to open /boot/efi
"gdbus error freedesktop policykit1 error failed unix process subject does not
have uuid set"
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nautilus 1:3.38.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-gener
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs
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), libmu
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: AS
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 Wim
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.ubun
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
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 a
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
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/184
Title:
gnome-shell crashed with SIGSEGV in _st_
*** 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
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:
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 an
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()
em 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,
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 th
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1868660
Title:
gnome-shell crashed wi
Happened again, but now it refers to icon instead of font.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1868440
Title:
gnome-shell crashed with SIGSEGV in st_theme_node_get_font
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 U
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
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
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-
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 Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubu
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 Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu
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
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
arred.
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:
>
> C
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/+sou
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
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:
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 c
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 availa
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: U
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1797198
Title:
[nvidia] After lo
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
Tested.
Works OK
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1794923
Title:
Corrupt sreen in CIV VI
Status in llvm-toolchain-7 package in Ubuntu:
Confirmed
Status in mesa package i
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:
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
DistroRe
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
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
> dupli
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
>
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1748450
Title:
gno
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 comput
*** 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.
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
Have crashed a couple of times. Updated Bionic Beaver with oibaf ppa.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1752950
Title:
deja-dup-monitor crashed with SIGSEGV in __pthread
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1630218
Title:
gnome-shell crashed with signal 5 in g_log_d
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
>:
>
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 resul
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: g
Installed the Daily Build from 2917-09-27.
This version works OK
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1702078
Title:
Boot to blank screen
Status in xorg package in Ubuntu:
C
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 T
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
i
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 a
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 a
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 x8
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
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 buil
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501894
Title:
Xorg crashed with SIGABRT
Status in xorg-server package in Ubuntu
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.
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
I enabled proposed and updated.
During the upgrade I got a notification about "broken packages", but the
notification was removed.
After the upgrade System Settings/Software & Updates/Additional Drivers was
set to version 340.76 from nvidia-340-updates. However Nvidia X Server
Settings still said t
I enabled proposed and updated.
During the upgrade I got a notification about "broken packages", but the
notification was removed.
After the upgrade System Settings/Software & Updates/Additional Drivers was
set to version 340.76 from nvidia-340-updates. However Nvidia X Server
Settings still said t
Public bug reported:
I think this bug is related to
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1212601
The bug happened when I copied a media file with strange Audio/Video properties
in Utopic.
The Audio/Video properties are shown OK in Ubuntu 14.04.
ProblemType: Crash
DistroRelease:
Seems to always happen after a check of video properties when Totem
cannot read the video properties.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1371885
Title:
nautilus crashed with
Public bug reported:
Right clicked a video in Nautilus. Selected to play with Totem.
The video is stored on my NAS.
Before that, looked at the file properties. The Audio/Video tab in 14.10 is
different compared to 14.04. In 14.10 the Basic tab shows type: Matroska
video, but the Audio/Video tab
Changed in grub to use upstart, booted, used synaptic to update nvidia-
prime. This worked OK. nfs-common, that also gave an update error under
systemd, updated OK.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
h
Happened again at today's upgrade of nvidia-prime (0.6.5) to 0.6.6.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1322320
Title:
package nvidia-prime 0.6.4 failed to install/upg
Public bug reported:
I run dpkg -i /var/cache/apt/archives/*.deb and dpkg --configure -a on
the system. After this I get I get the mesage that nvidia-prime is in a
bad state and should be re-installed. When I do that I get the message
E: /var/cache/apt/archives/nvidia-prime_0.6.5_amd64.deb: subpro
I replaced a Geforce GTX 520 card with the Geforce GTS 250 card in one
of my computers with Ubuntu 13.10 and the Nouveau driver. The cards
behaved in the same way. The login screen worked as expected.
You may close the bug.
MVH/Per-Inge
On 01/09/2014 03:47 AM, Christopher M. Penalver wrote
I will check. I am currently not using this card, but I will install it
and check.
I think the problem is related to this specific graphic card a Geforce
GTS 250.
Regards/Per-Inge
On Thu, 09 Jan 2014 02:47:19 -, "Christopher M. Penalver"
wrote:
> Per-Inge, this bug was reporte
Hi,
Not in my case. It has only happened once.
On 2013-10-21 14:52, Alberto Salvia Novella wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
>
> * Is this reproducible?
> * If so, what specific steps should we take to re
Thanks,
My system is also working OK now after updates today.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1218815
Title:
[radeon] Graphic glitches and screen corrupt
I have made updates today and yesterday according to the attachment.
My computer with Radeon HD 6670 has the same behaviour as mentioned by WeeGee.
The update of unity-system-compositor makes it a little better. In case I place
the cursor in the input field in the login screen, there are no corru
Public bug reported:
Happened when I booted directly after update. The computer only uses wifi for
communications. Connected over IEEE 802.11n. Security Mode WPA/WPA2-Personal.
Wifi is up and running.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: wpasupplicant 1.0-3ubuntu2
ProcVersionS
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1218815
Title:
[radeon] Graphic glitches a
Not in my case. I still have the delay on a fully updated 13.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1129157
Title:
lightdm pausing a long time at boot
Status in “consolek
I changed IPV6 to ignore, but didn't change anything.
Feb 23 15:15:25 pi-GA-990FXA-UD3-1304 dbus[903]: [system] Successfully
activated service 'org.freedesktop.nm_dispatcher'
Feb 23 15:15:33 pi-GA-990FXA-UD3-1304 ntpdate[2034]: adjust time server
91.189.94.4 offset 0.295083 sec
Feb 23 15:15:47 p
This is what I get in syslog after the reboot. I stopped XBMC and then made a
reboot.
The delay between spin down of the fans and presentation of the login screen
was about 20 sec.
** Attachment added: "part-of-syslog"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1129157/+attachmen
In my case this happens at every boot. I upgraded to Raring last week.
The boot behaves as normal, but instead of showing the login screen
there is a pause of about 20 sec.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu
Nvidia 310.14 was in use and then I changed to Nvidia 310.19 in System
Sources. So the kernel must have been built for a Nvidia driver.
When you change from Nouveau to Nvidia you get a message to reboot the
system. In this case when I changed between Nvidia drivers I didn't got
such a message. I
Public bug reported:
I changed Nvidia driver by use of Software Sources from 310.14 to 310.19,
nvidia-exprimental-310 to nvidia-310 updates.
I expeted the message that a reboot was required. I didn't got that message.
Instead I logged out and the crash happend.
After I turned off the computer,
Public bug reported:
The crash happend when I used this search string
gcc -I /usr/include/python2.7 -c
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gedit 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic x86_64
NonfreeKernelModules: nvidi
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1063734
Title:
nautilus crashed with SIGSEGV
Status in “nautilus” package in Ubuntu:
New
Bug descr
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1063340
Title:
evolution-calendar-factory crashed with SIGABRT
Status in “evolution-data
*** This bug is a duplicate of bug 1053670 ***
https://bugs.launchpad.net/bugs/1053670
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1054596
Tit
In my case I think it's related to the graphic card an Nvidia Geforce
GTS250. There are some problems with this card. First the Nomodeset
option is needed to install Ubuntu both in Oneiric and Precise. Then I
have to boot in recovery mode to be able to login and get the system
working, else I g
*** This bug is a duplicate of bug 917979 ***
https://bugs.launchpad.net/bugs/917979
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/918040
Title:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/910810
Title:
gnome-terminal crashed with SIGABRT in raise()
Status in “gnome-terminal” package
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/901101
Title:
rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
Status in “rhythmbox”
Public bug reported:
Corrupt login screen during ISO-testing of Precise Alpha 1.
The login screen har a lot of artifacts. ctrl+alt+f1, control+alt+del does not
work. No input fields are working.
However if I boot with recovery mode, selects the alternative to start as root,
type exit and then se
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/897835
Title:
Corrupt login screen
Status in “lightdm” package in Ubuntu:
New
Bug description:
Corrupt login screen during ISO-test
Public bug reported:
After uninstall of Nvidia current with jockey in Ubuntu 11.10, reboot is
not working correctly. The login screen doesn't show any input form, or
a screen with wrong background that doesn't accept input.
** Affects: jockey (Ubuntu)
Importance: Undecided
Status: N
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/850159
Title:
NetworkManager crashed with SIGSEGV in g_type_instance_get_private()
Status in “
*** This bug is a duplicate of bug 835129 ***
https://bugs.launchpad.net/bugs/835129
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/835300
*** This bug is a duplicate of bug 657829 ***
https://bugs.launchpad.net/bugs/657829
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/834401
Title:
1 - 100 of 104 matches
Mail list logo
