[Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
There is an easy workaround to this, as mentioned in #17 (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/comments/17) Just downgrade libmutter for the time being. For anyone complaining about how long this takes to resolve: it hasn't even beem three weeks. Ubuntu is an ooen source project that you are using for free. If you think it takes too long, take a look at the source code and fix it yourself. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1600606] Re: Totem is missing the playlist. Please reintroduce it.
When you open multiple files with Totem, they are put in a queue and will play after each other. The previous and Next buttons still work, but there is no way to see the playlist or to edit it. Get rid of the playlist functionality entirely or make the playlist view / sidebar accessible via the menu or preferences. The implementation as it stands now provides is confusing and has unexpected behavior. So, this is a bug, since the user experience is broken and it should be reported upstream as such. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1600606 Title: Totem is missing the playlist. Please reintroduce it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1600606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 692619] Re: ISRC codes containing letters are lost
Although this bug has "expired" in 2011, I'm still experiencing this issue with Ubuntu 14.04, Brasero 3.10.0. ISRC codes are not saved at all. As soon as you close the track information dialog and re-open it, the ISRC code is gone. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/692619 Title: ISRC codes containing letters are lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/692619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 363859] Re: empathy should allow custom group sorting
This is a basic feature and on a 'wishlist' for more than 4 years. What's the point of groups if you can't edit, rename and order them? It should make accessing your contacts more easily, not more cumbersome. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/363859 Title: empathy should allow custom group sorting To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/363859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 751803] Re: GNOME Terminal window initially opens at 80x23
When I pin the terminal application to the launcher, and launch it, it doesn't get an arrow indicating the application is active. When I click the launcher again, it opens a new terminal window instead of showing the current active one, or triggering expose. The only way to get back to the other terminal application is to minimize windows on top, or using Alt-Tab. Does this behaviour corresponds with what you are describing here, Nathan? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/751803 Title: GNOME Terminal window initially opens at 80x23 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 198420] Re: Keyboard layout settings not saved after reboot
I have the same problem here. Whatever keyboard layout / localization I choose, after reboot it's reverted to the defaults. Checking the 'Separate layout for each window' option seems like a reasonable workaround. Thanks Gavin. -- Keyboard layout settings not saved after reboot https://bugs.launchpad.net/bugs/198420 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to meta-gnome2 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
Since I removed the symlink /etc/rc2.d/S98mountnfs, pointing to /etc/init.d/mountnfs.sh. This issue is resolved for me. As I mentioned earlier, I have created that symlink myself. Perhaps you're dealing with a different issue. Please describe what you're experiencing, perhaps in a new bugreport. -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
I have to admit that you could be right Scott. Earlier in this bugreport I mentioned that my nfs filesystem wasn't mounted in the boot process, because my network wasn't fully configured yet at that time in de boot process. Because of that it seems to be a logical decision to make a symlink from /etc/init.d/mountnfs.sh to /etc/rc2.d at the end of the boot process. I guess I might have did just that. The boot process worked perfectly fine until just recently, by the way. I'm sorry to have bothered you with this false bugreport. ** Changed in: gdm (Ubuntu) Status: Confirmed => Rejected -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
Isn't the /etc/init.d/mountnfs script a bit superfluous anyway? Because my nfs filesystem is mounted automatically (by specifying 'auto' in /etc/fstab) Also portmap is also started by the portmap script way before the mountnfs script is started. -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
Or perhaps I shouldn't wait... ;-) I think I'm getting closer to the answer here: I was playing a bit with the startup order of the scripts and I found out: if I remove '/etc/rc2.d/S98mountnfs' everthing works fine. My nfs filesystem is mounted anyway (I gave it the auto option). Also, I think a reinstall would eventually leave me with the same problem, because I will configure my system as it is now... ** Also affects: initscripts (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41871] Re: xmms' volume slider should not mess with PCM but with master
** Changed in: gxine (Ubuntu) Sourcepackagename: gxine => libxine-main1 -- xmms' volume slider should not mess with PCM but with master https://launchpad.net/bugs/41871 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
Hmmm... perhaps I should just wait until my Ubuntu 6.06 LTS cd's arrive from shipit, and do a clean install, like Brendan said. Thanks for all your input anyway! -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41871] Re: xmms' volume slider should not mess with PCM but with master
I created a new user account and foud out that the defaults for some programs are different indeed: XMMS==> Alsa/PCM mixer Mplayer ==> Alsa/PCM mixer GXine==> Alsa/PCM mixer Totem ==> Software mixer Can some package maintainers have a look at this and try to package these multimedia packages so that they all use the same mixer channel, or a software mixer? ** Changed in: xmms (Ubuntu) Severity: Normal => Wishlist Status: Unconfirmed => Confirmed ** Changed in: mplayer (Ubuntu) Severity: Normal => Wishlist Status: Unconfirmed => Confirmed ** Changed in: totem (Ubuntu) Severity: Normal => Wishlist Status: Rejected => Confirmed ** Also affects: gxine (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed ** Changed in: gxine (Ubuntu) Severity: Normal => Wishlist Status: Unconfirmed => Confirmed -- xmms' volume slider should not mess with PCM but with master https://launchpad.net/bugs/41871 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41871] Re: xmms' volume slider should not mess with PCM but with master
** Also affects: mplayer (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- xmms' volume slider should not mess with PCM but with master https://launchpad.net/bugs/41871 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
As I mentioned in the upstream bugreport: I removed gdm from my default startup procedure, and started it by hand. Now everything was fine. This tells me that this issue is not an issue of gdm, but more an issue of how my machine boots up and the state my machine is in at the time gdm is started. Upstream closed the bug with reason 'NOTABUG'. I asked them If they had any idea of what could create this situation. Does anybody out here have an idea about this? -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41871] Re: xmms' volume slider should not mess with PCM but with master
I found out that in MPlayer the mixer can also be configured to use OSS or ALSA, assign a mixer channer or enable a sofware mixer wich doens't affect any channel. Unfortunately I am not in the position to make any choices about what's important in Ubuntu ;-) But you have a point about the usabilty and default configurations of the multimedia packages. It shouldn't be that hard to configure xmms, Totem and MPlayer all to use a software mixer, or perhaps the master channel. Perhaps some people at Ubuntu can shine a light on this? -- xmms' volume slider should not mess with PCM but with master https://launchpad.net/bugs/41871 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
I removed gdm from my default startup procedure, and started it by hand. Now everything was fine. This tells me that this issue is not an issue of gdm, but more an issue of how my machine boots up and the state my machine is in at the time gdm is started. What do you think Sebastien? -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41871] Re: xmms' volume slider should not mess with PCM but with master
Does above information resolve your issue, or am I interpreting your information badly? -- xmms' volume slider should not mess with PCM but with master https://launchpad.net/bugs/41871 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
Thank you for your efforts. I made a report for this on bugzilla.gnome.org: http://bugzilla.gnome.org/show_bug.cgi?id=343091 If anything usefull comes out, I will update this report. -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
The strangest thing about this is still that if I restart gdm manually everything works fine. Anyone knows where this 'socket' is located? -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
The original translation is: "Could not access GDM configuration file." -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
I found out that the lines in syslog are most likely to be produced by gdmsetup: [terminal output] [EMAIL PROTECTED]:~# gdmsetup Failed to connect to socket, sleep 1 second and retry Trying failed command again. Try 2 of 5. Failed to connect to socket, sleep 1 second and retry Trying failed command again. Try 3 of 5. Failed to connect to socket, sleep 1 second and retry Trying failed command again. Try 4 of 5. Failed to connect to socket, sleep 1 second and retry Trying failed command again. Try 5 of 5. Command failed 5 times, aborting. Kon het configuratiebestand van GDM niet benaderen. [EMAIL PROTECTED]:~# [/terminal output] The last line is dutch and means as much as: Could not approach (find?) the GDM configuration file. Still all permissions are setup right. I even tried to give the gdm group write access to the configuration files, but that also didn't work. -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
Yes I have a /etc/gdm/gdm.conf configuration file with the following permissions: -rw-r--r-- 1 root root This is the default, because of my reinstall of gdm (see above) all configuration files were deleted and the default files from the package were installed again. I use NIS and NSF as a client. Those work fine now. I also installed courier-imap and postfix to migrate some mail, but those are uninstalled now. As I mentioned before, I installed my system using a Kubuntu CD. So I have also kdm installed. Somthing I noticed was the different starting order of gdm and kdm: /etc/rc2.d/S13gdm /etc/rc2.d/S99kdm When I rename S13gdm to S99gdm, I never see the default Ubuntu theme, but the circles theme is loaded. It works now, but whithin gnome, I cannot restart/shutdown my machine. To do that, I must logout first. -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
Sorry for the double post: I refreshed my browser window... -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
Yes I have a /etc/gdm/gdm.conf configuration file with the following permissions: -rw-r--r-- 1 root root This is the default, because of my reinstall of gdm (see above) all configuration files were deleted and the default files from the package were installed again. I use NIS and NSF as a client. Those work fine now. I also installed courier-imap and postfix to migrate some mail, but those are uninstalled now. As I mentioned before, I installed my system using a Kubuntu CD. So I have also kdm installed. Somthing I noticed was the different starting order of gdm and kdm: /etc/rc2.d/S13gdm /etc/rc2.d/S99kdm When I rename S13gdm to S99gdm, I never see the default Ubuntu theme, but the circles theme is loaded. It works now, but whithin gnome, I cannot restart/shutdown my machine. To do that, I must logout first. -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
It's not thta long ago that I reinstalled my entire system. I installed from the Kubuntu Flight 4 CD, and dist-upgraded from there. I tried to reinstall gdm (apt-get --purge remove gdm; apt-get install gdm), but that doensn't help. Seems like this is not in gdm at all, but perhaps gdm is started to soon in the startup process. If I login to tty1 and restart gdm from there, everithing works fine. I had a similar problem before, when my NFS filesystems could not be mounted and my NIS client couldn't connect to the server, because the startup scripts were started before I got an IP address from de DHCP server. -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] Re: First attempt to login on gdm fails
H... I guess you can ignore my lines from Xorg.0.log. This logfile is from 18:45, while my syslog lines are from 19:47. The last time I was using Xgl which writes it's logs to /var/log/Xorg.93.log BWT: The lines in syslog appear during my login attempt. This issue occures while using Xgl and normal Xorg. I have tested this with various user accounts. -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46193] First attempt to login on gdm fails
Public bug reported: Binary package hint: gdm I'm currently using Ubuntu 6.06 LTS, but this issue also occurred before the last 2 major updates. My gdm version is currently: gdm-2.14.6-0ubuntu1 Every time, after (re)booting my machine, the first attempt to login on gdm fails. I can see the brown background and the (busy)mouse cursor. After a minute or less, gdm will restart, and it shows up again with the 'circels' theme. Now I am able to login, but I am only able to restart/shutdown my machine through gdm (so I have to log out first). In my /var/log/Xorg.0.log i find these lines: - AUDIT: Tue May 23 18:45:16 2006: 4604 X: client 1 rejected from local host AUDIT: Tue May 23 18:45:16 2006: 4604 X: client 2 rejected from local host AUDIT: Tue May 23 18:55:40 2006: 4604 X: client 4 rejected from local host AUDIT: Tue May 23 18:55:42 2006: 4604 X: client 1 rejected from local host AUDIT: Tue May 23 18:55:42 2006: 4604 X: client 2 rejected from local host I will also attach a snippet of my /var/log/syslog wich contains some usefull info! ** Affects: gdm (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed ** Attachment added: "/var/log/syslog" http://librarian.launchpad.net/2837964/syslog -- First attempt to login on gdm fails https://launchpad.net/bugs/46193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41871] Re: xmms' volume slider should not mess with PCM but with master
Indeed, the Totem volume control doesn't affect the master volume, or any other hardware mixer: Totem uses a software mixer. The slider from the gnome mixer applet only affects the master volume. XMMS by default (in Ubuntu) defaults to the hardware PCM mixer. I don' t know about mplayer... If you open XMMS and decrease the volume, the PCM mixer is decreased. The software mixer from Totem, nor the master volume is affected by this. You can however increase the volume without opening XMMS, by opening the gnome-mixer window and increase the PCM slider. -- xmms' volume slider should not mess with PCM but with master https://launchpad.net/bugs/41871 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41871] Re: xmms' volume slider should not mess with PCM but with master
This is not a bug, it's just a setting: If you open the option dialog in xmms you can configure your Audio I/O plugin: 1) ALSA: you can choose to use a software mixer, or a hardware mixer. If you go for the hardware mixer you can select any mixer device (Master, PCM, Line, Synth, etc.) from your soundcard. 2) OSS: here you can only choose a (hardware) audiocard and mixer device. In the mixer tab, you can (un)check the option that causes XMMS to "use master, not PCM" -- xmms' volume slider should not mess with PCM but with master https://launchpad.net/bugs/41871 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39655] The gimp crashes after closing 'Colourmap' dialog.
Public bug reported: Affects: gimp (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Open the 'Colourmap' dialog through the menu in the image window: --> Dialogues --> Colourmap The Gimp continues to work fine. You can edit the colourmap, open, close and save images, apply filters, etc. But as soon as you close the Colourmap dialog the Gimp crashes. This occurs with a fresh install with Kubuntu 6.06 (Dapper Drake) Flight CD 6, with a clean homedir. It still happens after applying all updates. Some terminal output:-- [EMAIL PROTECTED]:~$ gimp --verbose -c --debug-handlers --stack-trace-mode always INIT: gimp_load_config Parsing '/etc/gimp/2.0/gimprc' Parsing '/home/lazy-r/.gimp-2.2/gimprc' gimp_composite: use=yes, verbose=no Processor instruction sets: +mmx +sse -sse2 -3dnow -altivec -vis Adding theme 'Default' (/usr/share/gimp/2.0/themes/Default) Adding theme 'Small' (/usr/share/gimp/2.0/themes/Small) Writing '/home/lazy-r/.gimp-2.2/themerc' INIT: gimp_initialize INIT: gimp_real_initialize INIT: gui_initialize_after_callback INIT: gimp_restore INIT: gui_restore_callback GimpClipboard: writable pixbuf format: image/png GimpClipboard: writable pixbuf format: image/x-icon GimpClipboard: writable pixbuf format: image/bmp GimpClipboard: writable pixbuf format: image/x-bmp GimpClipboard: writable pixbuf format: image/x-MS-bmp GimpClipboard: writable pixbuf format: image/jpeg INIT: gimp_real_restore Starting extension: 'extension_script_fu' INIT: gui_restore_after_callback loading menu '/usr/share/gimp/2.0/menus/toolbox-menu.xml' for /toolbox-menubar loading menu '/usr/share/gimp/2.0/menus/image-menu.xml' for /dummy-menubar loading menu '/usr/share/gimp/2.0/menus/image-menu.xml' for /image-menubar *** glibc detected *** corrupted double-linked list: 0xb771b358 *** gimp: terminated: Aborted ---end - When I kill gimp: - (script-fu:5456): LibGimpBase-WARNING **: script-fu: wire_read(): error Killed ---end -- The gimp crashes after closing 'Colourmap' dialog. https://launchpad.net/malone/bugs/39655 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
