[Desktop-packages] [Bug 177929] Re: Should autodetect filename character encoding in zip files
*** This bug is a duplicate of bug 580961 *** https://bugs.launchpad.net/bugs/580961 This is what we call Distributed Bureaucracy out of Centralized Anarchy! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/177929 Title: Should autodetect filename character encoding in zip files Status in file-roller package in Ubuntu: Triaged Status in xarchiver package in Ubuntu: Fix Released Bug description: Binary package hint: file-roller Many compressed file such as zip don't specify filename encoding. But file-roller read every file as UTF-8, so it sometimes makes encoding problem. I think may be, you could think that it's not a big problem or it's not a bug or we don't need those feature. If you deal with only English it's not a problem at all. But it's a big problem for East Asian people such as Chinese, Japanese and Korean. Because zip file is still popular. And many people compress zip file in Windows, and share the zip files. Windows don't use UTF-8. Many CJK people want to uncompress these zip files. There are some way to solve this problem (by another software). But all are too complex to Ubuntu newbies. I wish file-roller support encoding select function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/177929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920121] Re: Unable to do anything after pressing the Super key
*** This bug is a duplicate of bug 1871262 *** https://bugs.launchpad.net/bugs/1871262 I comment here because I can reproduce the issue and want to add more specifics. The issue happened since upgrade to 21.04 dev branch with gnome-shell both on Wayland and Xorg. It appears occasionally, not every time though, when Super key was pressed or Mouse was moved onto the hot corner, calling up activity (application) previews. Then suddenly screen doesn't respond to any keyboard or mouse input, with window previews staying there. (In fact mouse movement is visible but clicking to close a window is no longer effective. I can restart the gnome-shell by inputting alt+F2 & r) How to reproduce : 1. Press 'Super', or move mouse to top-left corner. 2. Try typing into the dash box while (or even before) window previews show up. 3. There are chances the screen freezes. Applications cannot be switched or closed, and repressing Super key cannot disappear the previews. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1920121 Title: Unable to do anything after pressing the Super key Status in gnome-shell package in Ubuntu: Confirmed Bug description: I press super key, the various application windows appear on desktop but i'm unable to do anything: i can just click on the red 'X' top right of the window to close it but if i click on the window i can't get focus on it. to exit this situation i can only reboot so I was unable to open the problem while it was active. I can just attach the journal relative to it. The problem seems random, trying to reproduce it I had the problem 3 times out of 6 attempts. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 19 08:49:44 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-28 (18 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228) RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458158] Re: Lock Screen Closes Applications
Same issue appears on Ubuntu 20.10 (only since recent couple of days) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1458158 Title: Lock Screen Closes Applications Status in gnome-screensaver package in Ubuntu: Invalid Bug description: When I use Lock Screen, all applications were closed after the screen was unlocked. Usually when I unlocked the locked screen, all of opened applications were still there. However, recently things didn't work like before and sometimes I have to enter password twice before I can unlock the screen. Ubuntu: 14.04 Desktop Environment: Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1458158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697373] Re: [screensaver] Screen blanks during video playback in Chrome under Xwayland
I confirm that also happens in firefox 57 on Ubuntu 17.10. Firefox: 57.0 Ubuntu: 17.10 Gnome-shell 3.26.2 xwayland:2:1.19.5-0ubuntu2 PS I noticed there is a '-v' option for wayland that runs with "screen- saver without video blanking". Is that helpful? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1697373 Title: [screensaver] Screen blanks during video playback in Chrome under Xwayland Status in chromium-browser package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: gnome-shell / gdm / wayland Test Case: 1. Launch netflix in chrome 2. Play a video 3. Wait until the display times out. Expected result The screen does not dim Actual result The display goes black. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 12 09:21:46 2017 DisplayManager: gdm3 InstallationDate: Installed on 2013-09-03 (1377 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1697373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1044408] Re: gnome-shell-calendar-server crashed with signal 5 in source_registry_object_manager_thread()
It's Nov 2017 and gnome 3.26 now. The bug is reborn. Where did the 'fix' go? Why can't these bugs be quarantined since the fixes were done? The same bugs were fixed once and brought back always on the same project, over and over again. It seems the whole community are trying so hard to maintain all the packages as well as all the bugs, in the same time. When we talk about teamwork today, do we keep in mind teamwork begins from remembering history in a decent way? $sudo apt-get remove evolution-data-server Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: caribou fonts-cantarell gir1.2-accountsservice-1.0 gir1.2-caribou-1.0 gir1.2-clutter-1.0 gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gmenu-3.0 gir1.2-gnomebluetooth-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-1 gir1.2-networkmanager-1.0 gir1.2-nm-1.0 gir1.2-nmgtk-1.0 gir1.2-rsvg-2.0 gir1.2-telepathyglib-0.12 gir1.2-telepathylogger-0.2 gir1.2-upowerglib-1.0 gjs libcaribou-common libcaribou0 libebook-1.2-19 libgdm1 libgjs0g libmozjs-52-0 libtelepathy-logger3 switcheroo-control Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: chrome-gnome-shell evolution-data-server gdm3 gnome-session gnome-session-wayland gnome-shell gnome-shell-extension-top-icons-plus gnome-shell-extensions ubuntu-session 0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded. After this operation, 13.3 MB disk space will be freed. Do you want to continue? [Y/n] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1044408 Title: gnome-shell-calendar-server crashed with signal 5 in source_registry_object_manager_thread() Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Quantal: Won't Fix Status in gnome-shell package in Debian: Fix Released Bug description: [Impact] If a user has uninstalled everything evolution (or added gnome-shell to a minimal command line Ubuntu install), gnome-shell will refuse to start. In .cache/gdm/session.log or .xsession-errors, this is printed: (gnome-shell-calendar-server): ShellCalendarServer-ERROR **: calendar_sources_init: Error calling StartServiceByName for org.gnome.evolution.dataserver.Sources0: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/evolution/evolution-source-registry: Success [Test Case] 1. sudo apt-get uninstall evolution-data-server (unless this will remove gnome-shell) 2. Log out, and try to log into GNOME Shell [Regression Potential] None [Workaround] Make sure evolution-data-server is installed; it is not Evolution and is needed for gnome-shell to start. Original Bug Report === crash occurred upon reboot after I updated the system. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-shell 3.5.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu4 Architecture: i386 Date: Fri Aug 31 09:09:53 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: source_registry_object_manager_thread (data=0x9804090) at e-source-registry.c:734 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 start_thread () from /lib/i386-linux-gnu/libpthread.so.0 clone () from /lib/i386-linux-gnu/libc.so.6 Title: gnome-shell-calendar-server crashed with signal 5 in source_registry_object_manager_thread() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1044408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1075928] Re: Please, silence IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed
I have the same problem ever since upgrading to Ubuntu 12.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1075928 Title: Please, silence IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed Status in “gtk+2.0” package in Ubuntu: New Bug description: On Kubuntu 12.10, whenever a gtk application is opened from the konsole, the terminal gets flooded with Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed which makes the konsole almost impossible to use after a gtk application has been backgrounded. The only way to start gtk apps from the konsole (or a terminal) keeping the konsole usable is to start them redirecting stderr to /dev/null, which should not be the case. This message turns a probably innocuous bug in gtk apps into a severe annoyance also to the konsole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1075928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 366728] Re: LD_LIBRARY_PATH not loading from .profile nor /etc/environment
*** This bug is a duplicate of bug 47958 *** https://bugs.launchpad.net/bugs/47958 Now there is no /etc/gdm/Xsession. So is it not appropriate to adopt the workaround as proposed in #21 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/366728 Title: LD_LIBRARY_PATH not loading from .profile nor /etc/environment Status in “xorg” package in Ubuntu: Confirmed Status in “xorg” package in Debian: Incomplete Bug description: Hi everybody, Today I installed Ubuntu 9.04 (wubi) and I tried to add a LD_LIBRARY_PATH to my .profile file, the command is: export ROOTSYS=/usr/share/QtRoot/root export LD_LIBRARY_PATH=$ROOTSYS/lib:$LD_LIBRARY_PATH Now, when I login, I tape printenv on the bash and the LD_LIBRARY_PATH is not set. This same 2 lines on .profile, have been working perfectly on the last 3 Ubuntu versions. Thank you very much, and please someone fix it quickly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/366728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069847] [NEW] GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
Public bug reported: Since upgrade to Quantal, Ubuntu keeps printing the warning 'GLib- CRITICAL **: g_variant_new_string: assertion `string != NULL' failed' on every opened gtk application. I don't know where it comes from. Someone said it may be related to canberra and/or canberra-pixbuf packages. I'm not sure it's the case. The warning shows over and over again on each gtk-based window action, like open a new window, click on menus or buttons and so on. Application runs with no problem, just the warning is really driving me crazy. I googled a lot and found little information on this issue. I think maybe if I file it there is someone who knows something about it and can help me out. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libcanberra0 0.29-0ubuntu2 Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Mon Oct 22 22:23:37 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: libcanberra UpgradeStatus: Upgraded to quantal on 2012-09-16 (35 days ago) ** Affects: libcanberra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1069847 Title: GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed Status in “libcanberra” package in Ubuntu: New Bug description: Since upgrade to Quantal, Ubuntu keeps printing the warning 'GLib- CRITICAL **: g_variant_new_string: assertion `string != NULL' failed' on every opened gtk application. I don't know where it comes from. Someone said it may be related to canberra and/or canberra-pixbuf packages. I'm not sure it's the case. The warning shows over and over again on each gtk-based window action, like open a new window, click on menus or buttons and so on. Application runs with no problem, just the warning is really driving me crazy. I googled a lot and found little information on this issue. I think maybe if I file it there is someone who knows something about it and can help me out. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libcanberra0 0.29-0ubuntu2 Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Mon Oct 22 22:23:37 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: libcanberra UpgradeStatus: Upgraded to quantal on 2012-09-16 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1069847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060886] Re: lightdm does not pass Xserver DPI setting to gnome-session
** Attachment added: "xorg.conf" https://bugs.launchpad.net/bugs/1060886/+attachment/3367939/+files/xorg.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1060886 Title: lightdm does not pass Xserver DPI setting to gnome-session Status in “lightdm” package in Ubuntu: New Bug description: While most desktop users start gnome-session through lightdm login, lightdm does not pass DISPLAY DPI setting in /etc/X11/xorg.conf to the started gnome-session. I can see relative keywords in /var/log/Xorg.0.log indicating DPI setting is adopted by Xserver, and I see big font size in the unity-greeter interface indicating larger DPI setting in xorg.conf take effects. However inside the desktop, DPI is reset to default (96,96) with no reason. Further I use xrandr to set DPI to a larger value but see no effect. Using xpdyinfo shows DPI is still (96,96). So does gnome just abandoned the display dpi feature in the application level? or is it mandatory to set dpi always to (96,96) by gnome? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu5 Uname: Linux 3.6.0-030600-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Wed Oct 3 17:31:57 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-16 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1060886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060886] [NEW] lightdm does not pass Xserver DPI setting to gnome-session
Public bug reported: While most desktop users start gnome-session through lightdm login, lightdm does not pass DISPLAY DPI setting in /etc/X11/xorg.conf to the started gnome-session. I can see relative keywords in /var/log/Xorg.0.log indicating DPI setting is adopted by Xserver, and I see big font size in the unity-greeter interface indicating larger DPI setting in xorg.conf take effects. However inside the desktop, DPI is reset to default (96,96) with no reason. Further I use xrandr to set DPI to a larger value but see no effect. Using xpdyinfo shows DPI is still (96,96). So does gnome just abandoned the display dpi feature in the application level? or is it mandatory to set dpi always to (96,96) by gnome? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu5 Uname: Linux 3.6.0-030600-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Wed Oct 3 17:31:57 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-16 (16 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dpi quantal running-unity third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1060886 Title: lightdm does not pass Xserver DPI setting to gnome-session Status in “lightdm” package in Ubuntu: New Bug description: While most desktop users start gnome-session through lightdm login, lightdm does not pass DISPLAY DPI setting in /etc/X11/xorg.conf to the started gnome-session. I can see relative keywords in /var/log/Xorg.0.log indicating DPI setting is adopted by Xserver, and I see big font size in the unity-greeter interface indicating larger DPI setting in xorg.conf take effects. However inside the desktop, DPI is reset to default (96,96) with no reason. Further I use xrandr to set DPI to a larger value but see no effect. Using xpdyinfo shows DPI is still (96,96). So does gnome just abandoned the display dpi feature in the application level? or is it mandatory to set dpi always to (96,96) by gnome? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu5 Uname: Linux 3.6.0-030600-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Wed Oct 3 17:31:57 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-16 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1060886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1035261] Re: Port compiz to gsettings and consequently remove unity-2d
It's ridiculous the bug affects me today when updating to compiz 0.9.8.4, regression? again ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1035261 Title: Port compiz to gsettings and consequently remove unity-2d Status in Compiz: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-session” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Fix Released Status in “nux” package in Ubuntu: Fix Released Status in “ubuntu-meta” package in Ubuntu: Fix Released Status in “ubuntu-release-upgrader” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-2d” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Porting compiz and so unity to gsettings has a lot of consequences: - compiz: * remove the conffile for 2nd (autologin) fallback mechanism * build with gsettings support * add migration scripts * add xml files for the g-c-c integration (we used the metacity ones before) - unity : * gconf -> gsettings patches (2) * rebuild with the new gsettings compiz * add transitional packages for all unity-2d packages * add migration scripts - nux: * remove the X11 Xsession.d detection script - gnome-control-center: * should be ported in both the keyboard part by reverting the gsettings revert patch * in the unity background configuration panels to support gsettings * in the display configuration panels to support gsettings - gnome-settings-daemon to drop the gsettings revert patch: - metacity should be updated to >> 2.34.2 (gsettings integration, shared with compiz). Sync back with debian, demote to universe -> this forces us to drop a lot of patches to make unity-2d running - consequently, dropping unity-2d because of metacity patches won't be ported, and unity-2d isn't maintained to port from gconf to gsettings:. Removal from the archive - lightdm to transition people from unity-2d to unity-3d session - unity-greeter to drop hardware detection capability for nux - gnome-session to drop the unity-2d session and recommends - release-upgrader in precise to detect if the card can't run unity-3d, and if so, show a warning to tell to stay on the LTS - ubuntu-desktop seed to remove dep on unity-2d People forcing the upgrade or installing on a machine without hardware acceleration will then use unity with llvmpipe. --- WHAT IS REMAINING: ubuntu-release-upgrade -> we will deal that with mvo later on. all above components that are fix commited (apart unity): - bzr pull the vcs, release and dput it - metacity to sync with debian Unity: Packaging branches lp:~didrocks/unity/gsettings-transition -> continued at lp:~timo-jyrinki/unity/gsettings-transition2 - build with latest compiz, check compiz version for build-dep (already bumped, but check if not shipped in a new tarball) - check that I ship correctly the .convert script and bump if needed the dep from unityc-ommon to compiz-gnome (already bumped, but check if not shipped in a new tarball) Compiz: packaging branches lp:~timo-jyrinki/compiz/ubuntu_quantal_trunk (against trunk) -> pushed to lp:ubuntu/compiz now / lp:~timo-jyrinki/compiz/ubuntu_quantal (merged in all the branches not yet in trunk, and additional changes) - merge all the gsettings branches to lp:compiz MISC: - PPA including all of above: https://launchpad.net/~timo-jyrinki/+archive/prerelease TESTING THE MIGRATION: 1. have the old g-c-c, change unity values in it (launcher size, hide mode…), change keybindings (a lot of them in different categories, launcher, navigation… like changing workspace keys) 2. install new g-c-c (lp:~ubuntu-desktop/gnome-control-center/ubuntu), compiz, unity with all the settings migration 3. logout/login 4. check that the keys are transitionned to the new system: launcher size/hide mode are the changed values and corresponds and the values are shown in the new g-c-c. Same thing with the changed keybidings. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1035261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 959874] Re: gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification()
No, It affects my Acer laptop too. Gnome-settings-daemon crashes when pressing Fn+left/right arrows, which in my case is the XFree86 key to control LCD brightness. However Fn+up/down arrows which is for volume control works normally. I'm working on Ubuntu 12.10, amd64. By the way, why do I see a lot of bugs marked as "Fix Released" which actually are still there ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/959874 Title: gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Precise: Fix Released Bug description: I started seeing this problem after updating today (2012-03-19). g-s-d crashes every time I try to use the hotkeys to adjust the keyboard backlight brightness. I see lines like the following in syslog: Mar 19 20:55:17 ubuntu-mba kernel: [ 250.180733] gnome-settings-[4019]: segfault at f0 ip 7f9dc774235b sp 7fff0cedffe0 error 4 in libmedia-keys.so[7f9dc7735000+25000] Mar 19 20:55:17 ubuntu-mba gnome-session[3722]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly Mar 19 20:55:17 ubuntu-mba gnome-session[3722]: CRITICAL: We failed, but the fail whale is dead. Sorry The machine is a MacBook Air 4,1. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 19 20:50:21 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111208) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f19aa61235b:cmpq $0x0,(%rdi) PC (0x7f19aa61235b) ok source "$0x0" ok destination "(%rdi)" (0x00f0) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/959874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1058451] Re: gnome-power-manager suspends my system when wget is running
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1058451 Title: gnome-power-manager suspends my system when wget is running Status in “gnome-power-manager” package in Ubuntu: New Bug description: Gnome-power-manager is supposed to facilitate better power usage. But it proves it's stupid. It's stupid because it make my system suspended when I was downloading important files using wget. I see very clearly in the preference page of gnome-power-manager that it promises the user it won't suspend the system until there is 'no activity' taking placing for 1 hour in power mode [AC] and for half an hour in power mode [Battery]. And just like many other system tools in gnome, it's lying again. It suspends my system even when wget is running in the gnome-terminal and there is network activities launched by the user himself, without asking. I call this stupid. I call this irresponsible. I call this dishonest. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-power-manager 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Sat Sep 29 11:07:31 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to quantal on 2012-09-16 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1058451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1058451] [NEW] gnome-power-manager suspends my system when wget is running
Public bug reported: Gnome-power-manager is supposed to facilitate better power usage. But it proves it's stupid. It's stupid because it make my system suspended when I was downloading important files using wget. I see very clearly in the preference page of gnome-power-manager that it promises the user it won't suspend the system until there is 'no activity' taking placing for 1 hour in power mode [AC] and for half an hour in power mode [Battery]. And just like many other system tools in gnome, it's lying again. It suspends my system even when wget is running in the gnome- terminal and there is network activities launched by the user himself, without asking. I call this stupid. I call this irresponsible. I call this dishonest. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-power-manager 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Sat Sep 29 11:07:31 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to quantal on 2012-09-16 (12 days ago) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1058451 Title: gnome-power-manager suspends my system when wget is running Status in “gnome-power-manager” package in Ubuntu: New Bug description: Gnome-power-manager is supposed to facilitate better power usage. But it proves it's stupid. It's stupid because it make my system suspended when I was downloading important files using wget. I see very clearly in the preference page of gnome-power-manager that it promises the user it won't suspend the system until there is 'no activity' taking placing for 1 hour in power mode [AC] and for half an hour in power mode [Battery]. And just like many other system tools in gnome, it's lying again. It suspends my system even when wget is running in the gnome-terminal and there is network activities launched by the user himself, without asking. I call this stupid. I call this irresponsible. I call this dishonest. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-power-manager 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Sat Sep 29 11:07:31 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to quantal on 2012-09-16 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1058451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1046699] Re: Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated
Today is 19th Sep., no positive change. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1046699 Title: Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated Status in “glib2.0” package in Ubuntu: New Bug description: The Quantal i386 libglib2.0-0 still produce lot of warnings while upgrading into the upgrading dialog box: Préparation du remplacement de libglib2.0-0:i386 2.33.12-2 (en utilisant .../libglib2.0-0_2.33.12-3_i386.deb) ... Dépaquetage de la mise à jour de libglib2.0-0:i386 ... Traitement des actions différées (« triggers ») pour « man-db »... Paramétrage de libglib2.0-data (2.33.12-3) ... Paramétrage de libglib2.0-0:i386 (2.33.12-3) ... warning: Schema 'com.canonical.notify-osd' has path '/apps/notify-osd/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'com.canonical.Unity.ApplicationsLens' has path '/desktop/unity/lenses/applications/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'com.canonical.Unity.Runner' has path '/desktop/unity/runner/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'com.canonical.Unity.FilesLens' has path '/desktop/unity/lenses/files/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'com.canonical.indicator.session' has path '/apps/indicator-session/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'com.ubuntu.update-manager' has path '/apps/update-manager/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard' has path '/apps/onboard/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.auto-show' has path '/apps/onboard/auto-show/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.keyboard' has path '/apps/onboard/keyboard/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.window' has path '/apps/onboard/window/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.window.landscape' has path '/apps/onboard/window/landscape/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.window.portrait' has path '/apps/onboard/window/portrait/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.icon-palette' has path '/apps/onboard/icon-palette/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.icon-palette.landscape' has path '/apps/onboard/icon-palette/landscape/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.icon-palette.portrait' has path '/apps/onboard/icon-palette/portrait/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.universal-access' has path '/apps/onboard/universal-access/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.theme-settings' has path '/apps/onboard/theme-settings/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.lockdown' has path '/apps/onboard/lockdown/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'apps.onboard.scanner' has path '/apps/onboard/scanner/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'org.freedesktop.Geoclue' has path '/apps/geoclue/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'org.freedesktop.Telepathy.Logger' has path '/apps/telepathy-logger/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'org.freedesktop.gstreamer-0.10.default-elements' has path '/desktop/gstreamer/0.10/default-elements/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'org.gnome.Vino' has path '/desktop/gnome/remote-access/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'org.gnome.crypto.cache' has path '/desktop/gnome/crypto/cache/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'org.gnome.crypto.pgp' has path '/desktop/gnome/crypto/pgp/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'org.gnome.seahorse' has path '/apps/seahorse/'. Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated. warning: Schema 'org.gno
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in isn't supported and may not works as expected
I know what's going on here. It seems fontconfig requires now one rule applies to one pattern. I rewritten the above codes in a 'separted' form, one pattern per font, everything goes fine. Yeah, users should be OK with this, except that it makes linux people more and more stupid. AR PL ZenKai Uni sans-serif AR PL ZenKai Uni MBE sans-serif AR PL UKai CN sans-serif AR PL UKai HK sans-serif AR PL UKai TW sans-serif AR PL UKai TW MBE sans-serif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in isn't supported and may not works as expected Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: New Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: New Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: New Status in “fonts-unfonts-extra” package in Debian: New Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-uming/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in isn't supported and may not works as expected
still no. language-selector 0.87 $~leafpad Fontconfig warning: "/etc/fonts/conf.d/41-arphic-ukai.conf", line 16: Having multiple in isn't supported and may not works as expected Fontconfig warning: "/etc/fonts/conf.d/41-arphic-ukai.conf", line 16: Having multiple in isn't supported and may not works as expected Fontconfig warning: "/etc/fonts/conf.d/41-arphic-ukai.conf", line 16: Having multiple in isn't supported and may not works as expected Fontconfig warning: "/etc/fonts/conf.d/41-arphic-ukai.conf", line 16: Having multiple in isn't supported and may not works as expected Fontconfig warning: "/etc/fonts/conf.d/41-arphic-ukai.conf", line 16: Having multiple in isn't supported and may not works as expected $~ cat /etc/fonts/conf.d/41-arphic-ukai.conf AR PL ZenKai Uni AR PL ZenKai Uni MBE AR PL UKai CN AR PL UKai HK AR PL UKai TW AR PL UKai TW MBE sans-serif so? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in isn't supported and may not works as expected Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: New Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: New Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: New Status in “fonts-unfonts-extra” package in Debian: New Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-uming/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher
one of the most creative thing of linux developers is, they are very good at transforming a bug into a feature. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in D-Bus interfaces for querying and manipulating user account information: Confirmed Status in “accountsservice” package in Ubuntu: Triaged Status in “lightdm” package in Ubuntu: Triaged Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 193325] Re: "unknown media type" during update
Today is 2012.07.20. I'm using Ubuntu 12.04, and I still ran across this bug. One who have used Ubuntu for years would say this is the typical linux story: the same bug appears repeatedly, developers being confident everytime they found a workaround claimed as a fix, and being forgetful everytime they faced a bug report met before. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/193325 Title: "unknown media type" during update Status in Nautilus: Confirmed Status in shared MIME database: Fix Released Status in “shared-mime-info” package in Ubuntu: Fix Released Bug description: Messages below seen during the latest round of updates. The messages from several packages seem to be mixed around, so I'm not sure which one triggered them. I suspect nautilus. Setting up shared-mime-info (0.23-3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ucf (3.004-0ubuntu3) ... Setting up seahorse (2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ubuntu-gdm-themes (0.24) ... Setting up linux-restricted-modules-common (2.6.24.9-8.25) ... Setting up nautilus-data (1:2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up compiz-core (1:0.7.0-0ubuntu3) ... To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/193325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 832235] Re: package gnome-icon-theme 2.31.0-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
same here. Disgusting dpkg dependences, Irresponsible packagers . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/832235 Title: package gnome-icon-theme 2.31.0-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in “gnome-icon-theme” package in Ubuntu: New Bug description: I installed gnome 3 and after uninstalling using ppa purge it resulted in this error ProblemType: Package DistroRelease: Ubuntu 11.04 Package: gnome-icon-theme 2.31.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia AptOrdering: gnome-icon-theme: Configure evolution: Configure evolution-exchange: Configure gnome-control-center: Configure Architecture: amd64 Date: Tue Aug 23 23:32:01 2011 DpkgTerminalLog: Setting up gnome-icon-theme (2.31.0-0ubuntu2) ... update-alternatives: error: alternative path /usr/share/icons/gnome/scalable/places/ubuntu-logo.svg doesn't exist. dpkg: error processing gnome-icon-theme (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: gnome-icon-theme Title: package gnome-icon-theme 2.31.0-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to natty on 2011-08-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/832235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 710171] Re: gnome3-session is not installable as gnome-shell doesn't exist
Nope, the problem is, several months ago the Natty users CAN install gnome-shell from the gnome3 ppa, and in fact many of them did install gnome-shell from the gnome3 ppa, whereas now they CAN NOT. The same gnome3 ppa still exists and one can see all the package lists on their web page, but apt-get fails to get any packages from the ppa with error message : E: Package 'gnome-shell' has no installation candidate. Maybe the funniest thing is, there is no explanation on the gnome3 team ppa web page at all, who just behave as nothing is wrong. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/710171 Title: gnome3-session is not installable as gnome-shell doesn't exist Status in “gnome-session” package in Ubuntu: Fix Released Bug description: Binary package hint: gnome3-session $ sudo apt-get install gnome3-session Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. gnome3-session : Depends: gnome-shell but it is not installable E: Broken packages $ sudo apt-get install gnome-shell Reading package lists... Done Building dependency tree Reading state information... Done Package gnome-shell is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'gnome-shell' has no installation candidate ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome3-session (not installed) ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic i686 Architecture: i386 Date: Sun Jan 30 13:47:39 2011 InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 LC_MESSAGES=en_GB.utf8 SHELL=/bin/bash SourcePackage: gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/710171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
