[Desktop-packages] [Bug 1259083] Re: GTK window layout problems with python
** Package changed: python3-defaults (Ubuntu) = pygobject (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1259083 Title: GTK window layout problems with python Status in “pygobject” package in Ubuntu: New Bug description: In some applications like for example software updates and winetricks having a list view, the list view does not fill the window vertically (please see the attached image). I don't know if that is a problem of python3 or gtk bindigs btu I noticed that the problem is shown by all phyton3 based applications. Also resizing of the window is not possible. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: python3 3.3.2-14ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Dec 9 10:01:48 2013 InstallationDate: Installed on 2013-11-08 (30 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1259083/+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 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
I have now applied a patch from Ted to start indicators via upstart user session in ubiquity and it fails the installer in a similar fashion. This clearly shows that indicators under upstart user session tasks are not ready yet, nor were tested under lightdm ubiquity. ** Changed in: lightdm (Ubuntu) Importance: Undecided = Critical -- 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/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+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 1184878] Re: when upstart init the session jobs, it should be robust against environment changes (fallback?)
This is not a problem with upstart packaging. /sbin is on the default path in ubuntu, and hence init binary is shipped there and is a reasonable location for the executable, same as e.g. ifconfig. Adding extra symlinks, is not, since quite a lot of things will not work. Other binaries that are used by user session upstart jobs are also /sbin/start /sbin/stop /sbin/reload /sbin/restart /sbin/initctl /sbin/initctl. If one doesn't want an upstart managed user-session, one should comment it out from /etc/upstart-xsessions, similarly lightdm/ubuntu-greeter should manage to start such sessions without init user-session. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Status: New = Confirmed ** Changed in: upstart (Ubuntu) Status: Confirmed = Invalid -- 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/1184878 Title: when upstart init the session jobs, it should be robust against environment changes (fallback?) Status in “lightdm” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Invalid Bug description: A file that is commonly modified is /etc/environment. If you remove the PATH line in this file, you can start a session upstart-less quite easily, and things will still work. PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games However, if upstart manage your session, you can't log in (you will be rejected and going back to the greeter quickly). I thnk we should be more fortified against this pebkac issue, especially has we have no really good log for it to know what happened (nothing in lightdm or upstart logs rather than exiting the session and gnome-session logs were not there as it's not executed). What happens is: /usr/sbin/lightdm-session: 5: exec: init: not found in .xsession-errors. indeed, which init doesn't return anything as /sbin isn't in path. We should maybe hardcode /sbin/init in this script? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: upstart 1.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue May 28 09:51:48 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-28 (364 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionVersion: init (upstart 1.8) UpstartRunningSystemVersion: init (upstart 1.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1184878/+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 1184878] Re: when upstart init the session jobs, it should be robust against environment changes (fallback?)
actually, if init is not on the path we could either add /sbin to path in Xsession.d scripts, or fallback in Xsession.d to non-upstart managed user-session. Even better we could simply merge sbin - bin, as well as complete the /usr merge. =) -- 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/1184878 Title: when upstart init the session jobs, it should be robust against environment changes (fallback?) Status in “lightdm” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Invalid Bug description: A file that is commonly modified is /etc/environment. If you remove the PATH line in this file, you can start a session upstart-less quite easily, and things will still work. PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games However, if upstart manage your session, you can't log in (you will be rejected and going back to the greeter quickly). I thnk we should be more fortified against this pebkac issue, especially has we have no really good log for it to know what happened (nothing in lightdm or upstart logs rather than exiting the session and gnome-session logs were not there as it's not executed). What happens is: /usr/sbin/lightdm-session: 5: exec: init: not found in .xsession-errors. indeed, which init doesn't return anything as /sbin isn't in path. We should maybe hardcode /sbin/init in this script? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: upstart 1.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue May 28 09:51:48 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-28 (364 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionVersion: init (upstart 1.8) UpstartRunningSystemVersion: init (upstart 1.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1184878/+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 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
/sbin must be in all users path on Ubuntu. It is the default, and many thing will not work, if /sbin is not the default path. Default path on ubuntu is usually set in /etc/environment and has: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games Can you please verify what PATH is set on the affected environments? -- 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/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+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 1185565] Re: Indicators should have Upstart jobs
I agree with larsu on this one. Can we revert this? Or instead e.g. fix it properly - rebase upstart-dbus activation patches and still use dbus activation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in “indicator-application” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+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 1185565] Re: Indicators should have Upstart jobs
given how similar all the indicators are, i'm not sure why there is a unique job for each one: instance $INDICATOR export INDICATOR start on indicators-loaded or indicator-services-start stop on desktop-end or indicator-services-end respawn exec /usr/lib/x86_64-linux-gnu/indicator-$INDICATOR/indicator-$INDICATOR-service and then something else, e.g. can decide which indicators are wanted and simply do: start indicator INDICATOR=sound Such that to avoid boilerplate indicator-*.conf jobs. Each instance can individually be stopped, startered, restarted and gets it's own log file Similarly there is upstart-dbus-bridge, such that instead the indicators can do start on dbus INTERFACE=com.ubuntu.foo, so I don't think removing dbus activation gains us anything, so far it only broke showing indicators in the ubiquity-dm and non-upstart mananged user-sessions where indicators can be used. At the moment, all user sessions on the desktop can be fully started without being managed by upstart and users can disable that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in “indicator-application” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+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 967229] Re: Text mode shown briefly with various cryptic texts when logging out or shutting down
Fedora reference: https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=9d1c6c1e3bf176d3f89de4ec5551f9960c4986ed -- 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/967229 Title: Text mode shown briefly with various cryptic texts when logging out or shutting down Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Triaged Status in “lightdm” package in Ubuntu: Fix Released Status in “plymouth” package in Ubuntu: Triaged Bug description: Text mode hits in for about a half a second every time one logs out or shuts down the computer. UPDATE: log out part fixed in lightdm in Ubuntu 13.04 -, shut down problem still there. The attached video Text-mode in logout and shutdown.webm is a combination of two clips showing this on one of my computers. This one has slightly more text output than my other machines, but on every machine it catches attention by being ugly and I'd guess cryptic or suspicious for ordinary people in the otherwise smooth experience starting from the bootup ubuntu logo. Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook, Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop machine. The video is from the sandy bridge one. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Mar 28 18:25:44 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120316) MachineType: ASUSTeK Computer Inc. UX31E ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/967229/+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 967229] Re: Text mode shown briefly with various cryptic texts when logging out or shutting down
Ordering of the splash ahead of emitting rc runlevel level has been done before in Fedora, to properly show shutdown splash to avoid scary messages. I have also noticed that there are additional messages generated on the VT through the lifecycle of the machine - that is after lightdm cleared it and shutdown initiated. Therefore I add clearing VT messages before lightdm shutdowns. Instead of introducing a dummy intermediate job to negotiate whether or not there is a DM to stop, I use the wait-for-state facility and therefore make the following dependency chain: starting rc RUNLEVEL=[016] - waits to start shutdown-plymouth (if any) - (stopping plymouth) - waits to stop lightdm (if any) This also splits plymouth into two jobs, instead of having duplicate / ORed start on, exec post-start scripts. Semantically it also makes sense, it's two different instances. This also makes desktop-shutdown event redundant. To try this out: cd /etc/init; sudo patch -p0 path/to/patch I have tested it on trusty and have a message-less shutdown. The patch can equally be applied on precise, please test it on the affected precise machines / OEM devices. ** Patch added: message-less-shutdown.patch https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/967229/+attachment/3924322/+files/message-less-shutdown.patch -- 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/967229 Title: Text mode shown briefly with various cryptic texts when logging out or shutting down Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Triaged Status in “lightdm” package in Ubuntu: Fix Released Status in “plymouth” package in Ubuntu: Triaged Bug description: Text mode hits in for about a half a second every time one logs out or shuts down the computer. UPDATE: log out part fixed in lightdm in Ubuntu 13.04 -, shut down problem still there. The attached video Text-mode in logout and shutdown.webm is a combination of two clips showing this on one of my computers. This one has slightly more text output than my other machines, but on every machine it catches attention by being ugly and I'd guess cryptic or suspicious for ordinary people in the otherwise smooth experience starting from the bootup ubuntu logo. Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook, Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop machine. The video is from the sandy bridge one. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Mar 28 18:25:44 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120316) MachineType: ASUSTeK Computer Inc. UX31E ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
[Desktop-packages] [Bug 1250039] Re: dual-screen monitor setup regressed
It looks racy - it does come up properly, but very rarely. If it does come up in dual-screen mode, $ service lightdm restart, causes it to loose of the screens (turn black). Upon login, the other display shows lightdm background with (13.10) instantly which is later replaced by my user background. Btw, I thought login screen is suppose to use my login background? or the converged setting not available yet? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1250039 Title: dual-screen monitor setup regressed Status in “lightdm” package in Ubuntu: New Status in “unity-greeter” package in Ubuntu: New Bug description: For a few weeks in trusty I had following with my dual screen setup: one screen with mouse pointer had normal login screen the other screen, with background picture + ubuntu logo overlay And if i move mouse pointer across they change - the other one becomes active/background-only. This awesome behaviour has regressed, I know get: one screen always with normal login screen the other one stays always black, but does display white mouse pointer if i move to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250039/+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 1257760] Re: Lightdm doesn't launch Plasma on Kubuntu Trusty anymore
** Changed in: kde-workspace (Ubuntu) Assignee: (unassigned) = Kubuntu Developers (kubuntu-dev) -- 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/1257760 Title: Lightdm doesn't launch Plasma on Kubuntu Trusty anymore Status in “kde-workspace” package in Ubuntu: Triaged Status in “lightdm” package in Ubuntu: Invalid Status in “lightdm-kde” package in Ubuntu: Triaged Bug description: When trying to start the KDE Desktop using lightdm on a Live Kubuntu CD, lightdm fails to start the session. [Steps to reproduce] * Download the latest Kubuntu Trusty ISO * Click on Try Kubuntu * Plasma fails to come up Lightdm Log : [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.9.4, UID=0 PID=5237 [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Registered seat module xlocal [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Registered seat module surfaceflinger [+0.00s] DEBUG: Adding default seat [+0.00s] DEBUG: Seat: Starting [+0.00s] DEBUG: Seat: Creating user session [+0.09s] DEBUG: Seat: Failed to find session configuration ubuntu [+0.09s] DEBUG: Seat: Can't find session 'ubuntu' [+0.09s] DEBUG: Seat: Creating greeter session [+0.09s] DEBUG: Seat: Failed to find session configuration default [+0.09s] DEBUG: Seat: Failed to create greeter session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1257760/+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 1232454] Re: Computer will suspend very soon because of inactivity. dialog when resuming from suspend
On ubuntu, ok cancel are useless, instead actions should be dropped, and at most a bubble (notify-osd) be shown. -- 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/1232454 Title: Computer will suspend very soon because of inactivity. dialog when resuming from suspend Status in Gnome Settings Daemon: Unknown Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10 today, every time I unlock my computer after leaving it for a long time I get this prompt: -- Power Automatic suspend Computer will suspend very soon because of inactivity. -- However, the computer doesn't actually suspend. And even if I do this manually (which works) and then resume, the prompt is still there (and in that case, not true at all). This is ugly and seems broken! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-desktop 1.304 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sat Sep 28 15:32:42 2013 InstallationDate: Installed on 2012-08-03 (420 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1232454/+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 1072518] Re: Restarting network crashes (apparently) the desktop manager
** Description changed: - The unity UI and windows decorations dissappear when I do one of the - following: + === WARNING === + + Doing: sudo restart networking or sudo /etc/init.d/networking restart. - This renders me unable to focus any of the open windows with - mouse/keyboard, leaving the system unusable. I have to drop to terminal - (CTRL-ALT-F2) and do a sudo reboot. + WILL TEAR DOWN MOST OF YOUR DESKTOP = - I am not sure what parts of the desktop are going down, so I posted this - bug under ubuntu-desktop. I'd be happy to follow up with more - information as needed. + Networking is a generic job which brings up all networking interfaces in + the right order at boot. - ProblemType: Bug - DistroRelease: Ubuntu 12.10 - Package: ubuntu-desktop 1.287 - ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 - Uname: Linux 3.5.0-17-generic x86_64 - ApportVersion: 2.6.1-0ubuntu6 - Architecture: amd64 - Date: Mon Oct 29 09:45:12 2012 - EcryptfsInUse: Yes - InstallationDate: Installed on 2012-10-20 (8 days ago) - InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) - MarkForUpload: True - ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: ubuntu-meta - UpgradeStatus: No upgrade log present (probably fresh install) + It should never be stopped nor restarted. + + It is only stop at shutdown to correctly bring down all the networking + interfaces in the right order again. + + === DO NOT RESTART NETWORKING === + + + If you want to reconfigure all networking interface you can use something like: + + ifdown eth0 + ifup eth0 -- 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/1072518 Title: Restarting network crashes (apparently) the desktop manager Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: === WARNING === Doing: sudo restart networking or sudo /etc/init.d/networking restart. WILL TEAR DOWN MOST OF YOUR DESKTOP = Networking is a generic job which brings up all networking interfaces in the right order at boot. It should never be stopped nor restarted. It is only stop at shutdown to correctly bring down all the networking interfaces in the right order again. === DO NOT RESTART NETWORKING === If you want to reconfigure all networking interface you can use something like: ifdown eth0 ifup eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1072518/+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 1072518] Re: Restarting network crashes (apparently) the desktop manager
** Description changed: === WARNING === Doing: sudo restart networking or sudo /etc/init.d/networking restart. WILL TEAR DOWN MOST OF YOUR DESKTOP = Networking is a generic job which brings up all networking interfaces in the right order at boot. It should never be stopped nor restarted. It is only stop at shutdown to correctly bring down all the networking interfaces in the right order again. === DO NOT RESTART NETWORKING === + If you want to reconfigure all networking interface you can use + something like: - If you want to reconfigure all networking interface you can use something like: + ifdown eth0 + ifup eth0 - ifdown eth0 - ifup eth0 + Or all interfaces with: + + ifdown -a --exclude=lo ifup -a --exclude=lo -- 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/1072518 Title: Restarting network crashes (apparently) the desktop manager Status in Ubuntu: Incomplete Bug description: === WARNING === Doing: sudo restart networking or sudo /etc/init.d/networking restart. WILL TEAR DOWN MOST OF YOUR DESKTOP = Networking is a generic job which brings up all networking interfaces in the right order at boot. It should never be stopped nor restarted. It is only stop at shutdown to correctly bring down all the networking interfaces in the right order again. === DO NOT RESTART NETWORKING === If you want to reconfigure all networking interface you can use something like: ifdown eth0 ifup eth0 Or all interfaces with: ifdown -a --exclude=lo ifup -a --exclude=lo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1072518/+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 1250039] [NEW] dual-screen monitor setup regressed
Public bug reported: For a few weeks in trusty I had following with my dual screen setup: one screen with mouse pointer had normal login screen the other screen, with background picture + ubuntu logo overlay And if i move mouse pointer across they change - the other one becomes active/background-only. This awesome behaviour has regressed, I know get: one screen always with normal login screen the other one stays always black, but does display white mouse pointer if i move to it ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1250039 Title: dual-screen monitor setup regressed Status in “lightdm” package in Ubuntu: New Status in “unity-greeter” package in Ubuntu: New Bug description: For a few weeks in trusty I had following with my dual screen setup: one screen with mouse pointer had normal login screen the other screen, with background picture + ubuntu logo overlay And if i move mouse pointer across they change - the other one becomes active/background-only. This awesome behaviour has regressed, I know get: one screen always with normal login screen the other one stays always black, but does display white mouse pointer if i move to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250039/+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
Re: [Desktop-packages] [Bug 1250039] Re: dual-screen monitor setup regressed
On 11 November 2013 11:07, Sebastien Bacher seb...@ubuntu.com wrote: Thank you for your bug report. When did that issue start? What package did you upgrade before getting it? I'll have a look, but it's hard to tell as I reboot my machine to see the login screen infrequently. Regards, Dmitrijs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1250039 Title: dual-screen monitor setup regressed Status in “lightdm” package in Ubuntu: New Status in “unity-greeter” package in Ubuntu: New Bug description: For a few weeks in trusty I had following with my dual screen setup: one screen with mouse pointer had normal login screen the other screen, with background picture + ubuntu logo overlay And if i move mouse pointer across they change - the other one becomes active/background-only. This awesome behaviour has regressed, I know get: one screen always with normal login screen the other one stays always black, but does display white mouse pointer if i move to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250039/+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 1250039] Re: dual-screen monitor setup regressed
Hm downgrading lightdm didn't fix things. Also I'm using custom wallpaper yet unity-greeter is showing default / stock one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1250039 Title: dual-screen monitor setup regressed Status in “lightdm” package in Ubuntu: New Status in “unity-greeter” package in Ubuntu: New Bug description: For a few weeks in trusty I had following with my dual screen setup: one screen with mouse pointer had normal login screen the other screen, with background picture + ubuntu logo overlay And if i move mouse pointer across they change - the other one becomes active/background-only. This awesome behaviour has regressed, I know get: one screen always with normal login screen the other one stays always black, but does display white mouse pointer if i move to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250039/+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 1243235] Re: Please demote libav to universe
** Changed in: alsa-plugins-extra (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1243235 Title: Please demote libav to universe Status in “alsa-plugins” package in Ubuntu: Fix Released Status in “alsa-plugins-extra” package in Ubuntu: Fix Released Status in “libav” package in Ubuntu: Fix Released Status in “strigi” package in Ubuntu: Fix Released Bug description: Ready to be demoted: Source and binary movements to universe --- o libav: ffmpeg ffmpeg-doc libav-doc libav-tools libavcodec-dev libavcodec53 libavdevice-dev libavdevice53 libavfilter-dev libavfilter2 libavformat-dev libavformat53 libavutil-dev libavutil51 libpostproc-dev libpostproc52 libswscale-dev libswscale2 libav demotion: I would like libav to be demoted to universe in Trusty. It is a package that takes considerable resources to maintain security updates for, resulting in it being vulnerable in Debian and Ubuntu. Not only does anything in main currently depend on it, but having it in main results in split packaging (libav and libav-extras) which puts an extra burden on maintenance. It is currently being seeded in supported-desktop-extra. $ reverse-depends -c main src:libav No reverse dependencies found $ reverse-depends -b -c main src:libav Reverse-Build-Depends = * alsa-plugins (for libavcodec-dev) * alsa-plugins (for libavutil-dev) * strigi(for libpostproc-dev) * strigi(for libswscale-dev) strigi: --- I don't believe strigi actually needs libpostproc-dev and libswscale-dev. Here is the current build log with them: -- checking for module 'libavcodec' -- package 'libavcodec' not found -- checking for module 'libavformat' -- package 'libavformat' not found -- checking for module 'libavdevice' -- package 'libavdevice' not found -- checking for module 'libavutil' -- found libavutil, version 51.22.1 -- checking for module 'libswscale' -- found libswscale, version 2.1.0 -- checking for module 'libpostproc' -- found libpostproc, version 52.0.0 -- Could NOT find FFmpeg (missing: AVCODEC_LIBRARIES AVCODEC_INCLUDE_DIRS AVFORMAT_LIBRARIES AVFORMAT_INCLUDE_DIRS) ** FFmpeg not found. Support for indexing FFMPEG is disabled Here is the build log after they have been removed: -- checking for module 'libavcodec' -- package 'libavcodec' not found -- checking for module 'libavformat' -- package 'libavformat' not found -- checking for module 'libavdevice' -- package 'libavdevice' not found -- checking for module 'libavutil' -- package 'libavutil' not found -- checking for module 'libswscale' -- package 'libswscale' not found -- checking for module 'libpostproc' -- package 'libpostproc' not found -- Could NOT find FFmpeg (missing: FFMPEG_LIBRARIES FFMPEG_INCLUDE_DIRS AVCODEC_LIBRARIES AVCODEC_INCLUDE_DIRS AVFORMAT_LIBRARIES AVFORMAT_INCLUDE_DIRS AVUTIL_LIBRARIES AVUTIL_INCLUDE_DIRS SWSCALE_LIBRARIES SWSCALE_INCLUDE_DIRS) ** FFmpeg not found. Support for indexing FFMPEG is disabled alsa-plugins: - alsa-plugins needs libavcodec-dev and libavutil-dev for the libasound2-plugins-extra package in universe. We have three options: 1- Stop building libasound2-plugins-extra $ reverse-depends -s libasound2-plugins-extra No reverse dependencies found 2- Leave libavcodec-dev and libavutil-dev in main (not ideal) 3- Add an alsa-plugins-extras source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1243235/+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 1241539] Re: ubiquity-dm is missing keyboard, input, sound, system indicators
** Changed in: ubiquity (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1241539 Title: ubiquity-dm is missing keyboard, input, sound, system indicators Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-keyboard” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Fix Released Bug description: [Impact] Impacts any installs via ubiquity, but only the installation setup, not the desktop or live session. [Test case] Run an install with the new indicator packages available to the installer. This may require building a new ISO with the right packages pre-loaded. [Regression potential] Medium; adds a new ubiquity profile to be used in the installer. This would mean the indicators will be visible from the installer, but does not risk causing regressions on the desktop. ubiquity-dm is missing keyboard, input, sound, system indicators those need ubiquity profile defined. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1241539/+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 1223688] Re: Sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main)
** Changed in: texlive-lang (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-lang in Ubuntu. https://bugs.launchpad.net/bugs/1223688 Title: Sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main) Status in “texlive-lang” package in Ubuntu: Fix Released Bug description: Please sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main) Changelog entries since current saucy version 2013.20130722-1: texlive-lang (2013.20130905-1) unstable; urgency=low * new upstream checkout * provide a bunch of transitional packages to easy update from stable (Closes: #721838) * bump standards version to 3.9.4, no changes necessary -- Norbert Preining prein...@debian.org Thu, 05 Sep 2013 11:47:05 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1223688/+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 1243235] Re: Please demote libav to universe
** Also affects: strigi (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1243235 Title: Please demote libav to universe Status in “alsa-plugins” package in Ubuntu: New Status in “libav” package in Ubuntu: New Status in “strigi” package in Ubuntu: New Bug description: libav demotion: I would like libav to be demoted to universe in Trusty. It is a package that takes considerable resources to maintain security updates for, resulting in it being vulnerable in Debian and Ubuntu. Not only does anything in main currently depend on it, but having it in main results in split packaging (libav and libav-extras) which puts an extra burden on maintenance. It is currently being seeded in supported-desktop-extra. $ reverse-depends -c main src:libav No reverse dependencies found $ reverse-depends -b -c main src:libav Reverse-Build-Depends = * alsa-plugins (for libavcodec-dev) * alsa-plugins (for libavutil-dev) * strigi(for libpostproc-dev) * strigi(for libswscale-dev) strigi: --- I don't believe strigi actually needs libpostproc-dev and libswscale-dev. Here is the current build log with them: -- checking for module 'libavcodec' -- package 'libavcodec' not found -- checking for module 'libavformat' -- package 'libavformat' not found -- checking for module 'libavdevice' -- package 'libavdevice' not found -- checking for module 'libavutil' -- found libavutil, version 51.22.1 -- checking for module 'libswscale' -- found libswscale, version 2.1.0 -- checking for module 'libpostproc' -- found libpostproc, version 52.0.0 -- Could NOT find FFmpeg (missing: AVCODEC_LIBRARIES AVCODEC_INCLUDE_DIRS AVFORMAT_LIBRARIES AVFORMAT_INCLUDE_DIRS) ** FFmpeg not found. Support for indexing FFMPEG is disabled Here is the build log after they have been removed: -- checking for module 'libavcodec' -- package 'libavcodec' not found -- checking for module 'libavformat' -- package 'libavformat' not found -- checking for module 'libavdevice' -- package 'libavdevice' not found -- checking for module 'libavutil' -- package 'libavutil' not found -- checking for module 'libswscale' -- package 'libswscale' not found -- checking for module 'libpostproc' -- package 'libpostproc' not found -- Could NOT find FFmpeg (missing: FFMPEG_LIBRARIES FFMPEG_INCLUDE_DIRS AVCODEC_LIBRARIES AVCODEC_INCLUDE_DIRS AVFORMAT_LIBRARIES AVFORMAT_INCLUDE_DIRS AVUTIL_LIBRARIES AVUTIL_INCLUDE_DIRS SWSCALE_LIBRARIES SWSCALE_INCLUDE_DIRS) ** FFmpeg not found. Support for indexing FFMPEG is disabled alsa-plugins: - alsa-plugins needs libavcodec-dev and libavutil-dev for the libasound2-plugins-extra package in universe. We have three options: 1- Stop building libasound2-plugins-extra $ reverse-depends -s libasound2-plugins-extra No reverse dependencies found 2- Leave libavcodec-dev and libavutil-dev in main (not ideal) 3- Add an alsa-plugins-extras source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1243235/+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 1230252] Re: libxdamage-dev should be Multi-Arch:same
Thanks. I think I uploaded it into saucy anyway, sorry about that. I guess it will be able to get back in sync. libxdamage (1:1.1.4-1ubuntu1) saucy; urgency=low * Mark libxdamage-dev as Multi-Arch: same. -- Dmitrijs Ledkovs dmitrij.led...@ubuntu.com Fri, 11 Oct 2013 17:47:45 +0100 ** Changed in: libxdamage (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxdamage in Ubuntu. https://bugs.launchpad.net/bugs/1230252 Title: libxdamage-dev should be Multi-Arch:same Status in “libxdamage” package in Ubuntu: Fix Released Bug description: I often compile stuff for the host (amd64) and target (i386) architectures using multilib compiler. Unfortunately I need libxdamage-dev and at the moment I constantly have to re-install it. It would be great is libxdamage-dev was converted to multiarch:saem. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libxdamage-dev 1:1.1.4-1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,mousepoll,gnomecompat,regex,animation,resize,snap,compiztoolbox,wall,vpswitch,imgpng,expo,fade,place,ezoom,workarounds,dbus,move,scale,unitymtgrabhandles,session,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 25 13:28:30 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2012-01-12 (621 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic.efi.signed root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: libxdamage UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F16 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF16:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Sep 16 09:03:27 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 25381 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxdamage/+bug/1230252/+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 1246013] [NEW] Whould be nice for libgl1-mesa-dev to be multiarched
Public bug reported: As per title. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1246013 Title: Whould be nice for libgl1-mesa-dev to be multiarched Status in “mesa” package in Ubuntu: New Bug description: As per title. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1246013/+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 1246013] Re: Whould be nice for libgl1-mesa-dev to be multiarched
** Tags added: multiarch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1246013 Title: Whould be nice for libgl1-mesa-dev to be multiarched Status in “mesa” package in Ubuntu: New Bug description: As per title. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1246013/+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 885324] Re: Completely replace lcms1 by lcms2 in Ubuntu
It's best to use transition tracker: http://people.canonical.com/~ubuntu-archive/transitions/lcms2.html It shows proper dependencies rounds rathers information based on the archive state across both source and binary packages across all architectures. ** Description changed: Many packages in Ubuntu use the liblcms1 library (source package lcms). This library is discontinued upstream and replaced by liblcms2. Due to this, bugs in liblcms1 are not fixed any more upstream and important improvements in color reproduction and safety against crashes are not done. Therefore we should remove lcms1 and migrate all programs using it to lcms2. + + Launchpad doesn't usually scale to track transitions like these. Please see a tracker instead: + http://people.canonical.com/~ubuntu-archive/transitions/lcms2.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/885324 Title: Completely replace lcms1 by lcms2 in Ubuntu Status in digiKam - digital photo management: Fix Released Status in Enblend: Fix Released Status in Inkscape: A Vector Drawing Tool: Fix Released Status in Wine: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “dcraw” package in Ubuntu: New Status in “digikam” package in Ubuntu: Fix Released Status in “enblend” package in Ubuntu: New Status in “enblend-enfuse” package in Ubuntu: New Status in “f-spot” package in Ubuntu: Triaged Status in “geeqie” package in Ubuntu: New Status in “gimp” package in Ubuntu: Triaged Status in “imagemagick” package in Ubuntu: Fix Released Status in “inkscape” package in Ubuntu: Fix Released Status in “lcms” package in Ubuntu: New Status in “libkdcraw” package in Ubuntu: Fix Released Status in “libmng” package in Ubuntu: New Status in “libraw” package in Ubuntu: Fix Released Status in “openjdk-6” package in Ubuntu: New Status in “poppler” package in Ubuntu: Fix Released Status in “python-imaging” package in Ubuntu: New Status in “rawstudio” package in Ubuntu: New Status in “scribus” package in Ubuntu: New Status in “shotwell” package in Ubuntu: Fix Released Status in “ufraw” package in Ubuntu: New Status in “wine1.4” package in Ubuntu: Triaged Status in “xsane” package in Ubuntu: New Bug description: Many packages in Ubuntu use the liblcms1 library (source package lcms). This library is discontinued upstream and replaced by liblcms2. Due to this, bugs in liblcms1 are not fixed any more upstream and important improvements in color reproduction and safety against crashes are not done. Therefore we should remove lcms1 and migrate all programs using it to lcms2. Launchpad doesn't usually scale to track transitions like these. Please see a tracker instead: http://people.canonical.com/~ubuntu-archive/transitions/lcms2.html To manage notifications about this bug go to: https://bugs.launchpad.net/digikam/+bug/885324/+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 1078720] Re: gnome-sudoku: port to python3
** Changed in: gnome-sudoku (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1078720 Title: gnome-sudoku: port to python3 Status in GNOME Games: Confirmed Status in “gnome-sudoku” package in Ubuntu: Fix Committed Bug description: Please port gnome-sudoku to python3. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-games/+bug/1078720/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: systemd (Ubuntu Saucy) Status: In Progress = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 963460] Re: Ubiquity calls check-language-support with zh-hans instead of a locale (zh_CN)
** Changed in: ubiquity (Ubuntu) Status: Fix Committed = Fix Released -- 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/963460 Title: Ubiquity calls check-language-support with zh-hans instead of a locale (zh_CN) Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Fix Released Status in “language-selector” source package in Precise: Fix Released Status in “ubiquity” source package in Precise: Fix Released Bug description: In Precise, using check-language-support -l zh_CN returns: cmap-adobe-gb1 firefox-locale-zh-hans fonts-arphic-uming ibus-sunpinyin ibus-table-wubi language-pack-gnome-zh-hans language-pack-zh-hans libreoffice-help-zh-cn libreoffice-l10n-zh-cn poppler-data thunderbird-locale-zh-cn thunderbird-locale-zh-hans ttf-arphic-ukai ttf-wqy-zenhei whereas check-language-support -l zh-hans returns: cmap-adobe-gb1 firefox-locale-zh-hans fonts-arphic-uming ibus-sunpinyin ibus-table-wubi language-pack-gnome-zh-hans language-pack-zh-hans poppler-data thunderbird-locale-zh-hans ttf-arphic-ukai ttf-wqy-zenhei You will notice that zh-hans does not have any of the *-zh-cn packages listed. This is an issue because in situations where you want to install zh_CN language/locale support using Ubiquity, Ubiquity will automatically convert zh_CN to zh-hans and then only install those packages. The same is true for zh_TW and zh-hant where the *-zh-tw will not be installed if the user chooses zh_TW. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/963460/+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 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm
Maybe network-manager should ship shell snippet in pm-utils configuration directory to issue sleep false on resume/thaw? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: network-manager has decided that networking is disabled, cannot be re- enabled from lightdm Status in “network-manager” package in Ubuntu: Confirmed Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1231359] Re: Sync gnome-common 3.10.0-1 (main) from Debian unstable (main)
** Changed in: gnome-common (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-common in Ubuntu. https://bugs.launchpad.net/bugs/1231359 Title: Sync gnome-common 3.10.0-1 (main) from Debian unstable (main) Status in “gnome-common” package in Ubuntu: Incomplete Bug description: Please sync gnome-common 3.10.0-1 (main) from Debian unstable (main) Changelog entries since current saucy version 3.7.4-1: gnome-common (3.10.0-1) unstable; urgency=low * New upstream release. - Use autoreconf instead of running the individual tools manually. This also means gnome-autogen.sh no longer fails with newer automake versions. Closes: #722231 * Drop debian/patches/02_autogen_required_versions.patch, it no longer applies and the minimum required versions are available since a very long time now. * Wrap dependencies. -- Michael Biebl bi...@debian.org Tue, 24 Sep 2013 13:11:33 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-common/+bug/1231359/+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 1223687] Re: Sync texlive-base 2013.20130905-1 (main) from Debian unstable (main)
unsubscribing sponsors. ** Changed in: texlive-base (Ubuntu) Assignee: Dmitrijs Ledkovs (xnox) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1223687 Title: Sync texlive-base 2013.20130905-1 (main) from Debian unstable (main) Status in “texlive-base” package in Ubuntu: Incomplete Bug description: Please sync texlive-base 2013.20130905-1 (main) from Debian unstable (main) Changelog entries since current saucy version 2013.20130722-1: texlive-base (2013.20130905-1) unstable; urgency=low * new upstream checkout - don't ship strange duplicates of Nimbus Sans (Closes: #690125) * remove /etc/texmf/dvipdfm/config/config (Closes: #713797) * do not ship marvosym.ttf via dependency (Closes: #721716) * bump standards version to 3.9.4, no changes necessary * fix man section of updmap.cfg man page * fix man page of mptopdf * stop shipping TeX Gyre Math fonts, they are in tex-gyre package -- Norbert Preining prein...@debian.org Thu, 05 Sep 2013 11:46:27 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1223687/+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 1223689] Re: Sync texlive-extra 2013.20130905-1 (main) from Debian unstable (main)
** Changed in: texlive-extra (Ubuntu) Assignee: Dmitrijs Ledkovs (xnox) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1223689 Title: Sync texlive-extra 2013.20130905-1 (main) from Debian unstable (main) Status in “texlive-extra” package in Ubuntu: Incomplete Bug description: Please sync texlive-extra 2013.20130905-1 (main) from Debian unstable (main) Changelog entries since current saucy version 2013.20130722-1: texlive-extra (2013.20130905-1) unstable; urgency=low * new upstream checkout - fix siunitx typo (Closes: #719871) * add a latexdef - texdef link (Closes: #719427) * texlive-pictures suggests texlive-latex-extra (Closes: #705951, #683567) * texlive-pcitures suggest libtcltk-ruby (Closes: #600375) * bump standards version to 3.9.4, no changes necessary * fonts-font-awesome instead of shipping the font -- Norbert Preining prein...@debian.org Thu, 05 Sep 2013 11:46:54 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1223689/+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 1223688] Re: Sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main)
we are way past feature freeze. if individual fixes for bugs are needed, please file separate bugs about those. ** Changed in: texlive-lang (Ubuntu) Status: New = Incomplete ** Changed in: texlive-lang (Ubuntu) Assignee: Dmitrijs Ledkovs (xnox) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-lang in Ubuntu. https://bugs.launchpad.net/bugs/1223688 Title: Sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main) Status in “texlive-lang” package in Ubuntu: Incomplete Bug description: Please sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main) Changelog entries since current saucy version 2013.20130722-1: texlive-lang (2013.20130905-1) unstable; urgency=low * new upstream checkout * provide a bunch of transitional packages to easy update from stable (Closes: #721838) * bump standards version to 3.9.4, no changes necessary -- Norbert Preining prein...@debian.org Thu, 05 Sep 2013 11:47:05 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1223688/+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 1230252] [NEW] libxdamage-dev should be Multi-Arch:same
Public bug reported: I often compile stuff for the host (amd64) and target (i386) architectures using multilib compiler. Unfortunately I need libxdamage- dev and at the moment I constantly have to re-install it. It would be great is libxdamage-dev was converted to multiarch:saem. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libxdamage-dev 1:1.1.4-1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,mousepoll,gnomecompat,regex,animation,resize,snap,compiztoolbox,wall,vpswitch,imgpng,expo,fade,place,ezoom,workarounds,dbus,move,scale,unitymtgrabhandles,session,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 25 13:28:30 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2012-01-12 (621 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic.efi.signed root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: libxdamage UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F16 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF16:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Sep 16 09:03:27 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 25381 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 ** Affects: libxdamage (Ubuntu) Importance: Wishlist Status: Confirmed ** Tags: amd64 apport-bug compiz-0.9 multiarch saucy ubuntu ** Tags added: multiarch ** Changed in: libxdamage (Ubuntu) Status: New = Confirmed ** Changed in: libxdamage (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxdamage in Ubuntu. https://bugs.launchpad.net/bugs/1230252 Title: libxdamage-dev should be Multi-Arch:same Status in “libxdamage” package in Ubuntu: Confirmed Bug description: I often compile stuff for the host (amd64) and target (i386) architectures using multilib compiler. Unfortunately I need libxdamage-dev and at the moment I constantly have to re-install it. It would be great is libxdamage-dev was converted to multiarch:saem. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libxdamage-dev 1:1.1.4-1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,mousepoll,gnomecompat,regex,animation,resize,snap,compiztoolbox,wall,vpswitch,imgpng,expo,fade,place,ezoom,workarounds,dbus,move,scale,unitymtgrabhandles,session,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 25 13:28:30 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard:
[Desktop-packages] [Bug 1229383] Re: Gray bars at top of screen when selecting live/install mode
*** This bug is a duplicate of bug 1207890 *** https://bugs.launchpad.net/bugs/1207890 This is actually ubiquity-panel bug, part of ubiquity. Not an xorg bug. ** This bug has been marked a duplicate of bug 1207890 too many panels displayed during install (see screenshot) -- 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/1229383 Title: Gray bars at top of screen when selecting live/install mode Status in “xorg” package in Ubuntu: New Bug description: I've seen this on both a Dell laptop, and in virtualbox so far. Booting up the 20130923.1 amd64 desktop image, I see multiple gray bars at the top of the screen where you pick whether you want to go to a live session, or install. I'll attach a screenshot in just a moment. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CasperVersion: 1.336 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 23 22:58:12 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0456] LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130923.1) MachineType: Dell Inc. Inspiron N4010 MarkForUpload: True ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 021CN3 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/19/2011:svnDellInc.:pnInspironN4010:pvrA11:rvnDellInc.:rn021CN3:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N4010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 23 22:52:43 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6204 vendor AUO xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1229383/+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 1227188] [NEW] brightness doesn't work on Lenovo IdeaPad Yoga 13
Public bug reported: Similar to bug 11588934, I get acpi_video0 intel_backlight, or (ideapad intel_backlight) depending on the osi_* kernel cmd line settings. The one that is preferred / used (acpi_video0 / ideapad) do not work. Whereas intel_backlight is the one that does work. I have Lenovo IdeaPad Yoga 13. I have now specified: /etc/X11/xorg.conf.d/backlight.conf Section Device Identifier Device0 Option Backlight intel_backlight EndSection I guess a similar blacklist as was applied for HP should be applied in upstream kernel for Yoga? Regards, Dmitrijs. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 18 09:54:16 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2013-08-29 (20 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829) MachineType: LENOVO 2191 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic.efi.signed root=UUID=5c176060-d588-4044-87b6-50b785b931b1 ro quiet splash acpi_backlight=legacy acpi_osi=Linux vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN54WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN54WW:bd01/21/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Sep 18 09:47:52 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 864 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu -- 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/1227188 Title: brightness doesn't work on Lenovo IdeaPad Yoga 13 Status in “xorg” package in Ubuntu: New Bug description: Similar to bug 11588934, I get acpi_video0 intel_backlight, or (ideapad intel_backlight) depending on the osi_* kernel cmd line settings. The one that is preferred / used (acpi_video0 / ideapad) do not work. Whereas intel_backlight is the one that does work. I have Lenovo IdeaPad Yoga 13. I have now specified: /etc/X11/xorg.conf.d/backlight.conf Section Device Identifier Device0 Option Backlight intel_backlight EndSection I guess a similar blacklist as was applied for HP should be applied in upstream kernel for Yoga? Regards, Dmitrijs. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 18 09:54:16 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes,
[Desktop-packages] [Bug 1227188] Re: brightness doesn't work
** Attachment added: dmidecode.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1227188/+attachment/3827396/+files/dmidecode.txt ** Summary changed: - brightness doesn't work + brightness doesn't work on Lenovo IdeaPad Yoga 13 -- 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/1227188 Title: brightness doesn't work on Lenovo IdeaPad Yoga 13 Status in “xorg” package in Ubuntu: New Bug description: Similar to bug 11588934, I get acpi_video0 intel_backlight, or (ideapad intel_backlight) depending on the osi_* kernel cmd line settings. The one that is preferred / used (acpi_video0 / ideapad) do not work. Whereas intel_backlight is the one that does work. I have Lenovo IdeaPad Yoga 13. I have now specified: /etc/X11/xorg.conf.d/backlight.conf Section Device Identifier Device0 Option Backlight intel_backlight EndSection I guess a similar blacklist as was applied for HP should be applied in upstream kernel for Yoga? Regards, Dmitrijs. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 18 09:54:16 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2013-08-29 (20 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829) MachineType: LENOVO 2191 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic.efi.signed root=UUID=5c176060-d588-4044-87b6-50b785b931b1 ro quiet splash acpi_backlight=legacy acpi_osi=Linux vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN54WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN54WW:bd01/21/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Sep 18 09:47:52 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 864 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1227188/+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 1223687] Re: Sync texlive-base 2013.20130905-1 (main) from Debian unstable (main)
Is this needed for Saucy, or can this wait until next cycle? We are now post FeatureFreeze. Ditto the rest of texlive-* sync requests from you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1223687 Title: Sync texlive-base 2013.20130905-1 (main) from Debian unstable (main) Status in “texlive-base” package in Ubuntu: New Bug description: Please sync texlive-base 2013.20130905-1 (main) from Debian unstable (main) Changelog entries since current saucy version 2013.20130722-1: texlive-base (2013.20130905-1) unstable; urgency=low * new upstream checkout - don't ship strange duplicates of Nimbus Sans (Closes: #690125) * remove /etc/texmf/dvipdfm/config/config (Closes: #713797) * do not ship marvosym.ttf via dependency (Closes: #721716) * bump standards version to 3.9.4, no changes necessary * fix man section of updmap.cfg man page * fix man page of mptopdf * stop shipping TeX Gyre Math fonts, they are in tex-gyre package -- Norbert Preining prein...@debian.org Thu, 05 Sep 2013 11:46:27 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1223687/+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 1223687] Re: Sync texlive-base 2013.20130905-1 (main) from Debian unstable (main)
** Changed in: texlive-base (Ubuntu) Status: New = Incomplete ** Changed in: texlive-base (Ubuntu) Assignee: (unassigned) = Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1223687 Title: Sync texlive-base 2013.20130905-1 (main) from Debian unstable (main) Status in “texlive-base” package in Ubuntu: Incomplete Bug description: Please sync texlive-base 2013.20130905-1 (main) from Debian unstable (main) Changelog entries since current saucy version 2013.20130722-1: texlive-base (2013.20130905-1) unstable; urgency=low * new upstream checkout - don't ship strange duplicates of Nimbus Sans (Closes: #690125) * remove /etc/texmf/dvipdfm/config/config (Closes: #713797) * do not ship marvosym.ttf via dependency (Closes: #721716) * bump standards version to 3.9.4, no changes necessary * fix man section of updmap.cfg man page * fix man page of mptopdf * stop shipping TeX Gyre Math fonts, they are in tex-gyre package -- Norbert Preining prein...@debian.org Thu, 05 Sep 2013 11:46:27 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1223687/+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 1223688] Re: Sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main)
Is this needed for Saucy, or can this wait until next cycle? We are now post FeatureFreeze. Ditto the rest of texlive-* sync requests from you. ** Changed in: texlive-lang (Ubuntu) Status: New = Incomplete ** Changed in: texlive-lang (Ubuntu) Assignee: (unassigned) = Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-lang in Ubuntu. https://bugs.launchpad.net/bugs/1223688 Title: Sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main) Status in “texlive-lang” package in Ubuntu: Incomplete Bug description: Please sync texlive-lang 2013.20130905-1 (main) from Debian unstable (main) Changelog entries since current saucy version 2013.20130722-1: texlive-lang (2013.20130905-1) unstable; urgency=low * new upstream checkout * provide a bunch of transitional packages to easy update from stable (Closes: #721838) * bump standards version to 3.9.4, no changes necessary -- Norbert Preining prein...@debian.org Thu, 05 Sep 2013 11:47:05 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1223688/+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 1223689] Re: Sync texlive-extra 2013.20130905-1 (main) from Debian unstable (main)
** Changed in: texlive-extra (Ubuntu) Status: New = Incomplete ** Changed in: texlive-extra (Ubuntu) Assignee: (unassigned) = Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1223689 Title: Sync texlive-extra 2013.20130905-1 (main) from Debian unstable (main) Status in “texlive-extra” package in Ubuntu: Incomplete Bug description: Please sync texlive-extra 2013.20130905-1 (main) from Debian unstable (main) Changelog entries since current saucy version 2013.20130722-1: texlive-extra (2013.20130905-1) unstable; urgency=low * new upstream checkout - fix siunitx typo (Closes: #719871) * add a latexdef - texdef link (Closes: #719427) * texlive-pictures suggests texlive-latex-extra (Closes: #705951, #683567) * texlive-pcitures suggest libtcltk-ruby (Closes: #600375) * bump standards version to 3.9.4, no changes necessary * fonts-font-awesome instead of shipping the font -- Norbert Preining prein...@debian.org Thu, 05 Sep 2013 11:46:54 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1223689/+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 1032639] Re: can not link against libxml2
This is an intentional toolchain change, which brings significant benefits and features to Ubuntu. Similar changes are adopted by other distributions such as Debian and Fedora. Here are further details: https://wiki.debian.org/ToolChain/DSOLinking http://fedoraproject.org/wiki/UnderstandingDSOLinkChange -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1032639 Title: can not link against libxml2 Status in “libxml2” package in Ubuntu: Invalid Bug description: When I try tolink against libxml2 I get undefined symbol errors from libxml2. Installed packages are: libxml2 libxml2-dev I try to build the tutorial file from libxml2: http://www.xmlsoft.org/tutorial/apc.html I try to build the programm like this: gcc -o main $(xml2-config --cflags --libs) main.o on other platforms (debian testing or ubuntu 10.04) this works flawlessly. the complete output: $ gcc -o main $(xml2-config --cflags --libs) main.o main.o: In function `parseStory': main.c:(.text+0x2f): undefined reference to `xmlStrcmp' main.c:(.text+0x4f): undefined reference to `xmlNodeListGetString' main.c:(.text+0x73): undefined reference to `xmlFree' main.o: In function `parseDoc': main.c:(.text+0xa9): undefined reference to `xmlParseFile' main.c:(.text+0xe9): undefined reference to `xmlDocGetRootElement' main.c:(.text+0x124): undefined reference to `xmlFreeDoc' main.c:(.text+0x13e): undefined reference to `xmlStrcmp' main.c:(.text+0x172): undefined reference to `xmlFreeDoc' main.c:(.text+0x197): undefined reference to `xmlStrcmp' main.c:(.text+0x1cd): undefined reference to `xmlFreeDoc' collect2: ld returned 1 exit status $ xml2-config --cflags -I/usr/include/libxml2 xml2-config --libs -L/usr/lib/x86_64-linux-gnu -lxml2 $ ls -l /usr/lib/x86_64-linux-gnu/libxml2.* -rw-r--r-- 1 root root 2187982 May 18 21:52 /usr/lib/x86_64-linux-gnu/libxml2.a -rw-r--r-- 1 root root 947 May 18 21:52 /usr/lib/x86_64-linux-gnu/libxml2.la lrwxrwxrwx 1 root root 16 May 18 21:52 /usr/lib/x86_64-linux-gnu/libxml2.so - libxml2.so.2.7.8 lrwxrwxrwx 1 root root 16 May 18 21:52 /usr/lib/x86_64-linux-gnu/libxml2.so.2 - libxml2.so.2.7.8 -rw-r--r-- 1 root root 1417368 May 18 21:52 /usr/lib/x86_64-linux-gnu/libxml2.so.2.7.8 $ nm -D /usr/lib/x86_64-linux-gnu/libxml2.so |grep -e xmlStrcmp -e xmlNodeListGetString -e 'xmlFree$' -e xmlParseFile -e xmlDocGetRootElement -e 'xmlFreeDoc$' 00054bd0 T xmlDocGetRootElement 00358a08 D xmlFree 000537e0 T xmlFreeDoc 00051d50 T xmlNodeListGetString 0004e370 T xmlParseFile 000aa9b0 T xmlStrcmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1032639/+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 1203024] Re: 'Install 3rd party software' does not install proper drivers for Nvidia Geforce GTX 580
It looks like drivers were installed: Jul 8 03:59:55 ubuntu ubiquity: Building dependency tree... Jul 8 03:59:55 ubuntu ubiquity: Jul 8 03:59:55 ubuntu ubiquity: Reading state information... Jul 8 03:59:55 ubuntu ubiquity: The following extra packages will be installed: Jul 8 03:59:55 ubuntu ubiquity: dkms fakeroot nvidia-settings-313-updates python-xkit Jul 8 03:59:55 ubuntu ubiquity: screen-resolution-extra Jul 8 03:59:55 ubuntu ubiquity: Suggested packages: Jul 8 03:59:55 ubuntu ubiquity: dpkg-dev debhelper Jul 8 03:59:55 ubuntu ubiquity: Recommended packages: Jul 8 03:59:55 ubuntu ubiquity: nvidia-settings-310 Jul 8 03:59:55 ubuntu ubiquity: The following NEW packages will be installed: Jul 8 03:59:55 ubuntu ubiquity: dkms fakeroot nvidia-310 nvidia-settings-313-updates python-xkit Jul 8 03:59:55 ubuntu ubiquity: screen-resolution-extra Jul 8 03:59:55 ubuntu ubiquity: 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Jul 8 03:59:55 ubuntu ubiquity: Need to get 69.2 MB/69.4 MB of archives. In particular nvidia-310 was selected for your card. Was that not right for your graphics card? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1203024 Title: 'Install 3rd party software' does not install proper drivers for Nvidia Geforce GTX 580 Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Status in “ubiquity” package in Ubuntu: Incomplete Bug description: To run the installer on a machine with an Nvidia Geforce GTX 580 graphics card it is necessary to use the 'nomodeset'-option. After installation, Unity runs slowly and in a very low resolution. This can be fixed by installing the nvidia-current package. I asked on the ubiquity irc chat about this, and the response was that this is a bug, hence this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1203024/+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 1203024] Re: 'Install 3rd party software' does not install proper drivers for Nvidia Geforce GTX 580
What is the output of: $ ubuntu-drivers list ? We use Modaliases stanza on the package to figure out if your hardware needs it. Could you also do: $ lspci And then lookup modalias for your card in: $ cat /sys/devices/pci*/*$(DEVICE)/modalias ** Also affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New = Invalid ** Changed in: ubiquity (Ubuntu) Status: Confirmed = Opinion ** Changed in: ubiquity (Ubuntu) Status: Opinion = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1203024 Title: 'Install 3rd party software' does not install proper drivers for Nvidia Geforce GTX 580 Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Status in “ubiquity” package in Ubuntu: Incomplete Bug description: To run the installer on a machine with an Nvidia Geforce GTX 580 graphics card it is necessary to use the 'nomodeset'-option. After installation, Unity runs slowly and in a very low resolution. This can be fixed by installing the nvidia-current package. I asked on the ubiquity irc chat about this, and the response was that this is a bug, hence this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1203024/+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 1219983] Re: Sync blt 2.4z-6 (main) from Debian unstable (main)
by now, this has already been synced
** Changed in: blt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to blt in Ubuntu.
https://bugs.launchpad.net/bugs/1219983
Title:
Sync blt 2.4z-6 (main) from Debian unstable (main)
Status in “blt” package in Ubuntu:
Fix Released
Bug description:
Please sync blt 2.4z-6 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Build using Tk 8.5 installed in a multiarch location.
* Stop building for Tk 8.4. LP: #1155269.
The Tk changes were merged into Debian, so the delta is no longer necessary.
Changelog entries since current saucy version 2.4z-5ubuntu2:
blt (2.4z-6) unstable; urgency=low
* QA upload, orphan the package.
[ Paul E. Johnson ]
* Fix zooming (Closes: #524149)
* Fix crash in wish (Closes: #636629)
* Version 2.4z-6 introduces quilt-3.0 patches.
* Changes in control and rules file to silence lintian warnings.
* 02-debian-all.diff includes all of the changes that were applied
to the source code by previous packager. Almost all of the changes
are corrections in spelling in the blt documentation and examples.
* Apply 3 changes based on revisions developed by the fedora linux team.
+ 03-fedora-patch-2.diff
+ 04-fedora-tk8.5.6.patch.diff
+ 05-tk8.5-zoomstack.diff
* Those patches are required to solve segmentation faults that are observed
when blt is used with tcltk 8.5. We have a substantial amount of
experience using this patched version of blt in the Swarm
Simulation System (www.swarm.org) and have observed no ill-effects.
* new patches for man page cleanups to silence lintian warningss.
* patch configure according to Debian hardening policy.
[ Georges Khaznadar ]
* changed the source format to 3.0 (quilt)
* modified every diff file in debian/patches to comply with the
build tools
* checked that the package is built successfully
* modified Standards-Version - 3.9.4, comptaibility level - 9
* added a build-depedency on quilt and ${misc:Depends} clauses
* changed the build-depedency on debhelper (now: = 9)
* set the urgency flag to low (normal is not allowed)
* removed the leading article in blt-dev's and blt-demo's description lines
[ Matthias Klose ]
* Allow to build using Tcl/Tk 8.5 installed in a multiarch location.
* Stop building for Tk 8.4.
* Allow parallel builds.
-- Matthias Klose d...@debian.org Fri, 30 Aug 2013 11:13:17 +0200
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blt/+bug/1219983/+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 1051935] Re: Fails with SystemError when too many files are open
** Changed in: ubiquity (Ubuntu Saucy) Assignee: (unassigned) = Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to oneconf in Ubuntu. https://bugs.launchpad.net/bugs/1051935 Title: Fails with SystemError when too many files are open Status in “gdebi” package in Ubuntu: Confirmed Status in “oneconf” package in Ubuntu: Fix Released Status in “python-apt” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Confirmed Status in “gdebi” source package in Saucy: Confirmed Status in “oneconf” source package in Saucy: Fix Released Status in “python-apt” source package in Saucy: Fix Released Status in “ubiquity” source package in Saucy: Confirmed Bug description: This error occurs each time I try to install a .deb file with Gdebi in Ubuntu 12.10, after the deb installation finishes. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gdebi 0.8.5build1 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Mon Sep 17 15:33:34 2012 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120914) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb'] SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1051935/+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 1051935] Re: Fails with SystemError when too many files are open
** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to oneconf in Ubuntu. https://bugs.launchpad.net/bugs/1051935 Title: Fails with SystemError when too many files are open Status in “gdebi” package in Ubuntu: Confirmed Status in “oneconf” package in Ubuntu: Fix Released Status in “python-apt” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Confirmed Status in “gdebi” source package in Saucy: Confirmed Status in “oneconf” source package in Saucy: Fix Released Status in “python-apt” source package in Saucy: Fix Released Status in “ubiquity” source package in Saucy: Confirmed Bug description: This error occurs each time I try to install a .deb file with Gdebi in Ubuntu 12.10, after the deb installation finishes. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gdebi 0.8.5build1 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Mon Sep 17 15:33:34 2012 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120914) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb'] SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1051935/+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 1198864] Re: Community Wallpaper selection 13.10
We believe this bug is now fixed with the below upload: ubuntu-wallpapers (13.04.0+13.10.20130823-0ubuntu1) saucy; urgency=low [ Iain Lane ] * AUTHORS: fix raring alignment * Add raring-wallpapers to POTFILES.in * Add Saucy contest wallpapers and packaging * Copyright → 2013 * Add saucy-wallpapers.xml.in to POTFILES.in [ Dmitrijs Ledkovs ] * Update pot [ Ubuntu daily release ] * Automatic snapshot from revision 109 -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 23 Aug 2013 18:06:53 + ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1198864 Title: Community Wallpaper selection 13.10 Status in “ubuntu-wallpapers” package in Ubuntu: Fix Released Bug description: This is where we will put the wallpaper selection as chosen by community volunteers for 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1198864/+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 1216223] Re: Wallpapers for saucy salamander should be at least FullHD
The images submitted to flickr should be off highest resolution, as I believe Flickr doesn't limit the size?! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1216223 Title: Wallpapers for saucy salamander should be at least FullHD Status in “ubuntu-wallpapers” package in Ubuntu: Incomplete Bug description: Hello, I think the wallpapers for saucy salamander should be at least in FullHD, winning authors (incl. me) have not been contacted yet so I presume you will use pictures from flickr... please do not do that, let users to have fantastic wallpapers in best resolution/quality avaliable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1216223/+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 1216223] Re: Wallpapers for saucy salamander should be at least FullHD
The package with winning wallpapers has been uploaded into saucy. Which images are of sub-optimal quality? ** Changed in: ubuntu-wallpapers (Ubuntu) Status: Confirmed = Incomplete ** Changed in: ubuntu-wallpapers (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1216223 Title: Wallpapers for saucy salamander should be at least FullHD Status in “ubuntu-wallpapers” package in Ubuntu: Incomplete Bug description: Hello, I think the wallpapers for saucy salamander should be at least in FullHD, winning authors (incl. me) have not been contacted yet so I presume you will use pictures from flickr... please do not do that, let users to have fantastic wallpapers in best resolution/quality avaliable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1216223/+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 1216330] [NEW] file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Public bug reported: opened a tar.xz with .git/* in it. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: file-roller 3.8.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Sat Aug 24 15:54:47 2013 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2012-01-12 (589 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True ProcCmdline: file-roller /tmp/ocaml-estring_20130822.orig.tar.xz SegvAnalysis: Segfault happened at: 0x41cb30:mov(%rbx),%rsi PC (0x0041cb30) ok source (%rbx) (0x0047) not located in a known VMA region (needed readable region)! destination %rsi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () _gtk_marshal_BOOLEAN__BOXED (closure=0x16e86f0, return_value=0x7fffded2a840, n_param_values=optimised out, param_values=0x7fffded2a8f0, invocation_hint=optimised out, marshal_data=optimised out) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkmarshalers.c:85 g_closure_invoke (closure=0x16e86f0, return_value=0x7fffded2a840, n_param_values=2, param_values=0x7fffded2a8f0, invocation_hint=0x7fffded2a890) at /build/buildd/glib2.0-2.37.6/./gobject/gclosure.c:777 signal_emit_unlocked_R (node=node@entry=0x1294810, detail=detail@entry=0, instance=instance@entry=0x14345a0, emission_return=emission_return@entry=0x7fffded2a9c0, instance_and_params=instance_and_params@entry=0x7fffded2a8f0) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3582 g_signal_emit_valist (instance=optimised out, signal_id=optimised out, detail=optimised out, var_args=var_args@entry=0x7fffded2aa88) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3336 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip kvm libvirtd lpadmin plugdev sambashare sbuild sudo ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy -- 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/1216330 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in “file-roller” package in Ubuntu: New Bug description: opened a tar.xz with .git/* in it. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: file-roller 3.8.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Sat Aug 24 15:54:47 2013 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2012-01-12 (589 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True ProcCmdline: file-roller /tmp/ocaml-estring_20130822.orig.tar.xz SegvAnalysis: Segfault happened at: 0x41cb30: mov(%rbx),%rsi PC (0x0041cb30) ok source (%rbx) (0x0047) not located in a known VMA region (needed readable region)! destination %rsi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () _gtk_marshal_BOOLEAN__BOXED (closure=0x16e86f0, return_value=0x7fffded2a840, n_param_values=optimised out, param_values=0x7fffded2a8f0, invocation_hint=optimised out, marshal_data=optimised out) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkmarshalers.c:85 g_closure_invoke (closure=0x16e86f0, return_value=0x7fffded2a840, n_param_values=2, param_values=0x7fffded2a8f0, invocation_hint=0x7fffded2a890) at /build/buildd/glib2.0-2.37.6/./gobject/gclosure.c:777 signal_emit_unlocked_R (node=node@entry=0x1294810, detail=detail@entry=0, instance=instance@entry=0x14345a0, emission_return=emission_return@entry=0x7fffded2a9c0, instance_and_params=instance_and_params@entry=0x7fffded2a8f0) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3582 g_signal_emit_valist (instance=optimised out, signal_id=optimised out, detail=optimised out, var_args=var_args@entry=0x7fffded2aa88) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3336 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip kvm libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1216330/+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 1215751] Re: package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.6 failed to install/upgrade: './usr/bin/xml2-config' is different from the same file on the system
/usr/bin/xml2-config is different between architectures, yet is shipped
in a non-arch specific location.
# diff -U 4 amd64-foo/usr/bin/xml2-config i386-foo/usr/bin/xml2-config
--- amd64-foo/usr/bin/xml2-config 2013-07-16 19:47:12.0 +0100
+++ i386-foo/usr/bin/xml2-config2013-07-16 19:48:44.0 +0100
@@ -2,9 +2,9 @@
prefix=/usr
exec_prefix=${prefix}
includedir=${prefix}/include
-libdir=${prefix}/lib/x86_64-linux-gnu
+libdir=${prefix}/lib/i386-linux-gnu
usage()
{
cat EOF
** Changed in: libxml2 (Ubuntu)
Status: New = Confirmed
** Also affects: libxml2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: libxml2 (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: libxml2 (Ubuntu Precise)
Status: New = Won't Fix
** Changed in: libxml2 (Ubuntu Precise)
Status: Won't Fix = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1215751
Title:
package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.6 failed to install/upgrade:
'./usr/bin/xml2-config' is different from the same file on the system
Status in “libxml2” package in Ubuntu:
Confirmed
Status in “libxml2” source package in Precise:
Confirmed
Bug description:
Installation of libxml2 using dpkg and dselect. 64-bits Ubuntu 12.04
LTS.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libxml2-dev 2.7.8.dfsg-5.1ubuntu4.6
ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
Uname: Linux 3.2.0-52-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Fri Aug 23 15:44:09 2013
DuplicateSignature:
package:libxml2-dev:2.7.8.dfsg-5.1ubuntu4.6:'./usr/bin/xml2-config' is
different from the same file on the system
ErrorMessage: './usr/bin/xml2-config' is different from the same file on the
system
InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64
(20120823.1)
MarkForUpload: True
SourcePackage: libxml2
Title: package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.6 failed to install/upgrade:
'./usr/bin/xml2-config' is different from the same file on the system
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1215751/+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 1194896] Re: eog crashed with SIGSEGV in g_type_check_instance_cast()
** Changed in: eog (Ubuntu) Importance: Undecided = Critical ** Changed in: eog (Ubuntu) Importance: Critical = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1194896 Title: eog crashed with SIGSEGV in g_type_check_instance_cast() Status in “eog” package in Ubuntu: Confirmed Bug description: I was looking at an SVG file. Then I clicked Edit - Preferences and started changing the Background and Transparent Parts options. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: eog 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Wed Jun 26 11:07:42 2013 ExecutablePath: /usr/bin/eog InstallationDate: Installed on 2013-06-26 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130626) MarkForUpload: True ProcCmdline: eog /tmp/DirectionalDragArea.svg SegvAnalysis: Segfault happened at: 0x7f7ba02d7fec g_type_check_instance_cast+28: mov(%rax),%rdi PC (0x7f7ba02d7fec) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: eog StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () eog_scroll_view_set_use_bg_color () g_object_set_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: eog crashed with SIGSEGV in g_type_check_instance_cast() 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/eog/+bug/1194896/+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 763457] Re: please provide opencl-icd virtual package
The required changes are too risky for stable releases, and fall out of scope from both Stable Release Updates [1] and Backports [2] process. I am against from making such updates available in the Ubuntu Archive. It will be a support nightmare. Installing nvidia-current on e.g. intel machine renders many things unusable (e.g. unable to login into desktop session). In the past, the solution was for pyopencl to not depend on ocl-icd / nvidia-current, and simply let it fail. I'm not sure what's the best way to solve this. [1] https://wiki.ubuntu.com/StableReleaseUpdates [2] https://wiki.ubuntu.com/UbuntuBackports ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Quantal) Status: Confirmed = Won't Fix ** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Quantal) Status: Confirmed = Won't Fix ** Changed in: nvidia-graphics-drivers-319 (Ubuntu Quantal) Status: Confirmed = Won't Fix ** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu Quantal) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/763457 Title: please provide opencl-icd virtual package Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “nvidia-common” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pyopencl” package in Ubuntu: Fix Released Status in “fglrx-installer” source package in Quantal: Won't Fix Status in “nvidia-common” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers-304” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers-304-updates” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers-319” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers-319-updates” source package in Quantal: Won't Fix Status in “pyopencl” source package in Quantal: Fix Released Status in “pyopencl” package in Debian: Fix Released Bug description: The package python-pyopencl depends on nvidia-current, which makes it impossible to correctly use on AMD / ATI systems. In debbugs #628702 debian started using a virtual package opencl-icd instead of depending directly on particular graphics driver / opencl implementation. We should follow the same. TODO * syn pyopencl * nvidia-graphics-drivers or nvidia-common (not sure) to provide opencl-icd * fglrx-installer to provide opencl-icd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/763457/+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 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
libx11 is in precise unapproved queue. Unsubscribing ubuntu-sponsors for now. If more uploads needed, please re-subscribe the team, when ready. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “libx11” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Won't Fix Status in “gnome-settings-daemon” source package in Precise: New Status in “libx11” source package in Precise: In Progress Status in “udev” source package in Precise: New Status in “x11proto-core” source package in Precise: Fix Released Status in “xserver-xorg-input-evdev” source package in Precise: Won't Fix Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “libx11” source package in Raring: New Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Won't Fix Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+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 859600] Re: Please convert gnome-keyring to multiarch
@Adam Conrad (adconrad) Updated SRU uploaded into precise-proposed queue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch Status in “gnome-keyring” package in Ubuntu: Fix Released Status in “gnome-keyring” source package in Precise: New Status in “gnome-keyring” source package in Quantal: In Progress Status in “gnome-keyring” source package in Raring: Fix Released Status in “gnome-keyring” package in Debian: New Bug description: [Impact] Several applications are relying on this package as seen in comments 5 and 6. [Test case] Attempt to install both i386/amd64 versions of libp11-kit-gnome-keyring and preferably verify if the reported applications in this bug are able to run successfully. 1. Run the command 'wine notepad'. Notice the warning from p11-kit. 2. sudo apt-get install libp11-kit-gnome-keyring:i386 3. Run the command 'wine notepad' again. Notice that the warning is gone. [Regression Potential] Minimal, several rdepends build testing have been completed successfully and nothing in the keyring code is attempting to dlopen any hardcoded library paths. gnome-keyring is still installing libraries to /usr/lib instead of the multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The attached patch does the conversion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+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 1207038] Re: Update to 1.1.5
** Changed in: libimobiledevice (Ubuntu) Assignee: (unassigned) = Dmitrijs Ledkovs (xnox) ** Changed in: libimobiledevice (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207038 Title: Update to 1.1.5 Status in “libimobiledevice” package in Ubuntu: In Progress Bug description: The 1.1.5 update brings improved support for iOS 6 and more: http://cgit.sukimashita.com/libimobiledevice.git/tree/NEWS The soname was bumped with one replaced symbol. http://cgit.sukimashita.com/libimobiledevice.git/commit/?id=370ba8c119e05ab0121559fd22848b7d7083189e $ reverse-depends libimobiledevice3 Reverse-Depends === * clementine [amd64 i386 powerpc] * gvfs-backends * ideviceinstaller * ifuse * ipheth-utils * libgpod-common * libgpod4 * libgpod4-nogtk * libimobiledevice-dev * libimobiledevice-doc * libimobiledevice-utils * libimobiledevice3-dbg * nautilus-ideviceinfo * python-imobiledevice * upower I've checked that everything builds; only two packages needed backported patches (ideviceinstaller and clementine). clementine upstream fixed the build problem by dropping libimobiledevice support and I've backported that commit. In addition to sponsoring this patch, I'll also need someone to upload no-change rebuilds of gvfs and upower. I believe I can handle the rest of the transition. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libimobiledevice3 1.1.4-1ubuntu6 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Wed Jul 31 14:13:39 2013 InstallationDate: Installed on 2013-06-14 (47 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: libimobiledevice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207038/+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 1207038] Re: Update to 1.1.5
I take it debian/patches/[ab] are just spurious cruft in the patch?! $ diffstat update-libimobiledevice-1-1-5.debdiff changelog | 20 control | 17 libimobiledevice4.install |2 libimobiledevice4.symbols | 41 + patches/05_remove_gcry_need.patch |2 patches/06_cython_detection.patch | 45 - patches/07_cython_0.16_check.patch| 82 --- patches/08_cython_0.16_fix.patch | 20 patches/a | 156 ++ patches/b | 671 ++ patches/git_add_utils.patch | 148 + patches/git_explicitly_cast_ssl_enabled.patch | 20 patches/git_fix_insecure_tmp.patch| 186 +++ patches/git_handle_unset_environment.patch| 52 -- patches/git_utf8_devices_names.patch | 23 patches/link_against_pthread.patch| 37 + patches/series|7 rules |2 18 files changed, 1290 insertions(+), 241 deletions(-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207038 Title: Update to 1.1.5 Status in “libimobiledevice” package in Ubuntu: In Progress Bug description: The 1.1.5 update brings improved support for iOS 6 and more: http://cgit.sukimashita.com/libimobiledevice.git/tree/NEWS The soname was bumped with one replaced symbol. http://cgit.sukimashita.com/libimobiledevice.git/commit/?id=370ba8c119e05ab0121559fd22848b7d7083189e $ reverse-depends libimobiledevice3 Reverse-Depends === * clementine [amd64 i386 powerpc] * gvfs-backends * ideviceinstaller * ifuse * ipheth-utils * libgpod-common * libgpod4 * libgpod4-nogtk * libimobiledevice-dev * libimobiledevice-doc * libimobiledevice-utils * libimobiledevice3-dbg * nautilus-ideviceinfo * python-imobiledevice * upower I've checked that everything builds; only two packages needed backported patches (ideviceinstaller and clementine). clementine upstream fixed the build problem by dropping libimobiledevice support and I've backported that commit. In addition to sponsoring this patch, I'll also need someone to upload no-change rebuilds of gvfs and upower. I believe I can handle the rest of the transition. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libimobiledevice3 1.1.4-1ubuntu6 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Wed Jul 31 14:13:39 2013 InstallationDate: Installed on 2013-06-14 (47 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: libimobiledevice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207038/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
** Changed in: pyopencl (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in “boinc” package in Ubuntu: Confirmed Status in “fglrx-installer” package in Ubuntu: New Status in “nvidia-cuda-toolkit” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-310-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-313-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pycuda” package in Ubuntu: Confirmed Status in “pyopencl” package in Ubuntu: Fix Released Status in “starpu-contrib” package in Ubuntu: Confirmed Status in “viennacl” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
** Changed in: pycuda (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in “boinc” package in Ubuntu: Confirmed Status in “fglrx-installer” package in Ubuntu: New Status in “nvidia-cuda-toolkit” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-310-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-313-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pycuda” package in Ubuntu: In Progress Status in “pyopencl” package in Ubuntu: Fix Released Status in “starpu-contrib” package in Ubuntu: Confirmed Status in “viennacl” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1208861] Re: Sync libxslt 1.1.28-2 (main) from Debian unstable (main)
This bug was fixed in the package libxslt - 1.1.28-2 Sponsored for Aron Xu (happyaron) --- libxslt (1.1.28-2) unstable; urgency=low * debian/patches/000[4-8].patch: Upstream post release patches. -- Aron Xu a...@debian.org Thu, 01 Aug 2013 13:55:48 +0800 ** Changed in: libxslt (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxslt in Ubuntu. https://bugs.launchpad.net/bugs/1208861 Title: Sync libxslt 1.1.28-2 (main) from Debian unstable (main) Status in “libxslt” package in Ubuntu: Fix Released Bug description: Please sync libxslt 1.1.28-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Resynchronize on Debian, remaining ubuntu difference: * 0004-fix-python-multiarch-include.patch: fix for multiarch python version The patch was introduced in 1.1.27-1ubuntu1, the patch header says it is used to fix an FTBFS. I have locally tried to build 1.1.28-2 without the patch and the build was successful, so that the patch can be dropped to elimite diffs with Debian. Changelog entries since current saucy version 1.1.28-1ubuntu1: libxslt (1.1.28-2) unstable; urgency=low * debian/patches/000[4-8].patch: Upstream post release patches. -- Aron Xu a...@debian.org Thu, 01 Aug 2013 13:55:48 +0800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1208861/+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 1159862] Re: instant crashed with SIGSEGV
** Changed in: docbook-to-man (Ubuntu) Importance: Low = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to docbook-to-man in Ubuntu. https://bugs.launchpad.net/bugs/1159862 Title: instant crashed with SIGSEGV Status in “docbook-to-man” package in Ubuntu: Confirmed Bug description: Was rebuilding packages in sbuild ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: docbook-to-man 1:2.0.0-31 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 25 15:09:34 2013 ExecutablePath: /usr/bin/instant InstallationDate: Installed on 2012-01-12 (437 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True ProcCmdline: /usr/bin/instant -croff.cmap -sroff.sdata -tdocbook-to-man.ts -d ProcEnviron: LD_LIBRARY_PATH=set TERM=xterm-256color XDG_RUNTIME_DIR=set LD_PRELOAD=set SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x2aaae241:mov%rbx,0x78(%rax) PC (0x2aaae241) ok source %rbx ok destination 0x78(%rax) (0x0078) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: docbook-to-man StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: instant crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docbook-to-man/+bug/1159862/+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 1206314] Re: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped()
This error pops up in default install, after booting and logging in for the first time. ** Information type changed from Private to Public ** Changed in: webapps-applications (Ubuntu) Importance: Medium = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webapps-applications in Ubuntu. https://bugs.launchpad.net/bugs/1206314 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped() Status in “webapps-applications” package in Ubuntu: Confirmed Bug description: o sitema não emula corretamente travando. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-webapps-common 2.4.16+13.10.20130719-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Mon Jul 29 21:29:14 2013 ExecutablePath: /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py InstallationDate: Installed on 2013-07-14 (15 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130529) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py Signal: 5 SourcePackage: webapps-applications StacktraceTop: g_settings_get_mapped () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_callable_info_invoke () from /usr/lib/libgirepository-1.0.so.1 g_function_info_invoke () from /usr/lib/libgirepository-1.0.so.1 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1206314/+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 1206314] Re: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped()
** Changed in: webapps-applications (Ubuntu) Assignee: (unassigned) = Robert Bruce Park (robru) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webapps-applications in Ubuntu. https://bugs.launchpad.net/bugs/1206314 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped() Status in “webapps-applications” package in Ubuntu: Confirmed Bug description: o sitema não emula corretamente travando. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-webapps-common 2.4.16+13.10.20130719-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Mon Jul 29 21:29:14 2013 ExecutablePath: /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py InstallationDate: Installed on 2013-07-14 (15 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130529) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py Signal: 5 SourcePackage: webapps-applications StacktraceTop: g_settings_get_mapped () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_callable_info_invoke () from /usr/lib/libgirepository-1.0.so.1 g_function_info_invoke () from /usr/lib/libgirepository-1.0.so.1 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1206314/+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 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
Uploaded into precise-proposed unapproved queue. Pending a member of ubuntu-sru team to accept the package: Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading accountsservice_0.6.15-2ubuntu9.7.dsc: done. Uploading accountsservice_0.6.15-2ubuntu9.7.debian.tar.gz: done. Uploading accountsservice_0.6.15-2ubuntu9.7_source.changes: done. Successfully uploaded packages. Unsubscribing ubuntu-sponsors, Subscribing ubuntu-sru team. ** Changed in: accountsservice (Ubuntu Precise) Status: Triaged = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: In Progress Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+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 1204236] [NEW] please demote gksu to universe
Public bug reported: please demote gksu to universe, all reverse dependencies in main are fixed. ** Affects: gksu (Ubuntu) Importance: Low Status: Confirmed ** Affects: libgksu (Ubuntu) Importance: Low Status: Confirmed ** Also affects: libgksu (Ubuntu) Importance: Undecided Status: New ** Changed in: gksu (Ubuntu) Status: New = Confirmed ** Changed in: libgksu (Ubuntu) Status: New = Confirmed ** Changed in: gksu (Ubuntu) Importance: Undecided = Low ** Changed in: libgksu (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gksu in Ubuntu. https://bugs.launchpad.net/bugs/1204236 Title: please demote gksu to universe Status in “gksu” package in Ubuntu: Confirmed Status in “libgksu” package in Ubuntu: Confirmed Bug description: please demote gksu to universe, all reverse dependencies in main are fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1204236/+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 902801] Re: Please remove OOo from all supported Ubuntu repositories
Once a release is made, the packages are frozen and thus are not changed. Precise and Lucid are the only two current stable releases that still have openoffice package. Openoffice is no longer present in quantal/raring. And all other releases mentioned have now reached end of life. ** Changed in: openoffice.org (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. https://bugs.launchpad.net/bugs/902801 Title: Please remove OOo from all supported Ubuntu repositories Status in “openoffice.org” package in Ubuntu: Fix Released Bug description: Please remove OOo from the Main repository: + for all releases and move to Universe, or + for Natty onwards, continue to package it for future releases, and move it to Universe for Natty onwards, or + for Natty onwards, no longer package it for future releases, and move to Universe for Maverick and prior releases, or + for all releases and no longer package it in Ubuntu. The reason for this request is to clear up whether OOo is officially supported software, or Community maintained software, i.e. not officially supported software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/902801/+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 1202116] [NEW] gnome-session crashed with SIGSEGV in g_object_unref()
Public bug reported: Crash! =) ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-session-bin 3.8.2.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Wed Jul 17 09:10:03 2013 ExecutablePath: /usr/bin/gnome-session InstallationDate: Installed on 2012-01-12 (551 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True ProcCmdline: gnome-session --session=ubuntu ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f1732cdfb04 g_object_unref+20: cmpq $0x50,(%rax) PC (0x7f1732cdfb04) ok source $0x50 ok destination (%rax) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: g_object_unref (_object=0x22c79e0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:3086 ?? () ?? () dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 message_queue_dispatch (source=source@entry=0x213e4d0, callback=optimised out, user_data=optimised out) at dbus-gmain.c:90 Title: gnome-session crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy third-party-packages -- 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/1202116 Title: gnome-session crashed with SIGSEGV in g_object_unref() Status in “gnome-session” package in Ubuntu: New Bug description: Crash! =) ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-session-bin 3.8.2.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Wed Jul 17 09:10:03 2013 ExecutablePath: /usr/bin/gnome-session InstallationDate: Installed on 2012-01-12 (551 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True ProcCmdline: gnome-session --session=ubuntu ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f1732cdfb04 g_object_unref+20:cmpq $0x50,(%rax) PC (0x7f1732cdfb04) ok source $0x50 ok destination (%rax) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: g_object_unref (_object=0x22c79e0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:3086 ?? () ?? () dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 message_queue_dispatch (source=source@entry=0x213e4d0, callback=optimised out, user_data=optimised out) at dbus-gmain.c:90 Title: gnome-session crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1202116/+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 1200185] Re: failed to execute '/lib/udev/usb-db'
Thanks, pitti. Will see if I can fix above rules as per your recommendation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1200185 Title: failed to execute '/lib/udev/usb-db' Status in “argyll” package in Ubuntu: New Status in “colord” package in Ubuntu: New Status in “systemd” package in Ubuntu: Invalid Bug description: systemd-udev reports failure to execute usb-db, indeed there is no /lib/udev/usb-db on my system, yet argyll and colord reference those in the udev rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argyll/+bug/1200185/+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 1200185] [NEW] failed to execute '/lib/udev/usb-db'
Public bug reported: systemd-udev reports failure to execute usb-db, indeed there is no /lib/udev/usb-db on my system, yet argyll and colord reference those in the udev rules. ** Affects: argyll (Ubuntu) Importance: Medium Status: New ** Affects: colord (Ubuntu) Importance: Medium Status: New ** Affects: systemd (Ubuntu) Importance: Medium Status: New ** Also affects: argyll (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: argyll (Ubuntu) Importance: Undecided = Medium ** Changed in: colord (Ubuntu) Importance: Undecided = Medium ** Changed in: systemd (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1200185 Title: failed to execute '/lib/udev/usb-db' Status in “argyll” package in Ubuntu: New Status in “colord” package in Ubuntu: New Status in “systemd” package in Ubuntu: New Bug description: systemd-udev reports failure to execute usb-db, indeed there is no /lib/udev/usb-db on my system, yet argyll and colord reference those in the udev rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argyll/+bug/1200185/+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 1194740] Re: [precise] Saving xls files originally created in Excel 2003 causes considerable increase of file size
For series tasks, ubuntu-sru team is using status to specifically track packages that have been published in -proposed and waiting validation. This bug has not yet bee uploaded into precise-proposed, as far as I can tell. Thus resetting back to In Progress. How did the PPA testing go? Is this ready for upload into precise- proposed? ** Changed in: libreoffice (Ubuntu Precise) Status: Fix Committed = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1194740 Title: [precise] Saving xls files originally created in Excel 2003 causes considerable increase of file size Status in LibreOffice Productivity Suite: Fix Released Status in “libreoffice” package in Ubuntu: Fix Released Status in “libreoffice” source package in Precise: In Progress Bug description: This is a regression in upstream between 3.5.4 and 3.5.5. [Impact] when opening a received xls created by Microsoft Excel 2003, then saving as xls again by LibreOffice, file size becomes considerably larger. i.e. 32KB - 1.4MB (40x larger) [Test Case] A. to confirm the regression is fixed 1. open the xls file(32KB) attached in upstream bug https://bugs.freedesktop.org/attachment.cgi?id=64725 2. save it as xls in LibreOffice Calc 3. confirm that the file size becomes almost 1.4MB 4. update to -proposed 5. open the file in the upstream bug again and save it as xls 6. confirm that the file size is almost the same as the original(32KB) B. to confirm not happening another regression 1. create a new document in LibreOffice Calc 2. make the height of A5 cell 50mm 3. focus to A5 cell 4. save as xls and close the document 5. open the xls file again 6. confirm that the height of A5 cell is 50mm, the height of other rows stay default height. above steps of B1.-6. should be tested with both current and -proposed version Note: with 3.5.4 or lower version, when opening the xls file again in step 5, the height of all cells becomes 50mm. [Regression Potential] the patch causing this regression was intended to fix fdo#50304. https://bugs.freedesktop.org/show_bug.cgi?id=50304 to prevent fdo#50304 from happening again by this SRU, additional test case is described above. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: libreoffice-calc 1:3.5.7-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CasperVersion: 1.315.1 Date: Wed Jun 26 06:35:48 2013 LiveMediaBuild: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ja_JP.UTF-8 SHELL=/bin/bashSourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1194740/+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 1159862] Re: instant crashed with SIGSEGV
i got same crash again... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to docbook-to-man in Ubuntu. https://bugs.launchpad.net/bugs/1159862 Title: instant crashed with SIGSEGV Status in “docbook-to-man” package in Ubuntu: Confirmed Bug description: Was rebuilding packages in sbuild ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: docbook-to-man 1:2.0.0-31 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 25 15:09:34 2013 ExecutablePath: /usr/bin/instant InstallationDate: Installed on 2012-01-12 (437 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True ProcCmdline: /usr/bin/instant -croff.cmap -sroff.sdata -tdocbook-to-man.ts -d ProcEnviron: LD_LIBRARY_PATH=set TERM=xterm-256color XDG_RUNTIME_DIR=set LD_PRELOAD=set SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x2aaae241:mov%rbx,0x78(%rax) PC (0x2aaae241) ok source %rbx ok destination 0x78(%rax) (0x0078) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: docbook-to-man StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: instant crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docbook-to-man/+bug/1159862/+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 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt
** Attachment added: NetworkManager.conf.dpkg-new https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+attachment/3724115/+files/NetworkManager.conf.dpkg-new -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1197712 Title: 0.9.8.0-0ubuntu13 is causing conf prompt Status in “network-manager” package in Ubuntu: New Bug description: Got a conf promt. not sure why =) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+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 1197712] [NEW] 0.9.8.0-0ubuntu13 is causing conf prompt
Public bug reported: Got a conf promt. not sure why =) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1197712 Title: 0.9.8.0-0ubuntu13 is causing conf prompt Status in “network-manager” package in Ubuntu: New Bug description: Got a conf promt. not sure why =) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+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 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt
** Attachment added: Screenshot from 2013-07-04 10:26:58.png https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+attachment/3724102/+files/Screenshot%20from%202013-07-04%2010%3A26%3A58.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1197712 Title: 0.9.8.0-0ubuntu13 is causing conf prompt Status in “network-manager” package in Ubuntu: New Bug description: Got a conf promt. not sure why =) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+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 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt
** Attachment added: NetworkManager.conf https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+attachment/3724117/+files/NetworkManager.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1197712 Title: 0.9.8.0-0ubuntu13 is causing conf prompt Status in “network-manager” package in Ubuntu: New Bug description: Got a conf promt. not sure why =) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+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 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1197712 Title: 0.9.8.0-0ubuntu13 is causing conf prompt Status in “network-manager” package in Ubuntu: New Bug description: Got a conf promt. not sure why =) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+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 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt
I use ethernet as default connection, automatically connect and allow all users to use. This network connection also has VPN connections established on it, on boot. I do not believe I manually edited that file. Manpage suggests that plugins may do so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1197712 Title: 0.9.8.0-0ubuntu13 is causing conf prompt Status in “network-manager” package in Ubuntu: New Bug description: Got a conf promt. not sure why =) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+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 1183344] Re: Depends: python-gtk2 (= 2.24.0-3build1) but 2.24.0-3ubuntu1 is to be installed
In both raring saucy, python-glade2 and python-gtk2 are at matching version numbers (see below). Can you please do following: * Execute $ apt-get update * Show the ouput of $ apt-cache policy python-glade2 python-gtk2 $ rmadison -S -s raring pygtk pygtk | 2.24.0-3ubuntu1 |raring | source python-glade2 | 2.24.0-3ubuntu1 |raring | amd64, armhf, i386, powerpc python-gtk2 | 2.24.0-3ubuntu1 |raring | amd64, armhf, i386, powerpc python-gtk2-dbg | 2.24.0-3ubuntu1 |raring | amd64, armhf, i386, powerpc python-gtk2-dev | 2.24.0-3ubuntu1 |raring | all python-gtk2-doc | 2.24.0-3ubuntu1 |raring | all $ rmadison -S -s saucy pygtk pygtk | 2.24.0-3ubuntu1 | saucy | source python-glade2 | 2.24.0-3ubuntu1 | saucy | amd64, armhf, i386, powerpc python-gtk2 | 2.24.0-3ubuntu1 | saucy | amd64, armhf, i386, powerpc python-gtk2-dbg | 2.24.0-3ubuntu1 | saucy | amd64, armhf, i386, powerpc python-gtk2-dev | 2.24.0-3ubuntu1 | saucy | all python-gtk2-doc | 2.24.0-3ubuntu1 | saucy | all ** Changed in: pygtk (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1183344 Title: Depends: python-gtk2 (= 2.24.0-3build1) but 2.24.0-3ubuntu1 is to be installed Status in “pygtk” package in Ubuntu: Incomplete Bug description: Trying to install python-glade2, error shows up: The following packages have unmet dependencies: python-glade2 : Depends: python-gtk2 (= 2.24.0-3build1) but 2.24.0-3ubuntu1 is to be installed Info: 1) Ubuntu release: 13.04 2) python-gtk2 version: 2.24.0-3ubuntu1 3) Expected: python-glade2 installs 4) What happened: installation failed, unmet dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1183344/+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 1196452] [NEW] gnome-session crashed with SIGSEGV in g_object_unref()
*** This bug is a duplicate of bug 1196163 *** https://bugs.launchpad.net/bugs/1196163 Public bug reported: Something happened. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-session-bin 3.8.2.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-0.7-generic 3.10.0-rc7 Uname: Linux 3.10.0-0-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Fri Jun 28 22:39:05 2013 ExecutablePath: /usr/bin/gnome-session InstallationDate: Installed on 2012-01-12 (535 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True ProcCmdline: gnome-session --session=ubuntu ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9624419b04 g_object_unref+20: cmpq $0x50,(%rax) PC (0x7f9624419b04) ok source $0x50 ok destination (%rax) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: g_object_unref (_object=0xe6cdd0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:3086 ?? () ?? () dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 message_queue_dispatch (source=source@entry=0xda67d0, callback=optimised out, user_data=optimised out) at dbus-gmain.c:90 Title: gnome-session crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo ** Affects: gnome-session (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-crash saucy third-party-packages ** Information type changed from Private to Public ** Changed in: gnome-session (Ubuntu) Importance: Undecided = Low -- 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/1196452 Title: gnome-session crashed with SIGSEGV in g_object_unref() Status in “gnome-session” package in Ubuntu: New Bug description: Something happened. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-session-bin 3.8.2.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-0.7-generic 3.10.0-rc7 Uname: Linux 3.10.0-0-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Fri Jun 28 22:39:05 2013 ExecutablePath: /usr/bin/gnome-session InstallationDate: Installed on 2012-01-12 (535 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True ProcCmdline: gnome-session --session=ubuntu ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9624419b04 g_object_unref+20:cmpq $0x50,(%rax) PC (0x7f9624419b04) ok source $0x50 ok destination (%rax) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: g_object_unref (_object=0xe6cdd0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:3086 ?? () ?? () dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 message_queue_dispatch (source=source@entry=0xda67d0, callback=optimised out, user_data=optimised out) at dbus-gmain.c:90 Title: gnome-session crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1196452/+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 1196163] Re: gnome-session crashed with SIGSEGV in g_object_unref()
** Information type changed from Private to Public -- 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/1196163 Title: gnome-session crashed with SIGSEGV in g_object_unref() Status in “gnome-session” package in Ubuntu: Confirmed Bug description: Right after startup. Also the date applet crashed. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-session-bin 3.8.2.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-0.7-generic 3.10.0-rc7 Uname: Linux 3.10.0-0-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Sat Jun 29 20:56:52 2013 ExecutablePath: /usr/bin/gnome-session InstallationDate: Installed on 2012-03-30 (456 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) MarkForUpload: True ProcCmdline: gnome-session --session=ubuntu SegvAnalysis: Segfault happened at: 0x7f438c697b04 g_object_unref+20:cmpq $0x50,(%rax) PC (0x7f438c697b04) ok source $0x50 ok destination (%rax) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () ?? () dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 Title: gnome-session crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1196163/+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 1168370] Re: grip-test no longer responds to input
0.3.6daily13.06.10-0ubuntu1 - saucy 0.3.6daily13.06.19~13.04-0ubuntu1 - raring-proposed The version string used for an SRU is higher than the released version in saucy, which doesn't seem right. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgrip in Ubuntu. https://bugs.launchpad.net/bugs/1168370 Title: grip-test no longer responds to input Status in libgrip: multitouch gesture library for GTK: Fix Released Status in libgrip raring series: In Progress Status in “libgrip” package in Ubuntu: Fix Released Status in “libgrip” source package in Raring: Fix Committed Bug description: [Impact] * The library was not supplying and gestures to client callers because of underlying change in the underlying gesture recognizer conflicting with an incorrect assumption in the libgrip library design. The assumption was that touch input device IDs were persistent across gesture recognizer instances, which has never been guaranteed to be true. * This bug renders the entire libgrip functionally useless, a fairly serious regression. * The bug fix moves to the latest version of the GEIS interface so obviates dependency on incorrect behaviour in the previous implementation. [Test Case] * Using a touchscreen, invoke the eog photo viewer program and attempt to zoom a photo using the pinch gesture. Without this patch, there will be no response, with the patch the photo should zoom. See also #1120149. [Regression Potential] * A programming error in the library could result in crashes in the eog or evince applications. To manage notifications about this bug go to: https://bugs.launchpad.net/libgrip/+bug/1168370/+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 707794] Re: libqt4-opengl on armel should be compiled with OpenGL ES 2.x support
For qwtplot3d it seems like glu is needed, yet that is only available for GL and not GLES. There is a partial glu port to GLES at https://code.google.com/p/glues/ which doesn't seem to be packaged yet. ** Also affects: qtiplot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to avogadro in Ubuntu. https://bugs.launchpad.net/bugs/707794 Title: libqt4-opengl on armel should be compiled with OpenGL ES 2.x support Status in “avogadro” package in Ubuntu: Won't Fix Status in “clementine” package in Ubuntu: Triaged Status in “kdeartwork” package in Ubuntu: Fix Released Status in “kdeedu” package in Ubuntu: Fix Released Status in “kdegames” package in Ubuntu: Fix Released Status in “kipi-plugins” package in Ubuntu: Fix Released Status in “koffice” package in Ubuntu: Fix Released Status in “mythtv” package in Ubuntu: Fix Released Status in “phonon-backend-gstreamer” package in Ubuntu: Fix Released Status in “pyside” package in Ubuntu: Fix Released Status in “qt4-x11” package in Ubuntu: Fix Released Status in “qtiplot” package in Ubuntu: New Status in “qwtplot3d” package in Ubuntu: Confirmed Status in “sofa-framework” package in Ubuntu: New Status in “avogadro” source package in Natty: Won't Fix Status in “kdeartwork” source package in Natty: Fix Released Status in “kdeedu” source package in Natty: Fix Released Status in “kdegames” source package in Natty: Fix Released Status in “kipi-plugins” source package in Natty: Fix Released Status in “koffice” source package in Natty: Fix Released Status in “mythtv” source package in Natty: Fix Released Status in “phonon-backend-gstreamer” source package in Natty: Fix Released Status in “pyside” source package in Natty: Fix Released Status in “qt4-x11” source package in Natty: Fix Released Status in “qwtplot3d” source package in Natty: Confirmed Status in “sofa-framework” source package in Natty: New Bug description: Qt supports having the opengl library compatible with OpenGL and OpenGL ES 2.x (you can chose during build time), but currently it's compiled with OpenGL support on all architectures. As on ARM we only have accelerated OpenGL ES drivers, it'd be good if we could change the qt4-x11 packaging to use OpenGL ES on ARM by default, and continue using OpenGL at all other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avogadro/+bug/707794/+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 1187250] Re: package hyphen-ru (not installed) failed to install/upgrade: trying to overwrite '/usr/share/hyphen/hyph_ru_RU.dic', which is also in package openoffice.org-hyphen
Всё будет хорошо. ** Changed in: openoffice.org-hyphenation (Ubuntu) Status: Confirmed = In Progress ** Changed in: openoffice.org-hyphenation (Ubuntu) Assignee: (unassigned) = Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org-hyphenation in Ubuntu. https://bugs.launchpad.net/bugs/1187250 Title: package hyphen-ru (not installed) failed to install/upgrade: trying to overwrite '/usr/share/hyphen/hyph_ru_RU.dic', which is also in package openoffice.org-hyphenation 0.6 Status in “hyphen-ru” package in Ubuntu: Confirmed Status in “openoffice.org-hyphenation” package in Ubuntu: In Progress Bug description: на ровном месте упало ProblemType: Package DistroRelease: Ubuntu 13.10 Package: hyphen-ru (not installed) Uname: Linux 3.9.0-030900-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 AptOrdering: hyphen-ru: Install hyphen-ru: Configure Architecture: amd64 Date: Tue Jun 4 14:14:40 2013 DpkgTerminalLog: Unpacking hyphen-ru (from .../hyphen-ru_20030310-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/hyphen-ru_20030310-1_all.deb (--unpack): trying to overwrite '/usr/share/hyphen/hyph_ru_RU.dic', which is also in package openoffice.org-hyphenation 0.6 ErrorMessage: trying to overwrite '/usr/share/hyphen/hyph_ru_RU.dic', which is also in package openoffice.org-hyphenation 0.6 InstallationDate: Installed on 2013-05-13 (21 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: hyphen-ru Title: package hyphen-ru (not installed) failed to install/upgrade: trying to overwrite '/usr/share/hyphen/hyph_ru_RU.dic', which is also in package openoffice.org-hyphenation 0.6 UpgradeStatus: Upgraded to saucy on 2013-06-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hyphen-ru/+bug/1187250/+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 1015497] Re: Cannot select gtk dropdown list value in multiple applications: ubiquity, landscape client
@menulio-svytuokle each theme needs to be fixed individually, please open a new bug against broken theme. It is known that Adwaita, Radiance and Ambience themes are fixed. Other themes, might not be. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/1015497 Title: Cannot select gtk dropdown list value in multiple applications: ubiquity, landscape client Status in GTK+ GUI Toolkit: New Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “light-themes” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Quantal: Fix Released Status in “light-themes” source package in Quantal: Fix Released Status in “ubiquity” source package in Quantal: Invalid Bug description: Ubuntu Desktop 20120619 TEST CASE: 1. On Quantal, install the package gtk-3-examples $ sudo apt-get install gtk-3-examples 2. Launch 'gtk3-demo' 3. In the list double-click on 'Combo Box' 4. Try to change the value in the combo boxed 'Some stock icons' or 'Where are we' ACTUAL RESULT: The user cannot change the selection ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubiquity 2.11.5 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu4 Architecture: amd64 CasperVersion: 1.317 Date: Wed Jun 20 10:31:42 2012 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120619) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1015497/+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 1183738] Re: libxml2 can not coexist with libxml2-i386 on 64-bit systems
Can you please give the output of: $ sudo apt-get install libxml2:i386 libxml2:amd64 Regards, Dmitrijs. ** Changed in: libxml2 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1183738 Title: libxml2 can not coexist with libxml2-i386 on 64-bit systems Status in “libxml2” package in Ubuntu: Incomplete Bug description: In Ubuntu 13.04 (64-bit), libxml2-i386 can not be installed in the same time with libxml2(-amd64), though some packages (for example, skype, wine) depend on libxml2-i386. As much software depends on libxml2-amd64 (such as KDE), it is impossible to install wine, skype, etc. in 64-bit system using KDE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1183738/+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 1183738] Re: libxml2 can not coexist with libxml2-i386 on 64-bit systems
Multi-arch packages must be of the same version number to install. Please make sure you are _not_ using -proposed Ubuntu Archive repositories. If you are recompiling yourself, make sure you compile both architectures of the package. ** Changed in: libxml2 (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1183738 Title: libxml2 can not coexist with libxml2-i386 on 64-bit systems Status in “libxml2” package in Ubuntu: Invalid Bug description: In Ubuntu 13.04 (64-bit), libxml2-i386 can not be installed in the same time with libxml2(-amd64), though some packages (for example, skype, wine) depend on libxml2-i386. As much software depends on libxml2-amd64 (such as KDE), it is impossible to install wine, skype, etc. in 64-bit system using KDE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1183738/+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
Re: [Desktop-packages] [Bug 1183738] Re: libxml2 can not coexist with libxml2-i386 on 64-bit systems
On 24 May 2013 12:23, Sergey protsero...@gmail.com wrote: Ah... It's all my stupidness. Though I don't have -proposed repo, the problem lies in choosing repositories: long time ago I used apt-pin to make packages from raring preferable, so apt took libxml2:i386 not from raring-updates, but from raring, while libxml2:amd64 was from raring-updates. So, everything works, thank you. I also posted a bugreport for wine with the same problem (https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1183743) and I do not know, how to close it. Marked as duplicate. For future reference, one bug can affect multiple packages, simply use Also affects distribution to select additional packages. Regards, Dmitrijs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1183738 Title: libxml2 can not coexist with libxml2-i386 on 64-bit systems Status in “libxml2” package in Ubuntu: Invalid Bug description: In Ubuntu 13.04 (64-bit), libxml2-i386 can not be installed in the same time with libxml2(-amd64), though some packages (for example, skype, wine) depend on libxml2-i386. As much software depends on libxml2-amd64 (such as KDE), it is impossible to install wine, skype, etc. in 64-bit system using KDE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1183738/+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 1182170] Re: libreoffice FTBFS in saucy
Yeah, my bits are at: dget http://people.canonical.com/~xnox/repo/libreoffice_4.0.2-0ubuntu2.dsc Please note the hsqldb transition / new upstream release is in saucy- proposed now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1182170 Title: libreoffice FTBFS in saucy Status in “libreoffice” package in Ubuntu: New Bug description: libreoffice 1:4.0.2-0ubuntu1 (and the prepared 1:4.0.3-0ubuntu1 update) fails to build from source in saucy. pbuilder build log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1182170/+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 1182281] Re: Sync libraw 0.14.7-2 (main) from Debian unstable (main)
This bug was fixed in the package libraw - 0.14.7-2 Sponsored for Logan Rosen (logan) --- libraw (0.14.7-2) unstable; urgency=low * Team upload. * Upload to unstable. * debian/control: - Remove deprecated DM-Upload-Allowed field. - Bump Standards-Version to 3.9.4. -- Luca Falavigna dktrkr...@debian.org Sun, 12 May 2013 20:47:35 +0200 libraw (0.14.7-1) experimental; urgency=low * Team upload. * New upstream release (Closes: #682982). * debian/control: - Add DM-Upload-Allowed field. * debian/watch: - Use new redirector librawredir.debian.net. -- Luca Falavigna dktrkr...@debian.org Sat, 25 Aug 2012 13:35:59 +0200 ** Changed in: libraw (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libraw in Ubuntu. https://bugs.launchpad.net/bugs/1182281 Title: Sync libraw 0.14.7-2 (main) from Debian unstable (main) Status in “libraw” package in Ubuntu: Fix Released Bug description: Please sync libraw 0.14.7-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * New upstream release The new upstream was packaged in Debian, and there are no Ubuntu-specific changes to be kept. Changelog entries since current saucy version 0.14.7-0ubuntu1: libraw (0.14.7-2) unstable; urgency=low * Team upload. * Upload to unstable. * debian/control: - Remove deprecated DM-Upload-Allowed field. - Bump Standards-Version to 3.9.4. -- Luca Falavigna dktrkr...@debian.org Sun, 12 May 2013 20:47:35 +0200 libraw (0.14.7-1) experimental; urgency=low * Team upload. * New upstream release (Closes: #682982). * debian/control: - Add DM-Upload-Allowed field. * debian/watch: - Use new redirector librawredir.debian.net. -- Luca Falavigna dktrkr...@debian.org Sat, 25 Aug 2012 13:35:59 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libraw/+bug/1182281/+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 1181384] Re: Sync alsa-plugins 1.0.27-2 (main) from Debian unstable (main)
@themuso so it's ok to drop libasound2-plugins-extra package? why was it introduced in quantal then? Or is that delta still needs to be applied on top of debian? If we want to drop that package, shouldn't we need to still modify libasound2-plugins to replace -extra package? ** Changed in: alsa-plugins (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1181384 Title: Sync alsa-plugins 1.0.27-2 (main) from Debian unstable (main) Status in “alsa-plugins” package in Ubuntu: Incomplete Bug description: Please sync alsa-plugins 1.0.27-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * add new patch fix-ftbfs-libav9.patch: - Fix FTBFS with Libav9 Update to newer libav API - compatible to libav 0.8 and libav 9 (LP: #1076011) * add new patch fix-ftbfs-libav9.patch: - Fix FTBFS with Libav9 Update to newer libav API - compatible to libav 0.8 and libav 9 (LP: #1076011) * debian/control: Update Vcs-Bzr field for raring * debian/patches/usb_stream-Fix-build-with-glibc-2.16.patch: Fix FTBFS, thanks to Reinhard Tartler (LP: #1075718) * Merge from debian unstable, remaining changes: - Create libasound2-plugins-extra package which contains plugins that use libav. fix-ftbfs-libav9.patch is in debian too. Changelog entries since current saucy version 1.0.25-2ubuntu3: alsa-plugins (1.0.27-2) unstable; urgency=low * Upload to unstable. -- Jordi Mallach jo...@debian.org Thu, 09 May 2013 12:40:49 +0200 alsa-plugins (1.0.27-1) experimental; urgency=low * New upstream release. * Drop fix-ftbfs-libav9.patch, similar patch applied upstream. * Refresh use_libavutil.patch. * Explicitly pass --disable-static. -- Jordi Mallach jo...@debian.org Fri, 26 Apr 2013 23:24:50 +0200 alsa-plugins (1.0.26-1) experimental; urgency=low [ Elimar Riesebieter ] * Added fix-ftbfs-libav9.patch to updated the a52 plugin to use a newer API of libav. It should work with both libav 0.8 in wheezy and 9 in experimental. Thanks Reinhard Tartler for the patch. (closes: #692581) * Fix build with glibc 2.16. _GNU_SOURCE needs to be defined at first. Patch stolen from upstream. Thanks David Henningsson for the hint. (closes: #701448) * Bumped Standards-Version to 3.9.4. No changes needed. [ Jordi Mallach ] * New upstream release. * Drop pcm-usb-stream.patch, applied upstream. -- Jordi Mallach jo...@debian.org Mon, 01 Apr 2013 22:21:31 -0500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1181384/+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 1108719] Re: usb crashed with SIGSEGV in opendir() -- USB ports are in BIOS disabled -- cupsd crashes every time
** Also affects: cups (Ubuntu Saucy) Importance: High Status: Fix Committed ** Changed in: cups (Ubuntu Saucy) Status: Fix Committed = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1108719 Title: usb crashed with SIGSEGV in opendir() -- USB ports are in BIOS disabled -- cupsd crashes every time Status in “cups” package in Ubuntu: In Progress Status in “cups” source package in Precise: In Progress Status in “cups” source package in Raring: In Progress Status in “cups” source package in Saucy: In Progress Bug description: On 4 machines is USB for safety disabled, an HP DeskJet 500 is attached to one machine via LTP (IEEE 1284) and the other machines use the network share... - all working well. But every time i open up CUPS for configuration or something the process /usr/sbin/cupsd crashes and an crash report is generated (attached). . Xubuntu 12.04.1 Linux icafe-a 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:41:24 UTC 2013 i686 i686 i386 GNU/Linux CUPS Versions: 1.5.3-0ubuntu6 (/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_precise-updates_main_binary-i386_Packages) (/var/lib/dpkg/status) BTW: I was also not able to send the bug via apport, this crashes with package not installed. [IMPACT] If on a machine (mainly servers and high-security environments) the USB is turned off in the BIOS or a very old pre-USB-era machine is used the attempt of CUPS to detect available printers makes the USB CUPS backend being called and the backend crashes then due to absense of USB . The crash itself is harmless, but it makes Apport popping up with a crash report which is annoying. [TESTCASE] Turn off the USB support completely in the BIOS setup of the machine, boot and run either lpinfo -v or sudo /usr/lib/cups/backend/usb A crash report will pop up. Close it, do not generate the actual bug report. After installing the proposed package the backend will not crash any more and so no Apport pop-up will occur. [Regression Potential] The patch is very simple and adds only an error check to handle an error on initializing libusb properly. The probability of a regression caused by this is practically zero. NOTE: As the archives for the new development cycle are not open yet I am posting this SRU proposal without a fixed package in the new development branch. The fix is committed to Debian's GIT repo of CUPS though and so it will appear in the new development cycle with the first sync of the cups package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1108719/+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 929476] Re: System Settings - Automatically enable ALT+SHIFT language switch shortcut if 2 or more languages are enabled
** Tags added: release-s-incoming -- 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/929476 Title: System Settings - Automatically enable ALT+SHIFT language switch shortcut if 2 or more languages are enabled Status in Ayatana Design: Fix Committed Status in Gnome Settings Daemon: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Bug description: Inside 'System Settings/Keyboard Preferences/Options (keyboard Layout Options)' there is an option to enable keyboard layout switching using the ALT+SHIFT shortcut. See attached image keyboard_layout_options.png. This bug requests that this shortcut is switched on automatically for users of 2 or more languages. Note that this change should not be made until bug #36812 ( https://bugs.launchpad.net/xorg- server/+bug/36812 ) is also fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/929476/+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 1170741] Re: Ubuntu does not provide keyboard shortcut to change keyboard layouts by default
** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1170741 Title: Ubuntu does not provide keyboard shortcut to change keyboard layouts by default Status in One Hundred Paper Cuts: New Status in “gsettings-desktop-schemas” package in Ubuntu: Triaged Status in “ubuntu-settings” package in Ubuntu: New Bug description: After setting up alternative keyboard layout during installation, or post-install in the System Settings, one can only switch keyboard layouts using the keyboard indicator in the unity panel. One cannot use a keyboard shortcut to change the keyboard layout as none are enabled by default. A very common shortcut to change keyboard layouts is Alt-Shift. And if askubuntu.net is any indicator questions relating to keyboard shortcuts to switch layouts are very popular: http://askubuntu.com/questions/68127/how-to-switch-language-keyboard-combination http://askubuntu.com/questions/34210/toggling-language-with-altshift-doesnt-work And possibly many other similar question. I believe Ubuntu Operating system should provide/enable a keyboard layout switching shortcut by default when more than one keyboard layout is configured. I have tested and Alt-shift works correctly with Unity Hud and Unity Dash, with no conflicts or confusing behaviour (e.g. pressing alt clearly triggers hud, and one can use alt+shift to clearly change layout with or without HUD active). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 19 16:12:13 2013 InstallationDate: Installed on 2012-01-12 (462 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1 gnome-control-center-unity 1.2daily13.04.09-0ubuntu1 indicator-datetime 12.10.3daily13.03.27-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170741/+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 1170714] [NEW] colord is activated during ubiquity-dm installation session, is it really needed?
Public bug reported: Recently I started seeing this in syslog when launching ubiquity installer: Apr 10 10:51:27 ubuntu dbus[1094]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper) Apr 10 10:51:27 ubuntu colord: Using config file /etc/colord.conf Apr 10 10:51:27 ubuntu colord: Using mapping database file /var/lib/colord/mapping.db Apr 10 10:51:27 ubuntu colord: Using device database file /var/lib/colord/storage.db Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_camera.so Apr 10 10:51:27 ubuntu colord: plugin /usr/lib/colord-plugins/libcd_plugin_sane.so not loaded: plugin refused to load Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_scanner.so Apr 10 10:51:27 ubuntu colord: Daemon ready for requests Apr 10 10:51:27 ubuntu ubiquity[3150]: Ubiquity 2.14.1 Apr 10 10:51:27 ubuntu dbus[1094]: [system] Successfully activated service 'org.freedesktop.ColorManager' Apr 10 10:51:27 ubuntu colord: Profile added: icc-f5cf9cb1331928471dbcd67d7229aff5 Apr 10 10:51:27 ubuntu colord: Profile added: icc-d3ee37ff47fcdf614fb5cb62fb3e16a7 Apr 10 10:51:27 ubuntu colord: Profile added: icc-612c87ff43ce187a724c1c4354428d5c Apr 10 10:51:27 ubuntu colord: Profile added: icc-e1818e5a6f09a1cf9984b3752d306ff5 Apr 10 10:51:27 ubuntu colord: Profile added: icc-b8009c7e612e5ed5ddbd42dcb6eb349c Apr 10 10:51:27 ubuntu colord: Profile added: icc-ae0f19a77ff01ea1932ef5fd9609ef9d Apr 10 10:51:27 ubuntu colord: Profile added: icc-6590422afc1260c68d531b8de865eda1 Apr 10 10:51:27 ubuntu colord: Profile added: icc-9282466ab15c12d62ce889610bc427bd Apr 10 10:51:27 ubuntu colord: Profile added: icc-068a2ad86446468c029a0d55c061e46c Apr 10 10:51:27 ubuntu colord: Profile added: icc-de6232cfa581f3ce8c9c2548f3ac308f Apr 10 10:51:27 ubuntu colord: Profile added: icc-adb5ebe2a14b98599a170cd3ab54fe76 Apr 10 10:51:27 ubuntu colord: Profile added: icc-29f7c3bb18648f967e9cc450f5b0821e Apr 10 10:51:27 ubuntu colord: Profile added: icc-0ef971da00dac3a46e0c86550c54d5ad Apr 10 10:51:27 ubuntu colord: Profile added: icc-e7ecfce2d984c9f0c90f4ef1cdc9ac7e Apr 10 10:51:27 ubuntu colord: Profile added: icc-798efa4314bbd0274499de21fdf4ee5e Apr 10 10:51:27 ubuntu colord: Profile added: icc-c191d7b963b91ae51c83722957430c9c Apr 10 10:51:27 ubuntu colord: Profile added: icc-709099b11b3ec2828a314682a3c09f75 Apr 10 10:51:27 ubuntu colord: Profile added: icc-cecd8af52a99dfe8b57b9cd0f4e41ab0 Apr 10 10:51:27 ubuntu colord: Profile added: icc-ea21dae0f2e604aba058541c1972b7f1 Apr 10 10:51:27 ubuntu colord: Profile added: icc-aaa3a8cf35289974339049bc4cff354d Apr 10 10:51:27 ubuntu colord: Profile added: icc-819072bc37e0ea0042b6c3b28ce8da1a Apr 10 10:51:27 ubuntu colord: Profile added: icc-578e8c43d0440cff3239ced4417c691a Apr 10 10:51:28 ubuntu colord: Profile added: icc-f844a65e79050c828a5f8381a0798e49 Apr 10 10:51:28 ubuntu colord: Device added: xrandr-default Is colord really needed in the bare-minimal install ubuntu session? It was not loaded previously (e.g. early raring and previous releases). Or is it really necessary to load that now? It would interesting to trace what does activate it. I am randomly guessing gnome-settings-daemon ;-) ** Affects: colord (Ubuntu) Importance: Low Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Low Status: New ** Affects: ubiquity (Ubuntu) Importance: Low Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: colord (Ubuntu) Importance: Undecided = Low ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided = Low ** Changed in: ubiquity (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1170714 Title: colord is activated during ubiquity-dm installation session, is it really needed? Status in “colord” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: New Bug description: Recently I started seeing this in syslog when launching ubiquity installer: Apr 10 10:51:27 ubuntu dbus[1094]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper) Apr 10 10:51:27 ubuntu colord: Using config file /etc/colord.conf Apr 10 10:51:27 ubuntu colord: Using mapping database file /var/lib/colord/mapping.db Apr 10 10:51:27 ubuntu colord: Using device database file /var/lib/colord/storage.db Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_camera.so Apr 10 10:51:27 ubuntu colord: plugin /usr/lib/colord-plugins/libcd_plugin_sane.so not loaded: plugin refused to load Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_scanner.so Apr 10 10:51:27 ubuntu colord:
[Desktop-packages] [Bug 1170741] [NEW] Ubuntu does not provide keyboard shortcut to change keyboard layouts by default
Public bug reported: After setting up alternative keyboard layout during installation, or post-install in the System Settings, one can only switch keyboard layouts using the keyboard indicator in the unity panel. One cannot use a keyboard shortcut to change the keyboard layout as none are enabled by default. A very common shortcut to change keyboard layouts is Alt-Shift. And if askubuntu.net is any indicator questions relating to keyboard shortcuts to switch layouts are very popular: http://askubuntu.com/questions/68127/how-to-switch-language-keyboard-combination http://askubuntu.com/questions/34210/toggling-language-with-altshift-doesnt-work And possibly many other similar question. I believe Ubuntu Operating system should provide/enable a keyboard layout switching shortcut by default when more than one keyboard layout is configured. I have tested and Alt-shift works correctly with Unity Hud and Unity Dash, with no conflicts or confusing behaviour (e.g. pressing alt clearly triggers hud, and one can use alt+shift to clearly change layout with or without HUD active). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 19 16:12:13 2013 InstallationDate: Installed on 2012-01-12 (462 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1 gnome-control-center-unity 1.2daily13.04.09-0ubuntu1 indicator-datetime 12.10.3daily13.03.27-0ubuntu1 ** Affects: hundredpapercuts Importance: Undecided Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring third-party-packages ** Also affects: hundredpapercuts Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1170741 Title: Ubuntu does not provide keyboard shortcut to change keyboard layouts by default Status in One Hundred Paper Cuts: New Status in “gnome-control-center” package in Ubuntu: New Bug description: After setting up alternative keyboard layout during installation, or post-install in the System Settings, one can only switch keyboard layouts using the keyboard indicator in the unity panel. One cannot use a keyboard shortcut to change the keyboard layout as none are enabled by default. A very common shortcut to change keyboard layouts is Alt-Shift. And if askubuntu.net is any indicator questions relating to keyboard shortcuts to switch layouts are very popular: http://askubuntu.com/questions/68127/how-to-switch-language-keyboard-combination http://askubuntu.com/questions/34210/toggling-language-with-altshift-doesnt-work And possibly many other similar question. I believe Ubuntu Operating system should provide/enable a keyboard layout switching shortcut by default when more than one keyboard layout is configured. I have tested and Alt-shift works correctly with Unity Hud and Unity Dash, with no conflicts or confusing behaviour (e.g. pressing alt clearly triggers hud, and one can use alt+shift to clearly change layout with or without HUD active). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 19 16:12:13 2013 InstallationDate: Installed on 2012-01-12 (462 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1 gnome-control-center-unity 1.2daily13.04.09-0ubuntu1 indicator-datetime 12.10.3daily13.03.27-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170741/+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
Re: [Desktop-packages] [Bug 1170714] Re: colord is activated during ubiquity-dm installation session, is it really needed?
On 19 April 2013 15:37, Sebastien Bacher seb...@ubuntu.com wrote: hum, booting a precise iso in desktop mode, colord is running ... I think gnome-settings-daemon dbus activates it and that it's not new, do you have gnome-settings-daemon running? did it used to be the case? do you select the plugins you activate or not? I'm not talking about Desktop mode aka Try Ubuntu I'm talking about booting the Cd and clicking Install Ubuntu or better at the bootprompt (the a11y human/keyboard icon) press Esc and select Install Ubuntu. Regards, Dmitrijs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1170714 Title: colord is activated during ubiquity-dm installation session, is it really needed? Status in “colord” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: New Bug description: Recently I started seeing this in syslog when launching ubiquity installer: Apr 10 10:51:27 ubuntu dbus[1094]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper) Apr 10 10:51:27 ubuntu colord: Using config file /etc/colord.conf Apr 10 10:51:27 ubuntu colord: Using mapping database file /var/lib/colord/mapping.db Apr 10 10:51:27 ubuntu colord: Using device database file /var/lib/colord/storage.db Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_camera.so Apr 10 10:51:27 ubuntu colord: plugin /usr/lib/colord-plugins/libcd_plugin_sane.so not loaded: plugin refused to load Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_scanner.so Apr 10 10:51:27 ubuntu colord: Daemon ready for requests Apr 10 10:51:27 ubuntu ubiquity[3150]: Ubiquity 2.14.1 Apr 10 10:51:27 ubuntu dbus[1094]: [system] Successfully activated service 'org.freedesktop.ColorManager' Apr 10 10:51:27 ubuntu colord: Profile added: icc-f5cf9cb1331928471dbcd67d7229aff5 Apr 10 10:51:27 ubuntu colord: Profile added: icc-d3ee37ff47fcdf614fb5cb62fb3e16a7 Apr 10 10:51:27 ubuntu colord: Profile added: icc-612c87ff43ce187a724c1c4354428d5c Apr 10 10:51:27 ubuntu colord: Profile added: icc-e1818e5a6f09a1cf9984b3752d306ff5 Apr 10 10:51:27 ubuntu colord: Profile added: icc-b8009c7e612e5ed5ddbd42dcb6eb349c Apr 10 10:51:27 ubuntu colord: Profile added: icc-ae0f19a77ff01ea1932ef5fd9609ef9d Apr 10 10:51:27 ubuntu colord: Profile added: icc-6590422afc1260c68d531b8de865eda1 Apr 10 10:51:27 ubuntu colord: Profile added: icc-9282466ab15c12d62ce889610bc427bd Apr 10 10:51:27 ubuntu colord: Profile added: icc-068a2ad86446468c029a0d55c061e46c Apr 10 10:51:27 ubuntu colord: Profile added: icc-de6232cfa581f3ce8c9c2548f3ac308f Apr 10 10:51:27 ubuntu colord: Profile added: icc-adb5ebe2a14b98599a170cd3ab54fe76 Apr 10 10:51:27 ubuntu colord: Profile added: icc-29f7c3bb18648f967e9cc450f5b0821e Apr 10 10:51:27 ubuntu colord: Profile added: icc-0ef971da00dac3a46e0c86550c54d5ad Apr 10 10:51:27 ubuntu colord: Profile added: icc-e7ecfce2d984c9f0c90f4ef1cdc9ac7e Apr 10 10:51:27 ubuntu colord: Profile added: icc-798efa4314bbd0274499de21fdf4ee5e Apr 10 10:51:27 ubuntu colord: Profile added: icc-c191d7b963b91ae51c83722957430c9c Apr 10 10:51:27 ubuntu colord: Profile added: icc-709099b11b3ec2828a314682a3c09f75 Apr 10 10:51:27 ubuntu colord: Profile added: icc-cecd8af52a99dfe8b57b9cd0f4e41ab0 Apr 10 10:51:27 ubuntu colord: Profile added: icc-ea21dae0f2e604aba058541c1972b7f1 Apr 10 10:51:27 ubuntu colord: Profile added: icc-aaa3a8cf35289974339049bc4cff354d Apr 10 10:51:27 ubuntu colord: Profile added: icc-819072bc37e0ea0042b6c3b28ce8da1a Apr 10 10:51:27 ubuntu colord: Profile added: icc-578e8c43d0440cff3239ced4417c691a Apr 10 10:51:28 ubuntu colord: Profile added: icc-f844a65e79050c828a5f8381a0798e49 Apr 10 10:51:28 ubuntu colord: Device added: xrandr-default Is colord really needed in the bare-minimal install ubuntu session? It was not loaded previously (e.g. early raring and previous releases). Or is it really necessary to load that now? It would interesting to trace what does activate it. I am randomly guessing gnome-settings-daemon ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1170714/+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
Re: [Desktop-packages] [Bug 1170714] Re: colord is activated during ubiquity-dm installation session, is it really needed?
On 19 April 2013 15:32, Sebastien Bacher seb...@ubuntu.com wrote: Hey Dmitrijs, when is recently? gnome-settings-daemon didn't change much recently, it seems like the service gets dbus activated, ideally we shouldn't activate it if no profile is active for the user... Hmm... I haven't kept install logs of my old machine, but I can look at the launchpad reported bugs to see when it started appearing. Something like half way into raring development cycle - roughly. Regards, Dmitrijs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1170714 Title: colord is activated during ubiquity-dm installation session, is it really needed? Status in “colord” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: New Bug description: Recently I started seeing this in syslog when launching ubiquity installer: Apr 10 10:51:27 ubuntu dbus[1094]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper) Apr 10 10:51:27 ubuntu colord: Using config file /etc/colord.conf Apr 10 10:51:27 ubuntu colord: Using mapping database file /var/lib/colord/mapping.db Apr 10 10:51:27 ubuntu colord: Using device database file /var/lib/colord/storage.db Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_camera.so Apr 10 10:51:27 ubuntu colord: plugin /usr/lib/colord-plugins/libcd_plugin_sane.so not loaded: plugin refused to load Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_scanner.so Apr 10 10:51:27 ubuntu colord: Daemon ready for requests Apr 10 10:51:27 ubuntu ubiquity[3150]: Ubiquity 2.14.1 Apr 10 10:51:27 ubuntu dbus[1094]: [system] Successfully activated service 'org.freedesktop.ColorManager' Apr 10 10:51:27 ubuntu colord: Profile added: icc-f5cf9cb1331928471dbcd67d7229aff5 Apr 10 10:51:27 ubuntu colord: Profile added: icc-d3ee37ff47fcdf614fb5cb62fb3e16a7 Apr 10 10:51:27 ubuntu colord: Profile added: icc-612c87ff43ce187a724c1c4354428d5c Apr 10 10:51:27 ubuntu colord: Profile added: icc-e1818e5a6f09a1cf9984b3752d306ff5 Apr 10 10:51:27 ubuntu colord: Profile added: icc-b8009c7e612e5ed5ddbd42dcb6eb349c Apr 10 10:51:27 ubuntu colord: Profile added: icc-ae0f19a77ff01ea1932ef5fd9609ef9d Apr 10 10:51:27 ubuntu colord: Profile added: icc-6590422afc1260c68d531b8de865eda1 Apr 10 10:51:27 ubuntu colord: Profile added: icc-9282466ab15c12d62ce889610bc427bd Apr 10 10:51:27 ubuntu colord: Profile added: icc-068a2ad86446468c029a0d55c061e46c Apr 10 10:51:27 ubuntu colord: Profile added: icc-de6232cfa581f3ce8c9c2548f3ac308f Apr 10 10:51:27 ubuntu colord: Profile added: icc-adb5ebe2a14b98599a170cd3ab54fe76 Apr 10 10:51:27 ubuntu colord: Profile added: icc-29f7c3bb18648f967e9cc450f5b0821e Apr 10 10:51:27 ubuntu colord: Profile added: icc-0ef971da00dac3a46e0c86550c54d5ad Apr 10 10:51:27 ubuntu colord: Profile added: icc-e7ecfce2d984c9f0c90f4ef1cdc9ac7e Apr 10 10:51:27 ubuntu colord: Profile added: icc-798efa4314bbd0274499de21fdf4ee5e Apr 10 10:51:27 ubuntu colord: Profile added: icc-c191d7b963b91ae51c83722957430c9c Apr 10 10:51:27 ubuntu colord: Profile added: icc-709099b11b3ec2828a314682a3c09f75 Apr 10 10:51:27 ubuntu colord: Profile added: icc-cecd8af52a99dfe8b57b9cd0f4e41ab0 Apr 10 10:51:27 ubuntu colord: Profile added: icc-ea21dae0f2e604aba058541c1972b7f1 Apr 10 10:51:27 ubuntu colord: Profile added: icc-aaa3a8cf35289974339049bc4cff354d Apr 10 10:51:27 ubuntu colord: Profile added: icc-819072bc37e0ea0042b6c3b28ce8da1a Apr 10 10:51:27 ubuntu colord: Profile added: icc-578e8c43d0440cff3239ced4417c691a Apr 10 10:51:28 ubuntu colord: Profile added: icc-f844a65e79050c828a5f8381a0798e49 Apr 10 10:51:28 ubuntu colord: Device added: xrandr-default Is colord really needed in the bare-minimal install ubuntu session? It was not loaded previously (e.g. early raring and previous releases). Or is it really necessary to load that now? It would interesting to trace what does activate it. I am randomly guessing gnome-settings-daemon ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1170714/+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
Re: [Desktop-packages] [Bug 1170714] Re: colord is activated during ubiquity-dm installation session, is it really needed?
On 19 April 2013 17:40, Sebastien Bacher seb...@ubuntu.com wrote: booting the Cd and clicking Install Ubuntu right, which is why I asked do you have gnome-settings-daemon running? did it used to be the case? do you select the plugins you activate or not? right, right =) yes it is running, ubiquity-dm starts it. Regards, Dmitrijs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1170714 Title: colord is activated during ubiquity-dm installation session, is it really needed? Status in “colord” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: New Bug description: Recently I started seeing this in syslog when launching ubiquity installer: Apr 10 10:51:27 ubuntu dbus[1094]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper) Apr 10 10:51:27 ubuntu colord: Using config file /etc/colord.conf Apr 10 10:51:27 ubuntu colord: Using mapping database file /var/lib/colord/mapping.db Apr 10 10:51:27 ubuntu colord: Using device database file /var/lib/colord/storage.db Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_camera.so Apr 10 10:51:27 ubuntu colord: plugin /usr/lib/colord-plugins/libcd_plugin_sane.so not loaded: plugin refused to load Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_scanner.so Apr 10 10:51:27 ubuntu colord: Daemon ready for requests Apr 10 10:51:27 ubuntu ubiquity[3150]: Ubiquity 2.14.1 Apr 10 10:51:27 ubuntu dbus[1094]: [system] Successfully activated service 'org.freedesktop.ColorManager' Apr 10 10:51:27 ubuntu colord: Profile added: icc-f5cf9cb1331928471dbcd67d7229aff5 Apr 10 10:51:27 ubuntu colord: Profile added: icc-d3ee37ff47fcdf614fb5cb62fb3e16a7 Apr 10 10:51:27 ubuntu colord: Profile added: icc-612c87ff43ce187a724c1c4354428d5c Apr 10 10:51:27 ubuntu colord: Profile added: icc-e1818e5a6f09a1cf9984b3752d306ff5 Apr 10 10:51:27 ubuntu colord: Profile added: icc-b8009c7e612e5ed5ddbd42dcb6eb349c Apr 10 10:51:27 ubuntu colord: Profile added: icc-ae0f19a77ff01ea1932ef5fd9609ef9d Apr 10 10:51:27 ubuntu colord: Profile added: icc-6590422afc1260c68d531b8de865eda1 Apr 10 10:51:27 ubuntu colord: Profile added: icc-9282466ab15c12d62ce889610bc427bd Apr 10 10:51:27 ubuntu colord: Profile added: icc-068a2ad86446468c029a0d55c061e46c Apr 10 10:51:27 ubuntu colord: Profile added: icc-de6232cfa581f3ce8c9c2548f3ac308f Apr 10 10:51:27 ubuntu colord: Profile added: icc-adb5ebe2a14b98599a170cd3ab54fe76 Apr 10 10:51:27 ubuntu colord: Profile added: icc-29f7c3bb18648f967e9cc450f5b0821e Apr 10 10:51:27 ubuntu colord: Profile added: icc-0ef971da00dac3a46e0c86550c54d5ad Apr 10 10:51:27 ubuntu colord: Profile added: icc-e7ecfce2d984c9f0c90f4ef1cdc9ac7e Apr 10 10:51:27 ubuntu colord: Profile added: icc-798efa4314bbd0274499de21fdf4ee5e Apr 10 10:51:27 ubuntu colord: Profile added: icc-c191d7b963b91ae51c83722957430c9c Apr 10 10:51:27 ubuntu colord: Profile added: icc-709099b11b3ec2828a314682a3c09f75 Apr 10 10:51:27 ubuntu colord: Profile added: icc-cecd8af52a99dfe8b57b9cd0f4e41ab0 Apr 10 10:51:27 ubuntu colord: Profile added: icc-ea21dae0f2e604aba058541c1972b7f1 Apr 10 10:51:27 ubuntu colord: Profile added: icc-aaa3a8cf35289974339049bc4cff354d Apr 10 10:51:27 ubuntu colord: Profile added: icc-819072bc37e0ea0042b6c3b28ce8da1a Apr 10 10:51:27 ubuntu colord: Profile added: icc-578e8c43d0440cff3239ced4417c691a Apr 10 10:51:28 ubuntu colord: Profile added: icc-f844a65e79050c828a5f8381a0798e49 Apr 10 10:51:28 ubuntu colord: Device added: xrandr-default Is colord really needed in the bare-minimal install ubuntu session? It was not loaded previously (e.g. early raring and previous releases). Or is it really necessary to load that now? It would interesting to trace what does activate it. I am randomly guessing gnome-settings-daemon ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1170714/+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 1164567] Re: Wireless screen doesn't connect to selected wireless network
we do download and verify checksum of http://start.ubuntu.com /connectivity-check.html which should timeout/return eventually with a broken connection / captive portal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1164567 Title: Wireless screen doesn't connect to selected wireless network Status in “network-manager” package in Ubuntu: Incomplete Status in “ubiquity” package in Ubuntu: New Bug description: This is with the Ubuntu GNOME Beta 2 candidate image. 1. Select Try Ubuntu GNOME 2. Don't connect to wifi. 3. Find Install Ubuntu-GNOME in the Activities Overview and start the installation. 4. When you get to the Wireless screen, select a wifi network (In my case, the wifi network is an open network but captive portal) 5. Click Connect. 6. ...Nothing happens Workaround: Click the network menu in the top right corner and connect to the wifi point instead. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CasperVersion: 1.330 Date: Thu Apr 4 15:20:26 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper initrd=/casper/initrd.lz quiet splash -- LiveMediaBuild: Ubuntu-GNOME 13.04 Raring Ringtail - Alpha i386 (20130402.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1164567/+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
