After reboot something happened. Instead of the blank space a small
(smaller than it has to be) dot appeared. I don't know why. I only
updated the kernel.
** Attachment added: "screenshot20240821-2.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077474/+attachment/5807764/+fil
While switching to another workspace, the second dot (or line) remains
blank.
** Attachment added: "screenshot20240821.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077474/+attachment/5807686/+files/screenshot20240821.png
--
You received this bug notification because you a
Public bug reported:
Second workspace is not visible on the new dynamic activity indicator.
Earlier (in the 24.04 release) it worked.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu6~24.04.3
ProcVersionSignature: Ubuntu 6.8.0-40.40.1-lowlatency 6.8.12
Uname: Linux 6
Calendar sync doesn't work since yesterday evening. Maybe Google changed
something?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1981863
Title:
gnome calendar does not sync w
I don't know what happened, but gnome calendar syncing again with google
:-o Maybe the update of libgnutls30?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1981863
Title:
gnom
There are no error messages. I created a new user, logged in and added
my google account to gnome online accounts. Sync was not working and
there were no error messages. I assume that the original settings for a
new user should work. So maybe the problem is something else, not the
settings.
On júl
Sorry, I should write “maybe”. But calendar sync worked earlyer. Something
changed during the last update of ??.deb and since this sync does not
work.
Sebastien Bacher <1981...@bugs.launchpad.net> (időpont: 2022. júl. 18., H,
14:11) ezt írta:
> Thanks, but one mention that it works for one us
The same issue appears in gnome-todo...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1981863
Title:
gnome calendar does not sync with google calendar
Status in gnome-calenda
And see this:
https://askubuntu.com/questions/1411856/synchronization-issues-with-google-accounts-and-gnome-online-accounts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1981863
As I read in other forums, this works fine in Fedora. So this bug is
Ubuntu specific.
https://askubuntu.com/questions/1408669/gnome-calendar-not-working-in-
ubuntu-22-04lts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar i
Public bug reported:
In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar
41.2 does not sync calendar events from google calendar through GOA. But
when an event is created in gnome calendar, it is synchronized with
google calendar. So the synchronization works only in one direct
Memory usage increases only at the first time when a push Super+A.
Repeatedly pushing Super+A doesn't cause further jumps. However, this
allocated memory never seems to be released (memory usage doesn't drop
back to the original level).
On Jan 7 2022, at 8:32 am, Daniel van Vugt <1856...@bugs.laun
I switch off all the extensions except for Ubuntu ones. Every
lock/unlock action raises the memory usage by ~10MB until it reaches
~280MB. Super-A (app overview) raised further the usage.
After a while something happend (Not lock/unlock or Super-A) and now the
memory usage of gnome-shell is 302MB
Public bug reported:
When the screen is locked and unlocked extra ~100MB memory remains in
use and never freed up. After each lock/unlock action additional 10-20MB
will be used, and the memory consumption of gnome-shell grows and grows.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-
Public bug reported:
1. $ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
2. $ apt-cache policy nautilus
nautilus:
Installed: 1:3.36.3-0ubuntu1
Candidate: 1:3.36.3-0ubuntu1
Version table:
*** 1:3.36.3-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal-
When I switched off and on google calendar in gnome-calendar, this
happened:
GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars:
assertion failed: (self->completed_calendars <= g_hash_table_size
(self->calendars))
Bail out!
GcalTimeline:ERROR:../src/core/gcal-timeli
I just tried it out: if I switch off google calendar (set up in
Settings/Online accounts), everything is working as it should be. But I
need google calendar.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https:
Does anyone else experience this, or just me? With this issue the
calendar is unusable, but I couldn't find any bug report about this. But
this bug has been around for a long time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-cal
When launching gnome-calendar, the week view (current week) appears for
a second and disappear when the header (days of the week) is being
written. After switching to previous and next weeks the week view is
normal again. Returnig to the current week the week view is blank again.
--
You received
** Attachment added: "Képernyőkép erről: 2021-08-02 02-02-48.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+attachment/5515158/+files/K%C3%A9perny%C5%91k%C3%A9p%20err%C5%91l%3A%202021-08-02%2002-02-48.png
--
You received this bug notification because you are a mem
Public bug reported:
Description:Ubuntu 20.04.2 LTS
Release:20.04
gnome-calendar:
Installed: 3.36.2-0ubuntu1
Candidate: 3.36.2-0ubuntu1
Version table:
*** 3.36.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpk
Public bug reported:
Ubuntu 20.04, ubuntu session with wayland. After about one hour usage,
while firefox has been launched gnome-shell(?) crashed and falled back
to gdm login screen. This has happened several times.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu
In Ubuntu 20.04 (with the newest packages) the leak is present. After
logging in the memory usage of gnome-shell is 208MB. After pushing
Super+A it jumps to 213MB and stay there. After lock/unlock the screen
it jumps to 270MB and stays there. Repeated Super+A and lock/unlock
seems to do no further
In Ubuntu 20.04 (with the newest packages) the leak is present. After
logging in the memory usage of gnome-shell is 208MB. After pushing
Super+A it jumps to 213MB and stay there. After lock/unlock the screen
it jumps to 270MB and stays there. Repeated Super+A and lock/unlock
seems to do no further
Could be any connection between https://gitlab.gnome.org/GNOME/gjs/issues/52
and the problem here? (I am not an expert)
** Bug watch added: gitlab.gnome.org/GNOME/gjs/issues #52
https://gitlab.gnome.org/GNOME/gjs/issues/52
--
You received this bug notification because you are a member of Des
The same problem exists for Ubuntu 20.04, Gnome 3.36, gjs 1.63.92, mozjs
68.5.
Daniel van Vugt ezt írta (időpont: 2019.
okt. 31., Cs, 3:25):
> Thanks for testing that. Though I think you mean MB, not kB :)
>
> ** Summary changed:
>
> - memory usage is growing over time
> + Memory usage grows whe
Here is a similar issue:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1886
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886
--
You received this bug notification because you are a member of Desktop
Packages, which
I'm trying to catch that function(s) which leaks the memory, but
unfortunately I am not an expert. Can anyone help me what to do? I
copied /usr/bin/gnome-shell to /usr/bin/gnome-shell.bin and made a
script in /usr/bin/gnome-shell:
#!/bin/sh
if [ $USER = gstest ] ; then exec valgrind --tool=massif
What does it mean "doesn't free memory immediately"? Hours? Days? I never
experienced decrease in memory usage, except for small fluctuations. I think it
is a memory leak added to this slow garbage collection.
I also wrote about this problem to
https://gitlab.gnome.org/GNOME/gjs/issues/217# but
The main system which I use for work is Ubuntu 18.04.3 LTS. I use gnome with
many extensions (see above). At the beginning the memory usage of gnome-shell
is ~177MB. (Interesting that in another machine, which is a laptop and has
exactly the same system and almost the same hardware, gnome-shell
Yes, MB, not kB.
Today I made a new test. I logged in (ubuntu 19.10 on virtualbox, normal ubuntu
session) and started the gnome-system-monitor to see what is happening. The
memory usage of gnome-shell was ~202MB at the beginning. I locked the session,
and unlocked it. The memory usage jumped to
The test system was 19.10 in virtualbox. I removed almost every
extensions, except for the built in ones (ubuntu dock, ubuntu
appindicator, etc.). Gnome-shell uses ~200kB at the beginning. If I lock
the screen and unlock it, the memory usage jumps to ~210kB. Repeatedly
doing this, the memory usage
Public bug reported:
Many times after logging in gnome-shell uses 600-800kB of memory, and
also slows down quite a bit (e.g., 20-30 seconds waiting for login).
Only after multiple resets (Alt+F2 r) drops the memory usage below
200kB. I use my computer mainly for work, and the above phenomenon is
q
A similar bug ( Bug #1767817) was fixed in bionic (18.04) within 1-2
days when it turned out that it is fixed in disco (19.04). This bug is
also fixed in disco. Could it be backported to bionic?
On feb 20 2019, at 10:55 du, Balázs Pere wrote:
> In the current 19.04 (disco) it works well.
>
> On f
In the current 19.04 (disco) it works well.
On feb 20 2019, at 1:29 du, Balázs Pere wrote:
> When I choose a certain file type, the correct hits appears for a second, but
> after that all hits come back.
>
> On Feb 20 2019, at 1:28 pm, Balázs Pere wrote:
> > New packages in
> > https://launchp
When I choose a certain file type, the correct hits appears for a
second, but after that all hits come back.
On Feb 20 2019, at 1:28 pm, Balázs Pere wrote:
> New packages in
> https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16410497
> leaves unchanged this bug.
>
> On Feb 19 20
It seems to work well. Sometimes it hang up, shows "searching" in the
right bottom corner of nautilus window. If I delete back some characters
in the input field, it starts to work again.
On Feb 20 2019, at 9:11 am, Sebastien Bacher wrote:
> Yes, it's fixed in the Disco serie, I've uploaded a tes
New packages in https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/ppa/+build/16410497 leaves unchanged this bug.
On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote:
> Indeed, that seems fixed in the current Ubuntu serie but buggy in
> bionic, potentially something we want to fix in a SRU
>
>
Public bug reported:
When I click on searching in nautilus a down arrow appears on the right
(next to the input field). If I click on this arrow, a pop up menu
appears with "When" and "What" titles. Inside "What" I can choose file
types. Choosing a certain file type nothing happens, nautilus shows
If the users think it is important, developers should raise the level of
priority.
bdr529 <1767...@bugs.launchpad.net> ezt írta (időpont: 2019. febr. 17., V,
20:10):
> Ubuntu 18.10 with tracker installed:
> With Tracker Search Provider by hamiller Plugin for Gnome Shell, Full-text
> Search works,
Does anybody know what to change in the source code to made FTS work? I
can compile and install it...at my own risk.
--
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/1767817
Title:
Ful
I switched from nvidia driver to nouveau driver and the huge memory
usage disappeared. Small jumps (increase) in memory usage stayed with
us.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1
No comment...
** Attachment added: "screenshot of gnome-usage"
https://bugs.launchpad.net/gnome-shell/+bug/1672297/+attachment/5190499/+files/Screenshot%20from%202018-09-19%2011-33-32.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
I installed Ubuntu 18.10 gjs and libgjs0g 1.53.3-1 (of Ubuntu 18.10) to
Ubuntu 18.04. It seems that the memory leak lives forever...
Memory usage started from 170MB, and after two hours is over 360MB.
[image: Képernyőkép erről: 2018-09-02 23-46-44.png]
chris pollock <1672...@bugs.launchpad.net> e
Why don't want the developers fix this (and other) bug? Whether do they
want me to use the non-LTS releases? Or do they want me to use other
distros than Ubuntu?
So I would like to use Ubuntu 18.04 with full gnome functionality without
bugs. (e.g. without memory leak...)
bdr529 <1767...@bugs.launc
Ubuntu 18.04.1 is coming soon (tomorrow?). What about the bug fixes?
I know a temporary method, but it is not so nice (but it works, saves
~400MB RAM): run after login
sudo killall -u gdm
killall gnome-software
One more, clear gnome-calendar. It launches automatically, uses
constantly 2-400MB RAM
*** This bug is a duplicate of bug 1672297 ***
https://bugs.launchpad.net/bugs/1672297
This bug report concerns to the initial size of the system (not the
continuously growing size). Is it a duplicate of bug 1672297?
Daniel van Vugt ezt írta (időpont:
2018. máj. 30., Sze, 4:35):
>
> *** This
Public bug reported:
After I log in (ubuntu session) the systen(?), shell(?) uses a lot of memory.
When the computer has 2GB RAM, 1.2GB is used. When the computer has 4GB RAM,
1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried it out in
virtualbox with a newly installed system
+1 on 18.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1616332
Title:
gnome-software using hundreds of MB of memory when not in use
Status in gnome-software package in Ubu
I have three computers, two desktops and one laptop. Two of them has a newly
installed Ubuntu 18.04 and one has an upgraded 18.04 (from 17.10). In one
desktop I installed ubuntu 18.04 in virtualbox. For every operating system I
installed tracker. Full text search in nautilus doesn't work in any
Public bug reported:
Some minutes after I logged in I realized that gnome-calendar runs in
the background and uses more than 400MB memory. I don't launched it. Is
it normal?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20
I think nautilus 3.26 should do full text search. If not, there are two
possibilities
Remove the option from the search menu.
Implement/fix the full text search capability.
On máj 3 2018, at 5:35 du, Mordi wrote:
>
> I kind of figured this out. In addition to Tracker, you need Gnome
> Documents
Public bug reported:
1)
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
2)
nautilus:
Installed: 1:3.26.3-0ubuntu3
Jelölt:1:3.26.3-0ubuntu3
Verziótáblázat:
*** 1:3.26.3-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Sorry, there's no bug.
dconf reset -f /
solved the problem, although it is not the most elegant solution.
** Changed in: unity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matc
Public bug reported:
When I lock the screen (with Ctrl+Alt+l or Super+l) the old (gnome?)
screen appears to unlock. I tried to reinstall unity, unity-services,
lightdm, unity-greeter, but nothing has changed.
Remark: I have two other machines, one of them works correctly, but on
the other the lo
Public bug reported:
My machine is ASUS X202E. It has an Atmel maXTouch Digitizer. I modified
/usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to
the touchscreen section:
Option "EmulateThirdButton" "1"
Option "EmulateThirdButtonButton" "3"
Option "Emu
Maybe it has usability problems, but in many cases the touchscreen is
more confortable than a mouse. I don't believe that it is impossible or
very difficult to modify the code so that a touchscreen behave similarly
(or the same way) as the touchpad or mouse. In win8 Microsoft could do
this. Canonic
O.K., I understand. But what would be the solution. I would like to use
my touchscreen without mouse. But without mouse I haven't got right
mouse button. Touch and hold my finger on the screen should replace the
right click. I tried out easystroke with half success. Touch and hold
worked, but the s
The same issue like written in "Bug Description".
My mashine is ASUS X202E.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1084938
Title:
evdev settings doesn't work
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211381/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211393/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211382/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211388/+files/UdevLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211390/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bu
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211379/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev i
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211384/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211389/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211387/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "peripherals.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211391/+files/peripherals.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211386/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211380/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bu
apport information
** Attachment added: "xinput.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211392/+files/xinput.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211385/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
ht
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211383/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211378/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubun
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211377/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubun
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job
DistroCodename: trusty
DistroRelease: Ubuntu 14.04
DistroVariant: ubuntu
InstallationDate: Installed on 2013-10-15 (341 days ago)
InstallationMedia: Ubuntu 13
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211375/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https:
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211376/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211372/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211374/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https:
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1084938/+attachment/4211373/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.lau
Public bug reported:
per***@A***oda:~$ /usr/lib/unity/unity-panel-service --lockscreen-mode
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint o
Public bug reported:
ginn doesn't work. To solve the problem, see
http://askubuntu.com/questions/57586/how-can-i-disable-arbitrary-
default-multitouch-gestures-in-unity/90383#90383Answer #9
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersion
Public bug reported:
I can not edit somefiles, e.g.
http://www.sze.hu/~perebal/launchpad/nevsor.xlsx
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: libreoffice 1:4.1.2~rc3-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion
Public bug reported:
After upgradint to 13.10 (and installing unity8 and ubuntu-touch ?) X
failed to start. The next error log was generated by X:
(on ASUS X202E)
[ 2397.673]
X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 2397.675] X Protocol Version 11, Revision 0
[ 2397.676] Build Opera
I uninstalled Intel's 01.org drivers, because I thought the crash was
caused by it. But no affect, nautilus crashes as before.
--
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/1220580
Ti
Apport doesn't notice the problem, no bug reporting window appeard.
Interesting, that any other of my computers doesn't produce such a
problem. The affected computer is an ASUS X202E.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautil
Public bug reported:
Sometimes when I push Alt key or click on an icon in natilus' window,
nautilus crashes, the background of the screen becomes black. But other
action can produc such a crash.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu16 [modified: usr/bin/na
89 matches
Mail list logo
