This still happens in final Hardy.
--
System Monitor crashes when changing nice value of process
https://bugs.launchpad.net/bugs/206583
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
It seems to be fixed in Hardy since files aren't moved to Trash anymore
on NTFS partitions and Gnome shows an extra warning.
--
Gnome Trash doesn't show deleted files on ntfs-3g partitions
https://bugs.launchpad.net/bugs/106621
You received this bug notification because you are a member of
@mihai007
I guess it is a pulseaudio problem. Just close Rhythmbox, run in Terminal the
command killall pulseaudio and start Rhythmbox again. If pulseaudio is the
reason it is probably fixed with the new Kernel in proposed.
--
Rhythmbox sound problems (clicking/snapping/crackling) when not
Public bug reported:
Binary package hint: gnome-control-center
Sound applet often shows zero volume after loudness change with the volume
keys. The sound isn't actually muted the bar is just gone. If I change loudness
again the bar is shown like before. This happens every time after two to
I can confirm this. It could be fixed through enabling compiz but this
is among other things not such a good idea on slower computers. Maybe it
is a Metacity bug too.
** Summary changed:
- vlc does not switch to fullscreen properly when there are Alwas on Top
windows
+ [regression] vlc does not
I can confirm this with Hardy but it doesn't mute the sound it all it
only doesn't show the volume bar.
** Summary changed:
- [GUTSY] Regression - Volume Control using gnome panel applet and keyboard
shortcut alternates mute / % volume during sliding
+ Regression - Volume Control using gnome
I have two audio devices but if connected only the Audigy2 is used. The
volume keys change the Master controller. Afaik this happens with only
one connected sound card too but I am going to recheck it soon.
Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High
Definition Audio
** Attachment added: sound applet after changing volume afterwards
http://launchpadlibrarian.net/14364506/soundapplet-normal.png
--
Regression - Volume Control using gnome panel applet and keyboard shortcut
alternates mute / % volume during sliding
https://bugs.launchpad.net/bugs/126333
You
This still happens in Hardy. Since the visualization isn't shown without
user interaction there would be no problem if the plugin is deactivated
per default. At least as long as Xorg without nvidia driver or maybe
fglrx isn't able to manage more than one active 3D app.
--
visualisation plugin
Just for the records it happens with one sound card too. I guess it is a
general gnome sound applet problem. It even happens with Compiz.
--
Regression - Volume Control using gnome panel applet and keyboard shortcut
alternates mute / % volume during sliding
There is a trick to work around it. After activating full screen click
on the grey vlc window and then outside of it on the video output. After
that video should be on top.
--
[regression] vlc does not switch to fullscreen properly when there are Alwas
on Top windows
** Attachment added: lspci-vvnn
http://launchpadlibrarian.net/14418634/lspci-vvnn
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: gpm = gnome-power-manager
** Description changed:
- Binary package hint: gpm
+ Binary package hint: gnome-power-manager
Gnome Power Manager
Public bug reported:
Binary package hint: gnome-power-manager
Normally I remove the battery if my laptop is connected to AC to save the
lifetime of it. If I do this there is no battery tab in Gnome Power Manager
anymore. The battery tab is only shown in battery mode so it is impossible to
*** This bug is a duplicate of bug 197288 ***
https://bugs.launchpad.net/bugs/197288
I guess this is a duplicate of Bug #19728.
** This bug has been marked a duplicate of bug 197288
[hardy]new windows are put in background then some window has always on top
set
--
[regression] vlc does
*** This bug is a duplicate of bug 197288 ***
https://bugs.launchpad.net/bugs/197288
Typo, I mean Bug #197288.
--
[regression] vlc does not switch to fullscreen properly when there are Alwas
on Top windows
https://bugs.launchpad.net/bugs/222658
You received this bug notification because
** Changed in: metacity (Ubuntu)
Status: New = Confirmed
--
[hardy]new windows are put in background then some window has always on top set
https://bugs.launchpad.net/bugs/197288
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 197288 ***
https://bugs.launchpad.net/bugs/197288
** This bug has been marked a duplicate of bug 197288
[hardy]new windows are put in background then some window has always on top
set
--
fullscreen and always on top conflict
** Changed in: gnome-panel (Ubuntu)
Sourcepackagename: None = gnome-panel
--
Applications/Places/System menu is not flush to top of screen
https://bugs.launchpad.net/bugs/192096
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel
I can confirm this. It is a real show stopper since F-Spot is the only
installed image screensaver which is widely used I guess.
** Changed in: f-spot (Ubuntu)
Status: New = Confirmed
--
f-spot doesn't work with gnome-screensaver
https://bugs.launchpad.net/bugs/208629
You received this
It is possible a problem in the upstream version too. Maybe it has
something to do with the f-spot database upgrade (auto-upgrade db from
sqlite2 to sqlite3).
--
f-spot doesn't work with gnome-screensaver
https://bugs.launchpad.net/bugs/208629
You received this bug notification because you are a
** Summary changed:
- f-spot doesn't work with gnome-screensaver
+ [Hardy] f-spot doesn't work with gnome-screensaver
** Bug watch added: GNOME Bug Tracker #526477
http://bugzilla.gnome.org/show_bug.cgi?id=526477
** Also affects: f-spot via
http://bugzilla.gnome.org/show_bug.cgi?id=526477
The patch fixes the problem for me. It would be great if this one could
made it into Hardy.
--
[Hardy] f-spot doesn't work with gnome-screensaver
https://bugs.launchpad.net/bugs/208629
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I have created a diff of the patch against current Ubuntu Hardy F-Spot.
** Attachment removed: Slideshow Fixes
http://launchpadlibrarian.net/13174169/slideshow-fixes.patch
** Attachment added: slideshow-fixes.patch
http://launchpadlibrarian.net/13186483/slideshow-fixes.patch
--
f-spot
I can confirm this with current Hardy but it is possible to kill F-Spot with
alt + tab and then close it with force quit. I can see only parts of images
after a long loading time and I never see the control bar.
I have a Nvidia Geforce 440 Go with the proprietary driver.
Standard full screen
Btw. the screensaver slide show (with the fix of Bug #208629) works
without problems or high cpu usage but not the manual started one.
--
F-Spot crashes? takes up a lot of resources? in slideshow mode
https://bugs.launchpad.net/bugs/212034
You received this bug notification because you are a
Confirming with current Hardy and F-Spot. It hangs very often on exit.
--
Mono applications (f-spot.exe, gbrainy, ..) crash on exit with SIGSEGV
(/lib/ld-linux.so.2)
https://bugs.launchpad.net/bugs/123764
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Possible there is a crash dump of this problem under Bug #213823.
--
F-Spot crashes? takes up a lot of resources? in slideshow mode
https://bugs.launchpad.net/bugs/212034
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
It happens with the -nvidia and the nv driver but on another Hardy
system with Intel graphic and compiz slide show works fine.
--
F-Spot crashes? takes up a lot of resources? in slideshow mode
https://bugs.launchpad.net/bugs/212034
You received this bug notification because you are a member of
@Paul Fisher
Which graphic card do you have?
--
F-Spot crashes? takes up a lot of resources? in slideshow mode
https://bugs.launchpad.net/bugs/212034
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
--
desktop-bugs
It seems to be an OpenGL problem in combination with some
gpus/drivers/cpus? The screensaver slide show doesn't use OpenGL but the
manual started one.
--
F-Spot crashes? takes up a lot of resources? in slideshow mode
https://bugs.launchpad.net/bugs/212034
You received this bug notification
It seems to be a Xorg configuration problem at least for the -nv driver. F-Spot
crashes after starting slide show with F-Spot and -nv driver but it works fine
after running sudo dpkg-reconfigure xserver-xorg and restarting X so I guess
glx or something like this was missing. I haven't rechecked
** Changed in: evolution (Ubuntu)
Sourcepackagename: None = evolution
--
[hardy] Evolution server using 50% cpu
https://bugs.launchpad.net/bugs/212498
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in ubuntu.
--
desktop-bugs
I can confirm this behavior with Intel 915 graphich card and a Nvidia Geforce
8800 GTS/512. Latest updates are installed.
Everytime I change resolution or something like that and click apply nothing
changes and the message Sending client message is posted.
Console output:
I guess it is not the drivers fault.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Invalid
--
[intel 855GM] gnome-display-properties crashed with SIGSEGV in screen_info_new()
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a
I am closing the Trident driver. Thanks for pointing it out. Could you
please post your output of xrandr?
** Changed in: gnome-settings-daemon (Ubuntu)
Sourcepackagename: gnome-desktop = gnome-settings-daemon
** Changed in: xserver-xorg-video-trident (Ubuntu)
Status: New = Invalid
**
Sorry I have read over it.
What happens if you change your resolution with System - Preferences - Screen
Resolution? Does it still show the correct resolution after X logout and
relogin?
Maybe your wrong resolution happens because of changes in the
gnome-display-properties.
** Changed in:
You can run xrandr --auto in Gnome console. This should change the
resolution to 1024x768 so you can use the gnome-display-properties tool.
xrandr changes aren't saved so the GUI tool have to be used afterwards.
--
[hardy] [regression] gnome-settings-daemon update gives 400x300 resolution
after
My fault it should be xrandr --output default --auto.
--
[hardy] [regression] gnome-settings-daemon update gives 400x300 resolution
after login
https://bugs.launchpad.net/bugs/200411
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This seems to be fixed in current Hardy at least with my two graphic
cards.
--
[Hardy] Gnome screen resolution doesn't apply changes
https://bugs.launchpad.net/bugs/199718
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
What's with xrandr --output --default --mode 1024x768 ? Of course you
have to remove the from the command.
--
[hardy] [regression] gnome-settings-daemon update gives 400x300 resolution
after login
https://bugs.launchpad.net/bugs/200411
You received this bug notification because you are a
Last command was wrong, please use:
xrandr --output default --mode 1024x768
--
[hardy] [regression] gnome-settings-daemon update gives 400x300 resolution
after login
https://bugs.launchpad.net/bugs/200411
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Closed according to user comment.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete = Invalid
--
[hardy] [regression] gnome-settings-daemon update gives 400x300 resolution
after login
https://bugs.launchpad.net/bugs/200411
You received this bug notification because you
I can confirm this. I am not sure now which packages causes it but it is
not an only compiz problem since it appears with the vesa driver too. I
am going to test another desktop like fluxbox or something like that. I
guess it has something to do with the gnome-settings-daemon or the
panel.
Linux
Btw. it doesn't happen on my Hardy 32 Bit platform with Intel graphich
that's why I have waited so long to report it.
** Attachment added: lspci-vvnn
http://launchpadlibrarian.net/12626740/lspci-vvnn
--
[Hardy] [Regression] after login only a mouse is shown on a black screen (amd64)
** Attachment added: xorg.conf
http://launchpadlibrarian.net/12626754/xorg.conf
--
[Hardy] [Regression] after login only a mouse is shown on a black screen (amd64)
https://bugs.launchpad.net/bugs/201746
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/12626760/Xorg.0.log
--
[Hardy] [Regression] after login only a mouse is shown on a black screen (amd64)
https://bugs.launchpad.net/bugs/201746
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Attachment added: xsession-errors
http://launchpadlibrarian.net/12626761/xsession-errors
--
[Hardy] [Regression] after login only a mouse is shown on a black screen (amd64)
https://bugs.launchpad.net/bugs/201746
You received this bug notification because you are a member of Ubuntu
Desktop
** Attachment added: dmesg
http://launchpadlibrarian.net/12626763/dmesg
** Summary changed:
- Since last upgrade yesterday, after booting the sistem (everything normal
including sound), I can't see the desktop. Amd64 Nvidia Gforce
+ [Hardy] [Regression] after login only a mouse is shown on
Another problem is gdm. I have moved the user direcotory and created a new one
with write support but after this gdm doesn't login with this user. It just
changes the password field back to username field. I guess I have to
find/create another bug report for this but I guess it is worth
I can confirm this. It happens with every CD/DVD which is inserted (even video
DVDs which aren't mounted). A file operation isn't needed.
I am not sure if it is a hal or a gnome-volume-manager issue. This doesn't
happen in Gutsy but in Hardy since some time and of course in current.
This is bug
I have reported it upstream since I haven't find any bug report. Feel
free to confirm.
** Bug watch added: GNOME Bug Tracker #534752
http://bugzilla.gnome.org/show_bug.cgi?id=534752
** Also affects: metacity via
http://bugzilla.gnome.org/show_bug.cgi?id=534752
Importance: Unknown
I can confirm this issue and it even happens with Debian SID so I guess
it is a general Gnome or maybe Debian problem. Compiz isn't affected.
** Summary changed:
- [hardy]new windows are put in background then some window has always on top
set
+ [hardy] new windows are put in background when a
@Achim
This isn't a bug in F-Spot this is a bug in Gnome printer dialog. Many Gnome
apps have this problem afaik.
Many thanks for uploading. I haven't expected this to be in Hardy
without self compiling. Especially the printing dialog is very
important.
--
fspot print dialog [Hardy Heron]
Seems to work fine for me so far. I have tested importing, deleting,
categorizing, printing, slideshow, fullscreen and screensaver. I haven't a big
photo db here but I upgrade it soon on a client which has one. If there are any
problem I'll report back.
Btw. is this for hardy-updates or
Public bug reported:
Binary package hint: gvfs-backends
If X crashes or is restarted with ctrl + alt + backspace several autostarted
apps aren't closed. This are in standard Hardy installation gvfsd-burn,
gvfsd-trash, trackerd and dbus-daemon.
After trying to reproduce a crash I had over 20
Closing then for gnome-power-manager. The driver issue is Bug #241867.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Invalid
--
Brightness only works using manual controls
https://bugs.launchpad.net/bugs/214440
You received this bug notification because you are a member of
This bug/wish still exists and I have created a bug report at Gnome
since it is more an upstream issue. I hope that this gets fixed in
future since it is very confusing.
** Bug watch added: GNOME Bug Tracker #515223
http://bugzilla.gnome.org/show_bug.cgi?id=515223
** Also affects:
Many thanks.
Both problems seems to be fixed in current Hardy. Suspend works fine.
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-source-2.6.22 = linux
Status: Incomplete = Fix Released
** Changed in: gnome-applets (Ubuntu)
Status: New = Fix Released
--
Audigy 2 ZS
*** This bug is a duplicate of bug 87909 ***
https://bugs.launchpad.net/bugs/87909
I am closing this bug since it was more a bios problem than an Ubuntu
one but the sound card selection is another issue which is a duplicate
of Bug #87909.
** Changed in: ubuntu
Status: New = Invalid
*** This bug is a duplicate of bug 123601 ***
https://bugs.launchpad.net/bugs/123601
This is more a bug in Gnome sound settings than in Totem since it uses
the default Alsa card but Gnome doesn't change it. This problem has
already been reported. Marking as a duplicate.
** Changed in:
Might be connected to Bug #123601.
--
Volume applet should change according to default sound card.
https://bugs.launchpad.net/bugs/21270
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
*** This bug is a duplicate of bug 123601 ***
https://bugs.launchpad.net/bugs/123601
** This bug has been marked a duplicate of bug 123601
Gnome sound settings aren't connected and have no effect on Alsa
--
Sound selected to Audigy ES, but alsamix points to the wrong card.
*** This bug is a duplicate of bug 123601 ***
https://bugs.launchpad.net/bugs/123601
** This bug has been marked a duplicate of bug 123601
Gnome sound settings aren't connected and have no effect on Alsa
--
Sound is intermittent with two sound cards, needs better GUI control
*** This bug is a duplicate of bug 123601 ***
https://bugs.launchpad.net/bugs/123601
** This bug has been marked a duplicate of bug 123601
Gnome sound settings aren't connected and have no effect on Alsa
--
Gnome Volume Control change device function has no effect
*** This bug is a duplicate of bug 123601 ***
https://bugs.launchpad.net/bugs/123601
** This bug is no longer a duplicate of bug 87909
Gnome Volume Control change device function has no effect
** This bug has been marked a duplicate of bug 123601
Gnome sound settings aren't connected
*** This bug is a duplicate of bug 123601 ***
https://bugs.launchpad.net/bugs/123601
** This bug is no longer a duplicate of bug 87909
Gnome Volume Control change device function has no effect
** This bug has been marked a duplicate of bug 123601
Gnome sound settings aren't connected
** This bug is no longer a duplicate of bug 87909
Gnome Volume Control change device function has no effect
** Bug watch added: GNOME Bug Tracker #515223
http://bugzilla.gnome.org/show_bug.cgi?id=515223
** Also affects: gnome-control-center via
According to Sebastian Bacher's comment I have used a separate bug
report for the Ubuntu sound issue.
** Summary changed:
- Gnome Volume Control change device function has no effect
+ Gnome sound settings aren't connected and have no effect on Alsa
** Description changed:
- Binary package
I have created a script to work around this problem which is run on every
system start to change the four settings.
It only works with my Audigy2 and Intel sound card but it should be easy to
change the important parts.
** Attachment added: hotplug-sound.sh
I can confirm this but it is a gnome-panel issue and sadly not the only
one (changing icon positions). It is a little bit messed up in Gnome.
E.g try to move the panel if it has many icons and you put it on the
right or left side of a wide screen monitor.
** Changed in: gnome-panel (Ubuntu)
I am pretty sure that this bug has something to do with Bug #131646 and of
course Bug #130933.
You can test it through disabling compiz System - Preferences - Appearance -
Desktop Effects - None and then restart X. After that the panel should be fine.
Btw. please post the output of xrandr.
--
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Fix Released
--
[Gutsy] Display sleep sets wrong DPMS off time
https://bugs.launchpad.net/bugs/190537
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Binary package hint: gnome
I think this is a security risk and gnome has a great option for this. It is a
good idea to lock screen on suspend/hibernate only if people want it. Everybody
who enables screen saver locking wants to lock screen on suspend/hinbernate too.
The
I seems that this bug has been fixed in Gutsy.
--
switching to current logged in user freezes gdm
https://bugs.launchpad.net/bugs/78470
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I can confirm this. The same behavior still happens in Gutsy. It looks
unintuitive and gives an impression that operation hasn't worked out.
Since gnome panle user switcher is enabled by default in Gutsy a gdm theme with
a user list should be enabled by default. If this shows logged in users it
** Changed in: gnome-screensaver
Bugwatch: GNOME Bug Tracker #172912 = GNOME Bug Tracker #402475
Status: Invalid = Unknown
--
switch user should pre-fill the username for gdm
https://bugs.launchpad.net/bugs/42262
You received this bug notification because you are a member of Ubuntu
This seems to be fixed in current Gutsy.
--
switch user should pre-fill the username for gdm
https://bugs.launchpad.net/bugs/42262
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
I have the same problem under Gutsy. This is really weird at least for an audio
player.
Btw. Totem has the same problem while playing audio files even if the audio
visualisation is disabled under options.
--
visualisation plugin blocks video output when not active
I can confirm this bug and the workaround with current Gutsy. It mostly happens
on basses.
I am using Audigy 2 ZS Notebook.
--
Rhythmbox sound problems (clicking/snapping/crackling) when not using
crossfading backend
https://bugs.launchpad.net/bugs/116990
You received this bug notification
@Jon-o Addlerman
This has nothing to do with gdm, it is a known new Intel driver bug #127101.
--
switching to current logged in user freezes gdm
https://bugs.launchpad.net/bugs/78470
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
*** This bug is a duplicate of bug 47183 ***
https://bugs.launchpad.net/bugs/47183
** This bug has been marked a duplicate of bug 47183
Incorrect resolution even after changing desktop resolution
--
Gnome recognizes the resolution 1368x768 instead of 1366x768
This should be fixed in Gutsy because of change too new Intel driver but with
Gutsy Beta Live CD I have the problem that 1024x768 instead of 1366x768 is
saved in xorg.conf. This seems to be a regression and doesn't happen with Tribe
5 which still uses the i810 driver.
Of course it is no problem
Johnathon problem has something to do with wrong resolution given through i810
driver. If this driver is used xrandr provided the correct resolution but
1368x768 too (http://launchpadlibrarian.net/6931687/xrandr.txt) and it seems
that gnome screen resolution uses the highest possible
It is a shame that asoundconf setting, Sound Preferences (for keyboard volume
change), Gnome Volume Control and Gnome Volume Applet (for mouse volume change)
aren't connected and doesn't change automatically to active sound card.
Another point is that it is best to use mixer PCM with integrated
Alsamixer works correctly and changing volume with Gnome apps too but
they aren't connected and some settings are reseted every time I change
my soundcard configuration.
--
Gnome Volume Control change device function has no effect
https://bugs.launchpad.net/bugs/87909
You received this bug
Ok, system needs two recognized sound cards. I assume that in all options the
external is the default.
Under System - Preferences - Sound it is possible to choose a Device. I choose
the internal one and mixer PCM (for keyboard volume change). A standard user
would think that's it, now internal
** Changed in: bugzilla
Status: New = Invalid
--
gnome-video-thumbnailer uses all available CPU power when using bittorrent
https://bugs.launchpad.net/bugs/79030
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Same problem here but after disabling and enabling desktop effects it
works fine after restart. Maybe compiz settings have to be reseted.
--
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
https://bugs.launchpad.net/bugs/147943
You received this bug
I still got the problem. It seemed to work because compiz crashed
silently.
--
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
https://bugs.launchpad.net/bugs/147943
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
It is not a bug that one gui isn't able to manage two sound cards without
scripting or at least four settings changes?
Could you please make it at least Wishlist?
--
Gnome Volume Control change device function has no effect
https://bugs.launchpad.net/bugs/87909
You received this bug
** Changed in: gnome-panel (Ubuntu)
Sourcepackagename: None = gnome-panel
--
gnome panel crash when boot gutsy livecd RC
https://bugs.launchpad.net/bugs/152147
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-panel in ubuntu.
*** This bug is a duplicate of bug 147943 ***
https://bugs.launchpad.net/bugs/147943
** This bug is no longer a duplicate of bug 151130
panel missing on startup (gutsy beta compiz)
** This bug has been marked a duplicate of bug 147943
[MASTER] broken initial stacking (was: compiz hides
*** This bug is a duplicate of bug 147943 ***
https://bugs.launchpad.net/bugs/147943
** This bug has been marked a duplicate of bug 147943
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
--
panel missing on startup (gutsy beta compiz)
Ok, since the 1368x768 vsize problem seems to be fixed through changing
to new Intel driver in Gutsy this could be closed. There is still the
wrong resolution recognition in Gutsy (1024x768 instead of native)
since the new Intel driver but this is a different issue and reported
through Bug
** Changed in: gdm (Ubuntu)
Sourcepackagename: None = gdm
--
No login screen when using dual screen configuration and themed login screen
https://bugs.launchpad.net/bugs/152581
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gdm in
Even the 1024x768 issue is fixed in Gutsy RC so everything should work
fine.
--
Incorrect resolution even after changing desktop resolution
https://bugs.launchpad.net/bugs/47183
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
** Changed in: gnome-control-center (Ubuntu)
Sourcepackagename: None = gnome-control-center
--
change Desktop-Background should be Appearance
https://bugs.launchpad.net/bugs/152561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
*** This bug is a duplicate of bug 116990 ***
https://bugs.launchpad.net/bugs/116990
** This bug has been marked a duplicate of bug 116990
Rhythmbox sound problems (clicking/snapping/crackling) when not using
crossfading backend
--
intel-HDA cracking sound
@Davi Prieto
This has already been reported under bug #140860.
--
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
https://bugs.launchpad.net/bugs/147943
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact
It is the same I guess, check the screen shots.
--
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
https://bugs.launchpad.net/bugs/147943
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
1 - 100 of 187 matches
Mail list logo
