Public bug reported:
Starting gnome_sudoku results in
lsdm: gnome-sudoku
[1] 3110
lsdm: /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning:
g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed
import gobject._gobject
** Changed in: gnome-games (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-games in Ubuntu.
https://bugs.launchpad.net/bugs/1024377
Title:
gnome-sudoku crashes with SIGSEGV
Status in
The problem was caused by a PYTHONPATH setting.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-games in Ubuntu.
https://bugs.launchpad.net/bugs/1024377
Title:
gnome-sudoku crashes with SIGSEGV
Status in “gnome-games” package
Thank you for mentioning why firefox connects to Google.
After reading the privacy section of
http://en.wikipedia.org/wiki/Google_Safe_Browsing;, I have
banned all Google access via firewall rules -- I do not want Google to be able
to identify my computer.
--
You received this bug notification
Public bug reported:
A freshly started firefox with all extensions disabled, the flash
plugin enabled and all other plugins either disabled or in mode ask
before enabling, makes connections to some (not directly recognizable)
Google IP addresses.
At first, it used IP addresses from
Public bug reported:
Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version
in each case). From 14.04 on, I was unable to graphically log in. A few
seconds after the login (varying between 1 and 10 s), the screen changed
to a pattern with dense white stripes on the violet/red
For me, the situation has significantly improved with the latest Ubuntu
16.04: for "normal" operation, I no longer need "nouveau.config=NvMSI=0"
as kernel boot parameter.
I still see that things are not yet perfect:
* moving the mouse over the window top bar occasionally shows a black and
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047618/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047619/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047620/+files/Lspci.txt
--
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/1649566
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047626/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047627/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047621/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047625/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
In comment #6 I had reported that "apport-collect 1649566" reproduces
the freeze.
I was now able to successfully transfer the data by calling "apport-
collect" outside the X system. Because, it did not run under X, it might
not contail all information you would like. In this case, let me know
how
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047623/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047617/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047624/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047616/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047622/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Tags added: apport-collected ubuntu xenial
** Description changed:
Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version
in each case). From 14.04 on, I was unable to graphically log in. A few
seconds after the login (varying between 1 and 10 s),
Responses to your previous questions:
1) It may take a bit of time before I can make the tests with the current
Ubuntu version. And, I fear that such tests might not be reliable: after the
temporary use of the NVidia driver I could use the "nouveau" driver for some
time even without the special
Calling "apport-collect 1649566" reproducible causes the crash reported in this
ticket.
Is there a different way to provide the information you need?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
> 1) To see if this is already resolved in Ubuntu, could you please test
> http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
I tried, but the resulting DVD does not boot:
-- maybe, because it is for for the x64 platform while I typically use the
i386 platform
** Attachment added: "Full "kern.log""
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049380/+files/kern.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Attachment added: "Full dmesg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049379/+files/dmesg
--
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/1649566
I have lived for more than 1 year with the problem (as told earlier, the
freeze happens nowadays only occasionally) and, thus, I do not need a
backport but can wait for 18.04 to be released. Thank you again!
--
You received this bug notification because you are a member of Desktop
Packages,
Using a different drive, I could successfully burn the daily Ubuntu Live
CD. I was not able to reproduce the freeze with the corresponding
installation.
Thank you for your support.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in
> Then please post the results requested in
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/comments/21
> so it may be reviewed.
Comment 21:
>> If still reproducible, please post results following:
>> https://wiki.ubuntu.com/DebuggingKernelBoot
This is not applicable as booting is
** Attachment added: ""nouveau" related entries in "kern.log""
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049298/+files/nouveau.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
> 3) As per your snipped log, it looks like you are grabbing logs from your
> install. What is
> needed are the logs/video from booting
> http://cdimage.ubuntu.com/daily-live/current/.
You are right. All attachments come from the installation, not the
"current" Ubuntu.
I see no chance to get
Public bug reported:
I had nouveau related problems in Ubuntu 16.04: quite often, the display
screen was replaced by an irregular black and white pattern and the
system no longer reacted to the mouse or the keyboard.
Since the Ubuntu 18.04 upgrade, the problem shows itself slightly
differently.
32 matches
Mail list logo
