Hello and thank you for this bug report! (and sorry for this very long
delay!)
Do you still have this crash with the latest stable version? (3.3.0)
** Changed in: cairo-dock (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Package changed: cairo-dock (Ubuntu) = cairo-dock-plug-ins (Ubuntu)
** Also affects: cairo-dock-plug-ins
Importance: Undecided
Status: New
** Changed in: cairo-dock-plug-ins
Status: New = Fix Released
** Changed in: cairo-dock-plug-ins
Assignee: (unassigned) = Matthieu
Hello and thank you for this bug report! (and sorry for this very long
delay!)
Do you still have this crash with the latest stable version? (3.3.0)
** Changed in: cairo-dock (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Hello and thank you for this bug report! (and sorry for this very long
delay!)
Do you still have this crash with the latest stable version? (3.3.0)
** Changed in: cairo-dock (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: cairo-dock (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056646
Title:
SRU: Update cairo-dock packages in Ubuntu 12.04 LTS to the latest
** Changed in: cairo-dock (Ubuntu)
Status: Fix Released = Fix Committed
** Changed in: cairo-dock-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ubuntu
Importance: Undecided
Status: New
** Package changed: ubuntu = cairo-dock (Ubuntu)
** Changed in: cairo-dock (Ubuntu)
Status: New = Fix Committed
** Changed in: cairo-dock-core
Status: Fix Committed = Fix Released
--
You received this bug
** Also affects: cairo-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock-core
Status: Confirmed = Fix Released
** Changed in: cairo-dock (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
** Also affects: cairo-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock (Ubuntu)
Status: New = Fix Committed
** Changed in: cairo-dock-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of
** Also affects: cairo-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cairo-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cairo-dock-plug-ins (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock-plug-ins
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cairo-dock-plug-ins (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock-plug-ins
Status: Fix Committed = Fix Released
** Changed in: cairo-dock-plug-ins (Ubuntu)
Assignee: (unassigned) = Matthieu Baerts (matttbe)
--
You received this bug
-dock-plug-ins
Assignee: (unassigned) = Matthieu Baerts (matttbe)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/476842
Title:
Cairo-dock is unable to get CAPS Lock and NumLck values
To manage
** Changed in: cairo-dock-plug-ins
Status: Fix Committed = Fix Released
** Also affects: cairo-dock-plug-ins (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock-plug-ins (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because
** Also affects: cairo-dock-plug-ins (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock-plug-ins
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cairo-dock-plug-ins
Status: Fix Committed = Fix Released
** Changed in: cairo-dock-plug-ins
Milestone: 3.2.99.beta = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello and thank you for this bug report!
By modifing cairo dock with a bad info on desktop downbar
What did you do exactly? Is there a way to reproduce this crash?
What's this bad info?
PS: if you prefer, you can also report this bug in French in Glx-Dock
forums (but it's maybe better to
Public bug reported:
Hello,
With gnome-settings-daemon 3.8.5-0ubuntu4, we no longer have icon next
to buttons/menu items even if menus-have-icons and buttons-have-
icons options are enabled.
It seems it's due to this new patch: git_hardcode_deprecated_gtk_settings.patch
This patch has been
Hello,
It seems this fix introduces a new bug: LP: #1228886
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227537
Title:
crashes with gsettings-desktop-schemas 3.10
To manage notifications about
Hello and thank you for this bug report.
According to the stack trace, there is a crash in mesa.
I see that you're using Ubuntu 13.10 but with an old kernel (3.4.0 instead of
3.11.0-7-generic). Can you check that you're system is up to date?
(I just marked this bug as 'Invalid' but feel free to
*** This bug is a duplicate of bug 1152010 ***
https://bugs.launchpad.net/bugs/1152010
Hello Xrooters and thank you for this bug report,
Is there a way to reproduce this crash?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I forgot to say this: for those who have this bug, simply add this line
in a service which is launched before X' start (e.g. in
/etc/init/lightdm.conf, just after the line with 'script'):
echo OFF /sys/kernel/debug/vgaswitcheroo/switch
--
You received this bug notification because you are
I now have this crash all the time at startup (I'm using Ubuntu 13.10,
kernel 3.11)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170917
Title:
Powering down inactive GPU while running X causes
Hello and thank you for this bug report!
Switching settings in dock
@origpumu: what did you do exactly? It seems that this crash is due to
PowerManager applet. Did you just disable it? Did you just plug the battery
charger?
** Information type changed from Private to Public
** Changed in:
Strange :-/
But if you find a way to reproduce this crash each, it can be useful to fix
this bug ;)
@fabounet: any idea about this crash? :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219485
** 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/1215744
Title:
cairo-dock crashed with signal 7 in g_mapped_file_get_length()
To manage
Hello and thank you for this bug report!
Is it possible to give us more details about this bug? How do you reproduce it?
When did you this bug? At startup?
@fabounet: any idea? Why is there a null icon in this list?
http://bazaar.launchpad.net/~cairo-dock-team/cairo-dock-
** 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/1212981
Title:
cairo-dock assert failure: *** Error in `cairo-dock': invalid fastbin
entry (free):
)
Assignee: (unassigned) = Matthieu Baerts (matttbe)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212981
Title:
cairo-dock assert failure: *** Error in `cairo-dock': invalid fastbin
entry (free
** 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/1212268
Title:
cairo-dock crashed with SIGSEGV in _on_device_changed()
To manage notifications
Hello and thank you for this bug report!
Is it maybe possible to give us more details about this bug? How did you have
this bug? After having plugged a battery or something like that?
Did you just disable 'PowerManager' applet before the crash?
Is it maybe possible to try to reproduce this bug
Hello and thank you for this bug report.
But if I understand well the problem, this bug is not due to LaTeXila (the
editor) but with LaTeX.
If yes, please ask your question on a forum about LaTeX ;-) (e.g.
http://tex.stackexchange.com/ ).
If no, if this bug is due to the editor, please open a
*** This bug is a duplicate of bug 1152010 ***
https://bugs.launchpad.net/bugs/1152010
Hello Xrooters and thank you for this bug report!
Is it maybe possible to test the development version and check if you
still have this crash with it? It's easy to test it on Ubuntu by using
our Weekly
Hello and thank you for this bug report!
How did you have this bug? When displaying a menu? Which menu?
Is there a way to always reproduce this bug?
I'm not sure that this bug is due to Cairo-Dock but is it maybe possible
to test the development version by adding our 'Weekly ppa' and check if
Yes, I confirm that I'm not sure it's due to Cairo-Dock, it seems this
crash also affect other apps:
https://bugs.launchpad.net/bugs/+bugs?field.searchtext=FcFontMatchsearch=Search+Bug+Reportsfield.scope=allfield.scope.target=
(it's maybe due to a change in fontconfig (if you're not using a
@Martin: Thank you for this quick fix :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206687
Title:
Calibre has a .destkop file named 'calibre' but the class of the
window is 'Calibre-gui'
To
It's maybe better to rename the icon too:
debian/rules:
- cp manual/resources/logo.png debian/tmp/usr/share/pixmaps/calibre.png
+ cp manual/resources/logo.png debian/tmp/usr/share/pixmaps/calibre-gui.png
debian/local/calibre-gui.desktop
- Icon=calibre
+ Icon=calibre-gui
But why
@Ian Romanick: 3vi1 is able to reproduce this bug on 9.1.4.
It only affects Ivybridge GPU (no problem with an Ironlake GPU), what can we do
more?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180646
Public bug reported:
Hello,
Firstly, thank you for maintaining Calibre packages!
It seems that Calibre's launcher is named 'calibre.desktop' but when you
launch Calibre GUI, you can see that Calibre window's class is 'Calibre-
gui' and not 'Calibre'. (according to `xprop`)
It's maybe a detail
The upstream bug (GNOME #685303) has been marked as duplicate of this bug:
GNOME #700401.
= https://bugzilla.gnome.org/show_bug.cgi?id=700401
** Bug watch added: GNOME Bug Tracker #700401
https://bugzilla.gnome.org/show_bug.cgi?id=700401
** Changed in: rhythmbox
Importance: Critical =
Public bug reported:
Hello,
This bug is maybe not due to Indicator-Sound but since this indicator has been
ported to a service (since we have to load
/usr/share/unity/indicators/com.canonical.indicator.sound), its menu looks
different when using it with Cairo-Dock or with indicator-loader.
As
@Ayberk: Thank you for these details but it seems this ppa
(https://launchpad.net/~ubuntu-x-swat/+archive/intel-graphics-updates)
contains old packages and you're using llvmpipe:
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x301)
--
You received this bug notification because you
i965_dri.so is the OpenGL driver used for all of the GPUs mentioned in
this bug report (I see Ironlake and Ivy Bridge).
@Ian Romanick: ok, thank you! But it seems this bug *only* affects Ivy Bridge
GPU (Intel 4000 HD).
I'm using an Intel Ironlake Mobile and I don't have this problem.
--
You
** Changed in: cairo-dock-plug-ins
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197569
Title:
Move from zeitgeist-1.0 to zeitgeist-2.0
To manage
** Also affects: cairo-dock-plug-ins
Importance: Undecided
Status: New
** Changed in: cairo-dock-plug-ins
Status: New = Triaged
** Changed in: cairo-dock-plug-ins
Milestone: None = 3.2.99.beta
** Changed in: cairo-dock-plug-ins
Assignee: (unassigned) = Matthieu Baerts
It seems here that the jerky scrolling in some windows is caused by the
combination
of the orig. xi2: Reset scroll valuators on synthesized crossing events
commit which
is in the current libgtk3 ** bindings being set in compiz for Desktop-based
Viewport Switching , specifically, - next =
@Cavsfan: Is it possible to install the development version and send
here a backtrace of this crash? (more info on comment #11)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152010
Title:
** Changed in: cairo-dock-plug-ins (Ubuntu)
Assignee: (unassigned) = Matthieu Baerts (matttbe)
** Changed in: cairo-dock-plug-ins (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
*** This bug is a duplicate of bug 1152010 ***
https://bugs.launchpad.net/bugs/1152010
Hello and thank you for this bug report!
Is it maybe possible to test the development version and check if you
still have this crash with it? It's easy to test it by using our Weekly
ppa:
Is it maybe possible to test the development version and check if you
still have this crash with it? It's easy to test it on Ubuntu by using
our Weekly ppa: http://glx-dock.org/ww_page.php?p=ppa%20Weeklylang=en
If you still have the crash, it can be very useful to get a backtrace of this
crash
Ok, you're also using i915 video driver!
But it only affects Ivy Bridge cards! (Intel 4000HD)
@Intel devs: is this bug due to this i915 video driver or something
else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Assignee: Matthieu Baerts (matttbe)
Status: In Progress
** Affects: cairo-dock (Ubuntu)
Importance: High
Assignee: Matthieu Baerts (matttbe)
Status: In Progress
** Also affects: cairo-dock-core
Importance: Undecided
Status: New
** Changed in: cairo-dock
** Changed in: cairo-dock-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1193598
Title:
Cairo-Dock Session is broken with Gnome-Session 3.8
To manage
** Branch linked: lp:ubuntu/cairo-dock
** Changed in: cairo-dock (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: cairo-dock (Ubuntu)
Milestone: None = ubuntu-13.04-month-6
** Changed in: cairo-dock (Ubuntu)
Milestone: ubuntu-13.04-month-6 = ubuntu-13.06
--
You
** Changed in: cairo-dock (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1193598
Title:
Cairo-Dock Session is broken with Gnome-Session 3.8
To
Hello and thank you for this bug report!
Is it possible to give us more details about that?
* Are you using our Cairo-Dock session?
* Can you check if Cairo-Dock is running? e.g. by using these commands:
$ pidof cairo-dock
$ ps aux | grep cairo-dock
* Did you have this bug before?
Public bug reported:
Hello,
Firstly, thank you for maintaining all these gnome packages!
The latest version of gnome-menus has renamed applications.menu file:
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/gnome-
menus/saucy/revision/136/debian/gnome-menus.maintscript
(I just subscribe Jeremy to this bug report because the latest version
of gnome-menus was modified by him. I hope it's not a problem for him!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191290
@Jeremy: thank you for this quick answer!
This isn't breaking anything though, right?
It's not a problem for Cairo-Dock because if this file is not found
[$XDG_CONFIG_DIRS/menus/${XDG_MENU_PREFIX}applications.menu] the dock
will check first with some prefix (gnome-, kde-, etc.) and then check
PS: yes, I confirm that this bug is fixed with the version 3.8:
https://git.gnome.org/browse/gnome-session/tree/gnome-
session/main.c?id=3.8.2.1#n360
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If there is a different desktop that has trouble with the rename,
please file a bug.
It's just that this environment variable is used by a few applications: shell,
panel and menu-editors.
I guess that most of them are designed for GNOME and then will also check if
'gnome-applications.menu'
Note: the workaround has been updated and now works with SystemD ;)
*
https://bazaar.launchpad.net/~cairo-dock-team/cairo-dock-core/scripts/view/head:/refresh_cd_on_resuming.py
= 'download file'
* Info:
Alacarte has now its own menu/item editor =
http://ftp.gnome.org/pub/gnome/sources/alacarte/3.7/alacarte-3.7.90.news
** Changed in: alacarte (Ubuntu)
Status: Invalid = Fix Released
** Changed in: gnome-panel (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification
This bug seems to be fixed with the latest stable version of QtCreator
(2.7.1), someone can confirm? :)
** Also affects: qt
Importance: Undecided
Status: New
** Changed in: qt
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
PS: it seems I didn't see the comment #2 :)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qtcreator in Ubuntu.
https://bugs.launchpad.net/bugs/1153198
Title:
qtcreator window has no class
To manage notifications about this bug go to:
** Changed in: cairo-dock-plug-ins
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/535065
Title:
launcher icon corruption after wake-up from suspend
To manage
But do you have an Intel IvyBridge 4000HD as everybody else who has this
bug here? And are you using default video drivers of your distribution?
$ lsmod|grep ^i
$ sudo lshw -C display
$ glxinfo| grep OpenGL
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
(In reply to comment #25)
sorry for being late , i had an exam
here the 2 command in comment #21
as u can see on the video that the secound command made some effects work :O
thats why i made video not ss i can make ss for both commands if u want .
http://youtu.be/Fep3MOj4Qh8
If you only
@AbdoRefky: is it possible to create a new bug report which affects
Drivers/DRI/i915 because it's maybe not the same problem.
About apitrace, it should create this file in the same directory: cairo-
dock.trace. Is it possible to join this file to the new bug report?
@lylambda: can you confirm
@fabounet:
It seems there is a crash in Cairo-Pinguin:
There is an infinite loop, we can see these two frames are called until
it crashes:
#1998 0x7f1e084f3192 in on_build_container_menu (myApplet=0x23ca110,
pClickedIcon=optimised out, pClickedContainer=optimised out,
Hello and thank you for this bug report! (and sorry for the delay, we
didn't have access to this private bug report)
Are you able to reproduce this crash with the latest stable version?
(3.2.1) = http://www.glx-
dock.org/ww_page.php?p=From%20the%20repositorylang=en
** Changed in: cairo-dock
PS: @fabounet: Evan is not the user who had this crash but it affects a
few people (~50 according to errors.ubuntu.com)
** Summary changed:
- Crash due to Cairo-Pinguin: infinite loop in on_build_container_menu
+ Crash due to Cairo-Penguin: infinite loop in on_build_container_menu
--
You
(In reply to comment #20)
8 month's to solve a bug ?
This bug is still not fixed but it seems Mesa devs are really busy, no
need to insist ;)
i there any information should i upload to fix this bug ?
An 'apitrace' can maybe be useful.
$ apitrace trace --api=gl /usr/bin/cairo-dock
Can you
Created attachment 79885
apitrace of the bug
Hello,
It's maybe easier if this file is directly added here (and with a better
compression) ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180646
Created attachment 79886
apitrace replay with an Intel Ironlake Mobile
If I use the option 'replay' with an Intel Ironlake Mobile (i915), I
don't have this problem: all icons are correctly drawn.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Sebastien: bugwatch added ;) =
https://bugzilla.gnome.org/show_bug.cgi?id=699574
** Bug watch added: GNOME Bug Tracker #699574
https://bugzilla.gnome.org/show_bug.cgi?id=699574
** Also affects: gtk via
https://bugzilla.gnome.org/show_bug.cgi?id=699574
Importance: Unknown
Status:
/+archive/daily
** Changed in: latexila (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: latexila (Ubuntu)
Milestone: None = ubuntu-13.05
** Changed in: latexila (Ubuntu)
Assignee: (unassigned) = Matthieu Baerts (matttbe)
** Tags removed: raring
** Tags added: saucy
Public bug reported:
Hello,
Scrolling with a touchpad is now a bit jerky.
It's exactly the same bug than bug #1171156 introduced in Raring by an
upstream's patch in order to fix bug #1046988 (which was tracked by
upstream there: https://bugzilla.gnome.org/show_bug.cgi?id=690275 )
* Impact:
Up
Hello and thank you for this bug report,
Is it maybe possible to share a screenshot with us?
Do you also have this bug if you use the dock without the OpenGL backend?
$ cairo-dock -c
Or with the default theme?
$ cairo-dock -d ~/cd-tmp
--
You received this bug notification because you are
cairo-dock was installed before (old version of ubuntu ) and I simply
installed then the weekly-cairo-dock to that ! - have forgotten to
throw out
old-cairo-dock ???!!!
No need to remove older versions before the upgrade ;)
how do I solve this problem now ???
In fact, it will be easier for
Ok thank you,
Can you check that you're using Compiz? E.g. by launching this command from a
terminal which should print something if Compiz is running:
$ ps aux | grep [c]ompiz
If Compiz is running, can you give us more details about your video cards and
your video drivers?
$ glxinfo |
Public bug reported:
Hello,
This morning I upgrade my system. After having rebooted it, web addresses are
no longer resolved.
I can still ping servers and if I add entries in /etc/hosts it works fine.
I tested with my both network cards (eth and wlan) but I still have this bug
with the DNS.
I just reinstalled resolvconf and rebooted and now, everything works
fine :)
$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 mai 15 17:44 /etc/resolv.conf -
../run/resolvconf/resolv.conf
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
If this was in fact corrupted data from D-Bus or GTK, would there be
any way to verify this?
Yes I guess it's easy to verify this with GDB. (and with dbus-monitor
and 'cairo-dock -l debug' to have more debugs info)
A more likely cause would probably be that a corrupt indicator was
created, or
Hello and thank you for this bug report!
Is it maybe possible to give us a backtrace of this crash with GDB? It's
easy because it's explained there: http://glx-
dock.org/ww_page.php?p=dddlang=en
PS: I see that this bug is assigned to you, that means: you should be
the guy who will try to fix
Oh great, I just reassigned this bug to you ;)
** Changed in: cairo-dock (Ubuntu)
Assignee: (unassigned) = Stephen Kraemer (straemer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179297
Is there a way to create a notification for debugging purposes?
Yes, you can easily create an 'indicator' applet:
https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators#Python_version
I suspect that this might be caused by a notification coming up when
the dock isn't launched or
The previous modifications have been reverted because it seems this
patch causes other problems (LP: #1171156).
I guess I can change the status to 'Confirmed' until a new patch is
introduced (or until someone finds why there are some problems when
using this patched version with Compiz).
**
Here is a screencast without the patch (the scroll is smooth)
** Attachment added: Without the patch
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650661/+files/gtk_scroll_1171156_without_patch.ogv
--
You received this bug notification because you are a member
Another one with the patch (with the latest version of GTK). I scroll
down and then up but as you can see, the scroll down is not smooth (but
when scrolling up, it's ok)
** Attachment added: With the patch
According to the tests made by Doug, it seems this patch introduces a
more annoying problem than what we had with the previous version when
using Compiz (and maybe others WM). This maybe means that it introduces
unknown bugs or something is missing... Maybe more dangerous to use this
version than
@Sebastien, thank you for this new version :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171156
Title:
debian/patches/git_reset_scrolling.patch is adversely affecting
scrolling, particularly
Hello,
@Sebastien Bacher: it seems that due to this patch, the scroll is not so
smooth that before. I just reinstalled the previous version
(3.6.4-0ubuntu6) and the scroll is much better: no lag, just smooth :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Hello,
I'm using Ubuntu Raring 13.04 with the latest version of the kernel
available in these repos (3.8.0-19.29).
Sometimes I have a kernel OOPS at startup and it seems it's because I switch
off my ATI card.
I added this line in my /etc/rc.local file:
echo OFF
** Attachment added: Backtrace of this crash (from kern.log)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1170917/+attachment/3648935/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Linux Kernel Bug Tracker #49531
http://bugzilla.kernel.org/show_bug.cgi?id=49531
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=49531
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
@sladner84: if you also have this bug, please answer to the question on
comment 1.
PS: note that it's maybe possible that you're still trying to use a
Cairo-Dock session (but your session manager (lightdm, gdm, etc.) should
not launch it).
** Changed in: cairo-dock (Ubuntu)
Status:
** Also affects: fglrx-driver (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo-dock-core
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165353
** Description changed:
The Ubuntu X team would like to push mesa 9.1.1 for raring. It has been
on a staging ppa for roughly two months now, and we've tested it on a
variety of hw. During this time we've identified a regression with the
Intel driver having a slow blur effect, causing
301 - 400 of 1369 matches
Mail list logo
